Website review, no card needed
drinkaccelerator.com website review
Visit site (opens in a new tab)Reviewed 20 October 202624 issues · 76 checks
This review found 24 issues worth fixing on drinkaccelerator.com, 4 of them high impact, across 76 checks. The most urgent: scrollable region must have keyboard access (1 element). 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
85B- #15,932 of 117,291 reviewed websitesbeats 82%
- #10,176 of 66,888 online storesbeats 79%
- #9,892 of 60,999 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.2 s |
| May 9, 2026 | 1.2 s |
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 87 ms |
| May 9, 2026 | 101 ms |
| May 16, 2026 | 106 ms |
| May 23, 2026 | 114 ms |
| May 30, 2026 | 119 ms |
| Jun 6, 2026 | 110 ms |
| Jun 13, 2026 | 99 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 92 ms |
| Jul 4, 2026 | 91 ms |
| Jul 11, 2026 | 90 ms |
| Jul 18, 2026 | 87 ms |
| Jul 25, 2026 | 88 ms |
| Aug 1, 2026 | 89 ms |
| Aug 8, 2026 | 87 ms |
| Aug 15, 2026 | 88 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 80 ms |
| Sep 5, 2026 | 80 ms |
| Sep 12, 2026 | 80 ms |
| Sep 19, 2026 | 83 ms |
| Sep 26, 2026 | 87 ms |
| Oct 3, 2026 | 88 ms |
| Oct 10, 2026 | 81 ms |
| Oct 17, 2026 | 75 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.7 s
1.5 s
2.2 s
2.9 s
3.6 s
4.4 s
5.1 s
5.8 s
Speed
Mobile performance score: 62
62/100Your mobile performance score is 62 (desktop: 99). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
650 ms · 152 KiB4 images could be 152 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.
7 third-party services on the page
7 third-party services load with your homepage (pop-convert.com, Klaviyo and POWr and others), adding 413 KiB and 264 ms of main-thread time.
Use efficient cache lifetimes
169 KiB7 files are served with short cache lifetimes, so returning visitors download them again (169 KiB).
Render-blocking requests
150 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 101 ms. During a long task the page ignores taps.
Reduce unused JavaScript
94 KiBAbout 94 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need.
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.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 612 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.8 s
7.8 sYour largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 7.9 s
7.9 sThe page becomes fully interactive after 7.9 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.231
0.231The layout shifts by 0.231 while loading, so content jumps under the reader's thumb. Good is under 0.1.
45 images without width and height
45 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.0 s
1.0 sReal visitors wait 1.0 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.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 402 ms
402 msReal visitors wait 402 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 87 ms to 75 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 3.0 s
3.0 sVisually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 59 ms
59 msScripts block the page for only 59 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.2 MB in 211 requests
2.2 MBYour homepage downloads 2.2 MB in 211 requests on a phone: images 822 KiB (27), other files 735 KiB (104) and scripts 493 KiB (55). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.62 g of CO₂e: 73.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 71 images in the HTML carry an alt attribute.
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. 1 more 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.
Meta description is long (254 characters)
Your meta description is 254 characters; Google truncates after about 160, so the end of your pitch is cut.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
63 internal links, 41 external
The homepage links to 63 pages on drinkaccelerator.com and 41 external pages.
6 checks passed
Title: 34 characters
Your title is a healthy 34 characters: “Home of Accelerator Active Energy®”.
Canonical URL set
The canonical URL is https://www.drinkaccelerator.com/.
Structured data in place
Structured data found: 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.drinkaccelerator.com/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (459 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.drinkaccelerator.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.drinkaccelerator.com/pages/newsletter-1 and https://www.drinkaccelerator.com/pages/newsletter all use the title “Newsletter – Accelerator Active Energy”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://www.drinkaccelerator.com/pages/ultimatevarietypack, https://www.drinkaccelerator.com/pages/storelocator, https://www.drinkaccelerator.com/pages/newsletter-1, https://www.drinkaccelerator.com/pages/newsletter, https://www.drinkaccelerator.com/pages/collegeambassador and https://www.drinkaccelerator.com/pages/faq_ and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://www.drinkaccelerator.com/pages/about-us, https://www.drinkaccelerator.com/pages/storelocator, https://www.drinkaccelerator.com/pages/newsletter-1, https://www.drinkaccelerator.com/pages/products_, https://www.drinkaccelerator.com/pages/newsletter and https://www.drinkaccelerator.com/pages/collegeambassador and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
11 internal pages checked
We fetched 11 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 11 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
45 small tap targets
45 of 78 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 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 394 words of copy
The homepage carries about 394 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “BUY NOW ON AMAZON” and “SHOP NOW”.
26 calls to action
The homepage has 26 calls to action, for example “BUY NOW ON AMAZON”, “SHOP” and “SHOP NOW”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 7 testimonial or review blocks, a star rating and 1 trust badge.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
25 other companies contacted
Loading the homepage contacts 25 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 drinkaccelerator.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on drinkaccelerator.com, including 7 speed issues, 3 SEO issues and 2 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.