shopthryfty.com website review

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

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

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

8 third-party services load with your homepage (alia-prod.com, heatmap.com and Yotpo and others), adding 1.5 MB and 749 ms of main-thread time.

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

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

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

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

Shopify costs a phone 44 ms of main-thread work and 758 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 46 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.

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

Polyfills for old browsers add 29 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.

2 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Model is wearing size 20”.

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

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

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

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

Your homepage downloads 5.5 MB in 365 requests on a phone: images 2.6 MB (47), scripts 1.2 MB (81) and other files 1.1 MB (194). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Everyday_Stack_Polished_Steel_93.png at 390 px wide, shown at 48 px. Resized copies would save about 49 KiB.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

1 dropdown has no label.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

button, link, and menuitem elements do not have accessible names. (1 element).

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

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is only 16 characters: “Thryfty Detroit®”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 53 characters: “Real deal jewelry. Made for the future of streetwear.”. 70 to 160 characters is enough to sell the click.

The homepage links to 121 pages on shopthryfty.com and 8 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.thryftydetroit.com/collections/all, https://www.thryftydetroit.com/pages/reviews, https://www.thryftydetroit.com/pages/about-us, https://www.thryftydetroit.com/collections/the-mobs-picks, https://www.thryftydetroit.com/collections/new-arrivals and https://www.thryftydetroit.com/collections/sets and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.thryftydetroit.com/pages/reviews and https://www.thryftydetroit.com/pages/about-us have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.thryftydetroit.com/collections/all took over 3 s to send its HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://ws.heatmap.com/record/handshake' from origin 'https://www.thryftydetroit.com' has been bloc…”.

The homepage carries about 308 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity 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 37 cookies, 2 of them by other companies (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.