Speed test
How fast is it, and what is making it slow?
Not a single number. SiteRay reports when the page first shows something, when it shows the thing people came for, how long the browser is too busy to respond, and how much it moves about while loading — then what is responsible for each.
Three audits every 24 hours with a free account. No card, and nothing switches off.
What it measures
Checked on every run
Every speed tool can tell you a page is slow. The useful part is which of the four ways a page can be slow it actually is, because the fixes have nothing to do with each other: a slow largest paint is usually an image, a blocked main thread is almost always JavaScript, and layout shift is neither.
Performance
Largest Contentful Paint, Total Blocking Time, Cumulative Layout Shift and Speed Index — the lab versions of the Core Web Vitals Google ranks on, measured on a simulated mid-range phone and on a desktop.
Page weight and requests
How many bytes the page pulls and how many round trips it takes, split by images, scripts, stylesheets, fonts and third parties.
Third parties
Analytics, chat widgets, tag managers, embedded video and ad scripts, with what each costs. The usual answer to "why is this slow" is a tag somebody added in 2019.
Best practices
HTTPS, console errors, deprecated APIs, image aspect ratios, and third-party scripts that slow the page or leak referrers.
How it works
Three steps, about ninety seconds
Paste the address
Any public page. The engine resolves it, follows redirects and reports where it ended up.
It loads the page twice
Once at a phone viewport on a throttled connection, once on a desktop, in a real browser — not a lookup against a database of old crawls.
You get numbers, ranked
Four scores, the measurement behind each, and the problems in the order they are costing you. Results stay in your dashboard, so a re-run shows what moved.
Questions
What this does, and what it does not
- Is this the same as the field data in Search Console?
- No, and the two answer different questions. This is a lab measurement: one load, one connection profile, repeatable, which is what you need to test a fix. Search Console reports what real visitors on real devices experienced over 28 days, which is what you need to know whether it mattered. Use the lab to change things and the field to confirm it.
- Why does the score change between two runs of the same page?
- Because a page load is not deterministic — a third-party script responds faster one minute than the next, and a few points of movement is noise. Look at the measurements rather than the score, and if two runs disagree by a lot, the variability is itself the finding.
- How does the audit actually run?
- We load the page in a real browser twice — once on a simulated mid-range phone on a slow connection, once on a desktop — and record what happens. Nothing is estimated from a database of past crawls; every number comes from that load, on the day you asked for it.
- Is it free?
- Yes. Three audits every 24 hours with a free account, which exists so the engine is not run by scripts. There is no card, no trial, and nothing switches off.
Measure it now
One address, ninety seconds, and a list you can hand to whoever builds the site. If the list turns out to be longer than an afternoon, that is a conversation we are happy to have.