求助：PageSpeed Insights等工具报Lighthouse FAILED_DOCUMENT_REQUEST错误

Hey, I’ve run into this exact issue before—local Chrome DevTools Lighthouse audits work fine, but PageSpeed Insights and the Lighthouse extension throw timeout errors. Let’s walk through some actionable steps to fix this for your site, ebody.pt:

1. Check for Geographic/Server Access Restrictions #

Most of the time, this timeout happens because Google’s crawlers (used by PageSpeed Insights) are being blocked or throttled by your server or CDN:

• Double-check your server firewall/WAF rules to ensure you aren’t blocking Google’s IP ranges or crawler user agents
• Review your CDN’s access control policies—some default settings restrict non-human traffic that doesn’t match typical user patterns
• Test accessing your site from a server in a different region (like a US-based VPS) to mimic Google’s crawler environment; if it times out there too, that confirms a regional access issue

2. Validate Server Response Speed & Availability #

Just because you can load the site locally doesn’t mean it’s performant for global traffic:

• Use curl -I https://ebody.pt from a global testing tool or overseas server to measure response times—Lighthouse times out after ~30 seconds, so if your server takes longer to respond for international requests, that’s a problem
• Check your server’s resource usage (CPU, memory, bandwidth) to rule out bottlenecks that might slow responses for high-traffic or distant requests

3. Hunt for Blocking Third-Party Resources #

Sometimes slow-loading third-party scripts or assets can trigger Lighthouse timeouts, especially when accessed from regions where those services are slow:

• Temporarily disable non-essential third-party resources (ads, analytics, fonts, embedded widgets) and re-run the Lighthouse test to see if the timeout goes away
• Verify DNS resolution for your domain using overseas DNS servers—if your DNS provider has slow global propagation, that can delay initial connection

4. Ensure Compliance with Lighthouse’s Request Requirements #

Lighthouse’s crawler has specific behavior that differs from regular user traffic:

• Make sure your server properly handles GET requests (Lighthouse only sends GET requests) and doesn’t restrict access based on user agent or request headers that don’t match its crawler profile
• Check for HTTPS issues like invalid certificates, misconfigured redirects, or mixed-content errors—these can break the crawler’s ability to load the page reliably

5. Quick Test Workarounds #

If you’re still stuck, try these to narrow down the issue:

• Run Lighthouse locally via the CLI with lighthouse https://ebody.pt --disable-storage-reset—this skips some default resets that might conflict with your site’s setup, and can help you compare local vs. remote results
• Check Google Search Console’s Crawl Errors report—it will show you exactly what issues Google’s crawlers encounter when accessing your site, which often aligns with Lighthouse problems

内容的提问来源于stack exchange，提问作者João Ferreirinha