How is this different from Google PageSpeed Insights?

PageSpeed Insights loads the page in a real browser and reports Core Web Vitals from actual Chrome users. This tool measures the server side — response time, page weight, compression, caching, and render-blocking code — instantly and without rate limits. Use both: fix what we flag, then confirm with Google.

Why does my page score well here but badly on Google?

Our check measures the HTML document. Google also measures images, fonts, JavaScript execution, and layout shift in a real browser. A light HTML file can still be slowed down by a 4 MB hero image or a heavy page-builder theme.

Does speed really affect rankings?

Yes, but indirectly and modestly. Core Web Vitals are a confirmed ranking signal, and speed strongly affects bounce rate and conversions — which affect everything else.

What's the fastest fix for a slow site?

In order: compress and resize your images, turn on gzip/Brotli compression and caching, remove unused plugins and third-party scripts, then add defer to scripts that don't need to run immediately.

Free Page Speed Analyzer — Test Any Website's Load Speed

Why page speed decides whether you get the sale

Speed is the cheapest conversion fix most small businesses have. A visitor who taps your listing on a phone at a red light gives you about three seconds. If the page is still blank, they hit back and tap your competitor — and Google notices that pattern over time. You do not need a perfect score. You need a page that shows something useful fast.

What we measure, and why it matters

Server response time (TTFB): how long your host takes to send the first byte. Cheap shared hosting and bloated plugins are the usual culprits. Nothing else can be fast if this is slow.
Page weight: the size of the HTML document. Page builders regularly ship 400 KB of markup for a page with six sentences on it.
Compression: gzip or Brotli usually cuts transfer size by 60–80%. It is a hosting toggle, not a redesign.
Caching headers: tell browsers to reuse files they already downloaded, so repeat visits feel instant.
Render-blocking scripts: scripts without defer or async stop the browser from drawing anything until they finish downloading.
Image dimensions and lazy loading: missing width and height cause content to jump around while loading, which Google scores as layout shift.
Third-party domains: chat widgets, trackers, and font services each cost a DNS lookup and a handshake before your page finishes.

A realistic fix order

Start with images — resize anything wider than 2000 pixels and export as WebP. Then turn on compression and caching at your host or CDN. Then delete the plugins and scripts you stopped using two years ago. Then defer whatever JavaScript is left. Most sites gain more from those four steps than from any theme change, and none of them require a developer.

When you're done, run the test again here, then confirm real-world numbers with Google. For a broader look at everything else Google checks, run the full site audit from our free checker and work down the priority list.

Frequently asked questions

Aim for a server response under 600 milliseconds and a largest visible element painted within 2.5 seconds. Past about 3 seconds, roughly half of mobile visitors leave before the page finishes.