Website review, no card needed
sweatguard.co.uk website review
Visit site (opens in a new tab)Reviewed 11 November 202638 issues · 85 checks
This review found 38 issues worth fixing on sweatguard.co.uk, 13 of them high impact, across 85 checks. The most urgent: main-thread work: 22.8 s. 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
77C- #69,889 of 126,210 reviewed websitesbeats 39%
- #44,893 of 70,393 online storesbeats 31%
- #42,656 of 63,915 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 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.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
| Nov 7, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 113 ms |
| May 30, 2026 | 113 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 126 ms |
| Jun 20, 2026 | 130 ms |
| Jun 27, 2026 | 137 ms |
| Jul 4, 2026 | 136 ms |
| Jul 11, 2026 | 135 ms |
| Jul 18, 2026 | 130 ms |
| Jul 25, 2026 | 128 ms |
| Aug 1, 2026 | 129 ms |
| Aug 8, 2026 | 133 ms |
| Aug 15, 2026 | 139 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 161 ms |
| Sep 12, 2026 | 163 ms |
| Sep 19, 2026 | 162 ms |
| Sep 26, 2026 | 156 ms |
| Oct 3, 2026 | 152 ms |
| Oct 10, 2026 | 152 ms |
| Oct 17, 2026 | 150 ms |
| Oct 24, 2026 | 143 ms |
| Oct 31, 2026 | 145 ms |
| Nov 7, 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
1.5 s
2.9 s
4.4 s
5.8 s
7.3 s
8.8 s
10.2 s
11.7 s
Speed
Main-thread work: 22.8 s
A phone's processor spends 22.8 s on main-thread work while loading, 10.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
1.1 s · 491 KiBAbout 491 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Klaviyo adds 1.1 s
1.1 sKlaviyo costs a phone 1.1 s of main-thread work and 314 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 35
35/100Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Shopify and JSDelivr CDN and others), adding 1.2 MB and 5.2 s of main-thread time.
Shopify adds 898 ms
898 msShopify costs a phone 898 ms of main-thread work and 268 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.
JSDelivr CDN adds 868 ms
868 msJSDelivr CDN costs a phone 868 ms of main-thread work and 40 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 776 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
550 ms · 149 KiB23 files are served with short cache lifetimes, so returning visitors download them again (149 KiB).
Reduce unused CSS
600 ms · 63 KiBAbout 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
rechargecdn.com adds 627 ms
627 msrechargecdn.com costs a phone 627 ms of main-thread work and 296 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.
Clarity adds 543 ms
543 msClarity costs a phone 543 ms of main-thread work and 29 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.
2,013 HTML elements
The page has 2,013 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
50 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Duplicated JavaScript
50 ms · 8 KiB8 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.
Improve image delivery
58 KiB1 image could be 58 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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 CSS
3 KiB3 KiB could be saved by minifying CSS.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 59 ms
59 msYour server sent the HTML in 59 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: 22.1 s
22.1 sYour largest element takes 22.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 7.9 s
7.9 sScripts block taps and scrolling for 7.9 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 22.2 s
22.2 sThe page becomes fully interactive after 22.2 s. Good is under 3.8 s.
Speed Index: 12.2 s
12.2 sVisually, the page fills in at 12.2 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 113 ms to 142 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 37% slower for real visitors
+37%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user INP: 172 ms
172 msReal visitors wait 172 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.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.2 MB in 293 requests
5.2 MBYour homepage downloads 5.2 MB in 293 requests on a phone: images 2.6 MB (53), scripts 1.5 MB (100) and other files 766 KiB (117). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Mobile_final.svg weighs 1.9 MB. On a phone connection a single image that size takes seconds.
An image on the first screen is lazy-loaded
Mobile_final.svg 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).
About 1.5 g of CO₂ per visit
1.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.47 g of CO₂e: 176.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 90 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Sweat Guard® | Hyperhidrosis & Sweat Control Experts – Sweat Guard”.
Meta description is long (167 characters)
Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
90 internal links, 11 external
The homepage links to 90 pages on sweatguard.co.uk and 11 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Sweat Guard”.
Canonical URL set
The canonical URL is https://sweatguard.co.uk/.
Structured data in place
Structured data found: ItemList.
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://sweatguard.co.uk/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.
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 (768 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://sweatguard.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.
7 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.
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 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught Error: Goaffpro is already loaded. This message prevents duplicate loading of the script. Kindly ignore.”.
2 checks passed
Tap targets are thumb-sized
62 of 66 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 10 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 334 words of copy
The homepage carries about 334 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: “SHOP NOW” and “SHOP ALL PRODUCTS”.
5 calls to action
The homepage has 5 calls to action, for example “Shop all”, “Sign up & get 10% off” and “Shop Now”.
17 short forms
17 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
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 Tag Manager, Klaviyo, Microsoft Ads and Microsoft Clarity (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
36 other companies contacted
Loading the homepage contacts 36 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 sweatguard.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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Instafeed · Klaviyo Email Marketing Sms · Join Stories · Gdpr Cookie Consent · Freegifts · trustpilot.com · chimpstatic.com · metorik.com · rechargecdn.com · goaffpro.com · gorgias.chat · bogos.io · 9gtb.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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on sweatguard.co.uk, including 23 speed issues, 3 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.