03 · Technical

Nothing blocks Google or the AI crawlers, and phone speed looks like the main thing to work on

We tested the Harbour & Key homepage on a phone and on desktop, checked AI crawler access and ran a 231-page crawl of example-property.co.uk. Measured on 8 July 2026, prepared by Robin Laires.

The short version
What we found
On a phone, the main content of the homepage took 16.7 seconds to show. On desktop it took 2.0 seconds. Google and the AI crawlers can read the site.
Why it matters
Most property searches start on a phone, and Google's ranking systems look at this experience.
What could help
Trimming the scripts and styles a phone does not need for the first screen, and checking two legacy addresses that lead nowhere.
44 / 100
Homepage performance score on a phone
82 / 100
Homepage performance score on desktop
16.7 s
Time until the main content shows on a phone
4,033 KiB
Homepage weight on the mobile run
4 of 4
AI crawlers that get a 200 response
92 / 100
Technical SEO score, phone and desktop
What is working

Access is open

good

GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot all get a 200 response, the same as a plain browser and the regular Googlebot user agent. robots.txt is open and the sitemap is declared. The desktop score of 82 / 100 and the technical SEO score of 92 / 100 are also sound. From what we can see, the engines can read everything on the site. The gap is the amount on the money pages for them to lift (see content and trust and the scorecard).

At a glance

Scores and checks on the homepage

CheckResultStatus
Technical SEO score, homepage (mobile)92 / 100good
Technical SEO score, homepage (desktop)92 / 100good
AI crawler access (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot)200 on all fourgood
robots.txtOpen, sitemap declaredgood
llms.txtNot presentgood
Mobile performance score44 / 100critical
Desktop performance score82 / 100good
Finding

Main content takes 16.7 seconds to appear on a phone

critical
Phone
16.7 s
until the main content shows, score 44 / 100
Desktop
2.0 s
until the main content shows, score 82 / 100
Google's page performance test on the homepage, 8 July 2026. Google's target is under 2.5 s.
Mobile score
44 / 100
Desktop score
82 / 100
Technical SEO
92 / 100

It is the same server, the same page and the same content on both. That points to the build and not to hosting. Most property searches start on a phone, and Google's ranking systems measure exactly this experience.

What could help: cutting the 746 KiB of unused JavaScript and 144 KiB of unused CSS the mobile run carries. A first milestone of main content under 4 seconds could be set (Phase 1 of the action plan), then pushed toward 2.5 s.

Speed test

Homepage, mobile and desktop, 8 July 2026

MetricMobileDesktopTargetStatus
Performance score44 / 10082 / 10090+critical
Main content visible (largest contentful paint)16.7 s2.0 sunder 2.5 scritical
First paint8.3 s1.4 sunder 1.8 shigh
Main thread blocked (total blocking time)440 ms20 msunder 200 mshigh
Layout shift0.0290.012under 0.1good
Finding

746 KiB of unused JavaScript and a 4,033 KiB page

high
SignalValueStatus
Unused JavaScript, mobile run746 KiBhigh
Unused CSS, mobile run144 KiBmedium
Page weight, mobile4,033 KiBhigh

The mobile run downloads and parses 746 KiB of JavaScript that never gets used, plus 144 KiB of unused CSS, on a page that weighs 4,033 KiB. From what we can see, that is the direct cause of the 16.7 second wait and the 440 ms of blocked main thread.

What could help: trimming or deferring the scripts and styles the first screen does not need, then re-testing against the 4 second milestone.

AI crawler access

Every crawler we tried gets a 200

8 July 2026
CrawlerResponseStatus
GPTBot200good
OAI-SearchBot200good
ClaudeBot200good
PerplexityBot200good
Google-Extended (regular Googlebot user agent)200good
Plain browser200good

There is no llms.txt file, and the evidence here suggests that does not matter, because none of the engines need it to read the site. Nothing to fix here, and adding llms.txt would not change anything we measured.

Finding

Two legacy paths and one subdomain lead nowhere

medium
URLResponseNote
/dvd/disc_show.asp4047 old inbound links point here
/dvd/freetalk_show.asp4044 old inbound links point here
enquiries.example-property.co.uk/valuation403 to every client tested7 external links point here

The old /dvd/*.asp addresses are left over from a previous site build. They now return a 404, and 11 old inbound links still point at the two of them. The valuation subdomain returned a 403 to every client tested in this audit, while 7 external links point at it. The /valuation/ page on the main domain loads fine (200), so the subdomain could be an over-tight firewall rule or a dead end from an old funnel. It would need a look from inside to say which. More on this on the enquiries and tracking page.

What could help: a 301 from the /dvd/*.asp addresses to their current equivalents, and a check of the firewall rule on the enquiries subdomain. This looks like an afternoon of work (Phase 0 of the action plan).

Finding

The automated checks pass, and that is only part of the picture

good

The technical SEO score is 92 / 100 on both mobile and desktop, HTTPS is fine, and the site runs on WordPress with Yoast. That score covers basics such as crawlability and viewport. It does not cover content quality. The same audit found that 42 of the 53 core pages carry no H1 heading and 52 of 53 have no meta description (see the scorecard and site structure). A clean 92 here should not be read as the money pages being in good shape. Restoring the H1 headings and meta descriptions on the 53 core pages is tracked in Phase 0 of the action plan.

Method and limits

We ran Google's page performance test on the homepage, phone and desktop, on 8 July 2026, and crawled 231 pages. AI crawler access was checked on the same date. Speed figures come from one test and will vary between runs.

Real client work. Names and locations changed.