Page Speed and Weight
Measures the time to first byte, the HTML size, the compression in use, and the number of scripts, stylesheets and images the page pulls in.
- Sign-in requiredMembership is free
- Open on the Ücretsiz plan5 runs a day
- Saved to your historyReachable from your account
What does this tool look at?
Everything that decides whether Google can crawl and index your page: tags, redirects, robots, sitemaps and server responses.
- Time to first byte (TTFB)
- HTML size and gzip/brotli compression
- Script, stylesheet and image counts
- Cache-Control headers
What this tool measures
A page loses speed in two separate places: when the server is slow to answer, and when the browser has to download more files than it needs. This tool measures the first directly and shows the second by counting what the page asks for.
The first measurement is TTFB, the time to first byte. After the request goes out, how long does the server take to produce its first byte? That number is the sum of database queries, template rendering and caching decisions, and it has nothing to do with the images on the page.
The second measurement is the weight of the HTML itself plus the tag counts inside it: how many scripts, external stylesheets, images and preloaded fonts. Each one means a separate request. The tool also checks whether the response is compressed and what the Cache-Control header says.
How to use it
- 1
Enter the address of the page you want to measure
The homepage is usually the heaviest, but the real bottleneck is often a product listing or a search results page.
- 2
Look at the TTFB figure
Under 400 ms is good, over 900 ms is bad. A high number means the problem is on the server or the host, not the front end.
- 3
Confirm the compression line
An empty Content-Encoding means the response is not compressed. Turning on gzip or brotli is a one-line server setting.
- 4
Trim the excess in the resource table
More than twenty script tags usually means tracking codes and plugins stacked on top of each other.
When to use it
- Before and after changing hosting provider, to measure the same page and see the difference.
- When a PageSpeed score is low but the cause is unclear, to separate server from front end.
- After adding a new tracking snippet or chat widget, to see the jump in script count.
- To confirm from the Cache-Control header that caching is actually working.
Reading the result
TTFB above 900 ms
The server may be rebuilding the page on every request. A page cache or a CDN drops this figure in one move.
HTML above 400 KB
Usually inline styles or data embedded in the page. HTML should carry content; everything else belongs in its own file.
No compression
The cheapest win available. On text responses, gzip or brotli cuts size by roughly seventy percent.
Cache-Control undefined
The browser re-downloads everything on every visit. Give static files a long life and HTML a short one.
More than twenty-five scripts
Each one is a separate request and a separate execution. Removing unused tracking code is the quickest cleanup.
Questions about the Page Speed and Weight
Google's suggested threshold is 800 milliseconds, and under 200 ms is considered very good. This tool passes anything under 400 ms, warns between 400 and 900 ms, and fails above 900 ms. On shared hosting the figure fluctuates, so measure it a few times.
It does not. LCP, INP and CLS are measured in a real browser on real users' devices. This tool shows you the server side and the shape of the HTML, which feed into Core Web Vitals without replacing them.
The tool downloads only the HTML, not the images. That is deliberate: pulling thirty images would be slow and would put load on the server you are auditing. For the image side, look at the format breakdown in the Image Alt Text Checker.
It does, at a weight far below content quality. Its real effect is indirect: people bounce off a slow page and conversions fall. Speed does not make a bad page good; it removes the obstacle in front of a good one.
Use it alongside these
The other tools in the same category. Run them together and you see the whole picture.
The tool found the problem. Now for the fix
We run technical SEO, content and AI visibility work end to end. Let us review your site and come back with a clear list of what to do.
Monday – Saturday 09:00 – 18:00