Website review, no card needed
caffeinearmy.com website review
Visit site (opens in a new tab)Reviewed 8 November 202644 issues · 91 checks
This review found 44 issues worth fixing on caffeinearmy.com, 17 of them high impact, across 91 checks. The most urgent: page weight: 54.0 MB in 370 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
71C- #97,286 of 120,492 reviewed websitesbeats 17%
- #59,818 of 68,208 online storesbeats 10%
- #55,591 of 62,153 Shopify storesbeats 9%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.3 s |
| May 23, 2026 | 3.9 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 3.8 s |
| Aug 22, 2026 | 4.4 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 5.0 s |
| Sep 12, 2026 | 5.0 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.7 s |
| Oct 3, 2026 | 4.2 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 4.4 s |
| Oct 24, 2026 | 4.5 s |
| Oct 31, 2026 | 4.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 152 ms |
| May 23, 2026 | 130 ms |
| May 30, 2026 | 135 ms |
| Jun 6, 2026 | 129 ms |
| Jun 13, 2026 | 128 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 138 ms |
| Jul 11, 2026 | 136 ms |
| Jul 18, 2026 | 134 ms |
| Jul 25, 2026 | 130 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 137 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 155 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 188 ms |
| Sep 12, 2026 | 202 ms |
| Sep 19, 2026 | 179 ms |
| Sep 26, 2026 | 155 ms |
| Oct 3, 2026 | 141 ms |
| Oct 10, 2026 | 139 ms |
| Oct 17, 2026 | 149 ms |
| Oct 24, 2026 | 154 ms |
| Oct 31, 2026 | 162 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
1.3 s
2.6 s
3.9 s
5.1 s
6.4 s
7.7 s
9.0 s
10.3 s
Speed
replocdn.com adds 1.7 s
1.7 sreplocdn.com costs a phone 1.7 s of main-thread work and 2.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 11.0 s
A phone's processor spends 11.0 s on main-thread work while loading, 5.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 10
10/100Your mobile performance score is 10. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (replocdn.com, Google Tag Manager and alia-prod.com and others), adding 50.4 MB and 4.0 s of main-thread time.
Reduce unused JavaScript
2.2 MBAbout 2.2 MB of JavaScript is downloaded but never used on this page.
Improve image delivery
500 ms · 1.5 MB15 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Render-blocking requests
950 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Google Tag Manager adds 650 ms
650 msGoogle Tag Manager costs a phone 650 ms of main-thread work and 512 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.
Use efficient cache lifetimes
696 KiB27 files are served with short cache lifetimes, so returning visitors download them again (696 KiB).
alia-prod.com adds 507 ms
507 msalia-prod.com costs a phone 507 ms of main-thread work and 744 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 450 ms. During a long task the page ignores taps.
Hotjar adds 365 ms
365 msHotjar costs a phone 365 ms of main-thread work and 65 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.
Facebook adds 332 ms
332 msFacebook costs a phone 332 ms of main-thread work and 285 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.
Reduce unused CSS
150 ms · 53 KiBAbout 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.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Legacy JavaScript
185 KiBPolyfills for old browsers add 185 KiB JavaScript that modern phones do not need.
Minify CSS
14 KiB14 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: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.0 s
15.0 sYour largest element takes 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Caffeine Army Cinnamon Mocha”.
Speed Index: 16.2 s
16.2 sVisually, the page fills in at 16.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 48.2 s
48.2 sThe page becomes fully interactive after 48.2 s. Good is under 3.8 s.
Total Blocking Time: 3.0 s
3.0 sScripts block taps and scrolling for 3.0 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.721
0.721The layout shifts by 0.721 while loading, so content jumps under the reader's thumb. Good is under 0.1.
21 images without width and height
21 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.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 152 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.3 s to 4.9 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 141 ms
141 msReal visitors wait 141 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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 759 ms
759 msReal visitors wait 759 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 54.0 MB in 370 requests
54.0 MBYour homepage downloads 54.0 MB in 370 requests on a phone: media 44.1 MB (12), scripts 4.6 MB (136) and images 3.8 MB (33). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.
8 images far larger than shown
1.7 MB8 images are downloaded at several times the size a phone draws them, for example ecomm_grande_chocovanilla.png at 390 px wide, shown at 90 px. Resized copies would save about 1.7 MB.
An image on the first screen is lazy-loaded
cart_711x320_ba1b7f6d-2f13-4a79-ad05-3f0fc385338e.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
6 images below the first screen load straight away
6 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (216 KiB) 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.
About 15.3 g of CO₂ per visit
15.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 15.29 g of CO₂e: 1835.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
5 buttons without a name
5 buttons have no accessible name, so screen readers announce just “button”.
24 text elements with low contrast
24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
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 53 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 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
Title is short (13 characters)
Your title is only 13 characters: “Caffeine Army”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“SUBSCRIBE & SAVE 15%” and “”). One clear main headline is easier for people and search engines.
Meta description is long (215 characters)
Your meta description is 215 characters; Google truncates after about 160, so the end of your pitch is cut.
36 internal links, 3 external
The homepage links to 36 pages on caffeinearmy.com and 3 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://caffeinearmy.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://caffeinearmy.com/sitemap.xml.
AI search readiness
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.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,259 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://caffeinearmy.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages point its canonical at the homepage
https://caffeinearmy.com/products/caffeine-army%C2%AE-cappuccino-38ct-tts, https://caffeinearmy.com/products/caffeine-army-chocolate-economic-size, https://caffeinearmy.com/products/caffeine-army%C2%AE-vanilla-latte-38ct-tts, https://caffeinearmy.com/products/caffeine-army-chocovanilla-38ct and https://caffeinearmy.com/products/caffeine-army-coconut-cake-economic-size declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
6 pages share a title
/, https://caffeinearmy.com/products/caffeine-army%C2%AE-cappuccino-38ct-tts, https://caffeinearmy.com/products/caffeine-army-chocolate-economic-size, https://caffeinearmy.com/products/caffeine-army%C2%AE-vanilla-latte-38ct-tts, https://caffeinearmy.com/products/caffeine-army-chocovanilla-38ct and https://caffeinearmy.com/products/caffeine-army-coconut-cake-economic-size all use the title “Caffeine Army”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://caffeinearmy.com/pages/products, https://caffeinearmy.com/pages/about-us, https://caffeinearmy.com/pages/quality-control, https://caffeinearmy.com/policies/privacy-policy, https://caffeinearmy.com/policies/refund-policy and https://caffeinearmy.com/policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages share a meta description
https://caffeinearmy.com/products/caffeine-army-cinnamon-mocha-38ct and https://caffeinearmy.com/products/caffeine-army-cappuccino-economic-size use the same meta description. A description written for each page earns more clicks.
6 pages slow to respond
https://caffeinearmy.com/pages/quality-control, https://caffeinearmy.com/products/caffeine-army%C2%AE-cappuccino-38ct-tts, https://caffeinearmy.com/products/caffeine-army-chocolate-economic-size, https://caffeinearmy.com/products/caffeine-army%C2%AE-vanilla-latte-38ct-tts, https://caffeinearmy.com/products/caffeine-army-chocovanilla-38ct and https://caffeinearmy.com/products/caffeine-army-coconut-cake-economic-size took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 16 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
1 broken image
1 image failed to load on a phone, for example https://caffeinearmy.com/cdn/shop/t/153/assets/logo_shakers_small.png?v=43720.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
8 of 8 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
About 1,054 words of copy
The homepage carries about 1,054 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP MORNING SHOT”.
13 calls to action
The homepage has 13 calls to action, for example “Shop now”, “SUBSCRIBE & SAVE 15%” and “Shop all”.
7 short forms
7 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: a star rating, 1 trust badge and “3,000+ Reviews”.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar 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
21Opening the homepage sets 21 cookies, 1 of them by other companies (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.
60 other companies contacted
Loading the homepage contacts 60 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 caffeinearmy.com, 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 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Gorgias Live Chat Helpdesk · Triplewhale · Sami B2b Lock · Minmaxify Order Limits · Eg Auto Add To Cart · Smarty Discounts · Klaviyo Email Marketing Sms · Countdown Timer · Wholesale Lock Hide Price · Freegifts · stamped.io · b-cdn.net · superfiliate-cdn.com · nice-team.net · cloudfront.net · bogos.io
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
- The footer still says © 2024.
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on caffeinearmy.com, including 20 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.