SEO report for www.computinghistory.org.uk

Real-world speed Google PageSpeed

Loading Core Web Vitals from Google… this can take up to 30 seconds.

Authority & backlinks

Looking up which websites link to computinghistory.org.uk…

Indexing & crawling 69%

Can search engines reach, read and index this page?

• ✓

  Status codecritical

  The page returned HTTP 200.

• ✓

  Indexablecritical

  No noindex instruction – the page can appear in search.

• ✓

  robots.txthigh

  robots.txt found.

  Googlebot is allowed to crawl this page.

• ✗

  XML sitemaphigh

  No XML sitemap found at /sitemap.xml or in robots.txt.

  Fix: Create an XML sitemap listing every page and submit it in Google Search Console.

  Make one with the free XML sitemap generator

  Read the guide: XML sitemaps

• ✗

  Canonical URLhigh

  No canonical tag.

  Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.

  Read the guide: duplicate content

• !

  Redirectshigh

  2 redirects before the page loaded – a chain slows visitors and wastes crawl budget.

  https://computinghistory.org.uk/ → http://www.computinghistory.org.uk/ → https://www.computinghistory.org.uk/

  Fix: Link straight to the final address and make each redirect go to its destination in one hop.

  Read the guide: broken links and redirects

• ✓

  www / non-wwwmedium

  computinghistory.org.uk redirects to www.computinghistory.org.uk.

Search snippet & sharing 13%

How the page looks in Google results and when shared.

• ✗

  Title tagcritical

  “The Centre for Computing History - Computer and Video Game Museum - Cambridge”

  About 758px of Google's ~580px desktop width – it will probably be cut off.

  Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• !

  Meta descriptionhigh

  201 characters, ~1300px of ~990px.

  Long – Google will probably truncate it.

  Google sometimes rewrites descriptions to match the search; a good one is still used most often.

  Fix: Write a 140–155 character description that answers the searcher's question and invites the click.

  Write one free with the AI title & description writer

  Read the guide: how to write meta descriptions

• ✗

  Open Graph & social cardsmedium

  Open Graph title or image missing.

  No twitter:card tag.

  Fix: Add og:title, og:description, og:image (1200×630 PNG/JPG, absolute URL) and twitter:card=summary_large_image.

  Make the tags with the free Open Graph generator

  Read the guide: does social media help SEO?

• ✗

  Faviconlow

  No favicon linked.

  Fix: Add a square favicon at least 48×48px.

• ✗

  Languagelow

  No lang attribute on <html>.

  Fix: Add lang="en-GB" (or your language) to the <html> tag.

Content quality 77%

Is there enough clear, useful text that matches what the page targets?

• ✓

  Word countmedium

  744 words of main content (menus and footer excluded).

  Google has no minimum word count – this is a rough guide to whether the page answers the question in full.

• !

  Readabilitymedium

  Flesch reading ease 46 (fairly difficult), about 13 words per sentence.

  Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.

  Read the guide: how to write SEO content

• ✓

  Topic focushigh

  8 of 8 title keywords appear in the main content.

• !

  H1 headingcritical

  “Donate Today!”

  The H1 shares no keywords with the title.

  Fix: Use one H1 that states the page topic with its main keyword.

• ✓

  Heading structuremedium

  10 headings for 744 words.

  Levels are in order.

• ✓

  Text-to-code ratiolow

  15% of the HTML is visible text.

AI search readiness 50%

Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?

• ✓

  AI crawler accesshigh

  Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.

• ✓

  Snippet controlshigh

  No snippet restrictions – search and AI answers can quote this page.

• ✗

  llms.txtlow

  No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.

  Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.

  Make one with the free llms.txt generator

  Read the guide: do you need llms.txt?

• ✗

  Question-led contentmedium

  No headings phrased as questions.

  Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.

  Read the guide: how to write SEO content

• ✗

  Entity clarityhigh

  No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.

  Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✗

  Freshness signalsmedium

  No published/updated date found.

  Fix: Show a 'last updated' date and add dateModified to your structured data.

• ✓

  Trust pages (E-E-A-T)medium

  Links found to all three: about, contact and privacy.

Structured data 0%

Machine-readable facts for rich results and AI.

• ✗

  JSON-LD present & validhigh

  No JSON-LD structured data.

  Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).

  Make valid code with the free schema generator

  Read the guide: schema markup

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 80%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  65 internal and 7 external links.

• !

  Anchor text qualitymedium

  Same text used for different pages: “education group visits”.

  Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.

  Check every link's wording with the free anchor text checker

  Read the guide: internal linking

• ✓

  Broken links (sample)high

  Checked 12 internal link(s).

  No broken links found.

  1 link(s) point to a redirect – link to the final address instead.

• !

  Internal links to http://medium

  8 internal link(s) use http:// – each one goes through a redirect.

  Fix: Update internal links to use https:// (or relative links).

Performance 53%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

• ✓

  Server response (TTFB)high

  270 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).

• ✓

  HTML sizemedium

  33 kB of HTML.

• ✓

  Compressionmedium

  Compressed with gzip.

• ✗

  Render-blocking resourceshigh

  13 blocking script(s) and 8 stylesheet(s) in <head>.

  Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

  Read the guide: Core Web Vitals

• !

  Scripts & third partiesmedium

  19 script tag(s); files loaded from 2 other domain(s): fonts.googleapis.com, cdn.jsdelivr.net.

  Fix: Remove unused tracking and widget scripts; every third party adds connection time.

  Read the guide: Core Web Vitals

• ✗

  Imagesmedium

  22 image(s).

  12 without width/height – can cause layout shift (CLS).

  19 image(s) after the first three aren't lazy-loaded.

  0 use WebP/AVIF or responsive srcset.

  Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

  Read the guide: image SEO

• ✗

  Cachinglow

  No Cache-Control header.

  Fix: Set Cache-Control so browsers and CDNs can reuse the page.

• i

  HTTP/3low

  Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.

Security 54%

Visitor safety signals that browsers and Google check.

• !

  HTTPScritical

  7 file(s) load over insecure http:// (mixed content) – browsers may block them.

  Fix: Serve everything over HTTPS and update http:// file links.

  Read the guide: fixing a "Not secure" warning

• ✓

  HTTP → HTTPS redirecthigh

  http:// redirects to https://.

• ✗

  HSTSmedium

  No Strict-Transport-Security header.

  Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.

  Read the guide: the technical SEO checklist

• ✗

  Security headerslow

  Present: none.

  Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).

  Read the guide: the technical SEO checklist

• ✓

  Server fingerprintlow

  No X-Powered-By header (server: cloudflare).

Mobile & accessibility 42%

Usable on phones and by everyone – Google indexes the mobile version.

• ✗

  Mobile viewportcritical

  viewport: width=1200, maximum-scale=4

  Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.

  Read the guide: mobile-friendly websites

• ✓

  Image alt textmedium

  All 22 images have alt text.

• ✗

  Form labelsmedium

  1 of 1 form field(s) have no label.

  Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).

• ✓

  Link nameslow

  Every link has a readable name.

• ✓

  Tap-to-contactmedium

  One-tap contact: email.

Local SEO 33%

Signals that help you appear in Google Maps and 'near me' searches.

• ✗

  LocalBusiness markuphigh

  No LocalBusiness structured data.

  Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✓

  Contact details on pagemedium

  A UK phone number is shown.

  A UK postcode is shown.

  An email link is shown.

• ✗

  Map & directionslow

  No map or directions link.

  Fix: Add a Google Maps directions link so customers can find you.

  Read the guide: the local SEO checklist