Website review, no card needed

kindsnacks.co.uk logo

kindsnacks.co.uk website review

Visit site (opens in a new tab)Reviewed 6 November 202637 issues · 81 checks

This review found 37 issues worth fixing on kindsnacks.co.uk, 15 of them high impact, across 81 checks. The most urgent: page weight: 52.0 MB in 44 requests. 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

Real-visitor load time (LCP)75th percentile, phones
1.3 s905 msMay 16Oct 311.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 2026951 ms
May 23, 2026982 ms
May 30, 20261.0 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.3 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.3 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
115 ms92 msMay 16Oct 31103 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026100 ms
May 23, 202697 ms
May 30, 202698 ms
Jun 6, 2026104 ms
Jun 13, 2026102 ms
Jun 20, 2026106 ms
Jun 27, 2026112 ms
Jul 4, 2026105 ms
Jul 11, 2026107 ms
Jul 18, 2026108 ms
Jul 25, 2026100 ms
Aug 1, 202699 ms
Aug 8, 202697 ms
Aug 15, 202696 ms
Aug 22, 202695 ms
Aug 29, 2026103 ms
Sep 5, 2026105 ms
Sep 12, 2026103 ms
Sep 19, 2026106 ms
Sep 26, 2026100 ms
Oct 3, 202696 ms
Oct 10, 202696 ms
Oct 17, 202696 ms
Oct 24, 2026103 ms
Oct 31, 2026103 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

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

How it loaded on a phone

  1. kindsnacks.co.uk at 0.4 s0.4 s
  2. kindsnacks.co.uk at 0.8 s0.8 s
  3. kindsnacks.co.uk at 1.1 s1.1 s
  4. kindsnacks.co.uk at 1.5 s1.5 s
  5. kindsnacks.co.uk at 1.9 s1.9 s
  6. kindsnacks.co.uk at 2.3 s2.3 s
  7. kindsnacks.co.uk at 2.6 s2.6 s
  8. kindsnacks.co.uk at 3.0 s3.0 s

Speed

7 to fix42
  • Improve image delivery

    2.6 s · 586 KiB

    4 images could be 586 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.

  • Reduce unused JavaScript

    1.8 s · 363 KiB

    About 363 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Render-blocking requests

    2.0 s

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

  • Reduce unused CSS

    1.5 s · 330 KiB

    About 330 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 42

    42/100

    Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Optanon and Cloudflare CDN and others), adding 746 KiB and 564 ms of main-thread time.

  • Google Tag Manager adds 420 ms

    420 ms

    Google Tag Manager costs a phone 420 ms of main-thread work and 526 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

    150 ms · 68 KiB

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

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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.

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 801 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

9 to fix67
  • 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: 12.1 s

    12.1 s

    Your largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Alt Image”.

  • Time to Interactive: 12.1 s

    12.1 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • Real-user CLS: 0.14

    0.14

    For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 21% slower for real visitors

    +21%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.218

    0.218

    The layout shifts by 0.218 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 432 ms

    432 ms

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

  • Tap response (INP) held steady for real visitors

    +5%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 100 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user LCP: 1.1 s

    1.1 s

    Real visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 97 ms

    97 ms

    Real visitors wait 97 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 0.9 s

    0.9 s

    Real visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 316 ms

    316 ms

    Real visitors wait 316 ms for your server to start answering (75th percentile). Good is under 800 ms.

Images and page weight

5 to fix25
  • Page weight: 52.0 MB in 44 requests

    52.0 MB

    Your homepage downloads 52.0 MB in 44 requests on a phone: media 50.1 MB (5), scripts 841 KiB (15) and images 644 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    0051781-ChooseYourFlavourOnlineAssets-Website banner_v1 (1). weighs 603 KiB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    0051781-ChooseYourFlavourOnlineAssets-Website banner_v1 (1). 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).

  • 1 image in older formats

    1 image (603 KiB) is 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.

  • 1 image far larger than shown

    205 KiB

    1 image is downloaded at several times the size a phone draws it, for example 0051781-ChooseYourFlavourOnlineAssets-Website banner_v1 (1). at 1,440 px wide, shown at 390 px. Resized copies would save about 205 KiB.

  • About 14.7 g of CO₂ per visit

    14.74 g

    By the Sustainable Web Design model, a visit to your homepage emits about 14.74 g of CO₂e: 1769.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

1 to fixGoogle 9698
  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 55 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8580
  • Title is short (22 characters)

    Your title is only 22 characters: “Homepage | KIND Snacks”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“feast your eyes.” and “(opens in a new tab)”). One clear main headline is easier for people and search engines.

  • Structured data has 2 problems

    Structured data found (ItemList, Organization and WebSite) but with 2 problems, for example “WebSite: potentialAction.target is not an absolute URL ("?search[1]={search_term_string}&amp;s={sea…”.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 36 internal links, 78 external

    The homepage links to 36 pages on kindsnacks.co.uk and 78 external pages.

4 checks passed
  • Meta description: 72 characters

    Your meta description is 72 characters: “Nice to meet you, we're KIND, makers of nutritious and delicious snacks.”.

  • Canonical URL set

    The canonical URL is https://www.kindsnacks.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.kindsnacks.co.uk/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.kindsnacks.co.uk/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.

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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,363 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 2 pages share a title

    https://www.kindsnacks.co.uk/products/kind-bars/caramel-chocolate-peanut-single and https://www.kindsnacks.co.uk/product/peanut-butter-dark-chocolate all use the title “Peanut Butter Dark Chocolate | KIND Snacks”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.kindsnacks.co.uk/kindness and https://www.kindsnacks.co.uk/sustainability have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.kindsnacks.co.uk/faq and https://www.kindsnacks.co.uk/contact use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.kindsnacks.co.uk/kindness, whose canonical is https://www.kindsnacks.co.uk/kindness-hub. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.

2 checks passed
  • Tap targets are thumb-sized

    17 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 1,351 words of copy

    The homepage carries about 1,351 words of visible text.

2 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “contact us”, “where to buy” and “learn more”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 7 other companies contacted

    Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 kindsnacks.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Drupal
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Fastly

Hiring

Hiring
4 open roles
Job board
greenhouse

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on kindsnacks.co.uk, including 16 speed issues, 5 SEO issues and 5 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