↑↓ to move · Enter to open · Esc to close

Page Load Analyzer

Analyze one page load path on our server to inspect response timings, resource requests, caching, and compression. Nothing is stored.

This check runs on our server. The address you enter is used only for this check and is not stored.
Updated

This check runs on our server. The address you enter is used only for this check and is not stored.

Mode: Load view

Tick the box to show you are not a robot, then press Check.

How to use the Page Load Analyzer

  1. Enter the page URL you want to measure.
  2. Run the check.
  3. Review the timing breakdown, request counts, compression, caching, and render-blocking resources, then fix the slowest parts first.

How it works

This check runs on our server. The page address is used only for this check and is not stored.

The analyzer fetches one page, records DNS lookup time, TCP connect time, TLS time, time to first byte, and download time, then collects up to 50 linked resources from the HTML. It checks response headers on those resources to see whether compression and caching are in place.

Scripts and stylesheets found in the head are highlighted because they can block early rendering in the browser, even though this tool itself does not render the page.

Examples

  • A page with slow DNS or TLS can show most of its delay before the first byte arrives.
  • A page with uncompressed CSS and JavaScript files can trigger compression recommendations.
  • A head section full of synchronous CSS files can be listed as render-blocking even when the server responds quickly.

Limitations

  • This is not a browser. It does not run JavaScript, so it cannot measure LCP, CLS, or INP.
  • Resources added by scripts after the initial HTML are not counted.
  • The timing is measured from our server location and can differ from what your visitors see elsewhere.

Frequently asked questions

Is this the same as Core Web Vitals?

No. Core Web Vitals are browser-side user experience metrics. This tool measures the server-side response path and the initial HTML resource setup.

Why does the result differ from my browser devtools?

The request comes from our server location, and the tool does not execute JavaScript or use your local browser cache.

What should I fix first in the report?

Start with large delays in DNS, TLS, or TTFB, then look at uncompressed assets, missing cache headers, and render-blocking files near the top of the page.

Often used together with the Page Load Analyzer.

  • Page Size Checker

    Reports HTML size, resource totals by type, and the largest files for one page without running JavaScript.

  • Website SEO Analyzer

    Checks one page for SEO basics, response details, tags, headings, links, and structured data without running JavaScript.

  • Google SERP PreviewDeveloper Tools

    Previews how a title and meta description may appear in Google results.