thrills.co website review

17 images could be 612 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

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

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

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

About 79 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

8 third-party services load with your homepage (Klaviyo, Clarity and Shopify and others), adding 587 KiB and 506 ms of main-thread time.

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

Klaviyo costs a phone 205 ms of main-thread work and 312 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 163 KiB of JavaScript is downloaded but never used on this page.

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

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

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

8 KiB JavaScript is shipped twice across bundles.

6 KiB could be saved by minifying JavaScript.

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 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

Your homepage downloads 5.0 MB in 256 requests on a phone: images 2.8 MB (60), other files 1.2 MB (98) and scripts 787 KiB (84). Under 2 MB keeps phones on slow connections fast.

M-DOUBLE-D_b984acf3-fec5-419e-bb58-26020b93641a.jpg 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).

2 images further down the page (42 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

Interactive controls must not be nested: 22 elements on the page fail this check, rated serious by axe-core.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.

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

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

Your title is 81 characters, so Google will cut it off around 60: “Thrills Official: Mens & Womens Streetwear | Byron Bay Fashion Brand – THRILLS CO”.

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

The homepage links to 346 pages on thrills.co and 4 external pages.

https://thrills.co/collections/new-arrivals-womens, https://thrills.co/collections/womens-tees, https://thrills.co/collections/womens-hoodies-fleece, https://thrills.co/collections/womens-jackets, https://thrills.co/collections/womens-shirts and https://thrills.co/collections/womens-denim and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://d19ayerf5ehaab.cloudfront.net/css/product-widget/style.css' from origin 'https://t…”.

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

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