Website review, no card needed
hedleyandbennett.com website review
Visit site (opens in a new tab)Reviewed 8 November 202633 issues · 82 checks
This review found 33 issues worth fixing on hedleyandbennett.com, 14 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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
76C- #75,753 of 124,980 reviewed websitesbeats 35%
- #48,417 of 70,081 online storesbeats 26%
- #45,843 of 63,691 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 130 ms |
| May 23, 2026 | 137 ms |
| May 30, 2026 | 141 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 148 ms |
| Jun 20, 2026 | 147 ms |
| Jun 27, 2026 | 147 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 147 ms |
| Jul 18, 2026 | 148 ms |
| Jul 25, 2026 | 153 ms |
| Aug 1, 2026 | 150 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 146 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 152 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 157 ms |
| Sep 26, 2026 | 157 ms |
| Oct 3, 2026 | 157 ms |
| Oct 10, 2026 | 155 ms |
| Oct 17, 2026 | 154 ms |
| Oct 24, 2026 | 155 ms |
| Oct 31, 2026 | 155 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.5 s
0.9 s
1.4 s
1.9 s
2.3 s
2.8 s
3.2 s
3.7 s
Speed
Reduce unused JavaScript
1.2 s · 224 KiBAbout 224 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
1.4 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,588 HTML elements
The page has 3,588 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
150 ms · 2.5 MB41 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, userway.org and cookiehub.eu and others), adding 4.6 MB and 947 ms of main-thread time.
Shopify adds 807 ms
807 msShopify costs a phone 807 ms of main-thread work and 4.1 MB 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 377 ms. During a long task the page ignores taps.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
150 ms · 29 KiBAbout 29 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Use efficient cache lifetimes
31 KiB9 files are served with short cache lifetimes, so returning visitors download them again (31 KiB).
Legacy JavaScript
22 KiBPolyfills for old browsers add 22 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.
1 checks passed
Server response: 55 ms
55 msYour server sent the HTML in 55 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.
Largest Contentful Paint: 16.1 s
16.1 sYour largest element takes 16.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Shop All Aprons”.
Time to Interactive: 16.7 s
16.7 sThe page becomes fully interactive after 16.7 s. Good is under 3.8 s.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Total Blocking Time: 853 ms
853 msScripts block taps and scrolling for 853 ms in total while the page loads. Good is under 200 ms.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 930 ms
930 msReal visitors wait 930 ms for your server to start answering (75th percentile). Good is under 800 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 130 ms to 155 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 2.8 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 179 ms
179 msReal visitors wait 179 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.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 5.0 MB in 149 requests
5.0 MBYour homepage downloads 5.0 MB in 149 requests on a phone: images 3.6 MB (77), scripts 636 KiB (41) and HTML 411 KiB (1). Under 2 MB keeps phones on slow connections fast.
13 images below the first screen load straight away
13 images further down the page (523 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (113 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 1.4 g of CO₂ per visit
1.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.41 g of CO₂e: 169.0 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
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (1 element).
Elements with role="none" or role="presentation" have conflicts
Elements with role="none" or role="presentation" have conflicts (1 element).
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 0 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (16 characters)
Your title is only 16 characters: “Hedley & Bennett”. 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 canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
212 internal links, 13 external
The homepage links to 212 pages on hedleyandbennett.com and 13 external pages.
4 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Used by the best chefs, home cooks and makers in the world. Shop our quality aprons, knives, hats and kitchen gear for …”.
One H1 headline
Your main headline reads: “Damn Good Aprons”.
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.hedleyandbennett.com/sitemap.xml.
AI search readiness
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.hedleyandbennett.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 (1,679 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages share a meta description
https://www.hedleyandbennett.com/collections/all, https://www.hedleyandbennett.com/collections/all-aprons, https://www.hedleyandbennett.com/collections/knives, https://www.hedleyandbennett.com/collections/cooking-tools, https://www.hedleyandbennett.com/collections/cookware and https://www.hedleyandbennett.com/collections/kitchen-linens and 6 others use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://www.hedleyandbennett.com/pages/collaborations, https://www.hedleyandbennett.com/pages/bundle-and-save and https://www.hedleyandbennett.com/pages/gift-guide have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages slow to respond
https://www.hedleyandbennett.com/collections/all, https://www.hedleyandbennett.com/collections/all-aprons, https://www.hedleyandbennett.com/collections/knives, https://www.hedleyandbennett.com/collections/cooking-tools, https://www.hedleyandbennett.com/products/cedar-blue-denim-crossback-apron and https://www.hedleyandbennett.com/products/paprika-red-chefs-towels took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 146 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
10 broken images
10 images failed to load on a phone, for example https://www.hedleyandbennett.com/.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
74 of 78 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.
About 1,162 words of copy
The homepage carries about 1,162 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 Aprons”.
18 calls to action
The homepage has 18 calls to action, for example “SHOP NOW”, “Shop Aprons” and “Shop Now”.
98 short forms
98 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 3 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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
14 other companies contacted
Loading the homepage contacts 14 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 hedleyandbennett.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Los Angeles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on hedleyandbennett.com, including 18 speed issues, 4 SEO issues and 1 conversion gap. 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.