Website review, no card needed
dosedaily.co website review
Visit site (opens in a new tab)Reviewed 4 November 202631 issues · 83 checks
This review found 31 issues worth fixing on dosedaily.co, 10 of them high impact, across 83 checks. The most urgent: page weight: 19.2 MB in 519 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
88B- #5,880 of 124,378 reviewed websitesbeats 93%
- #3,183 of 69,877 online storesbeats 93%
- #3,083 of 63,539 Shopify storesbeats 93%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 4.7 s |
| Jul 4, 2026 | 4.7 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 4.8 s |
| Jul 25, 2026 | 4.8 s |
| Aug 1, 2026 | 4.9 s |
| Aug 8, 2026 | 4.8 s |
| Aug 15, 2026 | 4.4 s |
| Aug 22, 2026 | 4.1 s |
| Aug 29, 2026 | 4.0 s |
| Sep 5, 2026 | 3.9 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 212 ms |
| May 23, 2026 | 213 ms |
| May 30, 2026 | 217 ms |
| Jun 6, 2026 | 222 ms |
| Jun 13, 2026 | 233 ms |
| Jun 20, 2026 | 245 ms |
| Jun 27, 2026 | 250 ms |
| Jul 4, 2026 | 254 ms |
| Jul 11, 2026 | 251 ms |
| Jul 18, 2026 | 240 ms |
| Jul 25, 2026 | 237 ms |
| Aug 1, 2026 | 236 ms |
| Aug 8, 2026 | 237 ms |
| Aug 15, 2026 | 238 ms |
| Aug 22, 2026 | 239 ms |
| Aug 29, 2026 | 239 ms |
| Sep 5, 2026 | 236 ms |
| Sep 12, 2026 | 229 ms |
| Sep 19, 2026 | 221 ms |
| Sep 26, 2026 | 212 ms |
| Oct 3, 2026 | 205 ms |
| Oct 10, 2026 | 200 ms |
| Oct 17, 2026 | 196 ms |
| Oct 24, 2026 | 195 ms |
| Oct 31, 2026 | 189 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
Render-blocking requests
1.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Main-thread work: 9.4 s
A phone's processor spends 9.4 s on main-thread work while loading, 3.8 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 (Google Tag Manager, Facebook and TikTok and others), adding 1.7 MB and 1.6 s of main-thread time.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 731 ms
731 msGoogle Tag Manager costs a phone 731 ms of main-thread work and 539 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 JavaScript
474 KiBAbout 474 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
430 KiB50 files are served with short cache lifetimes, so returning visitors download them again (430 KiB).
Improve image delivery
430 KiB7 images could be 430 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 269 ms. During a long task the page ignores taps.
1,648 HTML elements
The page has 1,648 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 112 ms
112 msShopify costs a phone 112 ms of main-thread work and 366 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
99 KiBAbout 99 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
75 KiBPolyfills for old browsers add 75 KiB JavaScript that modern phones do not need.
Minify CSS
24 KiB24 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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 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.
Time to Interactive: 28.8 s
28.8 sThe page becomes fully interactive after 28.8 s. Good is under 3.8 s.
Total Blocking Time: 964 ms
964 msScripts block taps and scrolling for 964 ms in total while the page loads. Good is under 200 ms.
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.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 153 ms
153 msReal visitors wait 153 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 573 ms
573 msReal visitors wait 573 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 212 ms to 189 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Take care of the core systems quietly powering your body”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 19.2 MB in 519 requests
19.2 MBYour homepage downloads 19.2 MB in 519 requests on a phone: media 14.2 MB (2), scripts 2.4 MB (245) and other files 1.0 MB (202). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
hero-lineup-mobile-2026-02.jpg 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).
1 image in older formats
1 image (161 KiB) is 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 5.4 g of CO₂ per visit
5.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.43 g of CO₂e: 651.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
8 text elements with low contrast
8 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.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (5 elements).
1 checks passed
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 3 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 (25 characters)
Your title is only 25 characters: “Dose - Liquid Supplements”. Between 30 and 65 characters leaves room to say what you do and for whom.
55 internal links, 7 external
The homepage links to 55 pages on dosedaily.co and 7 external pages.
7 checks passed
Meta description: 134 characters
Your meta description is 134 characters: “Dose offers science-backed liquid supplements to support your body’s health core systems and overall wellness with prov…”.
One H1 headline
Your main headline reads: “Dose”.
Canonical URL set
The canonical URL is https://dosedaily.co/.
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://dosedaily.co/sitemap.xml.
AI search readiness
No llms.txt
There is no https://dosedaily.co/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,434 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://dosedaily.co/pages/formulations has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://dosedaily.co/pages/clinical-study and https://dosedaily.co/pages/reviews have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 25 found) and read each the way a search engine does.
5 checks passed
Linked pages load
8 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 8 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://ad.ipredictive.com/d/track/event?upid=117502&url=https%3A%2F%2Fdosedaily.co%2F&cust=&tn=&val=&cuid=38c1c055-3c46-4aa4-9609-8b158ed6b317&cache_buster=1793771195400&ps=2.
7 small tap targets
7 of 25 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.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
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 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 686 words of copy
The homepage carries about 686 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 LIVER” and “SHOP CHOLESTEROL”.
7 calls to action
The homepage has 7 calls to action, for example “Shop Now”, “Shop Liver” and “Shop Cholesterol”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 52 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Mixpanel.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
15 trackers load before any consent
15Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 10 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.
59 cookies set on arrival
59Opening the homepage sets 59 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.
91 other companies contacted
Loading the homepage contacts 91 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 dosedaily.co, 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
- Segment | Mixpanel
- Hosting
- Shopify
Company
- Headquarters
- Los Angeles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on dosedaily.co, including 17 speed issues and 1 SEO issue. 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.