Page Speed Tools
Measure how fast your server answers and how much each page weighs.
2 tools · Real Data
Before a browser can paint anything, your server has to answer and the HTML has to travel over the network. A slow first byte, a heavy document or a response sent without compression adds delay to every visit, on every device, and it often goes unnoticed on a fast office connection. These are also among the cheapest speed problems to fix, usually a hosting, caching or server setting rather than a redesign.
This hub focuses on that server and delivery layer. The Page Speed & Size Test fetches a live URL and reports time to first byte, DNS and connection time, total download time, page weight and whether the response was compressed, with a simple grade. The Gzip / Brotli Compression Test requests the same URL twice, once compressed and once raw, and shows which encoding the server used and how many bytes it saved.
Run both on your homepage and your heaviest template, fix compression first if it is missing, then look at server response time and page weight. Keep in mind what these tools do not measure: they time the HTML response, not rendering in a real browser, so they do not report Core Web Vitals such as LCP, INP or CLS. For those, use field data from Search Console or PageSpeed Insights alongside these checks.
Who uses these Page Speed tools
The audiences these tools fit best — each page collects the tools for that audience.
Frequently asked questions
What does the Page Speed & Size Test measure?
It fetches a live URL and reports time to first byte, total load time for the HTML document, page weight, whether compression was applied and a count of referenced resources, then combines them into a simple grade. Because it measures the server and network response, it is most useful for spotting slow hosting, missing caching or oversized HTML.
What is a good time to first byte?
There is no single official cutoff, but lower is better because every later step waits for it. As a working reference, many performance guides treat a TTFB under about 800 milliseconds as reasonable. Measure from more than one location and at different times of day, and if results swing widely, look at server caching and hosting capacity first.
What is the difference between Gzip and Brotli?
Both are compression methods a server can apply to text files such as HTML, CSS and JavaScript before sending them. Brotli usually produces smaller files than Gzip at similar settings and is supported by current browsers over HTTPS. Either is far better than sending uncompressed text; the Compression Test shows which one your server actually returns.
Do these tools measure Core Web Vitals?
No. Core Web Vitals (LCP, INP and CLS) are measured in a real browser, ideally from real visits. These tools time the server response and document download instead, which is often where a slow LCP starts. Pair them with the Core Web Vitals report in Search Console or with PageSpeed Insights for browser-level and field data.