80stees.com website review

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

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

About 722 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

Your mobile performance score is 63 (desktop: 69). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and loox.io and others), adding 1.3 MB and 773 ms of main-thread time.

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

12 images could be 277 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

19 KiB could be saved by minifying JavaScript.

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

Shopify costs a phone 47 ms of main-thread work and 344 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 41 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 long tasks block the main thread while loading, the longest for 117 ms. During a long task the page ignores taps.

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

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

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 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “This Is Boo Sheet T-Shirt”.

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

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

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

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

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

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

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

Your homepage downloads 3.5 MB in 285 requests on a phone: scripts 1.4 MB (80), other files 1.0 MB (148) and images 752 KiB (35). Under 2 MB keeps phones on slow connections fast.

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

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

9 links inside paragraphs rely on colour alone to stand out.

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

Alternative text of images should not be repeated as text: 48 elements on the page fail this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“Authentic 80s T‑Shirts & Retro Graphic Tees” and “Pick any 2.Save 10%.”). One clear main headline is easier for people and search engines.

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

1 link has no real href, so search engines can't follow it.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 1,702 pages on 80stees.com and 5 external pages.

/pages/catalog-faq, /collections/new-arrivals, /collections/80s-movies, /collections/jaws, /collections/top-gun and /collections/rocky 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 168 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5214473&Ver=2&mid=729fb0c3-a79a-42b5-8e54-4b7275d10d00&bo=1&sid=821c8940d2a711f1befcf9bff2c6b615&vid=821cc000d2a711f185cf931ce2850550&vids=1&msclkid=N&pi=918639831&lg=.

2 errors were logged to the browser console while the page loaded, for example “missing ) after argument list”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

3 links go through two or more redirects, for example https://www.80stees.com/checkout.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

80stees.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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