Website review, no card needed

naturepac.co.uk logo

naturepac.co.uk website review

Visit site (opens in a new tab)Reviewed 5 November 202641 issues · 86 checks

This review found 41 issues worth fixing on naturepac.co.uk, 13 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. 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
3.1 s1.0 sMay 16Oct 312.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.4 s
Jun 13, 20261.5 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.5 s
Aug 22, 20261.4 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.4 s
Sep 26, 20262.5 s
Oct 3, 20262.7 s
Oct 10, 20262.9 s
Oct 17, 20262.8 s
Oct 24, 20262.7 s
Oct 31, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
214 ms90 msMay 16Oct 31184 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026104 ms
May 23, 2026111 ms
May 30, 2026116 ms
Jun 6, 2026112 ms
Jun 13, 2026124 ms
Jun 20, 2026124 ms
Jun 27, 2026127 ms
Jul 4, 2026135 ms
Jul 11, 2026121 ms
Jul 18, 2026121 ms
Jul 25, 2026112 ms
Aug 1, 2026129 ms
Aug 8, 2026124 ms
Aug 15, 2026128 ms
Aug 22, 2026126 ms
Aug 29, 2026105 ms
Sep 5, 2026125 ms
Sep 12, 2026128 ms
Sep 19, 2026143 ms
Sep 26, 2026170 ms
Oct 3, 2026175 ms
Oct 10, 2026200 ms
Oct 17, 2026186 ms
Oct 24, 2026185 ms
Oct 31, 2026184 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 naturepac.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. naturepac.co.uk at 0.6 s0.6 s
  2. naturepac.co.uk at 1.1 s1.1 s
  3. naturepac.co.uk at 1.7 s1.7 s
  4. naturepac.co.uk at 2.2 s2.2 s
  5. naturepac.co.uk at 2.8 s2.8 s
  6. naturepac.co.uk at 3.3 s3.3 s
  7. naturepac.co.uk at 3.9 s3.9 s
  8. naturepac.co.uk at 4.4 s4.4 s

Speed

10 to fix36
  • Reduce unused JavaScript

    2.3 s · 906 KiB

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

  • Use efficient cache lifetimes

    1.9 s · 544 KiB

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

  • Improve image delivery

    1.4 s · 393 KiB

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

  • Mobile performance score: 36

    36/100

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

  • Main-thread work: 4.1 s

    A phone's processor spends 4.1 s on main-thread work while loading, 2.1 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 (Google Tag Manager, hsappstatic.net and Facebook and others), adding 2.5 MB and 1.7 s of main-thread time.

  • Google Tag Manager adds 630 ms

    630 ms

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

  • hsappstatic.net adds 412 ms

    412 ms

    hsappstatic.net costs a phone 412 ms of main-thread work and 715 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.

  • 16 long tasks on the main thread

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

  • 2,904 HTML elements

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

  • Reduce unused CSS

    150 ms · 53 KiB

    About 53 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 · 11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

  • Render-blocking requests

    150 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

  • Legacy JavaScript

    60 KiB

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

1 checks passed
  • Server response: 5 ms

    5 ms

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

Core Web Vitals

13 to fix33
  • 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: 20.5 s

    20.5 s

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

  • Time to Interactive: 26.8 s

    26.8 s

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

  • Speed Index: 9.5 s

    9.5 s

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

  • Total Blocking Time: 787 ms

    787 ms

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user CLS: 0.21

    0.21

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

  • Tap response (INP) got 72% slower for real visitors

    +72%

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

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

    +115%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 825 ms

    825 ms

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Cumulative Layout Shift: 0.169

    0.169

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

1 checks passed
  • Real-user INP: 177 ms

    177 ms

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

Images and page weight

2 to fix60
  • Page weight: 4.7 MB in 262 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 262 requests on a phone: scripts 2.7 MB (96), images 928 KiB (18) and other files 811 KiB (128). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    191 KiB

    3 images are downloaded at several times the size a phone draws them, for example Autumn_Home_Page_Photo_2000x.jpg at 2,000 px wide, shown at 390 px. Resized copies would save about 191 KiB.

  • 6 images below the first screen load straight away

    6 images further down the page (264 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.3 g of CO₂ per visit

    1.33 g

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

3 to fixGoogle 9396
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • 6 links without text

    6 visible links have no text or label, so screen readers cannot say where they go.

  • Alternative text of images should not be repeated as text (9 elements)

    Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

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

    Elements with visible text labels do not have matching accessible names. (3 elements).

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 53 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: 53 passed and 3 failed. 3 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 long (80 characters)

    Your title is 80 characters, so Google will cut it off around 60: “Eco-friendly food & takeaway packaging | Sustainable & Biodegradable – NaturePac”.

  • 3 H1 headlines

    There are 3 <h1> headlines (“NaturePac Cups”, “Custom Branded Packaging” and “That NaturePac Feeling”). One clear main headline is easier for people and search engines.

  • Meta description is long (199 characters)

    Your meta description is 199 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.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • Open Graph partly set

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 144 internal links, 6 external

    The homepage links to 144 pages on naturepac.co.uk and 6 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://naturepac.co.uk/.

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

2 to fix75
  • Some text only appears after JavaScript runs

    58%

    The HTML your server sends has 849 of the 1,453 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, 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.

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.

  • llms.txt published

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

Other pages

1 to fix95
  • 10 pages without a meta description

    https://naturepac.co.uk/collections/all-cups-lids, https://naturepac.co.uk/collections/all-double-wall-cups, https://naturepac.co.uk/collections/all-single-wall-cups, https://naturepac.co.uk/collections/hot-cup-lids, https://naturepac.co.uk/collections/cold-drink-cups and https://naturepac.co.uk/collections/cold-cup-lids and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • 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

3 to fixGoogle 7376
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97166816&tm=gtm002&Ver=2&mid=e2618e8c-d2bd-49d6-894d-61d41e483c4a&bo=1&sid=7b796490d8f611f198bd7be74176d57d&vid=7b798e80d8f611f1bd1a0bcc67576fac&vids=1&msclkid=N&pi=91.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load data from https://leadbooster-chat.pipedrive.com/chat-api/bundleInfo?url=https://naturepac.co.uk/”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    32 of 36 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 1,453 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: “Contact” and “Contact Us”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “London Based Coffee Shop”, “Contact” and “Shop NaturePac Cups”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 5 email links.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 2 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

    21

    Opening the homepage sets 21 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.

  • 51 other companies contacted

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

Apps your storefront loads

Klaviyo Email Marketing Sms · Reviews Co Uk Product And Merchant Review Collection · hulkapps.com · rechargecdn.com · pop-convert.com · b-cdn.net · hubapi.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
Tailwind CSS
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Company

Headquarters
Saint Ives

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on naturepac.co.uk, including 23 speed issues, 5 SEO issues and 1 conversion gap. 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