Free tool
Website check
Check a page
Enter the address of any public page. The check takes up to a minute.
What the scores measure
The four scores come from Google PageSpeed Insights, which runs Lighthouse, Google's free testing tool. It loads your page on a simulated mid-range mobile phone and a slower mobile connection, then scores it from 0 to 100:
- Speed looks at how quickly the main content appears and how soon the page responds when someone taps it.
- Accessibility runs automated checks for problems that block disabled visitors, such as missing image descriptions, low colour contrast and buttons without names.
- Search (SEO) checks basics that help search engines read and list the page, such as a title, a description and readable links.
- Best practices looks for common technical problems, such as errors in the browser and outdated code.
Scores from 90 to 100 are good, 50 to 89 need work and 0 to 49 are poor. Scores can change by a few points each time, because network speed, server load and third-party content such as adverts vary from one test to the next.
What the security header check covers
When a browser asks for a page, the server sends back a few instructions with it, called headers. Some of them tell the browser to always use a secure connection, to block the page being shown inside other sites, or to limit what scripts can run. We check whether the page uses https and whether a handful of these headers are there.
This is not a security audit or a penetration test. It does not look at your code, your server, your logins or how you store data, and a site can have every header and still have serious problems. Treat it as a quick sign of how carefully the site has been set up.
Why automated accessibility checks are only a start
Automated tools can spot problems a computer can see, such as an image with no description. They cannot tell whether that description makes sense, whether the page works with only a keyboard or whether a screen reader user can complete a form. A full picture needs manual testing with assistive technology. Our web accessibility service covers that kind of review. If the problems are speed or technical issues in how the site is built, code rescue is where we look at the code itself.
What happens to the address you enter
We send the address to Google PageSpeed Insights to run the test, and request the page once ourselves to read its headers. The result is kept in temporary memory for up to an hour so checking the same page again is quick, then it is gone. We don't save the address to a database, share it or use it to contact you, and you don't need to sign up or give an email address.
Common questions
Is this a security audit?
No. It looks at a few security headers the page sends back, which is a quick sign of how carefully a site is set up. A security audit or penetration test goes much further, looking at the code, the server, logins and how the site handles data.
Does a good accessibility score mean my site is accessible?
Not on its own. Automated checks find only part of the problems that stop disabled people using a site. To know for sure, someone needs to test it with a keyboard, a screen reader and other assistive technology.
Why did my score change when I ran it again?
Google loads the page fresh each time, and network speed, server load, adverts and other third-party content all vary. Small changes between runs are normal. Look at the band (poor, needs work or good) and the issues listed rather than a few points either way.
Do you keep the address I enter?
Only for up to an hour, in temporary memory, so checking the same page again is quick. It is not saved to a database, not shared with anyone except Google PageSpeed Insights, which runs the test, and not used to contact you. You do not need an account or an email address to see, print or copy your results.
Can I check a page that needs a login?
No. The check can only see what a visitor sees without logging in, so it works on public pages such as your home page, service pages and blog posts.