Free · A few seconds · No email needed

Free website inspection.

Put in your address. We run the same checks our census runs. If yours is fine, we say so.

Your website address

Free: every finding, in full. No account, no email needed.

Options: email me the report, what matters most, Spanish

Want us to email this report? (optional)

Results appear here either way. We send one email, your report, and nothing after it. Your address and the report go from your browser to Web3Forms, a form service that passes them to us.

What matters most right now? (one tap)

More phone calls Being found on Google Looking professional Just check everything

Many of my customers speak Spanish Remember this site's result so the next inspection shows what changed

Either way we keep one anonymous line. It holds the date, the kind of business, the town your site lists, the score and grade, and which checks failed or came back with a warning. It never holds your website address. Tick the box above and we keep the address in a separate record, with that result beside it.

What it does

Real measurements, honest limits.

First it checks our do-not-measure list, then reads your robots.txt, the file where a site says which automated readers are welcome. A listed site, or one whose robots.txt shuts us out, is not read, and the report says why.

Then it tries to tell what kind of business you are, so the checks fit. On the sites we have read, it could tell for about 55 in 100; the rest get the general checks.

It asks your site for up to 9 things in all, and measures the answers.

Is it secure, and built for phones
Can your phone number be tapped, and can a visitor reach you
Can Google read your business details from the site
How big the page is, and how fast it answers

Every number was measured; the report lists each thing we asked your site for.

The limits: it cannot see whether text is too light to read, how fast it feels on a phone, or anything the page's code adds later. A person has to look at those, and what it cannot measure stays out of the score.

Says who

Some of what we check is written down by the people who define how the web works. Here are the ones we opened at the source, with the sentence and a link, so whoever looks after your site can check us rather than take our word.

Your images carry a description for screen readers, the software that reads a page aloud: W3C WCAG All non-text content that is presented to the user has a text alternative that serves the equivalent purpose. Read it at the source: Your images carry a description for screen readers, the software that reads a page aloud
The page says which language it speaks: W3C WCAG The default human language of each web page can be programmatically determined. Read it at the source: The page says which language it speaks
Page title: W3C WCAG Web pages have titles that describe topic or purpose. Read it at the source: Page title
The page names which copy of itself is the real one: IETF The canonical link relation specifies the preferred IRI from resources with duplicative content. Read it at the source: The page names which copy of itself is the real one
No insecure resources: W3C this guarantee is weakened if the webpage loads subresources such as script or images over an insecure connection Read it at the source: No insecure resources
Security headers: OWASP Secure Headers Project (source of truth is its GitHub repo, per the project's own landing page). HSTS, the header that tells browsers to use only the secure connection, is IETF RFC 6797, Standards Track The OWASP Secure Headers Project (OSHP) describes HTTP response headers that your application can use to increase the security of your application. Read it at the source: Security headers
The instructions handed to search engines can be read: IETF The service makes available in a file named 'robots.txt' rules allowing owners to control crawler access to their URIs. Read it at the source: The instructions handed to search engines can be read
Your phone number can be tapped to dial: IETF The 'tel' URI describes resources identified by telephone numbers. Read it at the source: Your phone number can be tapped to dial
A map of your pages is offered to search engines: sitemaps.org The Sitemap protocol format consists of XML tags ... provide details about your pages to search engines. Read it at the source: A map of your pages is offered to search engines
A preview appears when someone shares or texts your link: Open Graph protocol (ogp.me) The Open Graph protocol enables any web page to become a rich object in a social graph. Read it at the source: A preview appears when someone shares or texts your link
That preview carries a picture: Open Graph protocol (ogp.me) The Open Graph protocol enables any web page to become a rich object in a social graph. Read it at the source: That preview carries a picture
Business information for Google: Google Search Central structured data documentation Google Search supports structured data in the following formats, unless documented otherwise. Read it at the source: Business information for Google
Built for phones: Google (web.dev / Chrome for Developers) Using the meta viewport value width=device-width tells the page to match the screen's width in device-independent pixels (DIP), a standard visual pixel unit. Read it at the source: Built for phones
Your layout adjusts to the size of the screen: Google Search Central Serves the same HTML code on the same URL... but can display the content differently based on the screen size. Read it at the source: Your layout adjusts to the size of the screen
Secure address (HTTPS): Google Search Central Blog, 2014 ('HTTPS as a ranking signal') we're starting to use HTTPS as a ranking signal Read it at the source: Secure address (HTTPS)
A missing page says it is missing: Google Search Console Help (Search Central) it returns a user-friendly "not found" message but not a 404 HTTP response code. We recommend returning a 404 response code for truly "not found" pages Read it at the source: A missing page says it is missing
Server response time: Google web.dev, Time to First Byte (TTFB) Good TTFB values are 0.8 seconds or less, and poor values are greater than 1.8 seconds. Read it at the source: Server response time
How many other companies run code on your page: Google web.dev, "Load Third-Party JavaScript" They can slow down your site's performance. They can cause privacy or security issues. They can be unpredictable and their behavior can have unintended consequences. Read it at the source: How many other companies run code on your page
Your words arrive with the page, not after: Google Search Central (Google for Developers) Some JavaScript sites may use the app shell model where the initial HTML does not contain the actual content Read it at the source: Your words arrive with the page, not after
Images keep their space while they load: Google web.dev, "Optimize Cumulative Layout Shift" Always include width and height size attributes on your images and video elements. Read it at the source: Images keep their space while they load
Hours where Google reads them: Google Search Central, Local Business structured data guide openingHoursSpecification: Array or single object... Hours during which the business location is open. Read it at the source: Hours where Google reads them
A link lets keyboard users skip past the menu: W3C WCAG (WCAG 2.2, W3C Recommendation 12 December 2024, Success Criterion 2.4.1 Bypass Blocks, Level A) A mechanism is available to bypass blocks of content that are repeated on multiple web pages. Read it at the source: A link lets keyboard users skip past the menu
Visible to Google Search: Google Search Central, "Block Search indexing with noindex" (last updated 2025-12-10); backed by "Robots meta tag, data-nosnippet, and X-Robots-Tag specifications" (last updated 2026-03-24) When Googlebot crawls that page and extracts the tag or header, Google will drop that page entirely from Google Search results, regardless of whether other sites link to it. Read it at the source: Visible to Google Search
Written to be understood: Rudolf Flesch, How to Write Plain English, chapter 2 (the Flesch Reading Ease formula and its Plain English line), read at the reproduction on appstate.edu. We did not read the printed book, and the year is not on that page The minimum score for Plain English is 60 Read it at the source: Written to be understood
Images load when needed: Google web.dev, "Browser-level image lazy loading for the web" (Osmani, Djirdeh, Bynens, Pollard; page last updated 2024-08-13 UTC); the mechanism from the WHATWG HTML Living Standard, section 2.5.7 Lazy loading attributes You can use the loading attribute to completely defer the loading of offscreen images Read it at the source: Images load when needed

Not everything we check has an outside body behind it. Some of it is how Google documents its own system, and some is our own judgment from reading thousands of local business websites. We label which is which rather than dressing our opinion up as a rule.

If your site passes, we say so. A good result has no serious problem to fix. That is what makes this worth anything.

Inspect another website Ask a question

Measured, not claimed

What 78,807 business websites actually score.

Every figure came from this same inspection, which we ran ourselves on business websites, almost all of them found on OpenStreetMap, the free public map. No site is named. The 4,160 chain and franchise websites are left out here; the Three Rings page counts them.

Middle score

11,543/78,807

Told nothing serious was found

19,088

Sites showing a phone number that cannot be tapped

311/2,615

Licensed trades, no license shown

All three verdicts, not just the flattering one: 11,543 were told nothing serious was found, 66,177 got a short list, 1,087 got several serious findings. Your report shows where you land.

Note: by the kind of business each site is listed as, about 42 in 100 are places to eat or drink, so the middle score leans toward them. If you run a different kind of business, treat it as a starting point rather than your benchmark.