theextremecollection.com website review

The page goes through 1 redirect before it starts loading, costing about 8.7 s. Link and advertise the final URL directly.

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and chatty.net and others), adding 783 KiB and 553 ms of main-thread time.

Shopify costs a phone 206 ms of main-thread work and 322 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.

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

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

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

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

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

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

4 KiB could be saved by minifying JavaScript.

Your largest element takes 15.7 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 16.7 s. Good is under 3.8 s.

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

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

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

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

8 images weigh 9.4 MB together. On a phone connection a single image that size takes seconds.

21 images are downloaded at several times the size a phone draws them, for example ChatGPT-Image-Sep-22-2026-03_04_56-PM.png at 1,121 px wide, shown at 326 px. Resized copies would save about 7.0 MB.

21 images (12.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.

20 images further down the page (11.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

Your homepage downloads 3.7 MB in 450 requests on a phone: other files 1.4 MB (274), scripts 1.3 MB (137) and images 677 KiB (18). Under 2 MB keeps phones on slow connections fast.

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

Images must have alternative text: 7 elements on the page fail this check, rated critical by axe-core.

Some list items are not inside a list.

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: 21 elements on the page fail this check, rated moderate by axe-core.

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

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

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

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

The homepage links to 48 pages on theextremecollection.com and 1 external page.

The HTML your server sends has 296 of the 720 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://theextremecollection.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://theextremecollection.com/pages/nuestro-club, https://theextremecollection.com/pages/personal-shopper, https://theextremecollection.com/pages/guante-blanco, https://theextremecollection.com/customer_authentication/redirect and https://theextremecollection.com/pages/porsche-experience are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://theextremecollection.com/pages/nuestro-club, https://theextremecollection.com/pages/personal-shopper, https://theextremecollection.com/pages/guante-blanco and https://theextremecollection.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://theextremecollection.com/collections/blazer, https://theextremecollection.com/collections/blazer-militar, https://theextremecollection.com/collections/punto, https://theextremecollection.com/collections/johanna-ortiz-x-the-extreme-collection, https://theextremecollection.com/collections/trajes-atelier and https://theextremecollection.com/collections/pantalones and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

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.

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

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