maatshi.com website review

11 images could be 316 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

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

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

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

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

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

6 third-party services load with your homepage (Shopify, Mailchimp and avada.io and others), adding 668 KiB and 151 ms of main-thread time.

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

About 58 KiB of JavaScript is downloaded but never used on this page.

About 47 KiB of CSS is downloaded but never applied on this page.

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

Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

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.

3 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Festive Salwar Suits”.

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

Real visitors wait 832 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Scripts block taps and scrolling for 222 ms in total while the page loads. Good is under 200 ms.

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

Your homepage downloads 11.9 MB in 295 requests on a phone: media 8.6 MB (2), images 1.6 MB (48) and other files 927 KiB (82). Under 2 MB keeps phones on slow connections fast.

DD10Z001a_05374c13-2f25-40f2-b766-3c0eacb774e3.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).

2 images further down the page (43 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.37 g of CO₂e: 404.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

2 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

22 visible links have no text or label, so screen readers cannot say where they go.

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Your meta description is 207 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 275 pages on maatshi.com and 14 external pages.

Your Organization JSON-LD is missing 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.

There is no https://www.maatshi.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.

https://www.maatshi.com/pages/new-arrivals, https://www.maatshi.com/collections/co-ord-sets, https://www.maatshi.com/collections/two-piece-sets-by-maatshi, https://www.maatshi.com/collections/salwar-suits-by-maatshi, https://www.maatshi.com/collections/cotton-salwar-suits and https://www.maatshi.com/collections/chanderi-salwar-suits-by-maatshi and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.maatshi.com/pages/new-arrivals, https://www.maatshi.com/collections/co-ord-sets, https://www.maatshi.com/collections/two-piece-sets-by-maatshi, https://www.maatshi.com/collections/salwar-suits-by-maatshi, https://www.maatshi.com/collections/cotton-salwar-suits and https://www.maatshi.com/collections/chanderi-salwar-suits-by-maatshi and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.maatshi.com/pages/new-arrivals, https://www.maatshi.com/collections/two-piece-sets-by-maatshi and https://www.maatshi.com/collections/salwar-suits-by-maatshi took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://www.maatshi.com/.

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

Large scripts ship without source maps.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 686 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 9 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.