Website review, no card needed
apothekary.com website review
Visit site (opens in a new tab)Reviewed 8 November 202651 issues · 88 checks
This review found 51 issues worth fixing on apothekary.com, 20 of them high impact, across 88 checks. The most urgent: shopify adds 1.0 s. 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- #112,315 of 118,152 reviewed websitesbeats 4%
- #65,649 of 67,126 online storesbeats 2%
- #60,124 of 61,204 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Shopify adds 1.0 s
1.0 sShopify costs a phone 1.0 s of main-thread work and 1.2 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.
Avoid multiple page redirects
1.1 sThe page goes through 1 redirect before it starts loading, costing about 1.1 s. Link and advertise the final URL directly.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.8 s
A phone's processor spends 8.8 s on main-thread work while loading, 4.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,010 HTML elements
The page has 4,010 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and Facebook and others), adding 2.8 MB and 2.4 s of main-thread time.
Reduce unused JavaScript
600 ms · 972 KiBAbout 972 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 959 KiB37 files are served with short cache lifetimes, so returning visitors download them again (959 KiB).
Google Tag Manager adds 658 ms
658 msGoogle Tag Manager costs a phone 658 ms of main-thread work and 577 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.
Render-blocking requests
450 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Reduce unused CSS
300 ms · 43 KiBAbout 43 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 339 ms. During a long task the page ignores taps.
shippedsuite.com adds 175 ms
175 msshippedsuite.com costs a phone 175 ms of main-thread work and 356 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
150 ms · 213 KiB10 images could be 213 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Legacy JavaScript
109 KiBPolyfills for old browsers add 109 KiB JavaScript that modern phones do not need.
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: 87 ms
87 msYour server sent the HTML in 87 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.
Largest Contentful Paint: 10.9 s
10.9 sYour largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Herbal drops styled as holiday gifts”.
Time to Interactive: 33.5 s
33.5 sThe page becomes fully interactive after 33.5 s. Good is under 3.8 s.
Speed Index: 10.9 s
10.9 sVisually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Real-user INP: 202 ms
202 msReal visitors wait 202 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
3 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 6.2 MB in 334 requests
6.2 MBYour homepage downloads 6.2 MB in 334 requests on a phone: scripts 2.9 MB (189), other files 1.8 MB (82) and images 785 KiB (31). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
f490f992e7362e61b3b08b623e1aff35aa360c02-1734x3015.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).
1 image far larger than shown
50 KiB1 image is downloaded at several times the size a phone draws it, for example b530212711c4194e41a9ba726721098fffda9a4e-698x686.png at 698 px wide, shown at 70 px. Resized copies would save about 50 KiB.
3 images below the first screen load straight away
3 images further down the page (132 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.76 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.76 g of CO₂e: 211.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Heading levels should only increase by one (2 elements)
Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.
62 form fields without a label
62 form fields have no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
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.
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 25 images in the HTML carry an alt attribute.
52 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: 52 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex”: Google is told not to list this page at all.
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
25 H1 headlines
There are 25 <h1> headlines (“The wait is over.”, “Give your mane a whole new character.” and “Plump up your summer skin”). One clear main headline is easier for people and search engines.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
76 internal links, 4 external
The homepage links to 76 pages on apothekary.com and 4 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://apothekary.com/.
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://apothekary.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 (1,269 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://apothekary.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
8 linked pages are broken
Your homepage links to https://apothekary.com/products/take-the-edge-off-legacy, https://apothekary.com/products/blissed-over-buzzed-set-legacy, https://apothekary.com/products/plump-it-up-legacy, https://apothekary.com/products/stop-your-wineing-legacy, https://apothekary.com/products/do-not-disturb-legacy and https://apothekary.com/products/chill-the-f-out-legacy and 2 others, which answer with an error. Visitors hit a dead end and search engines drop them.
6 pages without a title
https://apothekary.com/products/mane-character, https://apothekary.com/collections/new-arrivals, https://apothekary.com/pages/inside-scoop-spring-2023, https://apothekary.com/pages/introducing-take-the-edge-off, https://apothekary.com/collections/stress-reducing and https://apothekary.com/products/mind-over-matter have no <title>, so Google invents the link text in results.
6 linked pages hidden from search
https://apothekary.com/products/mane-character, https://apothekary.com/collections/new-arrivals, https://apothekary.com/pages/inside-scoop-spring-2023, https://apothekary.com/pages/introducing-take-the-edge-off, https://apothekary.com/collections/stress-reducing and https://apothekary.com/products/mind-over-matter are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
6 pages without a meta description
https://apothekary.com/products/mane-character, https://apothekary.com/collections/new-arrivals, https://apothekary.com/pages/inside-scoop-spring-2023, https://apothekary.com/pages/introducing-take-the-edge-off, https://apothekary.com/collections/stress-reducing and https://apothekary.com/products/mind-over-matter have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://apothekary.com/collections/new-arrivals, https://apothekary.com/pages/inside-scoop-spring-2023 and https://apothekary.com/collections/stress-reducing have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://apothekary.com/collections/stress-reducing and https://apothekary.com/products/mind-over-matter took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.
1 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343112799&tm=gtm002&Ver=2&mid=d513697b-eae3-46d9-8833-e32a7b7a3789&bo=1&sid=d0c7b6c0db1d11f1af16832205c3704a&vid=d0c7c530db1d11f199a11d30964f746b&vids=1&msclkid=N>m_.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Minified React error #421; visit https://reactjs.org/docs/error-decoder.html?invariant=421 for the full message or use …”.
2 checks passed
Tap targets are thumb-sized
186 of 193 tappable elements near the top are at least 24 px.
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 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 1,539 words of copy
The homepage carries about 1,539 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “START GIFTING” and “SHOP NOW”.
26 calls to action
The homepage has 26 calls to action, for example “Shop The Set”, “Learn More” and “Shop Now”.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 5 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.
36 cookies set on arrival
36Opening the homepage sets 36 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.
58 other companies contacted
Loading the homepage contacts 58 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 apothekary.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 · Okendo · Accessibly App · Stape Remix · glopal.com · snapchat.com · rechargecdn.com · afterpay.com · superfiliate-cdn.com · shippedsuite.com · cloudfront.net · postscript.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
Stack
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on apothekary.com, including 22 speed issues, 6 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.