deathiseasy.com website review

The page goes through 4 redirects before it starts loading, costing about 14.6 s. Link and advertise the final URL directly.

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

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

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

8 third-party services load with your homepage (Shopify, vitals.app and Google Tag Manager and others), adding 1.7 MB and 771 ms of main-thread time.

The HTML itself could arrive about 400 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

vitals.app costs a phone 281 ms of main-thread work and 739 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,809 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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

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

8 KiB JavaScript is shipped twice across bundles.

1 image could be 6 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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 22.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

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 5.0 MB in 583 requests on a phone: scripts 2.8 MB (299), other files 1.1 MB (226) and images 493 KiB (19). Under 2 MB keeps phones on slow connections fast.

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

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

1 link has no text or label, so screen readers cannot say where it goes.

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

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

The homepage links to 89 pages on deathiseasy.com and 2 external pages.

https://deathiseasy.com/collections/drop, https://deathiseasy.com/collections/woman-all, https://deathiseasy.com/collections/t-shirt, https://deathiseasy.com/collections/hoodie-1, https://deathiseasy.com/collections/sweater-1 and https://deathiseasy.com/collections/jackets and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://deathiseasy.com/collections/shorts/Shorts, whose canonical is https://deathiseasy.com/collections/shorts/shorts. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://deathiseasy.com/collections/drop, https://deathiseasy.com/collections/woman-all, https://deathiseasy.com/collections/t-shirt, https://deathiseasy.com/collections/hoodie-1, https://deathiseasy.com/collections/sweater-1 and https://deathiseasy.com/collections/jackets and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://deathiseasy.com/collections/jackets, https://deathiseasy.com/collections/shorts/Shorts and https://deathiseasy.com/collections/t-shirt-1 took over 3 s to send their HTML from our server.

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

13 errors were logged to the browser console during Google's test (“Error producing monorail event MonorailUnableToProduceError: Error producing to the Monorail Edge. …”).

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 297 words of visible text.