trueclassictees.com website review

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

getpurpledot.com costs a phone 1.3 s of main-thread work and 157 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (getpurpledot.com, Google Tag Manager and Shopify and others), adding 2.5 MB and 2.9 s of main-thread time.

About 1.2 MB of JavaScript is downloaded but never used on this page.

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

12 images could be 780 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Shopify costs a phone 263 ms of main-thread work and 562 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 258 ms of main-thread work and 551 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.

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

33 KiB could be saved by minifying JavaScript.

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

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.

3 KiB JavaScript is shipped twice across bundles.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

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

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

Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 296 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

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

Your homepage downloads 9.7 MB in 583 requests on a phone: scripts 3.5 MB (236), media 2.5 MB (1) and images 2.0 MB (69). Under 2 MB keeps phones on slow connections fast.

funny-johnson-sad-trimmed.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 is downloaded at several times the size a phone draws it, for example funny-johnson-sad-trimmed.png at 1,000 px wide, shown at 281 px. Resized copies would save about 18 KiB.

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

Your title is 68 characters, so Google will cut it off around 60: “Best High Quality, Soft, Slim Fitted T-Shirts for Men - True Classic”.

There are 2 <h1> headlines (“True Classic” and “Classic Crew Neck”). One clear main headline is easier for people and search engines.

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

Structured data found (Organization, ProductGroup and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://www.trueclassictees.com https://www.trueclassictees.com/search?q=…”.

The homepage links to 182 pages on trueclassictees.com and 15 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.

There is no https://www.trueclassictees.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.trueclassictees.com/pages/contact, https://www.trueclassictees.com/pages/deals-discounts, https://www.trueclassictees.com/pages/womens-clothing, https://www.trueclassictees.com/pages/kids-clothing and https://www.trueclassictees.com/pages/live-streaming/live have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.trueclassictees.com/pages/womens-clothing, https://www.trueclassictees.com/pages/kids-clothing, https://www.trueclassictees.com/pages/live-streaming/live and https://www.trueclassictees.com/pages/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 124 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://www.trueclassictees.com/.

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

6 errors were logged to the browser console while the page loaded, for example “Illegal return statement”.

Requests the notification permission on page load.

The homepage carries about 445 words of visible text.

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