quotrell.com website review

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

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

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

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

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

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

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

About 67 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.

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

11 KiB could be saved by minifying CSS.

6 third-party services load with your homepage (visually-io.com, Shopify and JSDelivr CDN and others), adding 304 KiB and 60 ms of main-thread time.

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 “Fall Winter '26”.

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

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

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

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

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

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

Your homepage downloads 2.9 MB in 116 requests on a phone: images 2.0 MB (65), scripts 469 KiB (32) and fonts 247 KiB (3). Under 2 MB keeps phones on slow connections fast.

IMG_9021.webp 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).

3 images (453 KiB) 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 0.83 g of CO₂e: 99.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

12 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

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

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

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

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/logo-quotrell_762097e6-1539-4d35-92af-7135c…”.

1 link has no real href, so search engines can't follow it.

The homepage links to 580 pages on quotrell.com and 12 external pages.

/collections/giftcards, /collections/men-all-tops, /collections/men-longsleeve, /collections/men-knitwear, /collections/outerwear-men and /collections/hoodies-men took over 3 s to send their HTML from our server.

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

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

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

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 1,022 words of visible text.

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