wearmandala.com website review

About 354 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

20 files are served with short cache lifetimes, so returning visitors download them again (304 KiB).

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.

32 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

8 third-party services load with your homepage (Facebook, Klaviyo and Accessibe Accessibility Overlay and others), adding 9.2 MB and 752 ms of main-thread time.

Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.

Shopify costs a phone 52 ms of main-thread work and 8.2 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.

A phone's processor spends 3.5 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Klaviyo costs a phone 170 ms of main-thread work and 367 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.

The page has 1,657 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

About 45 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

7 long tasks block the main thread while loading, the longest for 138 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

15 KiB could be saved by minifying JavaScript.

6 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 27.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Soft Stretch Wide Leg in Mauve”.

The page becomes fully interactive after 28.2 s. Good is under 3.8 s.

The first text or image appears after 7.0 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 104 ms to 157 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.9 MB in 360 requests on a phone: media 4.3 MB (4), images 4.2 MB (55) and other files 1.5 MB (145). Under 2 MB keeps phones on slow connections fast.

17 images are downloaded at several times the size a phone draws them, for example Scrub_One_Pocket_Pants_A_Joggers_RS_Shocking_Pink_Full-Body- at 1,890 px wide, shown at 52 px. Resized copies would save about 1.9 MB.

MD_Flare_Pants_Homepage_Desktop_GIF_V2.gif weighs 672 KiB. On a phone connection a single image that size takes seconds.

2 images (993 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 further down the page (419 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 3.38 g of CO₂e: 405.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

87 tap targets are too small or too close together to hit reliably with a finger.

24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Alternative text of images should not be repeated as text: 13 elements on the page fail this check, rated minor by axe-core.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 118 pages on wearmandala.com and 9 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://mandalascrubs.com/collections/all-womens-scrubs and https://mandalascrubs.com/collections/all-womens-classic-scrubs all use the title “Women's Scrubs | Mandala Scrubs”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mandalascrubs.com/collections/tops and https://mandalascrubs.com/collections/womens-scrub-pants have no meta description, so Google writes the search snippet from whatever text it finds.

https://mandalascrubs.com/collections/all-womens-scrubs and https://mandalascrubs.com/collections/all-womens-classic-scrubs use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://mandalascrubs.com/products/medical-compression-socks-15-20mmhg, whose canonical is https://mandalascrubs.com/products/medical-compression-socks-15-20mmhg-black. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://mandalascrubs.com/collections/womens-scrub-pants has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 54 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://d3k81ch9hvuctc.cloudfront.net/company/PCuL4n/images/8a6977bd-34e9-411b-bd37-db8f54d7a24f.png.

112 of 149 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 389 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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.

Opening the homepage sets 36 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 49 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.