trendiadecor.com website review

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

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

13 images could be 603 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

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

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

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

About 110 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

About 79 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.

6 third-party services load with your homepage (Shopify, crowai.co and Judge.me and others), adding 378 KiB and 65 ms of main-thread time.

1 long task block the main thread while loading, the longest for 53 ms. During a long task the page ignores taps.

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

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 JavaScript is shipped twice across bundles.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.0 MB in 311 requests on a phone: images 2.0 MB (33), other files 1.3 MB (209) and scripts 554 KiB (46). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Dresses_1_2.jpg at 360 px wide, shown at 113 px. Resized copies would save about 13 KiB.

1 image (73 KiB) is 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.

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

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

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

1 element hidden from screen readers can still receive keyboard focus.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

6 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 70 characters, so Google will cut it off around 60: “Trendia Express | Indian Ethnic Wear | Guaranteed 2–5 Biz Day Delivery”.

Your meta description is 274 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.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 119 pages on trendiadecor.com and 5 external pages.

https://www.trendiadecor.com/collections/women-kurta-sets, https://www.trendiadecor.com/collections/women-dresses, https://www.trendiadecor.com/collections/women-blouses, https://www.trendiadecor.com/collections/women-co-ord-sets, https://www.trendiadecor.com/collections/women-kurtas and https://www.trendiadecor.com/collections/all-decor-products and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.trendiadecor.com/collections/women-kurta-sets, https://www.trendiadecor.com/collections/all-decor-products, https://www.trendiadecor.com/collections/women-clothing and https://www.trendiadecor.com/collections/women-anarkali-sets have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load module script: Expected a JavaScript-or-Wasm module script but the server responded with a MIME type of …”.

Large scripts ship without source maps.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage carries about 470 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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