What is making your page slow to appear?
Speed advice usually arrives as a score with no instruction attached. This reads one request from your page and names the things actually standing between a visitor and the first thing they see, in the order they cost you.
What slowness actually costs
A slow page does not announce itself. It shows up later as traffic that arrived, waited, and left without ever appearing in a conversation about your product.
A blank screen is a closed tab
Visitors do not wait to find out whether a page is worth it. The longer nothing appears, the more of them leave before your site has said a single word.
Speed is priced into your ranking
Search treats how fast a page becomes usable as a ranking input. A slow page competes against faster ones with a handicap it never sees.
A jumping layout costs you the click
When an image loads late and pushes the page down, the button someone was about to press moves. They tap the wrong thing, or they stop trying.
One page in, a fix list out
Paste a page
Any page you want to appear quickly. No sign-up, nothing installed.
We request it once
We time the response, read its headers, and read the HTML the way a browser first receives it.
You get a ranked fix list
What is holding the first paint back, most costly first, with the fix for each.
What it checks
The four things that decide how quickly a page becomes something a person can look at, each read straight off the response and scored by how much it costs you.
Whether it is compressed
Text sent without gzip or Brotli is several times bigger than it needs to be. It is one setting, and it is the cheapest win here.
How long the server thinks
Nothing can render until the document arrives. Time spent waiting on the server sits in front of every other improvement.
What blocks the first paint
Scripts and stylesheets in the head that the browser must finish before it may draw anything at all.
What makes the layout jump
Images with no width and height, so the browser cannot reserve their space and the page shifts under the reader.
Straight talk about what it cannot see
This is one request, read honestly. Where a number would need a real browser, we do not invent one.
It is not a Core Web Vitals score
LCP, CLS and INP are measured while a browser lays a page out and a person interacts with it. We run neither, so we report what the response shows instead of a vital we did not measure.
It does not weigh your images
We do not download the images, scripts or stylesheets, so their file sizes are not in the report. Their number, and the size of the HTML, are.
The timing is from our server
One request from where we run, not from your visitors' phones or networks. Treat it as a comparison between your own pages, not a promise about theirs.
It reads the page as it arrives
Anything drawn by JavaScript after loading is invisible to it, which is itself worth knowing: that content is invisible to the first paint too.
Find out what your visitors wait for
Run it on your slowest page right now. Every Growth Tool is included in one subscription: get a plan and scan any site.
Check my page