What is making your page slow to appear?
Speed advice arrives as a score with no instruction attached.
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 any page
Any page you want to appear quickly. No sign-up, nothing installed.
It reads the markup
The head, the scripts, the styles, the images, the way a browser first receives them, in your own browser.
You get a ranked fix list
What is holding the first paint back, most costly first, with the fix for each.
What it checks
What blocks the first paint
Scripts in the head with no defer or async, which the browser must download and run before it may draw anything.
How heavy the head is
The stylesheets and inline CSS and JS the page ships up front, before the first screen can appear.
How big the HTML is
A large document takes longer to arrive and to parse, before a single image or script is even considered.
How many things must finish first
Every blocking stylesheet and script is one more round trip the reader waits through before anything is drawn.
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.
Whether images wait their turn
Images far down the page loading at once compete with the ones on the first screen for the same connection.
Straight talk about what it cannot see
It reads the markup you give it, in your browser, and is honest about the edges of that.
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 markup shows instead of a vital we did not measure.
It does not time your server or check compression
Those need a live request to your page, which happens on your machine, not ours. This reads the HTML you paste, so it stays silent on both rather than guessing.
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.
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. Free, and it runs in your browser.