Website review, no card needed

lancsfirerescue.org.uk logo

lancsfirerescue.org.uk website review

Visit site (opens in a new tab)Reviewed 2 November 202625 issues · 85 checks

This review found 25 issues worth fixing on lancsfirerescue.org.uk, 6 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. 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
967 ms680 msMay 16Oct 31766 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026720 ms
May 23, 2026713 ms
May 30, 2026839 ms
Jun 6, 2026861 ms
Jun 13, 2026915 ms
Jun 20, 2026932 ms
Jun 27, 2026913 ms
Jul 4, 2026934 ms
Jul 11, 2026879 ms
Jul 18, 2026895 ms
Jul 25, 2026853 ms
Aug 1, 2026847 ms
Aug 8, 2026845 ms
Aug 15, 2026791 ms
Aug 22, 2026809 ms
Aug 29, 2026805 ms
Sep 5, 2026820 ms
Sep 12, 2026856 ms
Sep 19, 2026823 ms
Sep 26, 2026815 ms
Oct 3, 2026779 ms
Oct 10, 2026764 ms
Oct 17, 2026785 ms
Oct 24, 2026767 ms
Oct 31, 2026766 ms
Real-visitor tap response (INP)75th percentile, phones
96 ms87 msMay 16Oct 3188 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202689 ms
May 23, 202688 ms
May 30, 202694 ms
Jun 6, 202694 ms
Jun 13, 202695 ms
Jun 20, 202695 ms
Jun 27, 202693 ms
Jul 4, 202695 ms
Jul 11, 202694 ms
Jul 18, 202695 ms
Jul 25, 202694 ms
Aug 1, 202694 ms
Aug 8, 202694 ms
Aug 15, 202691 ms
Aug 22, 202690 ms
Aug 29, 202691 ms
Sep 5, 202692 ms
Sep 12, 202693 ms
Sep 19, 202693 ms
Sep 26, 202693 ms
Oct 3, 202692 ms
Oct 10, 202691 ms
Oct 17, 202691 ms
Oct 24, 202689 ms
Oct 31, 202688 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 lancsfirerescue.org.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lancsfirerescue.org.uk at 0.5 s0.5 s
  2. lancsfirerescue.org.uk at 1.0 s1.0 s
  3. lancsfirerescue.org.uk at 1.6 s1.6 s
  4. lancsfirerescue.org.uk at 2.1 s2.1 s
  5. lancsfirerescue.org.uk at 2.6 s2.6 s
  6. lancsfirerescue.org.uk at 3.1 s3.1 s
  7. lancsfirerescue.org.uk at 3.6 s3.6 s
  8. lancsfirerescue.org.uk at 4.1 s4.1 s

Speed

8 to fix55
  • Reduce unused JavaScript

    4.0 s · 785 KiB

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

  • Mobile performance score: 55

    55/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and jQuery CDN and others), adding 1.7 MB and 719 ms of main-thread time.

  • Minify JavaScript

    600 ms · 107 KiB

    107 KiB could be saved by minifying JavaScript.

  • YouTube adds 389 ms

    389 ms

    YouTube costs a phone 389 ms of main-thread work and 1,013 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 · 126 KiB

    About 126 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.

  • Render-blocking requests

    300 ms

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

  • Google Tag Manager adds 199 ms

    199 ms

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

  • Improve image delivery

    165 KiB

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

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    26 KiB

    Polyfills for old browsers add 26 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.

  • Use efficient cache lifetimes

    1 KiB

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

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

4 to fix100
  • First Contentful Paint: 8.6 s

    8.6 s

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

  • Largest Contentful Paint: 13.8 s

    13.8 s

    Your largest element takes 13.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Lancashire Fire & Rescue Logo”.

  • Time to Interactive: 14.4 s

    14.4 s

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

  • Speed Index: 8.6 s

    8.6 s

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    +7%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.8 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: 0.7 s

    0.7 s

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

  • Real-user INP: 100 ms

    100 ms

    Real visitors wait 100 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.6 s

    0.6 s

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

  • Total Blocking Time: 139 ms

    139 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 2.3 MB in 55 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 55 requests on a phone: scripts 1.5 MB (20), images 528 KiB (17) and HTML 92 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    incidents-bg.80c34bc7.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.6 g of CO₂ per visit

    0.64 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9695
  • 2 tap targets too small

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

  • 3 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor 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. (1 element).

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://www.lancsfirerescue.org.uk/ogimage.jpg")”.

  • 15 links with vague text

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

  • No X (Twitter) card tag

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

  • 135 internal links, 21 external

    The homepage links to 135 pages on lancsfirerescue.org.uk and 21 external pages.

7 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Lancashire Fire and Rescue Service is dedicated to making Lancashire safer. Visit our website for fire safety advice an…”.

  • One H1 headline

    Your main headline reads: “Know your fire safety”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Official Website of LFRS | Lancashire Fire and Rescue Service”.

  • Canonical URL set

    The canonical URL is https://www.lancsfirerescue.org.uk/.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.lancsfirerescue.org.uk/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.lancsfirerescue.org.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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 7 pages without a meta description

    https://www.lancsfirerescue.org.uk/news-and-events, https://www.lancsfirerescue.org.uk/contact/fire-report-request, https://www.lancsfirerescue.org.uk/safety, https://www.lancsfirerescue.org.uk/safety/road-safety, https://www.lancsfirerescue.org.uk/safety/business-safety and https://www.lancsfirerescue.org.uk/safety/be-prepared and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7797
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

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

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • 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.

  • Thin social proof

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

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

    The homepage carries about 805 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request a home fire safety check” and “Get in Touch”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Contact”, “Get in touch” and “Fire report request”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie, 1 of them by other companies (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.

  • 19 other companies contacted

    Loading the homepage contacts 19 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 lancsfirerescue.org.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
jQuery
Analytics
Google Tag Manager
Hosting
AWS

Hiring

Hiring
1 open role
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on lancsfirerescue.org.uk, including 12 speed issues, 2 SEO issues and 2 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