prashantisarees.com website review

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

Your mobile performance score is 77 (desktop: 95). Pages that score under 90 lose visitors before the first paint.

22 images could be 781 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

cashfree.com costs a phone 84 ms of main-thread work and 519 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.

8 third-party services load with your homepage (Shopify, cashfree.com and openai.com and others), adding 706 KiB and 329 ms of main-thread time.

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

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

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.

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

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Prashanti Online is now Shipping from the USA”.

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

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

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

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

Your homepage downloads 3.6 MB in 189 requests on a phone: images 2.1 MB (39), other files 689 KiB (77) and scripts 472 KiB (59). Under 2 MB keeps phones on slow connections fast.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 82 characters, so Google will cut it off around 60: “Prashanti | Traditional & Contemporary sarees for today's women – Prashanti Sarees”.

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

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("//www.prashantisarees.com/cdn/shop/files/Prashanti-Logo…”.

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

The homepage links to 508 pages on prashantisarees.com and 23 external pages.

https://www.prashantisarees.com/en-us and / all use the title “Prashanti | Traditional & Contemporary sarees for today's women – Pra…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.prashantisarees.com/en-us/pages/whats-new, https://www.prashantisarees.com/en-us/collections/kanchipuram-exclusive-silk-sarees, https://www.prashantisarees.com/en-us/collections/pure-zari-in-bridal-kanchipurams, https://www.prashantisarees.com/en-us/collections/kora-kanchipuram-silk-sarees, https://www.prashantisarees.com/en-us/collections/silk-9-yards and https://www.prashantisarees.com/en-us/collections/dhoti-shirt-combo and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.prashantisarees.com/en-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/, https://www.prashantisarees.com/en-us/pages/whats-new, https://www.prashantisarees.com/en-us/collections/kanjivaram-silk-sarees, https://www.prashantisarees.com/en-us/collections/budget-kanchipurams and https://www.prashantisarees.com/en-us/collections/silk-sarees have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was 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.

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.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage has only about 45 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

Before a visitor clicks anything, the page loads 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 11 cookies, 7 of them by other companies (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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.