Website review, no card needed
manduka.com website review
Visit site (opens in a new tab)Reviewed 5 November 202632 issues · 84 checks
This review found 32 issues worth fixing on manduka.com, 11 of them high impact, across 84 checks. The most urgent: page weight: 6.3 MB in 397 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
85B- #14,493 of 105,835 reviewed websitesbeats 82%
- #9,175 of 59,562 online storesbeats 79%
- #8,922 of 54,287 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 190 ms |
| May 23, 2026 | 189 ms |
| May 30, 2026 | 189 ms |
| Jun 6, 2026 | 195 ms |
| Jun 13, 2026 | 196 ms |
| Jun 20, 2026 | 196 ms |
| Jun 27, 2026 | 203 ms |
| Jul 4, 2026 | 203 ms |
| Jul 11, 2026 | 202 ms |
| Jul 18, 2026 | 203 ms |
| Jul 25, 2026 | 199 ms |
| Aug 1, 2026 | 196 ms |
| Aug 8, 2026 | 193 ms |
| Aug 15, 2026 | 189 ms |
| Aug 22, 2026 | 189 ms |
| Aug 29, 2026 | 191 ms |
| Sep 5, 2026 | 188 ms |
| Sep 12, 2026 | 184 ms |
| Sep 19, 2026 | 180 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 181 ms |
| Oct 10, 2026 | 187 ms |
| Oct 17, 2026 | 189 ms |
| Oct 24, 2026 | 195 ms |
| Oct 31, 2026 | 196 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.0 s
2.0 s
2.9 s
3.9 s
4.9 s
5.9 s
6.8 s
7.8 s
Speed
Main-thread work: 6.0 s
A phone's processor spends 6.0 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,067 HTML elements
The page has 3,067 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 (Google Tag Manager, negate.io and rebuyengine.com and others), adding 2.8 MB and 1.7 s of main-thread time.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
996 KiBAbout 996 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
950 ms20 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Google Tag Manager adds 545 ms
545 msGoogle Tag Manager costs a phone 545 ms of main-thread work and 679 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
602 KiB19 images could be 602 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
rebuyengine.com adds 242 ms
242 msrebuyengine.com costs a phone 242 ms of main-thread work and 1.1 MB 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 316 ms
316 msnegate.io costs a phone 316 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.
Klaviyo adds 123 ms
123 msKlaviyo costs a phone 123 ms of main-thread work and 314 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 85 ms
85 msShopify costs a phone 85 ms of main-thread work and 364 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 197 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
132 KiB17 files are served with short cache lifetimes, so returning visitors download them again (132 KiB).
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
48 KiBPolyfills for old browsers add 48 KiB JavaScript that modern phones do not need.
Reduce unused CSS
16 KiBAbout 16 KiB of CSS is downloaded but never applied on this page.
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: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 29.5 s
29.5 sThe page becomes fully interactive after 29.5 s. Good is under 3.8 s.
Largest Contentful Paint: 8.3 s
8.3 sYour largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Woman balancing in an arm balance yoga pose on a Manduka yo…”.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 634 ms
634 msScripts block taps and scrolling for 634 ms in total while the page loads. Good is under 200 ms.
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.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 190 ms to 196 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 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: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 487 ms
487 msReal visitors wait 487 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.3 MB in 397 requests
6.3 MBYour homepage downloads 6.3 MB in 397 requests on a phone: scripts 2.2 MB (122), images 2.2 MB (58) and other files 1.2 MB (146). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
55 KiB3 images are downloaded at several times the size a phone draws them, for example Best_Sellers_58e53070-f777-49db-be61-cb522f8ce726.jpg at 600 px wide, shown at 175 px. Resized copies would save about 55 KiB.
2 images in older formats
2 images (66 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 (41 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.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.79 g of CO₂e: 214.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
ARIA commands must have an accessible name (2 elements)
ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
11 images without alt text
11 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (175 characters)
Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.
299 internal links, 11 external
The homepage links to 299 pages on manduka.com and 11 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Hot Yoga Starts Here”.
Title: 44 characters
Your title is a healthy 44 characters: “Premium Yoga Mats, Gear & Clothing | Manduka”.
Canonical URL set
The canonical URL is https://www.manduka.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://www.manduka.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.manduka.com/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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,599 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://www.manduka.com/collections/all and https://www.manduka.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.manduka.com/collections/all, https://www.manduka.com/policies/shipping-policy, https://www.manduka.com/pages/lets-partner-manduka, https://www.manduka.com/pages/manduka-teacher-programs and https://www.manduka.com/pages/hotel-spa-equipment-program 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 122 found) and read each the way a search engine does.
5 checks passed
Linked pages load
5 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 5 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 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
95 of 115 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 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 875 words of copy
The homepage carries about 875 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “shop now”.
8 calls to action
The homepage has 8 calls to action, for example “Shop All”, “Shop All Last Chance” and “Contact Us”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Ads and 1 more (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 (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.
53 other companies contacted
Loading the homepage contacts 53 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 manduka.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 18 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · Geo Pro Geolocation · Consentmo Gdpr · Attentive · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · Rebuy Personalization Engine · Microsoft Clarity · Gorgias Live Chat Helpdesk · Region Restrictions · Easylocation · Gdpr Backpack · Countdown Timer · hulkapps.com · cloudfront.net · attn.tv · googleapis.com · 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
- jQuery
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- El Segundo
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on manduka.com, including 18 speed issues, 1 SEO issue 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.