Website review, no card needed

muddyarchaeologist.co.uk logo

muddyarchaeologist.co.uk website review

Visit site (opens in a new tab)Reviewed 27 October 202637 issues · 80 checks

This review found 37 issues worth fixing on muddyarchaeologist.co.uk, 17 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of muddyarchaeologist.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. muddyarchaeologist.co.uk at 0.7 s0.7 s
  2. muddyarchaeologist.co.uk at 1.5 s1.5 s
  3. muddyarchaeologist.co.uk at 2.2 s2.2 s
  4. muddyarchaeologist.co.uk at 2.9 s2.9 s
  5. muddyarchaeologist.co.uk at 3.6 s3.6 s
  6. muddyarchaeologist.co.uk at 4.4 s4.4 s
  7. muddyarchaeologist.co.uk at 5.1 s5.1 s
  8. muddyarchaeologist.co.uk at 5.8 s5.8 s

Speed

8 to fix57
  • Use efficient cache lifetimes

    7.1 s · 4.0 MB

    65 files are served with short cache lifetimes, so returning visitors download them again (4.0 MB).

  • Improve image delivery

    3.6 s · 3.3 MB

    17 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.6 s faster on a phone.

  • Render-blocking requests

    3.3 s

    20 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57 (desktop: 79). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    750 ms · 134 KiB

    About 134 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • 7 third-party services on the page

    7 third-party services load with your homepage (convertkit.com, ck.page and Google Fonts and others), adding 2.7 MB and 16 ms of main-thread time.

  • thinkific.com adds 0 ms

    0 ms

    thinkific.com costs a phone 0 ms of main-thread work and 2.1 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • filekitcdn.com adds 0 ms

    0 ms

    filekitcdn.com costs a phone 0 ms of main-thread work and 481 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused JavaScript

    150 ms · 121 KiB

    About 121 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify CSS

    150 ms · 21 KiB

    21 KiB could be saved by minifying CSS.

  • Document request latency

    117 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 58 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    32 KiB

    Polyfills for old browsers add 32 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 190 ms of it running JavaScript. That is comfortably low.

  • Server response: 314 ms

    314 ms

    Your server sent the HTML in 314 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 10.3 s

    10.3 s

    Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 12.3 s

    12.3 s

    Visually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 17.5 s

    17.5 s

    The page becomes fully interactive after 17.5 s. Good is under 3.8 s.

  • First Contentful Paint: 4.5 s

    4.5 s

    The first text or image appears after 4.5 s on a phone. Good is under 1.8 s.

  • 5 images without width and height

    5 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 2 ms

    2 ms

    Scripts block the page for only 2 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 5.4 MB in 75 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 75 requests on a phone: images 4.6 MB (25), scripts 388 KiB (24) and stylesheets 199 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Still-BBC-New-Channel-Gillian-Hovell-22-Dec-2021-prehistoric weighs 674 KiB. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    731 KiB

    4 images are downloaded at several times the size a phone draws them, for example Still-BBC-New-Channel-Gillian-Hovell-22-Dec-2021-prehistoric at 900 px wide, shown at 161 px. Resized copies would save about 731 KiB.

  • 7 images in older formats

    7 images (1.2 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 2 images below the first screen load straight away

    2 images further down the page (758 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.5 g of CO₂ per visit

    1.54 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.54 g of CO₂e: 184.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

8 to fixGoogle 7691
  • Links look like plain text

    16 links inside paragraphs rely on colour alone to stand out.

  • 6 images without alt text

    6 images have no alt text, which hurts accessibility and image search.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 40 links without text

    40 visible links have no text or label, so screen readers cannot say where they go.

  • 7 text elements with low contrast

    7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Elements marked as presentational should be consistently ignored (15 elements)

    Elements marked as presentational should be consistently ignored: 15 elements on the page fail this check, rated minor by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

1 checks passed
  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8590
  • Meta description is long (377 characters)

    Your meta description is 377 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 49 internal links, 89 external

    The homepage links to 49 pages on muddyarchaeologist.co.uk and 89 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “The Muddy Archaeologist”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “Home - The Muddy Archaeologist”.

  • Canonical URL set

    The canonical URL is https://www.muddyarchaeologist.co.uk/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.muddyarchaeologist.co.uk/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,729 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.muddyarchaeologist.co.uk/llms.txt (14 KiB, 102 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

1 to fix0
  • 2 linked pages are broken

    Your homepage links to https://www.muddyarchaeologist.co.uk/[email protected] and https://www.muddyarchaeologist.co.uk/[email protected], which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 internal pages checked

    We fetched 2 pages linked from your homepage and read each the way a search engine does.

Best practices

3 to fixGoogle 6971
  • 1 broken image

    1 image failed to load on a phone, for example https://www.muddyarchaeologist.co.uk/wp-content/uploads/2023/01/Gillian-Hovell-BA-CV-Sept-2022.docx.pdf.

  • 4 small tap targets

    4 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 2,723 words of copy

    The homepage carries about 2,723 words of visible text.

3 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Shop”, “Contact” and “BOOK ME NOW!”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 4 other companies contacted

    Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at muddyarchaeologist.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2017.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Hosting
Gd Emea Dc Ld5

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on muddyarchaeologist.co.uk, including 13 speed issues, 3 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25