biggerthankiss.com website review

About 319 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

22 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

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

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

6 third-party services load with your homepage (Google Tag Manager, bandsintown.com and Shopify and others), adding 2.6 MB and 224 ms of main-thread time.

Unpkg costs a phone 3 ms of main-thread work and 1.8 MB 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.

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

Shopify costs a phone 16 ms of main-thread work and 485 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 18 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.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 25.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A white baseball with red stitching features Teenage Bottle…”.

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

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

The layout shifts by 0.264 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Your homepage downloads 6.1 MB in 141 requests on a phone: images 3.1 MB (35), scripts 2.4 MB (37) and other files 629 KiB (61). Under 2 MB keeps phones on slow connections fast.

12 images are downloaded at several times the size a phone draws them, for example 014cd7a3cfb84cd6be4faebf22b5e553_1500x1500.jpg at 1,500 px wide, shown at 346 px. Resized copies would save about 1.2 MB.

16 images further down the page (1.6 MB) 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.74 g of CO₂e: 209.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

<dt> and <dd> elements must be contained by a <dl>: 50 elements on the page fail this check, rated serious by axe-core.

<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 24 elements on the page fail this check, rated serious by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There are 2 <h1> headlines (“<img src="//biggerthankiss.com/cdn/shop/files/Log…” and “TOUR”). One clear main headline is easier for people and search engines.

The homepage links to 49 pages on biggerthankiss.com and 9 external pages.

https://biggerthankiss.com/collections/teenage-bottlerocket, https://biggerthankiss.com/collections/vintage-tees, https://biggerthankiss.com/collections/t-shirts, https://biggerthankiss.com/collections/hoodies, https://biggerthankiss.com/collections/accessories and https://biggerthankiss.com/collections/clearance and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://biggerthankiss.com/collections/vintage-tees/products/tnbrjackms-ts, https://biggerthankiss.com/collections/vintage-tees/products/tnbrologbl-ts and https://biggerthankiss.com/collections/vintage-tees/products/tnbrsodmsa-ts use the same meta description. A description written for each page earns more clicks.

Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://biggerthankiss.com/collections/2025-hoiday/products/tnbrrtrebr-bn, whose canonical is https://biggerthankiss.com/products/tnbrrtrebr-bn. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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.

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

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

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