Website review, no card needed
snoozi.co.uk website review
Visit site (opens in a new tab)Reviewed 8 November 202629 issues · 66 checks
This review found 29 issues worth fixing on snoozi.co.uk, 15 of them high impact, across 66 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
72C- #97,660 of 126,317 reviewed websitesbeats 20%
- #59,745 of 70,430 online storesbeats 12%
- #55,562 of 63,936 Shopify storesbeats 11%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 155 ms |
| May 23, 2026 | 159 ms |
| May 30, 2026 | 155 ms |
| Jun 6, 2026 | 155 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 157 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 162 ms |
| Jul 18, 2026 | 156 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 149 ms |
| Aug 8, 2026 | 145 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 141 ms |
| Aug 29, 2026 | 137 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 137 ms |
| Sep 26, 2026 | 135 ms |
| Oct 3, 2026 | 137 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 137 ms |
| Oct 24, 2026 | 140 ms |
| Oct 31, 2026 | 133 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
Speed
Render-blocking requests
1.7 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Main-thread work: 5.2 s
A phone's processor spends 5.2 s on main-thread work while loading, 3.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (hcaptcha.com, Google Tag Manager and Shopify and others), adding 3.6 MB and 2.1 s of main-thread time.
Reduce unused JavaScript
480 ms · 966 KiBAbout 966 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 480 ms faster on a phone.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
600 ms · 366 KiB13 files are served with short cache lifetimes, so returning visitors download them again (366 KiB).
hcaptcha.com adds 702 ms
702 mshcaptcha.com costs a phone 702 ms of main-thread work and 1.2 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.
Google Tag Manager adds 388 ms
388 msGoogle Tag Manager costs a phone 388 ms of main-thread work and 540 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.
Shopify adds 272 ms
272 msShopify costs a phone 272 ms of main-thread work and 1.2 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.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 209 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 36 KiBAbout 36 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.
Minify JavaScript
150 ms · 26 KiB26 KiB could be saved by minifying JavaScript.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
63 KiBPolyfills for old browsers add 63 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.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 32.1 s
32.1 sThe page becomes fully interactive after 32.1 s. Good is under 3.8 s.
Speed Index: 11.2 s
11.2 sVisually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 801 ms
801 msScripts block taps and scrolling for 801 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
9 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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 122 ms
122 msReal visitors wait 122 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 393 ms
393 msReal visitors wait 393 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 155 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.025
0.025The layout barely moves while loading (CLS 0.025, good is under 0.1).
Images and page weight
Page weight: 5.3 MB in 520 requests
5.3 MBYour homepage downloads 5.3 MB in 520 requests on a phone: scripts 3.1 MB (204), other files 1.5 MB (291) and HTML 494 KiB (6). Under 2 MB keeps phones on slow connections fast.
About 1.5 g of CO₂ per visit
1.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.49 g of CO₂e: 179.0 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
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 1 image in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (6 characters)
Your title is only 6 characters: “Snoozi”. Between 30 and 65 characters leaves room to say what you do and for whom.
No XML sitemap
No XML sitemap at https://snoozi.com/sitemap.xml, so Google discovers your pages only by following links.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
3 checks passed
Canonical URL set
The canonical URL is https://snoozi.com/password.
Structured data in place
Structured data found: BreadcrumbList.
robots.txt in place
robots.txt is in place.
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://snoozi.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.
1 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.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17498529&tm=gtm002&Ver=2&mid=f39125bf-5dcf-4e9e-adae-dc6352f9a2ac&bo=3&sid=37451fc0db1611f195962ba6e7f600dd&vid=37455360db1611f197b01b96c2c6e8ba&vids=1&msclkid=N>m_t.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.
1 checks passed
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Only about 46 words
The homepage has only about 46 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
2 checks passed
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
29 cookies set on arrival
29Opening the homepage sets 29 cookies, 1 of them by other companies (measured from a US location before any click).
38 other companies contacted
Loading the homepage contacts 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 snoozi.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Mable · Zoorix Sticky Atc · Seo Manager Venntov · Langshop · Cartbot · Klaviyo Email Marketing Sms · Analyzify Ga4 Ads Tracking · Forms · Countdown Timer · fera.ai · hyj.mobi
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
- E-commerce
- Shopify
- Analytics
- Google 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 29 issues on snoozi.co.uk, including 14 speed issues, 5 SEO issues and 4 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.