Website review, no card needed
hozelock.com website review
Visit site (opens in a new tab)Reviewed 30 October 202630 issues · 78 checks
This review found 30 issues worth fixing on hozelock.com, 7 of them high impact, across 78 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81B- #40,502 of 120,585 reviewed websitesbeats 61%
- #26,980 of 68,274 online storesbeats 54%
- #525 of 2,791 WooCommerce storesbeats 77%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 723 ms |
| May 16, 2026 | 736 ms |
| May 23, 2026 | 772 ms |
| May 30, 2026 | 787 ms |
| Jun 6, 2026 | 800 ms |
| Jun 13, 2026 | 820 ms |
| Jun 20, 2026 | 825 ms |
| Jun 27, 2026 | 833 ms |
| Jul 4, 2026 | 809 ms |
| Jul 11, 2026 | 794 ms |
| Jul 18, 2026 | 775 ms |
| Jul 25, 2026 | 775 ms |
| Aug 1, 2026 | 780 ms |
| Aug 8, 2026 | 734 ms |
| Aug 15, 2026 | 762 ms |
| Aug 22, 2026 | 784 ms |
| Aug 29, 2026 | 774 ms |
| Sep 5, 2026 | 839 ms |
| Sep 12, 2026 | 914 ms |
| Sep 19, 2026 | 940 ms |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 980 ms |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 72 ms |
| May 16, 2026 | 73 ms |
| May 23, 2026 | 73 ms |
| May 30, 2026 | 74 ms |
| Jun 6, 2026 | 74 ms |
| Jun 13, 2026 | 73 ms |
| Jun 20, 2026 | 75 ms |
| Jun 27, 2026 | 76 ms |
| Jul 4, 2026 | 76 ms |
| Jul 11, 2026 | 81 ms |
| Jul 18, 2026 | 80 ms |
| Jul 25, 2026 | 81 ms |
| Aug 1, 2026 | 81 ms |
| Aug 8, 2026 | 77 ms |
| Aug 15, 2026 | 77 ms |
| Aug 22, 2026 | 77 ms |
| Aug 29, 2026 | 77 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 82 ms |
| Sep 19, 2026 | 81 ms |
| Sep 26, 2026 | 83 ms |
| Oct 3, 2026 | 81 ms |
| Oct 10, 2026 | 78 ms |
| Oct 17, 2026 | 79 ms |
| Oct 24, 2026 | 78 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
1.9 MB12 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 146 KiBAbout 146 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
450 ms · 84 KiBAbout 84 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Facebook, Google Tag Manager and Cloudflare and others), adding 403 KiB and 433 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 192 KiB3 files are served with short cache lifetimes, so returning visitors download them again (192 KiB).
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 177 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 441 ms of it running JavaScript. That is comfortably low.
Server response: 66 ms
66 msYour server sent the HTML in 66 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user TTFB: 2.8 s
2.8 sReal visitors wait 2.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 6.2 s
6.2 sYour largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “WebBanner1140x487px Wellbeing GB”.
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 42% slower for real visitors
+42%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 0.7 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 6.2 s
6.2 sThe page becomes fully interactive after 6.2 s. Good is under 3.8 s.
Total Blocking Time: 366 ms
366 msScripts block taps and scrolling for 366 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 72 ms to 78 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 95 ms
95 msReal visitors wait 95 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.041
0.041The layout barely moves while loading (CLS 0.041, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Speed Index: 2.1 s
2.1 sVisually, the page fills in at 2.1 s (Speed Index), inside the 3.4 s “good” threshold.
Images and page weight
Page weight: 3.6 MB in 106 requests
3.6 MBYour homepage downloads 3.6 MB in 106 requests on a phone: images 3.0 MB (35), scripts 417 KiB (5) and stylesheets 200 KiB (59). Under 2 MB keeps phones on slow connections fast.
9 images in older formats
9 images (935 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.
1 image far larger than shown
319 KiB1 image is downloaded at several times the size a phone draws it, for example Wellbeing-Hub-1.png at 1,920 px wide, shown at 360 px. Resized copies would save about 319 KiB.
About 1.0 g of CO₂ per visit
1.03 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.03 g of CO₂e: 124.1 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
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
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.
28 links without text
28 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 73 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
138 internal links, 50 external
The homepage links to 138 pages on hozelock.com and 50 external pages.
6 checks passed
Meta description: 128 characters
Your meta description is 128 characters: “Hozelock combines a knowledge and passion for gardening, and pride in product craftsmanship. Created by gardeners for g…”.
Title: 61 characters
Your title is a healthy 61 characters: “Hozelock - Gardening, Watering, Pond Solutions | Hozelock Ltd”.
Canonical URL set
The canonical URL is https://www.hozelock.com/.
Structured data in place
Structured data found: Article, BreadcrumbList, ImageObject, Organization and Person.
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.hozelock.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.hozelock.com/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 (899 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.hozelock.com/hozelock-careers has no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.hozelock.com/product-category/watering/https-www-hozelock-com-product-category-watering-hose-storage, whose canonical is https://www.hozelock.com/product-category/watering/hose-storage. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
13 pages without an H1
https://www.hozelock.com/hozelock-careers, https://www.hozelock.com/contact-us, https://www.hozelock.com/product-category/watering/garden-hose, https://www.hozelock.com/product-category/watering/https-www-hozelock-com-product-category-watering-hose-storage, https://www.hozelock.com/product-category/watering/fittings-and-connectors and https://www.hozelock.com/product-category/watering/spray-guns and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.hozelock.com/hozelock-careers has 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.
1 page slow to respond
https://www.hozelock.com/hozelock-careers took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 72 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 15 pages that loaded have a <title>.
Best practices
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 38 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
About 299 words of copy
The homepage carries about 299 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: “BUY SPARE PARTS” and “LOGIN / REGISTER”.
11 calls to action
The homepage has 11 calls to action, for example “CONTACT US”, “Buy Natural Gardening” and “Natural Gardening Range - Buy Online”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics, Meta Pixel and Cloudflare Web Analytics.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
7 other companies contacted
Loading the homepage contacts 7 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 hozelock.com, 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
- E-commerce
- WooCommerce
- Analytics
- Google Analytics
- Hosting
- Cloudflare
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 hozelock.com, 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.