Website review, no card needed
drinkcirkul.com website review
Visit site (opens in a new tab)Reviewed 6 November 202650 issues · 94 checks
This review found 50 issues worth fixing on drinkcirkul.com, 18 of them high impact, across 94 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
63D- #114,755 of 120,787 reviewed websitesbeats 4%
- #66,874 of 68,384 online storesbeats 2%
- #61,209 of 62,314 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 206 ms |
| May 23, 2026 | 210 ms |
| May 30, 2026 | 213 ms |
| Jun 6, 2026 | 213 ms |
| Jun 13, 2026 | 213 ms |
| Jun 20, 2026 | 213 ms |
| Jun 27, 2026 | 207 ms |
| Jul 4, 2026 | 200 ms |
| Jul 11, 2026 | 194 ms |
| Jul 18, 2026 | 187 ms |
| Jul 25, 2026 | 187 ms |
| Aug 1, 2026 | 187 ms |
| Aug 8, 2026 | 186 ms |
| Aug 15, 2026 | 188 ms |
| Aug 22, 2026 | 187 ms |
| Aug 29, 2026 | 187 ms |
| Sep 5, 2026 | 187 ms |
| Sep 12, 2026 | 188 ms |
| Sep 19, 2026 | 194 ms |
| Sep 26, 2026 | 199 ms |
| Oct 3, 2026 | 202 ms |
| Oct 10, 2026 | 199 ms |
| Oct 17, 2026 | 195 ms |
| Oct 24, 2026 | 187 ms |
| Oct 31, 2026 | 179 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.4 s
2.8 s
4.2 s
5.6 s
7.0 s
8.4 s
9.8 s
11.2 s
Speed
Render-blocking requests
4.4 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.4 s.
Main-thread work: 17.1 s
A phone's processor spends 17.1 s on main-thread work while loading, 9.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 4
4/100Your mobile performance score is 4. 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 (alia-prod.com, Google Tag Manager and Google CDN and others), adding 2.5 MB and 3.4 s of main-thread time.
Reduce unused JavaScript
450 ms · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Use efficient cache lifetimes
750 ms · 795 KiB43 files are served with short cache lifetimes, so returning visitors download them again (795 KiB).
Reduce unused CSS
750 ms · 165 KiBAbout 165 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Google Tag Manager adds 661 ms
661 msGoogle Tag Manager costs a phone 661 ms of main-thread work and 752 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.
alia-prod.com adds 674 ms
674 msalia-prod.com costs a phone 674 ms of main-thread work and 487 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.
Google CDN adds 573 ms
573 msGoogle CDN costs a phone 573 ms of main-thread work and 736 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.
Hotjar adds 446 ms
446 msHotjar costs a phone 446 ms of main-thread work and 263 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 380 ms. During a long task the page ignores taps.
Minify JavaScript
300 ms · 49 KiB49 KiB could be saved by minifying JavaScript.
zakeke.com adds 339 ms
339 mszakeke.com costs a phone 339 ms of main-thread work and 16 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.
Improve image delivery
324 KiB13 images could be 324 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1,561 HTML elements
The page has 1,561 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 72 KiBPolyfills for old browsers add 72 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Duplicated JavaScript
28 KiB28 KiB JavaScript is shipped twice across bundles.
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: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user CLS: 0.89
0.89For real visitors the layout shifts by 0.89 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 1.406
1.406The layout shifts by 1.406 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 16.8 s
16.8 sVisually, the page fills in at 16.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 37.9 s
37.9 sThe page becomes fully interactive after 37.9 s. Good is under 3.8 s.
Largest Contentful Paint: 8.1 s
8.1 sYour largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s.
Total Blocking Time: 2.1 s
2.1 sScripts block taps and scrolling for 2.1 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
24 images without width and height
24 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 163 ms
163 msReal visitors wait 163 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 433 ms
433 msReal visitors wait 433 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 206 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 33.6 MB in 564 requests
33.6 MBYour homepage downloads 33.6 MB in 564 requests on a phone: media 24.9 MB (12), scripts 3.9 MB (138) and images 2.6 MB (61). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
549 KiB6 images are downloaded at several times the size a phone draws them, for example bottles-updated-nav.webp at 512 px wide, shown at 128 px. Resized copies would save about 549 KiB.
4 images in older formats
4 images (725 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.
2 images below the first screen load straight away
2 images further down the page (177 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 9.5 g of CO₂ per visit
9.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 9.51 g of CO₂e: 1141.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
Orphan list items
Some list items are not inside a list.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
13 internal links, 6 external
The homepage links to 13 pages on drinkcirkul.com and 6 external pages.
6 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Transform your water with the turn of a dial. Take control of your beverage to drink more water. The only bottle that i…”.
Title: 50 characters
Your title is a healthy 50 characters: “Cirkul | Finally, Water Is Your Favorite Beverage.”.
Canonical URL set
The canonical URL is https://drinkcirkul.com/.
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://drinkcirkul.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
8%A phone browser shows 784 words, but the HTML your server sends has only 65. 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.
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.
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://drinkcirkul.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://drinkcirkul.com/pages/careers and https://drinkcirkul.com/pages/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://drinkcirkul.com/blogs/cirkular has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://drinkcirkul.com/pages/faq, https://drinkcirkul.com/pages/store-locator and https://drinkcirkul.com/pages/contact-us 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.
10 internal pages checked
We fetched 10 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 10 pages we checked loaded without an error.
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 10 pages that loaded have a <title>.
Best practices
25 small tap targets
25 of 76 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
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”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
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.
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 784 words of copy
The homepage carries about 784 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: “Shop Now” and “Shop All”.
2 calls to action
The homepage has 2 calls to action, for example “Learn More” and “Contact Us”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Amplitude.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Tag Manager, Klaviyo and Snap Pixel and 1 more (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.
15 cookies set on arrival
15Opening the homepage sets 15 cookies (measured from a US location before any click).
46 other companies contacted
Loading the homepage contacts 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Osano
A consent management tool (Osano) 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 drinkcirkul.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Elevar Conversion Tracking · Applovin Shop Integration · Back In Stock · rechargecdn.com · zakeke.com · bazaarvoice.com · drinkcirkul.com · snapchat.com · integrations-itbl.co · loox.io · govx.com
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
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Amplitude
- Hosting
- Shopify
Company
- Founded
- 2015
- Headquarters
- Tampa
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on drinkcirkul.com, including 26 speed issues, 4 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.