Website audit
Audit your website the way Google measures it
Search engines judge a page on things you cannot see by looking at it: how long it takes to become usable, whether the layout jumps while it loads, whether the markup says what the page is. SiteRay measures those and shows you the numbers, not a grade out of ten.
Three audits every 24 hours with a free account. No card, and nothing switches off.
What it measures
Checked on every run
A score on its own is a number to argue with. A score with the measurement under it — 3.8 seconds to the largest paint, 420ms of blocked main thread — is something a developer can act on this afternoon, and something you can check again next week.
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.
Technical SEO
Title and meta description, crawlability, status codes, canonical tags, structured data, link text and whether the page is indexable at all.
Accessibility
Colour contrast, form labels, heading order, alt text, landmark structure and keyboard reachability — the automated half of WCAG, which is roughly a third of what a real audit covers and all of what a machine can check.
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
- 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.
- Why is my mobile score so much lower than desktop?
- Because the mobile run simulates a mid-range phone on a slow connection, which is what a large share of real visitors actually have. A gap of thirty or forty points between the two is normal and is not a fault in the measurement — it is the gap your visitors are living in.
- Will fixing these scores improve my rankings?
- Some of them, and not by themselves. Core Web Vitals are a ranking signal and a modest one; being crawlable, indexable and readable is a prerequisite rather than a bonus. Content and links still decide most of it. Anyone who tells you a speed fix will move you from page four to page one is selling something.
- 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.