niceshirtthanks.com website review

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

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

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

90 images could be 26.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

8 third-party services load with your homepage (alia-prod.com, Clarity and Klaviyo and others), adding 27.8 MB and 1.1 s of main-thread time.

Shopify costs a phone 78 ms of main-thread work and 26.1 MB 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.

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

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

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

alia-prod.com costs a phone 301 ms of main-thread work and 921 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.

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

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

Clarity costs a phone 292 ms of main-thread work and 29 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.

Klaviyo costs a phone 201 ms of main-thread work and 508 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 long tasks block the main thread while loading, the longest for 190 ms. During a long task the page ignores taps.

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

7 KiB could be saved by minifying JavaScript.

6 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.

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

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

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

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

7 images 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 146 ms to 145 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.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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 32.5 MB in 624 requests on a phone: images 28.7 MB (139), other files 1.8 MB (264) and scripts 1.4 MB (171). Under 2 MB keeps phones on slow connections fast.

30 images are downloaded at several times the size a phone draws them, for example download_57911308-f6a6-434d-97a9-9c97d84ba550.png at 2,000 px wide, shown at 110 px. Resized copies would save about 6.6 MB.

21 images further down the page (6.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

Gallery_test_2_no_tape_and_glue.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image (74 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 9.21 g of CO₂e: 1105.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Images must have alternative text: 22 elements on the page fail this check, rated critical by axe-core.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 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.

Your title is 92 characters, so Google will cut it off around 60: “Nice Shirt, Thanks! – Request a Surprise, Create Your Own or Shop Tees – NICE SHIRT. THAN…”.

There are 2 <h1> headlines (“” and “Click the button to get a random Gallery shirt”). One clear main headline is easier for people and search engines.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 89 pages on niceshirtthanks.com and 16 external pages.

https://niceshirtthanks.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://niceshirtthanks.com/products/request-comfort-colors-t-shirt declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://niceshirtthanks.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://niceshirtthanks.com/products/request-comfort-colors-t-shirt all use the title “Nice Shirt, Thanks! – Request a Surprise, Create Your Own or Shop Tee…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://niceshirtthanks.com/customer_authentication/redirect, https://niceshirtthanks.com/policies/shipping-policy, https://niceshirtthanks.com/pages/about-us and https://niceshirtthanks.com/pages/the-closet have no meta description, so Google writes the search snippet from whatever text it finds.

https://niceshirtthanks.com/products/t-shirt, https://niceshirtthanks.com/products/request-independent-trading-hoodie and https://niceshirtthanks.com/products/request-independent-trading-crew-neck use the same meta description. A description written for each page earns more clicks.

https://niceshirtthanks.com/customer_authentication/redirect, https://niceshirtthanks.com/collections/gallery, https://niceshirtthanks.com/products/t-shirt, https://niceshirtthanks.com/products/create-heavy-blend-t-shirt, https://niceshirtthanks.com/products/request-independent-trading-hoodie and https://niceshirtthanks.com/products/request-independent-trading-crew-neck and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 errors were logged to the browser console while the page loaded, for example “Error: Product GTIN GTIN1 is invalid!”.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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 18 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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.