Website review, no card needed
boostdrinks.com website review
Visit site (opens in a new tab)Reviewed 22 October 202625 issues · 97 checks
This review found 25 issues worth fixing on boostdrinks.com, 10 of them high impact, across 97 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
86B- #8,420 of 86,743 reviewed websitesbeats 87%
- #4,751 of 44,579 online storesbeats 85%
- #4,587 of 39,883 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.3 s |
| May 9, 2026 | 1.4 s |
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 104 ms |
| May 9, 2026 | 97 ms |
| May 16, 2026 | 94 ms |
| May 23, 2026 | 92 ms |
| May 30, 2026 | 89 ms |
| Jun 6, 2026 | 90 ms |
| Jun 13, 2026 | 93 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 97 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 97 ms |
| Jul 25, 2026 | 97 ms |
| Aug 1, 2026 | 99 ms |
| Aug 8, 2026 | 101 ms |
| Aug 15, 2026 | 97 ms |
| Aug 22, 2026 | 100 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 109 ms |
| Sep 19, 2026 | 110 ms |
| Sep 26, 2026 | 110 ms |
| Oct 3, 2026 | 110 ms |
| Oct 10, 2026 | 107 ms |
| Oct 17, 2026 | 111 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
boostdrinks.com does not allow embedding, so this is Google's rendering of the page.
Speed
Render-blocking requests
1.5 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.5 s.
Reduce unused JavaScript
1.1 s · 160 KiBAbout 160 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Improve image delivery
650 ms · 474 KiB18 images could be 474 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
Mobile performance score: 62
62/100Your mobile performance score is 62 (desktop: 99). Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 187 ms
187 msGoogle Tag Manager costs a phone 187 ms of main-thread work and 310 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.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Clarity and Klaviyo and others), adding 624 KiB and 416 ms of main-thread time.
Reduce unused CSS
150 ms · 26 KiBAbout 26 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 127 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
15 KiB3 files are served with short cache lifetimes, so returning visitors download them again (15 KiB).
Phones get a much slower page than desktops
Desktop scores 99 but mobile only 62. A gap that wide usually means heavy scripts and images that hit phones hardest.
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 JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 838 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.4 s
15.4 sYour largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 15.7 s
15.7 sThe page becomes fully interactive after 15.7 s. Good is under 3.8 s.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 104 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 74 ms
74 msScripts block the page for only 74 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 5.5 MB in 271 requests
5.5 MBYour homepage downloads 5.5 MB in 271 requests on a phone: media 1.7 MB (1), images 1.6 MB (30) and other files 1.0 MB (169). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (35 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.56 g of CO₂e: 187.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 checks passed
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. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“Boost Drinks”, “HYDRATION & ENERGY THAT HITS DIFFERENT” and “Boost Drinks”). One clear main headline is easier for people and search engines.
41 internal links, 9 external
The homepage links to 41 pages on boostdrinks.com and 9 external pages.
7 checks passed
Meta description: 119 characters
Your meta description is 119 characters: “Discover BOOST, a UK-based drinks brand offering drinks for everyday life: energy, sport, coffee and fizzy fruit juice.”.
Title: 55 characters
Your title is a healthy 55 characters: “BOOST | Energy drinks for whatever life throws your way”.
Canonical URL set
The canonical URL is https://www.boostdrinks.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.boostdrinks.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), 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 /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
/pages/contact, /policies/privacy-policy and /policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.
12 pages without an H1
/collections/boost-energy, /collections/boost-sport, /collections/boost-water, /collections/boost-coffee, /collections/boost-juicd and /collections/hydration-powders and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
8 pages with very little text
/collections/boost-energy, /collections/boost-sport, /collections/boost-water, /collections/boost-coffee, /collections/boost-juicd and /collections/hydration-powders and 2 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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 14 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
10 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
Short HSTS lifetime
HSTS is set, but max-age is 91 days; one year is the recommended minimum.
2 links through redirect chains
2 links go through two or more redirects, for example https://www.boostdrinks.com/customer_authentication/redirect?locale=en®ion_country=GB.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
7 checks passed
Served over HTTPS
The homepage is served over HTTPS (boostdrinks.com).
Valid certificate (42 days left)
The certificate from Let's Encrypt · YE2 verifies for boostdrinks.com and is valid for another 42 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
http:// redirects to https
http://boostdrinks.com redirects to the secure version.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
All 26 links work
All 26 links checked from your homepage (21 internal, 5 external) answered without errors.
Domain and trust
DNSSEC is off
boostdrinks.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
3 checks passed
Domain is 25 years old
25 yearsboostdrinks.com was registered in Jul 2001 through Lexsynergy Limited. An established domain carries more trust with email providers and search engines.
Certificate issuers are restricted
CAA records allow only globalsign.com, ssl.com, letsencrypt.org and pki.goog to issue certificates for boostdrinks.com, so a mis-issued certificate from anyone else is refused.
Registered until Jul 2027
boostdrinks.com is registered until Jul 2027.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 93 words
The homepage has only about 93 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP HYDRATION” and “SHOP ENERGY”.
5 calls to action
The homepage has 5 calls to action, for example “Shop Hydration”, “Shop Energy” and “Subscribe”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Email authentication
No DKIM key on the usual selectors
We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.
Email authentication score: 75/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
2 checks passed
DMARC policy: quarantine
DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:mailgun.org include:spf2.accessacloud.com include:eu._netblocks.mimecast.com include:_spfinc.boostdrinks…”.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel 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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
23 other companies contacted
Loading the homepage contacts 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Upkeep, stack and company
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
Company
- Founded
- 2001
- Headquarters
- Leeds
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This free review found 25 issues on boostdrinks.com, including 10 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.