Website review, no card needed
harrisonssauces.com website review
Visit site (opens in a new tab)Reviewed 17 November 202635 issues · 92 checks
This review found 35 issues worth fixing on harrisonssauces.com, 12 of them high impact, across 92 checks. The most urgent: render-blocking requests. 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
78C- #59,454 of 117,548 reviewed websitesbeats 44%
- #39,125 of 66,918 online storesbeats 36%
- #37,412 of 61,016 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
| Nov 7, 2026 | 2.1 s |
| Nov 14, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 119 ms |
| Jun 6, 2026 | 122 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 131 ms |
| Jun 27, 2026 | 138 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 139 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 137 ms |
| Aug 1, 2026 | 133 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 135 ms |
| Aug 22, 2026 | 141 ms |
| Aug 29, 2026 | 148 ms |
| Sep 5, 2026 | 151 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 150 ms |
| Sep 26, 2026 | 146 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 145 ms |
| Oct 17, 2026 | 146 ms |
| Oct 24, 2026 | 153 ms |
| Oct 31, 2026 | 153 ms |
| Nov 7, 2026 | 152 ms |
| Nov 14, 2026 | 142 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
1.0 s
1.6 s
2.1 s
2.6 s
3.1 s
3.6 s
4.1 s
Speed
Render-blocking requests
4.6 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.6 s.
Reduce unused JavaScript
3.2 s · 618 KiBAbout 618 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.2 s faster on a phone.
Improve image delivery
150 ms · 3.2 MB7 images could be 3.2 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.
Mobile performance score: 54
54/100Your mobile performance score is 54. 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 (Google Tag Manager, trengo.eu and Clarity and others), adding 1.3 MB and 761 ms of main-thread time.
Use efficient cache lifetimes
400 ms · 215 KiB21 files are served with short cache lifetimes, so returning visitors download them again (215 KiB).
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
300 ms · 83 KiBAbout 83 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.
trengo.eu adds 161 ms
161 mstrengo.eu costs a phone 161 ms of main-thread work and 415 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.
Google Tag Manager adds 168 ms
168 msGoogle Tag Manager costs a phone 168 ms of main-thread work and 315 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.
Klaviyo adds 105 ms
105 msKlaviyo costs a phone 105 ms of main-thread work and 329 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.
Duplicated JavaScript
250 ms · 8 KiB8 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 250 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 136 ms. During a long task the page ignores taps.
Legacy JavaScript
100 ms · 35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
22 KiB22 KiB could be saved by minifying CSS.
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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.9 s
16.9 sYour largest element takes 16.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “OUR FLAVOURS”.
Time to Interactive: 24.5 s
24.5 sThe page becomes fully interactive after 24.5 s. Good is under 3.8 s.
First Contentful Paint: 7.0 s
7.0 sThe first text or image appears after 7.0 s on a phone. Good is under 1.8 s.
Speed Index: 10.0 s
10.0 sVisually, the page fills in at 10.0 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 119 ms to 142 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.1 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: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 142 ms
142 msReal visitors wait 142 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 420 ms
420 msReal visitors wait 420 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 160 ms
160 msScripts block the page for only 160 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.7 MB in 321 requests
6.7 MBYour homepage downloads 6.7 MB in 321 requests on a phone: images 3.7 MB (58), scripts 1.9 MB (105) and other files 812 KiB (139). Under 2 MB keeps phones on slow connections fast.
About 1.9 g of CO₂ per visit
1.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.89 g of CO₂e: 226.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (27 elements)
All page content should be contained by landmarks: 27 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3, h3 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (172 characters)
Your meta description is 172 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (Organization, WebSite and WholesaleStore) but with 2 problems, for example “Organization: missing name”.
166 internal links, 12 external
The homepage links to 166 pages on harrisonssauces.com and 12 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Harrisons Sauces”.
Title: 63 characters
Your title is a healthy 63 characters: “Harrisons Sauces | Wholesale Sauce Suppliers UK & International”.
Canonical URL set
The canonical URL is https://harrisonssauces.com/.
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://harrisonssauces.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing name, 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://harrisonssauces.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 (647 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 71 found) and read each the way a search engine does.
7 checks passed
Linked pages load
3 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.
Every page has a meta description
All 3 pages that loaded have a meta description.
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 3 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343165548&tm=shpfy_ui&Ver=2&mid=92e31158-e59d-4cf1-bd93-778e1bb1fb64&bo=1&sid=0d41cd80e22411f18aa1afe49174e7b1&vid=0d41ff00e22411f1ad1b97db7881a407&vids=0&msclkid=N&pi.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “LazyLoad is not defined”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
18 of 18 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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.
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 318 words of copy
The homepage carries about 318 words of visible text.
5 checks passed
13 calls to action
The homepage has 13 calls to action, for example “Shop by Flavour”, “Shop by Size” and “Shop by Category”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 3 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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.
21 cookies set on arrival
21Opening the homepage sets 21 cookies, 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.
43 other companies contacted
Loading the homepage contacts 43 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 harrisonssauces.com, 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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Keepcart Coupon Protect · Xo Insert Code · Restockrocket · snapchat.com · elfsight.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
Stack
- Framework
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on harrisonssauces.com, including 17 speed issues, 2 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.