Website review, no card needed
hardhatwatches.uk website review
Visit site (opens in a new tab)Reviewed 7 November 202637 issues · 89 checks
This review found 37 issues worth fixing on hardhatwatches.uk, 8 of them high impact, across 89 checks. The most urgent: 4 text elements with low contrast. 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
88B- #6,017 of 126,192 reviewed websitesbeats 93%
- #3,200 of 70,389 online storesbeats 93%
- #3,099 of 63,913 Shopify storesbeats 93%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 134 ms |
| May 23, 2026 | 133 ms |
| May 30, 2026 | 132 ms |
| Jun 6, 2026 | 132 ms |
| Jun 13, 2026 | 134 ms |
| Jun 20, 2026 | 136 ms |
| Jun 27, 2026 | 137 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 137 ms |
| Jul 18, 2026 | 136 ms |
| Jul 25, 2026 | 135 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 137 ms |
| Aug 29, 2026 | 137 ms |
| Sep 5, 2026 | 141 ms |
| Sep 12, 2026 | 143 ms |
| Sep 19, 2026 | 145 ms |
| Sep 26, 2026 | 152 ms |
| Oct 3, 2026 | 154 ms |
| Oct 10, 2026 | 154 ms |
| Oct 17, 2026 | 155 ms |
| Oct 24, 2026 | 147 ms |
| Oct 31, 2026 | 152 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
Mobile performance score: 85
85/100Your mobile performance score is 85. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
600 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
2,050 HTML elements
The page has 2,050 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 0 ms
0 msShopify costs a phone 0 ms of main-thread work and 402 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.
3 third-party services on the page
3 third-party services load with your homepage (Shopify, Klaviyo and hardhatwatches.com.au), adding 410 KiB and 0 ms of main-thread time.
Reduce unused CSS
25 KiBAbout 25 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
12 KiB2 images could be 12 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
7 KiB2 files are served with short cache lifetimes, so returning visitors download them again (7 KiB).
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: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 39 ms of it running JavaScript. That is comfortably low.
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.3 s
4.3 sYour largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 4.3 s
4.3 sThe page becomes fully interactive after 4.3 s. Good is under 3.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 134 ms to 152 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 143 ms
143 msReal visitors wait 143 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.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 392 ms
392 msReal visitors wait 392 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.0 s
3.0 sVisually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
1 image over 500 KB
Black_Friday_-_Homepage-layout_-no-text.webp weighs 508 KiB. On a phone connection a single image that size takes seconds.
An image on the first screen is lazy-loaded
bf-sale-60-off.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).
6 images in older formats
6 images (945 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
5 KiB1 image is downloaded at several times the size a phone draws it, for example checkout-visa.webp at 940 px wide, shown at 300 px. Resized copies would save about 5 KiB.
1 image below the first screen load straight away
1 image further down the page (57 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.2 g of CO₂ per visit
0.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.24 g of CO₂e: 28.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 859 KiB in 47 requests
859 KiBYour homepage downloads 859 KiB in 47 requests on a phone: images 532 KiB (18), scripts 199 KiB (20) and HTML 85 KiB (1). That is a lean page.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
31 images without alt text
31 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
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.
Headings skip levels
Headings skip levels (h1 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 11 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 H1 headlines
There are 4 <h1> headlines (“The Best Tough Smart Watches in the UK”, “” and “Don't take our word for it, see what our customer…”). One clear main headline is easier for people and search engines.
Meta description is long (164 characters)
Your meta description is 164 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
128 internal links, 11 external
The homepage links to 128 pages on hardhatwatches.uk and 11 external pages.
5 checks passed
Title: 31 characters
Your title is a healthy 31 characters: “Buy The Toughest UK Smart Watch”.
Canonical URL set
The canonical URL is https://hardhatwatches.uk/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://hardhatwatches.uk/sitemap.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (3,972 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://hardhatwatches.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://hardhatwatches.uk/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://hardhatwatches.uk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://hardhatwatches.uk/products/hard-hat-big-rig and https://hardhatwatches.uk/products/hard-hat-foreman all use the title “Builder's Watch: Hard Hat Foreman – Built for Builders & Construction…”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://hardhatwatches.uk/collections/smartwatches, https://hardhatwatches.uk/collections/accessories, https://hardhatwatches.uk/customer_authentication/redirect, https://hardhatwatches.uk/collections/limited-edition-bundles and https://hardhatwatches.uk/pages/faq have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://hardhatwatches.uk/products/hard-hat-big-rig and https://hardhatwatches.uk/products/hard-hat-foreman use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://hardhatwatches.uk/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://hardhatwatches.uk/products/hard-hat-sport took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.
2 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.
Best practices
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
4 small tap targets
4 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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
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 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.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 735 words of copy
The homepage carries about 735 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now” and “SHOP NOW”.
5 calls to action
The homepage has 5 calls to action, for example “Apply discount code”, “Shop Now” and “Shop accessories”.
3 short forms
3 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 411 testimonial or review blocks, 40 customer or partner logos, a star rating and “Over 100,000+ Happy Customers”.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
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
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Klaviyo (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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
3 other companies contacted
Loading the homepage contacts 3 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 hardhatwatches.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pagefly Ai Page Builder · Kaching Bundles · Simprosys Google Shopping Feed · Klaviyo Email Marketing Sms · Countdown Timer · Zipify Oneclickupsell · loox.io
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
Stack
- Framework
- jQuery
- 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 37 issues on hardhatwatches.uk, including 7 speed issues, 3 SEO issues and 3 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.