envagor.com website review

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

Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

138 files are served with short cache lifetimes, so returning visitors download them again (45.0 MB).

4 images could be 163 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.

7 third-party services load with your homepage (Google Tag Manager, WordPress and Facebook and others), adding 1.1 MB and 454 ms of main-thread time.

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

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

Google Tag Manager costs a phone 237 ms of main-thread work and 453 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.

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

WordPress costs a phone 114 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.

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

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

31 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Envagor banner- Sakshi (34)”.

The layout shifts by 0.487 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

The first text or image appears after 2.7 s on a phone. Good is under 1.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 46.6 MB in 190 requests on a phone: media 44.8 MB (8), scripts 1.1 MB (85) and images 415 KiB (12). Under 2 MB keeps phones on slow connections fast.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

The homepage links to 69 pages on envagor.com and 13 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://envagor.com/shop-page/swoof/price-149-to-999 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://envagor.com/shop-page and https://envagor.com/shop-page/swoof/price-149-to-999 all use the title “Envagor® Shop | Oversized T-Shirts, Denims, Plazzos & Perfumes”. Search engines can't tell which page to show for a search, so each competes with the others.

https://envagor.com/shop, https://envagor.com/product/mens-graphic-t-shirt-thinking-print, https://envagor.com/product/baggy-denim-white-jeans-dripp-series, https://envagor.com/product/baggy-denim-grey-jeans-dripp-series, https://envagor.com/product/plazzo-cling-series-mango and https://envagor.com/product/plazzo-sena-series-brown and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://envagor.com/shop-page and https://envagor.com/shop-page/swoof/price-149-to-999 use the same meta description. A description written for each page earns more clicks.

https://envagor.com/shop-page, https://envagor.com/perfume, https://envagor.com/women, https://envagor.com/men, https://envagor.com/shop-page/swoof/price-149-to-999 and https://envagor.com/about-us have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

Social proof on the homepage: 19 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 363 words of visible text.

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