Website review, no card needed

homeserve.co.uk logo

homeserve.co.uk website review

Visit site (opens in a new tab)Reviewed 1 November 202630 issues · 84 checks

This review found 30 issues worth fixing on homeserve.co.uk, 8 of them high impact, across 84 checks. The most urgent: page weight: 4.2 MB in 119 requests. 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

Real-visitor load time (LCP)75th percentile, phones
2.5 s1.8 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.3 s
May 30, 20262.5 s
Jun 6, 20262.4 s
Jun 13, 20262.3 s
Jun 20, 20262.2 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20261.9 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
213 ms164 msMay 9Oct 24198 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026173 ms
May 16, 2026171 ms
May 23, 2026170 ms
May 30, 2026172 ms
Jun 6, 2026177 ms
Jun 13, 2026182 ms
Jun 20, 2026186 ms
Jun 27, 2026186 ms
Jul 4, 2026188 ms
Jul 11, 2026191 ms
Jul 18, 2026192 ms
Jul 25, 2026195 ms
Aug 1, 2026198 ms
Aug 8, 2026201 ms
Aug 15, 2026204 ms
Aug 22, 2026207 ms
Aug 29, 2026207 ms
Sep 5, 2026203 ms
Sep 12, 2026200 ms
Sep 19, 2026196 ms
Sep 26, 2026194 ms
Oct 3, 2026195 ms
Oct 10, 2026196 ms
Oct 17, 2026197 ms
Oct 24, 2026198 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of homeserve.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. homeserve.co.uk at 0.4 s0.4 s
  2. homeserve.co.uk at 0.8 s0.8 s
  3. homeserve.co.uk at 1.1 s1.1 s
  4. homeserve.co.uk at 1.5 s1.5 s
  5. homeserve.co.uk at 1.9 s1.9 s
  6. homeserve.co.uk at 2.3 s2.3 s
  7. homeserve.co.uk at 2.6 s2.6 s
  8. homeserve.co.uk at 3.0 s3.0 s

Speed

8 to fix66
  • Reduce unused JavaScript

    1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Trust Pilot and LivePerson and others), adding 2.9 MB and 1.1 s of main-thread time.

  • Mobile performance score: 66

    66/100

    Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 598 ms

    598 ms

    Google Tag Manager costs a phone 598 ms of main-thread work and 876 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.

  • Use efficient cache lifetimes

    489 KiB

    19 files are served with short cache lifetimes, so returning visitors download them again (489 KiB).

  • Improve image delivery

    462 KiB

    2 images could be 462 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • LivePerson adds 139 ms

    139 ms

    LivePerson costs a phone 139 ms of main-thread work and 1.3 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.

  • Main-thread work: 2.2 s

    A phone's processor spends 2.2 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

  • Render-blocking requests

    150 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

  • 9 long tasks on the main thread

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

  • Reduce unused CSS

    103 KiB

    About 103 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    13 KiB

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

  • 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.

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 42 ms

    42 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 24.1 s

    24.1 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • Largest Contentful Paint: 3.7 s

    3.7 s

    Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “At HomeServe, cookies keep our website running smoothly and…”. Most of its time is element render delay (2.5 s).

  • Total Blocking Time: 347 ms

    347 ms

    Scripts block taps and scrolling for 347 ms in total while the page loads. Good is under 200 ms.

  • 3 images without width and height

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

  • Tap response (INP) got 15% slower for real visitors

    +15%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 173 ms to 198 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.6 s

    1.6 s

    Real visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 171 ms

    171 ms

    Real visitors wait 171 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 659 ms

    659 ms

    Real visitors wait 659 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 13% faster for real visitors

    -13%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 4.2 MB in 119 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 119 requests on a phone: scripts 3.0 MB (41), images 728 KiB (17) and HTML 221 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (524 KiB) 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 (134 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.2 g of CO₂ per visit

    1.18 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9597
  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (14 elements)

    All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (6 elements).

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

1 to fixGoogle 8598
  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 81 internal links, 9 external

    The homepage links to 81 pages on homeserve.co.uk and 9 external pages.

8 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “HomeServe offers expert Home Emergency Cover you can count on for your plumbing, heating and electrics. Find out more a…”.

  • One H1 headline

    Your main headline reads: “Home emergency cover you can count on”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “Home Emergency Cover | HomeServe”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

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

AI search readiness

100
  • No llms.txt

    There is no https://www.homeserve.co.uk/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

3 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: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

4 to fix68
  • 2 pages without a title

    https://www.homeserve.co.uk/uk/loggedin/claims-proxy and https://www.homeserve.co.uk/uk/loggedin/my-homeserve have no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.homeserve.co.uk/insurance-cover/homeserve-premium-cover is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://www.homeserve.co.uk/uk/loggedin/claims-proxy, https://www.homeserve.co.uk/uk/loggedin/my-homeserve and https://www.homeserve.co.uk/insurance-cover have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.homeserve.co.uk/uk/loggedin/claims-proxy and https://www.homeserve.co.uk/uk/loggedin/my-homeserve have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

Best practices

2 to fixGoogle 10078
  • 1 broken image

    1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=836d3eaf-464b-469e-9952-bc03e5ec0ebb&referrer=&landingpage=https%3A%2F%2Fwww.homeserve.co.uk%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 503 ()”.

2 checks passed
  • Tap targets are thumb-sized

    13 of 13 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • 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.

  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No opening hours

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

  • 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 471 words of copy

    The homepage carries about 471 words of visible text.

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us”, “Log in/register” and “Learn more about BOXT”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 4 cookies set on arrival

    4

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

  • 18 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 homeserve.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Gatsby
Analytics
Google Tag Manager
Hosting
Fastly

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on homeserve.co.uk, including 14 speed issues, 1 SEO issue and 5 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