Website review, no card needed

snusmart.co.uk logo

snusmart.co.uk website review

Visit site (opens in a new tab)Reviewed 9 November 202642 issues · 83 checks

This review found 42 issues worth fixing on snusmart.co.uk, 15 of them high impact, across 83 checks. The most urgent: main-thread work: 18.2 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of snusmart.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. snusmart.co.uk at 0.8 s0.8 s
  2. snusmart.co.uk at 1.5 s1.5 s
  3. snusmart.co.uk at 2.3 s2.3 s
  4. snusmart.co.uk at 3.0 s3.0 s
  5. snusmart.co.uk at 3.8 s3.8 s
  6. snusmart.co.uk at 4.5 s4.5 s
  7. snusmart.co.uk at 5.3 s5.3 s
  8. snusmart.co.uk at 6.0 s6.0 s

Speed

12 to fix50
  • Main-thread work: 18.2 s

    A phone's processor spends 18.2 s on main-thread work while loading, 8.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Render-blocking requests

    1.3 s

    20 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.

  • 8,453 HTML elements

    The page has 8,453 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, snusmart.com and Clarity and others), adding 1.4 MB and 1.9 s of main-thread time.

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

  • Shopify adds 445 ms

    445 ms

    Shopify costs a phone 445 ms of main-thread work and 390 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.

  • snusmart.com adds 395 ms

    395 ms

    snusmart.com costs a phone 395 ms of main-thread work and 317 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 384 ms

    384 ms

    Clarity costs a phone 384 ms of main-thread work and 30 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.

  • Use efficient cache lifetimes

    378 KiB

    14 files are served with short cache lifetimes, so returning visitors download them again (378 KiB).

  • Cloudflare CDN adds 337 ms

    337 ms

    Cloudflare CDN costs a phone 337 ms of main-thread work and 85 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.

  • Reduce unused JavaScript

    337 KiB

    About 337 KiB of JavaScript is downloaded but never used on this page.

  • azurefd.net adds 119 ms

    119 ms

    azurefd.net costs a phone 119 ms of main-thread work and 321 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.

  • Reduce unused CSS

    150 ms · 48 KiB

    About 48 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.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 196 ms. During a long task the page ignores taps.

  • Minify JavaScript

    150 ms · 2 KiB

    2 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

  • Improve image delivery

    12 KiB

    2 images could be 12 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

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 22 ms

    22 ms

    Your server sent the HTML in 22 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix51
  • Time to Interactive: 16.8 s

    16.8 s

    The page becomes fully interactive after 16.8 s. Good is under 3.8 s.

  • Largest Contentful Paint: 7.1 s

    7.1 s

    Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “VELO FREEZING PEPPERMINT”.

  • First Contentful Paint: 3.1 s

    3.1 s

    The first text or image appears after 3.1 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 623 ms

    623 ms

    Scripts block taps and scrolling for 623 ms in total while the page loads. Good is under 200 ms.

  • Speed Index: 5.8 s

    5.8 s

    Visually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.

  • 13 images without width and height

    13 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.016

    0.016

    The layout barely moves while loading (CLS 0.016, good is under 0.1).

Images and page weight

3 to fix60
  • Page weight: 4.3 MB in 480 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 480 requests on a phone: other files 1.6 MB (276), scripts 1.3 MB (103) and images 1.0 MB (63). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Bezzer_21.png 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).

  • 2 images far larger than shown

    104 KiB

    2 images are downloaded at several times the size a phone draws them, for example Clew_2dfc223c-33ae-4ac0-b92d-581a32a23381.png at 2,098 px wide, shown at 120 px. Resized copies would save about 104 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 1.2 g of CO₂ per visit

    1.22 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.22 g of CO₂e: 147.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 use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 8389
  • ARIA attributes must conform to valid values (8 elements)

    ARIA attributes must conform to valid values: 8 elements on the page fail this check, rated critical by axe-core.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • Interactive controls must not be nested (8 elements)

    Interactive controls must not be nested: 8 elements on the page fail this check, rated serious by axe-core.

  • 7 text elements with low contrast

    7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 35 images without alt text

    35 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (7 elements)

    All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.

  • 74 form fields without a label

    74 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 49 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: 49 passed and 7 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8571
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (8 characters)

    Your title is only 8 characters: “SnusMart”. 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 social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 306 internal links, 8 external

    The homepage links to 306 pages on snusmart.co.uk and 8 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.snusmart.co.uk/.

  • 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.snusmart.co.uk/sitemap.xml.

AI search readiness

1 to fix88
  • 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 (3,489 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.snusmart.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 12 pages without a meta description

    https://www.snusmart.co.uk/collections/all, https://www.snusmart.co.uk/policies/shipping-policy, https://www.snusmart.co.uk/collections/velo, https://www.snusmart.co.uk/collections/clew, https://www.snusmart.co.uk/collections/bezzer and https://www.snusmart.co.uk/collections/camo and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.snusmart.co.uk/collections/all, https://www.snusmart.co.uk/policies/shipping-policy, https://www.snusmart.co.uk/collections/velo, https://www.snusmart.co.uk/collections/clew, https://www.snusmart.co.uk/collections/bezzer and https://www.snusmart.co.uk/collections/snowman and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 138 found) and read each the way a search engine does.

5 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.

  • 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

2 to fixGoogle 9687
  • 110 small tap targets

    110 of 215 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Shopify is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix85
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 2,055 words of copy

    The homepage carries about 2,055 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “CONTACT US”, “TRACK MY ORDER” and “Contact Us”.

  • 77 short forms

    77 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 9 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Opening hours shown

    Your opening hours are on the homepage.

  • 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 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Klaviyo 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.

  • 6 cookies set on arrival

    6

    Opening 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.

  • 28 other companies contacted

    Loading the homepage contacts 28 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 snusmart.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 19 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geo Pro Geolocation · Pandectes Gdpr · Sc Easy Redirects · Microsoft Clarity · Shopacado Discounts · Klaviyo Email Marketing Sms · Inbox · Na Side Cart · Helium Customer Fields · Hulk Age Verification · Triplewhale · C Hub Customer Accounts · Easylocation · Gdpr Cookie Consent · Custom Pricing Discounts By Appikon · Stape Remix · Fabrikator Inventory Assistant · trustpilot.com · socialsnowball.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
Analytics
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 42 issues on snusmart.co.uk, including 18 speed issues, 5 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25