Website review, no card needed
24bottles.com website review
Visit site (opens in a new tab)Reviewed 20 October 202628 issues · 70 checks
This review found 28 issues worth fixing on 24bottles.com, 14 of them high impact, across 70 checks. The most urgent: page weight: 16.3 MB in 251 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
80B- #45,944 of 116,487 reviewed websitesbeats 55%
- #30,819 of 66,776 online storesbeats 47%
- #29,661 of 60,929 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.9 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 145 ms |
| May 9, 2026 | 142 ms |
| May 16, 2026 | 139 ms |
| May 23, 2026 | 138 ms |
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 137 ms |
| Jun 13, 2026 | 139 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 150 ms |
| Jul 4, 2026 | 155 ms |
| Jul 11, 2026 | 158 ms |
| Jul 18, 2026 | 158 ms |
| Jul 25, 2026 | 158 ms |
| Aug 1, 2026 | 159 ms |
| Aug 8, 2026 | 161 ms |
| Aug 15, 2026 | 166 ms |
| Aug 22, 2026 | 173 ms |
| Aug 29, 2026 | 179 ms |
| Sep 5, 2026 | 184 ms |
| Sep 12, 2026 | 188 ms |
| Sep 19, 2026 | 193 ms |
| Sep 26, 2026 | 198 ms |
| Oct 3, 2026 | 204 ms |
| Oct 10, 2026 | 212 ms |
| Oct 17, 2026 | 217 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
Speed
Main-thread work: 8.2 s
A phone's processor spends 8.2 s on main-thread work while loading, 3.3 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 (Klaviyo, ZenDesk and Clarity and others), adding 1.6 MB and 1.3 s of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53 (desktop: 66). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
120 ms · 561 KiBAbout 561 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 120 ms faster on a phone.
Reduce unused CSS
420 ms · 46 KiBAbout 46 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 420 ms faster on a phone.
Klaviyo adds 372 ms
372 msKlaviyo costs a phone 372 ms of main-thread work and 635 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.
ZenDesk adds 247 ms
247 msZenDesk costs a phone 247 ms of main-thread work and 392 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 224 ms. During a long task the page ignores taps.
Improve image delivery
172 KiB7 images could be 172 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
150 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Use efficient cache lifetimes
38 KiB11 files are served with short cache lifetimes, so returning visitors download them again (38 KiB).
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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: 47 ms
47 msYour server sent the HTML in 47 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 20.6 s
20.6 sThe page becomes fully interactive after 20.6 s. Good is under 3.8 s.
Largest Contentful Paint: 5.2 s
5.2 sYour largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 795 ms
795 msScripts block taps and scrolling for 795 ms in total while the page loads. Good is under 200 ms.
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 49% slower for real visitors
+49%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 145 ms to 217 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 192 ms
192 msReal visitors wait 192 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 529 ms
529 msReal visitors wait 529 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.012
0.012The layout barely moves while loading (CLS 0.012, good is under 0.1).
Images and page weight
Page weight: 16.3 MB in 251 requests
16.3 MBYour homepage downloads 16.3 MB in 251 requests on a phone: media 12.8 MB (2), scripts 1.6 MB (112) and other files 804 KiB (96). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (81 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 4.6 g of CO₂ per visit
4.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.61 g of CO₂e: 553.2 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
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
7 checks passed
Meta description: 98 characters
Your meta description is 98 characters: “Discover the 24Bottles® World: Water Bottles, Thermos Flasks, Travel Cups, Sport Bottles and more.”.
Title: 59 characters
Your title is a healthy 59 characters: “Reusable Water Bottles, Flasks and Travel Cups | 24Bottles®”.
Canonical URL set
The canonical URL is https://24bottles.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://24bottles.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 432 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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 https://24bottles.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Best practices
12 small tap targets
12 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 432 words of copy
The homepage carries about 432 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more and customise”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.
29 cookies set on arrival
29Opening the homepage sets 29 cookies (measured from a US location before any click).
43 other companies contacted
Loading the homepage contacts 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: iubenda
A consent management tool (iubenda) 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 24bottles.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on 24bottles.com, including 13 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.