Website review, no card needed

purefreedom.co.uk logo

purefreedom.co.uk website review

Visit site (opens in a new tab)Reviewed 7 November 202621 issues · 83 checks

This review found 21 issues worth fixing on purefreedom.co.uk, 7 of them high impact, across 83 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
854 ms744 msMay 16Oct 31760 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026839 ms
May 23, 2026834 ms
May 30, 2026829 ms
Jun 6, 2026836 ms
Jun 13, 2026841 ms
Jun 20, 2026822 ms
Jun 27, 2026825 ms
Jul 4, 2026802 ms
Jul 11, 2026789 ms
Jul 18, 2026758 ms
Jul 25, 2026770 ms
Aug 1, 2026778 ms
Aug 8, 2026775 ms
Aug 15, 2026822 ms
Aug 22, 2026819 ms
Aug 29, 2026820 ms
Sep 5, 2026830 ms
Sep 12, 2026831 ms
Sep 19, 2026808 ms
Sep 26, 2026807 ms
Oct 3, 2026795 ms
Oct 10, 2026757 ms
Oct 17, 2026778 ms
Oct 24, 2026769 ms
Oct 31, 2026760 ms
Real-visitor tap response (INP)75th percentile, phones
91 ms78 msMay 16Oct 3180 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202679 ms
May 23, 202679 ms
May 30, 202683 ms
Jun 6, 202685 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202688 ms
Jul 4, 202687 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202688 ms
Aug 1, 202689 ms
Aug 8, 202688 ms
Aug 15, 202688 ms
Aug 22, 202687 ms
Aug 29, 202685 ms
Sep 5, 202683 ms
Sep 12, 202681 ms
Sep 19, 202679 ms
Sep 26, 202685 ms
Oct 3, 202686 ms
Oct 10, 202683 ms
Oct 17, 202682 ms
Oct 24, 202680 ms
Oct 31, 202680 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 purefreedom.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. purefreedom.co.uk at 0.5 s0.5 s
  2. purefreedom.co.uk at 1.0 s1.0 s
  3. purefreedom.co.uk at 1.4 s1.4 s
  4. purefreedom.co.uk at 1.9 s1.9 s
  5. purefreedom.co.uk at 2.4 s2.4 s
  6. purefreedom.co.uk at 2.9 s2.9 s
  7. purefreedom.co.uk at 3.4 s3.4 s
  8. purefreedom.co.uk at 3.9 s3.9 s

Speed

4 to fix64
  • Reduce unused JavaScript

    1.3 s · 229 KiB

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

  • Use efficient cache lifetimes

    850 ms · 172 KiB

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

  • Mobile performance score: 64

    64/100

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

  • 2,218 HTML elements

    The page has 2,218 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Duplicated JavaScript

    150 ms · 26 KiB

    26 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Klarna, Marker and Shopify and others), adding 467 KiB and 114 ms of main-thread time.

  • Improve image delivery

    160 KiB

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

  • Render-blocking requests

    150 ms

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

  • Reduce unused CSS

    60 ms · 22 KiB

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

  • 2 long tasks on the main thread

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

  • 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: 1.2 s

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

  • Server response: 14 ms

    14 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 10.5 s

    10.5 s

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

  • Time to Interactive: 10.6 s

    10.6 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

    0.8 s

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

  • Real-user INP: 80 ms

    80 ms

    Real visitors wait 80 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.5 s

    0.5 s

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

  • Real-user TTFB: 318 ms

    318 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 12 ms

    12 ms

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

Images and page weight

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

    2.3 MB

    Your homepage downloads 2.3 MB in 154 requests on a phone: other files 673 KiB (73), scripts 658 KiB (49) and images 597 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Nano-1-1_2.jpg 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).

  • 3 images in older formats

    3 images (233 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.

  • About 0.7 g of CO₂ per visit

    0.66 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.66 g of CO₂e: 79.6 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

5 to fixGoogle 10094
  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • 4 links without text

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

  • Headings should not be empty (4 elements)

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

  • Headings skip levels

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

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

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

2 checks passed
  • Every image has alt text

    All 49 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 4 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 10095
  • One H1 headline

    Your <h1> is empty.

  • 157 internal links, 0 external

    The homepage links to 157 pages on purefreedom.co.uk and 0 external pages.

7 checks passed
  • Meta description: 128 characters

    Your meta description is 128 characters: “Leading Supplier of Pure Water Window Cleaning Equipment that is built to last. Home of the Reelmaster & Nano Water Fed…”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Pure Freedom | Window Cleaning Systems & Equipment”.

  • Canonical URL set

    The canonical URL is https://purefreedom.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://purefreedom.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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://purefreedom.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 14 pages without a meta description

    https://purefreedom.co.uk/pages/system-builder, https://purefreedom.co.uk/collections/van-mounted-systems, https://purefreedom.co.uk/collections/all-hose-reels, https://purefreedom.co.uk/collections/all-trolleys, https://purefreedom.co.uk/collections/all-pumps-controllers and https://purefreedom.co.uk/collections/water-fed-poles and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://purefreedom.co.uk/collections/van-mounted-systems, https://purefreedom.co.uk/collections/all-hose-reels, https://purefreedom.co.uk/collections/all-trolleys, https://purefreedom.co.uk/collections/all-pumps-controllers, https://purefreedom.co.uk/collections/water-fed-poles and https://purefreedom.co.uk/collections/pole-hoses and 7 others 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 60 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    42 of 43 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.

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

    The homepage carries about 430 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BEST SELLING THE NANO TROLLEY SHOP NOW” and “SHOP NOW”.

  • 34 calls to action

    The homepage has 34 calls to action, for example “Sign in/ Register”, “Contact” and “BEST SELLING THE NANO TROLLEY SHOP NOW”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 67 testimonial or review blocks, a star rating and 2 trust badges.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads 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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 12 other companies contacted

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

Apps on your store

Your storefront loads 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

amazonaws.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on purefreedom.co.uk, including 8 speed issues, 1 SEO issue 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