Website review, no card needed

britvic.com logo

britvic.com website review

Visit site (opens in a new tab)Reviewed 29 October 202638 issues · 85 checks

This review found 38 issues worth fixing on britvic.com, 15 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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.5 s1.2 sMay 9Oct 241.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.2 s
May 16, 20261.4 s
May 23, 20261.3 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
123 ms100 msMay 9Oct 24105 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026115 ms
May 16, 2026120 ms
May 23, 2026118 ms
May 30, 2026119 ms
Jun 6, 2026113 ms
Jun 13, 2026111 ms
Jun 20, 2026111 ms
Jun 27, 2026108 ms
Jul 4, 2026111 ms
Jul 11, 2026112 ms
Jul 18, 2026112 ms
Jul 25, 2026112 ms
Aug 1, 2026112 ms
Aug 8, 2026105 ms
Aug 15, 2026105 ms
Aug 22, 2026105 ms
Aug 29, 2026105 ms
Sep 5, 2026112 ms
Sep 12, 2026112 ms
Sep 19, 2026111 ms
Sep 26, 2026110 ms
Oct 3, 2026109 ms
Oct 10, 2026105 ms
Oct 17, 2026103 ms
Oct 24, 2026105 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 britvic.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix53
  • Use efficient cache lifetimes

    5.0 s · 13.1 MB

    86 files are served with short cache lifetimes, so returning visitors download them again (13.1 MB).

  • Render-blocking requests

    8.8 s

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

  • Reduce unused CSS

    1.4 s · 253 KiB

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

  • Improve image delivery

    350 ms · 9.8 MB

    25 images could be 9.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Mobile performance score: 53

    53/100

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

  • Reduce unused JavaScript

    750 ms · 183 KiB

    About 183 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, cookiefirst.com and Google Fonts and others), adding 578 KiB and 145 ms of main-thread time.

  • Font display

    200 ms

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

  • Minify JavaScript

    150 ms · 38 KiB

    38 KiB could be saved by minifying JavaScript.

  • 4 long tasks on the main thread

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

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

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

  • Server response: 20 ms

    20 ms

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

Core Web Vitals

4 to fix100
  • First Contentful Paint: 10.7 s

    10.7 s

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

  • Largest Contentful Paint: 14.6 s

    14.6 s

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

  • Speed Index: 10.7 s

    10.7 s

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

  • Time to Interactive: 14.6 s

    14.6 s

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

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

    +10%

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

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

    1.7 s

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

  • Real-user INP: 111 ms

    111 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 560 ms

    560 ms

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

  • Tap response (INP) got 11% faster for real visitors

    -11%

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

  • Total Blocking Time: 187 ms

    187 ms

    Scripts block the page for only 187 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 21.3 MB in 103 requests

    21.3 MB

    Your homepage downloads 21.3 MB in 103 requests on a phone: images 18.8 MB (67), media 889 KiB (1) and stylesheets 825 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 9 images over 500 KB

    9 images weigh 9.7 MB together. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    5.2 MB

    6 images are downloaded at several times the size a phone draws them, for example tango-cash-stash-banner.png at 2,000 px wide, shown at 360 px. Resized copies would save about 5.2 MB.

  • 40 images in older formats

    40 images (16.3 MB) are 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.

  • 6 images below the first screen load straight away

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

  • About 6.1 g of CO₂ per visit

    6.05 g

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

Accessibility

5 to fixGoogle 8993
  • ARIA attributes must conform to valid names (3 elements)

    ARIA attributes must conform to valid names: 3 elements on the page fail this check, rated critical 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 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

  • 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 72 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

7 to fixGoogle 9265
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (22 characters)

    Your title is only 22 characters: “Home | Britvic Limited”. 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.

  • Meta description is long (299 characters)

    Your meta description is 299 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No XML sitemap

    No XML sitemap at https://www.britvic.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at britvic.com/robots.txt, the first file search crawlers ask for.

  • 14 links with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 68 internal links, 165 external

    The homepage links to 68 pages on britvic.com and 165 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://www.britvic.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

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.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

4 to fix81
  • 2 pages share a title

    https://www.britvic.com/about-us/where-we-operate and https://www.britvic.com/about-us/where-we-operate/great-britain all use the title “Great Britain | Britvic Limited”. 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.britvic.com/about-us/purpose-vision-and-values and https://www.britvic.com/about-us/our-strategy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.britvic.com/about-us/where-we-operate, https://www.britvic.com/about-us/where-we-operate/great-britain, https://www.britvic.com/about-us/where-we-operate/brazil and https://www.britvic.com/about-us/where-we-operate/other-international 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.britvic.com/about-us/where-we-operate, whose canonical is https://www.britvic.com/about-us/where-we-operate/great-britain. 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 53 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

2 to fixGoogle 9687
  • 73 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • 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 opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

4 checks passed
  • 14 calls to action

    The homepage has 14 calls to action, for example “Search and apply”, “Contact us” and “Learn more”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (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.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 5 other companies contacted

    Loading the homepage contacts 5 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 britvic.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Founded
1845
Headquarters
Hemel Hempstead

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 britvic.com, including 10 speed issues, 7 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