Website review, no card needed

stearn.co.uk logo

stearn.co.uk website review

Visit site (opens in a new tab)Reviewed 24 October 202635 issues · 81 checks

This review found 35 issues worth fixing on stearn.co.uk, 15 of them high impact, across 81 checks. The most urgent: improve image delivery. 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
883 ms655 msMay 2Oct 17746 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026845 ms
May 9, 2026735 ms
May 16, 2026724 ms
May 23, 2026730 ms
May 30, 2026708 ms
Jun 6, 2026714 ms
Jun 13, 2026697 ms
Jun 20, 2026713 ms
Jun 27, 2026735 ms
Jul 4, 2026722 ms
Jul 11, 2026747 ms
Jul 18, 2026720 ms
Jul 25, 2026703 ms
Aug 1, 2026705 ms
Aug 8, 2026681 ms
Aug 15, 2026731 ms
Aug 22, 2026817 ms
Aug 29, 2026839 ms
Sep 5, 2026793 ms
Sep 12, 2026857 ms
Sep 19, 2026804 ms
Sep 26, 2026760 ms
Oct 3, 2026748 ms
Oct 10, 2026714 ms
Oct 17, 2026746 ms
Real-visitor tap response (INP)75th percentile, phones
126 ms82 msMay 2Oct 17102 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026121 ms
May 9, 2026121 ms
May 16, 2026105 ms
May 23, 2026111 ms
May 30, 2026112 ms
Jun 6, 2026108 ms
Jun 13, 2026111 ms
Jun 20, 2026106 ms
Jun 27, 2026105 ms
Jul 4, 2026104 ms
Jul 11, 2026104 ms
Jul 18, 2026102 ms
Jul 25, 202695 ms
Aug 1, 202695 ms
Aug 8, 202687 ms
Aug 15, 202694 ms
Aug 22, 2026116 ms
Aug 29, 2026120 ms
Sep 5, 2026120 ms
Sep 12, 2026109 ms
Sep 19, 2026109 ms
Sep 26, 202694 ms
Oct 3, 202698 ms
Oct 10, 2026102 ms
Oct 17, 2026102 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 stearn.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix35
  • Improve image delivery

    2.2 s · 1.3 MB

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

  • Reduce unused JavaScript

    2.9 s · 529 KiB

    About 529 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 35

    35/100

    Your mobile performance score is 35 (desktop: 87). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Use efficient cache lifetimes

    750 ms · 1.2 MB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Civic and Google Fonts and others), adding 858 KiB and 756 ms of main-thread time.

  • Google Tag Manager adds 625 ms

    625 ms

    Google Tag Manager costs a phone 625 ms of main-thread work and 711 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 CSS

    300 ms · 44 KiB

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

  • Legacy JavaScript

    250 ms · 36 KiB

    Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • 9 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 87 but mobile only 35. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 98 ms

    98 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 14.1 s

    14.1 s

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

  • Cumulative Layout Shift: 0.666

    0.666

    The layout shifts by 0.666 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 14.4 s

    14.4 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Total Blocking Time: 458 ms

    458 ms

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

  • Speed Index: 4.3 s

    4.3 s

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

7 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.2 s

    1.2 s

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

  • Real-user INP: 104 ms

    104 ms

    Real visitors wait 104 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: 0.7 s

    0.7 s

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

  • Real-user TTFB: 328 ms

    328 ms

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

  • Tap response (INP) got 16% faster for real visitors

    -16%

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

Images and page weight

4 to fix25
  • Page weight: 13.1 MB in 43 requests

    13.1 MB

    Your homepage downloads 13.1 MB in 43 requests on a phone: images 12.0 MB (28), scripts 1,007 KiB (8) and stylesheets 49 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 13 images far larger than shown

    10.1 MB

    13 images are downloaded at several times the size a phone draws them, for example 17646-STEARNHEATINGGUIDEWEBSITEIMAGE.jpeg at 7,500 px wide, shown at 350 px. Resized copies would save about 10.1 MB.

  • 7 images over 500 KB

    7 images weigh 9.6 MB together. On a phone connection a single image that size takes seconds.

  • 15 images in older formats

    15 images (11.6 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.

  • About 3.7 g of CO₂ per visit

    3.71 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.71 g of CO₂e: 445.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 load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

3 to fixGoogle 9396
  • 10 tap targets too small

    10 tap targets are too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 7 links without text

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

2 checks passed
  • Every image has alt text

    All 29 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

5 to fixGoogle 9266
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (6 characters)

    Your title is only 6 characters: “Stearn”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 33 internal links, 6 external

    The homepage links to 33 pages on stearn.co.uk and 6 external pages.

3 checks passed
  • Canonical URL set

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

  • 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.stearn.co.uk/wp-sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.stearn.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.

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 12 pages without a meta description

    https://www.stearn.co.uk/about-stearn-electric, https://www.stearn.co.uk/catalogues, https://www.stearn.co.uk/web-guide, https://www.stearn.co.uk/enquiries, https://www.stearn.co.uk/contact-us and https://www.stearn.co.uk/catalogue/airvent and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages with very little text

    https://www.stearn.co.uk/catalogues, https://www.stearn.co.uk/web-guide, https://www.stearn.co.uk/catalogue/airvent, https://www.stearn.co.uk/catalogue/sunhouse, https://www.stearn.co.uk/catalogue/the-fires-guide and https://www.stearn.co.uk/catalogue/heating-guide and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 12 internal pages checked

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

6 checks passed
  • Linked pages load

    All 12 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 8 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 330 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

  • 5 other companies contacted

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

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

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on stearn.co.uk, including 14 speed issues, 5 SEO issues 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