thrifted.com website review

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

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

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

221 files are served with short cache lifetimes, so returning visitors download them again (5.1 MB).

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

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

8 third-party services load with your homepage (JSDelivr CDN, Shopify and Klaviyo and others), adding 593 KiB and 732 ms of main-thread time.

JSDelivr CDN costs a phone 360 ms of main-thread work and 99 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.

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

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

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

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

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.

4 KiB could be saved by minifying CSS.

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.

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

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

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

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

Real visitors wait 258 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 153 ms to 293 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 16.6 MB in 536 requests on a phone: images 14.9 MB (329), other files 793 KiB (86) and scripts 627 KiB (83). Under 2 MB keeps phones on slow connections fast.

7 images are downloaded at several times the size a phone draws them, for example 632C5738-AF27-4DB7-B26E-154A20224501.webp at 1,024 px wide, shown at 174 px. Resized copies would save about 659 KiB.

40 images (5.0 MB) 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.

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

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

<svg> elements with an img or image role must have alternative text: 5 elements on the page fail this check, rated serious by axe-core.

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

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

1 element hidden from screen readers can still receive keyboard focus.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Structured data found (Organization, Store and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("www.thrifted.com")”.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 254 pages on thrifted.com and 13 external pages.

/community/faq, /pages/returns-quicklinks, /policies/shipping-policy, /policies/terms-of-service and /pages/mens-vintage have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/all, /pages/womens-vintage-homepage, /collections/accessories, /pages/about-us, /community/faq and /pages/contact and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/mens-vintage and /collections/all-vintage-tops-ts took over 3 s to send their HTML from our server.

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

10 images failed to load on a phone, for example https://raw.githubusercontent.com/msikma/country-flags/refs/heads/master/flags/png/io.png.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 410 ()”.

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

1 link go through two or more redirects, for example https://instagram.com/thrifted_com.

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.

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage carries about 770 words of visible text.

DMARC is set to p=none, so mail pretending to be thrifted.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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, Klaviyo and Meta Pixel and 1 more (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 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.