Real-user data
Aggregated Chrome experience can reveal whether loading, interaction and layout stability are good for actual visitors. It only appears when Google has enough eligible traffic.
Free website speed check
Run a practical check across loading speed, page experience, search essentials and technical setup. You get the evidence immediately, with no email gate.
Your report
Lab values will appear here when the production Google API key is connected.
Priorities combine measured loading opportunities with visible technical gaps. They are a starting point, not an automatic quotation.
Copy a plain summary or start an email with the tested address and top priorities already included.
Three different views
A fast score can still hide an unstable page, missing search essentials or basic technical faults. Each evidence layer answers a different question.
Aggregated Chrome experience can reveal whether loading, interaction and layout stability are good for actual visitors. It only appears when Google has enough eligible traffic.
A simulated visit exposes loading work and repeatable opportunities. It helps diagnosis, but the score can move between runs and does not represent every visitor.
The server response, redirects, security headers, metadata, headings, images, control names, structured data and sitemap route are checked independently.
Read the report in the right order
Start with problems that customers feel, then remove the largest measured cause. Recheck after each meaningful change so one improvement does not hide another regression.
Real-user Core Web Vitals carry more context than one lab run when that field data is available.
Images, scripts, fonts, server delay and page builders need different fixes. The report narrows the first investigation.
A homepage result does not prove that product, booking, checkout or campaign pages are healthy. Test the page that matters to the customer action.
Useful evidence, honest limits
Automated checks are excellent at finding measurable symptoms. They cannot understand every design decision, user task or business constraint.
A manual review is needed before scope, cost or outcome can be promised.
Before relying on a score
Lab data comes from one controlled Lighthouse test and is useful for diagnosis. Real-user data is aggregated from eligible Chrome visits over time and better reflects a range of actual devices, connections and sessions. The two can disagree because they measure different conditions.
Server load, network conditions, third-party scripts, cache state and page changes can all alter one lab run. Treat a score as a measurement from that test, then look for repeatable causes and real-user evidence before deciding what to change.
Google only reports Chrome User Experience data when a page or origin has enough eligible traffic and meets its publication criteria. A missing field result is not a failure. The controlled lab test and independent technical scan can still provide useful evidence.
No. It checks the exact public page you submit, plus a small number of origin-level routes such as robots.txt and a common sitemap location. Test a representative product, service, booking or checkout page when that journey matters more than the homepage.
No. Automated accessibility checks find only some detectable issues and cannot certify compliance or replace testing with assistive technology and human judgement. The score is a useful warning signal, not a legal or accessibility pass.
It can improve visitor experience and technical quality, but no ranking change is guaranteed. Search visibility depends on relevance, content, competition, links, crawlability and many other signals beyond this report.
The checked result is held temporarily for 24 hours so the same page can reuse its report. The connection address is converted to a one-way protected hash for the daily allowance and the raw address is not stored by the checker. No email address is requested.
Each fresh report can use external testing capacity and server work. The limit keeps the free tool available for genuine website owners. Reopening a page already checked from the same connection uses the temporary cached report and does not consume another page allowance.
Yes. Add one public reference page and it will be checked using the same mobile or desktop view. The comparison is page against page, not business against business, and it uses one of the three different-page checks available to your connection that day.
When the report needs action
Ernest can investigate WordPress, WooCommerce, custom HTML, PHP, React and Node.js websites, then fix the causes that are worth changing.