Website review, no card needed
vitamedica.com website review
Visit site (opens in a new tab)Reviewed 10 November 202641 issues · 84 checks
This review found 41 issues worth fixing on vitamedica.com, 13 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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
73C- #89,144 of 120,386 reviewed websitesbeats 22%
- #55,831 of 68,161 online storesbeats 15%
- #52,301 of 62,115 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
| Nov 7, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 148 ms |
| May 30, 2026 | 145 ms |
| Jun 6, 2026 | 150 ms |
| Jun 13, 2026 | 161 ms |
| Jun 20, 2026 | 163 ms |
| Jun 27, 2026 | 165 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 159 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 162 ms |
| Aug 1, 2026 | 163 ms |
| Aug 8, 2026 | 169 ms |
| Aug 15, 2026 | 166 ms |
| Aug 22, 2026 | 156 ms |
| Aug 29, 2026 | 160 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 157 ms |
| Sep 26, 2026 | 159 ms |
| Oct 3, 2026 | 156 ms |
| Oct 10, 2026 | 165 ms |
| Oct 17, 2026 | 162 ms |
| Oct 24, 2026 | 154 ms |
| Oct 31, 2026 | 155 ms |
| Nov 7, 2026 | 153 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.2 s
2.5 s
3.7 s
5.0 s
6.2 s
7.5 s
8.7 s
10.0 s
Speed
Reduce unused JavaScript
4.6 s · 844 KiBAbout 844 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.6 s faster on a phone.
Use efficient cache lifetimes
1.8 s · 383 KiB29 files are served with short cache lifetimes, so returning visitors download them again (383 KiB).
Render-blocking requests
1.1 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.1 s
A phone's processor spends 7.1 s on main-thread work while loading, 2.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, negate.io and cometlytrack.com and others), adding 1.6 MB and 1.3 s of main-thread time.
Reduce unused CSS
300 ms · 93 KiBAbout 93 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 293 ms
293 msGoogle Tag Manager costs a phone 293 ms of main-thread work and 371 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.
negate.io adds 256 ms
256 msnegate.io costs a phone 256 ms of main-thread work and 40 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.
Shopify adds 124 ms
124 msShopify costs a phone 124 ms of main-thread work and 515 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.
reamaze.com adds 130 ms
130 msreamaze.com costs a phone 130 ms of main-thread work and 317 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.
Klaviyo adds 107 ms
107 msKlaviyo costs a phone 107 ms of main-thread work and 350 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.
Legacy JavaScript
200 ms · 43 KiBPolyfills for old browsers add 43 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 168 ms. During a long task the page ignores taps.
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.
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.36
0.36For real visitors the layout shifts by 0.36 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 18.9 s
18.9 sYour largest element takes 18.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 21.7 s
21.7 sThe page becomes fully interactive after 21.7 s. Good is under 3.8 s.
Speed Index: 11.0 s
11.0 sVisually, the page fills in at 11.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Real-user TTFB: 884 ms
884 msReal visitors wait 884 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 383 ms
383 msScripts block taps and scrolling for 383 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.127
0.127The layout shifts by 0.127 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 148 ms to 153 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 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 FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 4.2 MB in 441 requests
4.2 MBYour homepage downloads 4.2 MB in 441 requests on a phone: scripts 2.1 MB (115), other files 1.4 MB (276) and fonts 234 KiB (9). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (742 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.
3 images below the first screen load straight away
3 images further down the page (604 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.19 g of CO₂e: 143.0 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
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
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. (1 element).
2 checks passed
Every image has alt text
All 31 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “VitaMedica Clear Skin, Wellness, Recovery, & Anti-Aging Supplements”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (10 characters)
Your meta description is only 10 characters: “VitaMedica”. 70 to 160 characters is enough to sell the click.
2 H1 headlines
There are 2 <h1> headlines (“VitaMedica” and “VitaMedica”). One clear main headline is easier for people and search engines.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
70 internal links, 11 external
The homepage links to 70 pages on vitamedica.com and 11 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://vitamedica.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://vitamedica.com/sitemap.xml.
AI search readiness
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.
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 (568 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://vitamedica.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
8 pages share a meta description
https://vitamedica.com/collections/all, https://vitamedica.com/collections/recovery-solutions, https://vitamedica.com/collections/clear-skin-for-acne, https://vitamedica.com/collections/feel-great, https://vitamedica.com/collections/all-products and https://vitamedica.com/blogs/blog and 2 others use the same meta description. A description written for each page earns more clicks.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://vitamedica.com/collections/best-sellers/products/anti-aging-formula, whose canonical is https://vitamedica.com/products/anti-aging-formula. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://vitamedica.com/pages/about-us and https://vitamedica.com/pages/wholesale have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://vitamedica.com/collections/recovery-solutions and https://vitamedica.com/collections/feel-great took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).
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_CONNECTION_RESET”.
2 checks passed
Tap targets are thumb-sized
8 of 9 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 383 words of copy
The homepage carries about 383 words of visible text.
5 checks passed
14 calls to action
The homepage has 14 calls to action, for example “Shop”, “Shop All” and “Register / Login”.
18 short forms
18 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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.
30 cookies set on arrival
30Opening the homepage sets 30 cookies, 2 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.
47 other companies contacted
Loading the homepage contacts 47 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 vitamedica.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 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · Reamaze Live Chat Helpdesk · Powerful Form Builder · Klaviyo Email Marketing Sms · Region Restrictions · Preorder Manager · Koala Upsell Gift · Upsell Koala Discount · rechargecdn.com · loox.io · trafficmanager.net · rakutenadvertising.io · vitamedica.com · metorik.com · rebuyengine.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
- The footer still says © 2025.
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on vitamedica.com, including 21 speed issues, 5 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.