Page Speed Checker
This free page speed checker measures the parts of speed a server controls: time to first byte, how long the HTML takes to download and how big it is, whether compression and caching headers are set, and how many stylesheets, scripts, images, fonts and third-party hosts the page asks for. It is a server-side test, so it explains what it cannot measure (Core Web Vitals) and where to get those.
Page Speed Checker
Technical SEO
About this tool
Slow pages lose visitors before the first word appears, and speed feeds Google's page experience signals. But "the site is slow" has many causes: a slow server, a bloated HTML document, no compression, dozens of scripts, or heavy images. The first step is to separate the server's share from the front end's, because the fixes live in different places.
The checker requests the page twice from our server. The first request stops after the first kilobyte, so its time is close to the time to first byte: DNS, connection, TLS handshake and the server generating the response. The second downloads the whole HTML, giving the total time and the size on the wire and after decompression. It then reads the HTML to count stylesheets, external and inline scripts, render-blocking scripts in the head, images, iframes, preloaded fonts and the third-party hosts involved, and grades compression and caching from the headers.
This is a lab measurement from one server with no rendering: it does not run JavaScript, download images or paint the page, so it cannot report Largest Contentful Paint, Cumulative Layout Shift or Interaction to Next Paint. Use Google PageSpeed Insights or the Chrome User Experience Report for those field metrics. Timing also varies with distance; your visitors will see different numbers.
Frequently asked questions
What is a good time to first byte?
Google suggests under 800 milliseconds in the field and the best sites answer in under 200. Above 600 the server, the application or the database is usually the bottleneck: page caching, a faster host, PHP or database tuning and a CDN are the common fixes. TTFB caps everything that follows, so fix it first.
Why are the numbers different from PageSpeed Insights?
PageSpeed Insights renders the page in a simulated phone with a slow connection and reports Core Web Vitals, while this checker measures the raw server response from a data centre with no rendering. The two answer different questions: this one tells you how fast the server and HTML are, PageSpeed tells you how the page feels to a user.
How do I enable gzip or Brotli compression?
In Apache enable mod_deflate (or mod_brotli) for text types; in Nginx set gzip on with gzip_types for HTML, CSS, JavaScript, JSON and SVG; in cPanel use the Optimize Website option; on Cloudflare it is on by default. Compression typically cuts text transfers by 70 to 80 percent.
What are render-blocking scripts?
Script tags in the head without defer or async: the browser stops building the page until each one downloads and runs. Move them to the end of the body or add defer, and load third-party widgets async. Every blocking script delays the first paint by at least one round trip.
Does page speed affect rankings?
Yes, as part of Google's page experience signals, though relevance still comes first. In practice speed matters most through behaviour: faster pages get more of their visitors to stay, read and convert. Aim for a fast TTFB, compressed and cached assets, few scripts and properly sized images.