Website Health Check www.harridigital.co.uk

harridigital.co.uk · checked 7 Sep 2026, 18:28

Strong. Just polish left.

Nothing here should cost you sleep. The few things below would take it from good to sharp.

This report is from 47 days ago. Changed something since? Run it again for fresh numbers.
Download PDF Get help with your results

Where this site stands, area by area

Click an area for the detail and the evidence.

GooglePageSpeed Insights

Core Web Vitals

Google's lab test; Chrome has no real-visitor data for this site yet. Google's thresholds, unedited.

Phone

Source
LCP Largest Contentful Paint How long the biggest thing on the screen takes to appear
INP Interaction to Next Paint How quickly the page responds when someone taps or clicks
CLS Cumulative Layout Shift How much the page jumps about while it loads
Google's lab testOne simulated phone visit
2.0 sGood
0 msGood Total Blocking Time, the lab stand-in for INP
0.00Good

Desktop

Source
LCP Largest Contentful Paint How long the biggest thing on the screen takes to appear
INP Interaction to Next Paint How quickly the page responds when someone taps or clicks
CLS Cumulative Layout Shift How much the page jumps about while it loads
Google's lab testOne simulated desktop visit
421 msGood
0 msGood Total Blocking Time, the lab stand-in for INP
0.00Good

All five metrics, Google's thresholds and what to do

Scores move a few points between runs; that's normal. Fix the list, not the number.

Harri's read · AI-drafted

In short

This site scores highly across search, speed, accessibility and AI readiness. The top findings are that the site is correctly structured for search engines with proper headings, meta descriptions and image alt text all in place; that page load times are excellent with a time to first byte of 25 milliseconds and compression working well; and that the site is ready for discovery by AI systems with no blocking in place and proper structured data present. All of these reflect established best practice. The site is secure with HTTPS enabled, has strong accessibility standards met and maintains proper caching and headers.

Written by AI from the findings below. Everything else on this page is written by people.

AI readiness

Strong · 100

This section is ours, not Google's, and it only checks things we can actually see. Whether your robots.txt turns away the crawlers that ChatGPT, Perplexity, Claude and Google use to find sources. Whether the words on your page are in the HTML, or only appear after JavaScript runs, which most AI crawlers never do. Whether a machine can tell who you are from your page. Whether a bot-protection screen gets in the way.

Each of those is a fact about your site, and every card shows the evidence we found. What nobody outside those companies can measure is how often an AI assistant mentions you, or whether fixing these will change that, and Google says plainly that no special files or markup are needed for its AI features. So read this section as "nothing is stopping them reading you", not "you will be recommended". Where a check rests on good practice rather than a vendor's word, the card says so.

Nothing in this section needs attention.

Harri's read · AI readiness · for information

Training crawlers

Why it matters
GPTBot, ClaudeBot, Google-Extended and the like feed model training, not answers. Blocking them does not remove a site from ChatGPT search, Perplexity or Google's AI features, with one nuance: Google-Extended also governs whether the Gemini app can ground on a page. Bytespider has no vendor documentation and is reported to ignore robots.txt.
What to do
Decide on training separately from being found. If the file blocks a name Anthropic no longer documents (anthropic-ai, Claude-Web) while allowing ClaudeBot, it is not doing what it was meant to.
Effort
Quick win

Evidence we found: 0 training crawler(s) blocked.

Established

Harri's read · AI readiness · for information

llms.txt

Why it matters
llms.txt is a proposed convention: a plain-text page telling AI tools what a site is and where its important pages are. Being honest, no major AI vendor has confirmed it reads the file, and Google says it ignores it. It costs almost nothing, so it sits in the "why not" pile, not the "must" pile, and it moves no score here.
What to do
If you like, publish a short /llms.txt: one line on who you are, then your key pages with a line each.
Effort
Quick win

Evidence we found: /llms.txt present: yes.

Best practice, evidence still thin

What passed (5)
  • AI assistants are being turned away at the door. None of the answer engines' crawlers is blocked.
  • A bot-protection screen is standing in the way. No challenge page in the way.
  • The words are not in the page, only in the JavaScript. About 894 words are in the delivered HTML.
  • A machine cannot easily find the main content. Main landmark, subheadings and heading order all present.
  • The page has not told the machines who the business is. Organization with 6 key properties.

Search

Strong · 100

Nothing in this section needs attention.

What passed (15)
  • Search engines are being told to leave this page out. Indexable: HTTP 200, no noindex, not blocked in robots.txt.
  • The page title is doing very little. "Harri Digital | Web Design & SEO Agency, Plymouth & Devon" (57 characters, about 545px).
  • Google is writing the search listing for this page. Present, 155 characters.
  • The page does not say clearly which address is the real one. Self-referencing canonical.
  • The page has no clear main heading. One h1.
  • The page is not set up for phones. Viewport set for device width.
  • The page does not say what language it is in. lang="en-GB".
  • The secure page loads insecure pieces. No insecure references.
  • Shared links to this page will look bare. Open Graph title, description and absolute image present.
  • Many images have no description. 100% of images carry alt text.
  • The page carries no structured data. Structured data present: Organization, WebSite, WebPage.
  • There is very little text on this page. About 894 words of body text.
  • The site answers at more than one address. www, non-www, http and https all lead to one address in one hop.
  • The sitemap is missing or not where search engines look. Sitemap present (125 entries) and named in robots.txt.
  • Missing pages do not say they are missing. A made-up address correctly answered 404.

Not tested this time: the page gives no sign of when it was last updated.

Speed

Strong · 99 lab only, no real-visitor data yet

Google's PageSpeed Insights · unedited

99, good Phone performance
100, good Desktop performance
100, good SEO
100, good Accessibility
100, good Best practices

No real-visitor data yet: Chrome only reports it for sites with enough traffic. The numbers above are lab tests.

Core Web Vitals Phone Google's three measures of how a page feels, plus the two timings underneath them

  1. LCP Largest Contentful Paint How long the biggest thing on the screen takes to appear
    2.0 sGood

    Good: 2.5 s or under. Poor: over 4.0 s. Headline: Google's lab test.

    What it measures. The moment the largest image or block of text is on screen. For most visitors this is when the page feels loaded.

    Within Google's good range. Nothing to do here.

  2. INP Interaction to Next Paint How quickly the page responds when someone taps or clicks
    0 msGood

    Good: 200 ms or under. Poor: over 600 ms. Headline: Google's lab test (Total Blocking Time, the lab stand-in for this metric).

    What it measures. The delay between a tap, click or key press and the screen changing, measured across the whole visit. Long delays feel like the page is ignoring the visitor.

    Within Google's good range. Nothing to do here.

  3. CLS Cumulative Layout Shift How much the page jumps about while it loads
    0.00Good

    Good: 0.10 or under. Poor: over 0.25. Headline: Google's lab test.

    What it measures. How far things on the page move after they first appear, such as text that jumps when an image or advert loads above it. A high number means visitors tap the wrong thing.

    Within Google's good range. Nothing to do here.

  4. FCP First Contentful Paint How long until anything at all appears
    1.3 sGood

    Good: 1.8 s or under. Poor: over 3.0 s. Headline: Google's lab test.

    What it measures. The first moment any text or image is on screen. Before this the visitor is looking at a blank page.

    Within Google's good range. Nothing to do here.

  5. TTFB Time to First Byte How long the server takes to start answering
    7 msGood

    Good: 800 ms or under. Poor: over 1.8 s. Headline: Google's lab test.

    • Google's lab test: 7 ms · Good
    • Our fetch: 25 ms · Good

    What it measures. The wait between asking for the page and the first byte of it arriving. Everything else stacks on top of this.

    Within Google's good range. Nothing to do here.

Core Web Vitals Desktop Google's three measures of how a page feels, plus the two timings underneath them, from the desktop run

  1. LCP Largest Contentful Paint How long the biggest thing on the screen takes to appear
    421 msGood

    Good: 2.5 s or under. Poor: over 4.0 s. Headline: Google's lab test.

    What it measures. The moment the largest image or block of text is on screen. For most visitors this is when the page feels loaded.

    Within Google's good range. Nothing to do here.

  2. INP Interaction to Next Paint How quickly the page responds when someone taps or clicks
    0 msGood

    Good: 200 ms or under. Poor: over 600 ms. Headline: Google's lab test (Total Blocking Time, the lab stand-in for this metric).

    What it measures. The delay between a tap, click or key press and the screen changing, measured across the whole visit. Long delays feel like the page is ignoring the visitor.

    Within Google's good range. Nothing to do here.

  3. CLS Cumulative Layout Shift How much the page jumps about while it loads
    0.00Good

    Good: 0.10 or under. Poor: over 0.25. Headline: Google's lab test.

    What it measures. How far things on the page move after they first appear, such as text that jumps when an image or advert loads above it. A high number means visitors tap the wrong thing.

    Within Google's good range. Nothing to do here.

  4. FCP First Contentful Paint How long until anything at all appears
    313 msGood

    Good: 1.8 s or under. Poor: over 3.0 s. Headline: Google's lab test.

    What it measures. The first moment any text or image is on screen. Before this the visitor is looking at a blank page.

    Within Google's good range. Nothing to do here.

  5. TTFB Time to First Byte How long the server takes to start answering
    8 msGood

    Good: 800 ms or under. Poor: over 1.8 s. Headline: Google's lab test.

    • Google's lab test: 8 ms · Good
    • Our fetch: 25 ms · Good

    What it measures. The wait between asking for the page and the first byte of it arriving. Everything else stacks on top of this.

    Within Google's good range. Nothing to do here.

Google found

  • Reduce unused CSS about 0.1 s off your largest paint
  • Forced reflow
  • Network dependency tree

Full report on PageSpeed Insights

Nothing in this section needs attention.

What passed (2)
  • The server is slow to start answering. 25ms to first byte.
  • The page is sent uncompressed or without caching instructions. Compressed and carrying Cache-Control.

Accessibility and trust

Strong · 100

Nothing in this section needs attention.

What passed (4)
  • Some visitors will struggle to use this site. Google's accessibility score is 100 out of 100.
  • The site is not fully on https. https throughout, http redirects.
  • The site does not insist on https. HSTS set for 365 days.
  • Some routine security headers are missing. 5 of the 5 routine security headers set.

Everything we checked

CheckSectionSourceResultEvidence
Search engines are being told to leave this page out Search Harri pass Indexable: HTTP 200, no noindex, not blocked in robots.txt.
The page title is doing very little Search Harri pass "Harri Digital | Web Design & SEO Agency, Plymouth & Devon" (57 characters, about 545px).
Google is writing the search listing for this page Search Harri pass Present, 155 characters.
The page does not say clearly which address is the real one Search Harri pass Self-referencing canonical.
The page has no clear main heading Search Harri pass One h1.
The page is not set up for phones Search Harri pass Viewport set for device width.
The page does not say what language it is in Search Harri pass lang="en-GB".
The secure page loads insecure pieces Search Harri pass No insecure references.
Shared links to this page will look bare Search Harri pass Open Graph title, description and absolute image present.
Many images have no description Search Harri pass 100% of images carry alt text.
The page carries no structured data Search Harri pass Structured data present: Organization, WebSite, WebPage.
There is very little text on this page Search Harri pass About 894 words of body text.
The page gives no sign of when it was last updated Search Harri not tested No dates found; normal for a homepage.
The site answers at more than one address Search Harri pass www, non-www, http and https all lead to one address in one hop.
The sitemap is missing or not where search engines look Search Harri pass Sitemap present (125 entries) and named in robots.txt.
Missing pages do not say they are missing Search Harri pass A made-up address correctly answered 404.
The server is slow to start answering Speed Harri pass 25ms to first byte.
The page is sent uncompressed or without caching instructions Speed Harri pass Compressed and carrying Cache-Control.
AI assistants are being turned away at the door AI readiness Harri pass None of the answer engines' crawlers is blocked.
Training crawlers AI readiness Harri for information 0 training crawler(s) blocked.
A bot-protection screen is standing in the way AI readiness Harri pass No challenge page in the way.
llms.txt AI readiness Harri for information /llms.txt present: yes.
The words are not in the page, only in the JavaScript AI readiness Harri pass About 894 words are in the delivered HTML.
A machine cannot easily find the main content AI readiness Harri pass Main landmark, subheadings and heading order all present.
The page has not told the machines who the business is AI readiness Harri pass Organization with 6 key properties.
Some visitors will struggle to use this site Accessibility and trust Harri pass Google's accessibility score is 100 out of 100.
The site is not fully on https Accessibility and trust Harri pass https throughout, http redirects.
The site does not insist on https Accessibility and trust Harri pass HSTS set for 365 days.
Some routine security headers are missing Accessibility and trust Harri pass 5 of the 5 routine security headers set.
Links are crawlable Search Google pass Lighthouse: Links are crawlable
Links have descriptive text Search Google pass Lighthouse: Links have descriptive text
The page answers with a successful status Search Google pass Lighthouse: Page has successful HTTP status code
robots.txt is valid Search Google pass Lighthouse: robots.txt is valid
hreflang is valid (when present) Search Google pass Lighthouse: Document has a valid hreflang

No card, no catch

Want more than a score? Get a free extended review from our experts, not AI.

A score doesn't know your business. Tell us what you want the site to do for you and one of us in Plymouth will read this report with that in mind, then write you a one-page review covering search, speed, AI readiness and accessibility. It arrives within three working days. No sales pitch stapled to it. Most reviews don't turn into projects, and that's fine.

We'll send the review to Jack at j***@harridigital.co.uk.

Not Jack? Add your details

Not the person who ran this check? No problem, just tell us who you are so the review reaches you.

Which best describes you? (optional)

We use your details to send the review and nothing else, unless you tick the box above. This report is private to anyone with the link and is deleted after 90 days.

Or just talk to us

Run another site