shirtz.cool website review

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

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

129 images could be 6.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

Klaviyo costs a phone 135 ms of main-thread work and 327 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.

7 third-party services load with your homepage (Klaviyo, Hotjar and Shopify and others), adding 946 KiB and 254 ms of main-thread time.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

12 KiB could be saved by minifying CSS.

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.

2 KiB could be saved by minifying JavaScript.

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

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

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 10.0 MB in 285 requests on a phone: images 8.6 MB (162), scripts 706 KiB (69) and fonts 278 KiB (9). Under 2 MB keeps phones on slow connections fast.

8 images (628 KiB) are 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.

39 images are downloaded at several times the size a phone draws them, for example EnchantedArtboard2.jpg at 390 px wide, shown at 126 px. Resized copies would save about 174 KiB.

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

3 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

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

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

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

Your title is only 11 characters: “Cool Shirtz”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 37 characters: “Only Cool Shirtz - Shipped Worldwide.”. 70 to 160 characters is enough to sell the click.

There are 8 <h1> headlines (“Cool Shirtz”, “EXPLORE THECOLLECTION” and “EXPLORE THE COLLECTION”). One clear main headline is easier for people and search engines.

The homepage links to 160 pages on shirtz.cool and 13 external pages.

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

https://shirtz.cool/collections/minecraft-x-very-cool, https://shirtz.cool/collections/minecraft-x-very-cool-tops, https://shirtz.cool/collections/minecraft-x-very-cool-bottoms, https://shirtz.cool/collections/minecraft-x-very-cool-accessories, https://shirtz.cool/collections/minecraft-x-very-cool-decor and https://shirtz.cool/collections/tops and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://shirtz.cool/collections/minecraft-x-very-cool, https://shirtz.cool/collections/minecraft-x-very-cool-tops, https://shirtz.cool/collections/minecraft-x-very-cool-bottoms, https://shirtz.cool/collections/minecraft-x-very-cool-accessories, https://shirtz.cool/collections/minecraft-x-very-cool-decor and https://shirtz.cool/collections/tops and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

Social proof on the homepage: 9 testimonial or review blocks. 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 574 words of visible text.

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