Performance diagnostics
Page Speed Analyzer
Measure server response, transfer size, resource counts, compression, caching, and performance risks with optional PageSpeed Insights data.
Tool guide
What is the Page Speed Analyzer?
The Page Speed Analyzer measures the server response and inspects performance-related signals in a public page. When Google PageSpeed Insights is configured, it can display Lighthouse performance data. Without that integration, it provides a clearly labeled fallback audit based on response timing, transfer size, caching, compression, and resource references.
Fast pages support users, conversions, crawling efficiency, and Core Web Vitals, but one test from one location is not a complete performance profile. Use the report to find likely bottlenecks, then confirm improvements in a real browser, field analytics, and repeated tests.
Audit coverage
What this SEO tool checks
HTTP status, final URL, DNS, connection, and server response timing
HTML transfer size and content encoding
Cache-Control and compression headers
Counts of scripts, stylesheets, images, and iframes referenced in HTML
Image dimensions and optional Lighthouse performance metrics
Step-by-step
How to use the Page Speed Analyzer
- 1Enter a public URL
Use the final page you want visitors and search engines to load.
- 2Choose mobile or desktop
Mobile is usually the stricter and more useful starting point.
- 3Run the performance audit
The server fetches the page and requests PageSpeed data when the API is available.
- 4Prioritize high-impact fixes
Address slow server response, render-blocking assets, oversized images, and layout instability before minor micro-optimizations.
Interpretation
How to understand the results
- Server TTFB shows how quickly the tested server began receiving a response; geography and caching can change it.
- The fallback score is an estimate from technical signals and is not a Lighthouse score.
- When PageSpeed data loads, lab metrics describe a simulated run while field data reflects eligible real-user history.
Practical advice
SEO best practices
- Optimize and properly size images, using modern formats where practical.
- Cache static assets for long periods and version filenames when content changes.
- Reduce render-blocking CSS and unnecessary third-party JavaScript.
- Use a CDN and server/page caching when the audience is geographically distributed.
- Retest several times after changes because network and server load create variation.
Before you act
Limitations of this automated check
This tool cannot reproduce every visitor’s device, network, browser, cache state, or location. A single server-side request does not render the page or measure visual completion. Lighthouse and field metrics require the PageSpeed integration, and some sites block automated tests or return different content to remote servers.
Deeper explanation
Understand the decision behind the check
Use the practical guide below when you need context, common mistakes and a verification workflow instead of only a pass/fail result.
Common questions
Page Speed Analyzer FAQs
Is the fallback score a Google score?
No. It is a transparent estimate based on response and markup signals. Google Lighthouse data is labeled separately when available.
Why do speed test results change?
Network conditions, server load, cache state, test location, third-party services, and page updates all create normal variation.
Should I test mobile or desktop?
Start with mobile because slower devices and networks expose more problems, then verify desktop as well.
Does a fast score guarantee good rankings?
No. Speed and user experience are important, but relevance, content quality, links, and many other signals also matter.
Continue your audit