Chrome生成的脚本导致WP站点超时，求排查方向

Hey there, let's break down what might be going on with that Chrome-generated script causing your WordPress site to time out. I’ve run into similar headaches with clients before, so here are the most common sources and triggers to investigate:

1. Chrome的预加载/预渲染机制 #

Chrome has a built-in feature that preloads or prerenders pages it predicts you might visit next (you can check active predictions by typing chrome://predictors/ in your address bar). If your WP site has slow-loading pages, broken resources, or inconsistent server responses, Chrome might keep retrying the preload request indefinitely. This repeated traffic can pile up and trigger server timeouts—especially common if your site has dynamic, frequently changing content that throws off Chrome’s prediction logic.

2. DevTools调试残留或Service Worker故障 #

If you’ve used Chrome DevTools recently, leftover debugging sessions (like ongoing Performance recordings, persistent Network logs, or Service Worker debugging) can leave scripts running in the background. Additionally, if your WP site uses a PWA plugin or Workbox for offline support, a buggy Service Worker might cause Chrome to keep sending repeated sync requests to your server, leading to cumulative timeouts.

3. WordPress资源加载失败触发Chrome重试循环 #

If any script, stylesheet, or media file on your WP site fails to load (e.g., a broken ad script, outdated plugin asset, or slow third-party API), Chrome will automatically retry the request multiple times. If your server keeps returning errors or partial responses, this creates a loop where Chrome keeps hammering your site until it hits a timeout threshold. Check your site’s Network tab in DevTools to spot repeated failed requests.

4. Chrome扩展程序的注入脚本干扰 #

Many Chrome extensions (ad blockers, password managers, SEO tools, etc.) inject their own scripts into every page you visit. Sometimes these scripts clash with your WP site’s existing code—for example, an ad blocker might accidentally block a critical WP core script, causing Chrome to keep reloading or retrying the resource. Try disabling all extensions temporarily to see if the issue resolves.

5. WordPress Heartbeat API的过度请求 #

WP’s built-in Heartbeat API sends regular XHR requests to the server to keep sessions active, auto-save drafts, and update dashboard notifications. If your server is slow to respond to these requests, or if a plugin cranks up the heartbeat frequency unnecessarily, Chrome will keep sending these requests in quick succession, leading to server timeouts. You can adjust the heartbeat frequency via plugins or custom code to reduce the load.

Quick Troubleshooting Steps #

• Open Chrome DevTools (F12), go to the Network tab, and filter for XHR/JS requests to pinpoint which script is looping.
• Use Chrome’s Task Manager (Shift+Esc) to check if the problematic tab is using excessive CPU or memory.
• Disable all Chrome extensions and test the site again to rule out interference.
• Deactivate WP plugins one by one to identify conflicts, especially those related to caching, PWA, or analytics.

内容的提问来源于stack exchange，提问作者Doug Thaler