qforquinn.ca website review

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

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

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

8 third-party services load with your homepage (Shopify, upstackified.com and Klaviyo and others), adding 2.7 MB and 1.3 s of main-thread time.

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

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

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

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

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

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

Klaviyo costs a phone 186 ms of main-thread work and 333 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.

cloudfront.net costs a phone 126 ms of main-thread work and 857 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 63 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.

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

15 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 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Q for Quinn brand logo in dark grey on white background | Q…”.

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

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 147 ms to 188 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

5 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.7 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.2 MB in 321 requests on a phone: images 2.6 MB (62), scripts 1.7 MB (113) and other files 1.5 MB (122). Under 2 MB keeps phones on slow connections fast.

d03ec138-4878-4c0f-a147-07590bfc56aa.png weighs 785 KiB. On a phone connection a single image that size takes seconds.

gs-homepage-hero-mobile_4.png 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).

1 image (785 KiB) is 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 1.75 g of CO₂e: 209.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

3 elements hidden from screen readers can still receive keyboard focus.

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 314 pages on qforquinn.ca and 11 external pages.

Your homepage links to https://www.qforquinn.com/pages/underwear-fit-guide, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.qforquinn.com/collections/adult-bestsellers-1/Women, https://www.qforquinn.com/collections/all-adult/Women and https://www.qforquinn.com/collections/organic-cotton-womens-underwear/uw are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.qforquinn.com/pages/holiday-gift-guide and https://www.qforquinn.com/pages/adult-sock-size-chart have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.qforquinn.com/collections/adult-bestsellers-1 and https://www.qforquinn.com/collections/adult-bestsellers-1/Women use the same meta description. A description written for each page earns more clicks.

https://www.qforquinn.com/pages/shipping-and-returns, https://www.qforquinn.com/collections/adult-bestsellers-1, https://www.qforquinn.com/pages/holiday-gift-guide, https://www.qforquinn.com/collections/coming-soon, https://www.qforquinn.com/collections/adult-bestsellers-1/Women and https://www.qforquinn.com/collections/all-adult/Women 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 115 found) and read each the way a search engine does.

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

5 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 ()”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 1,068 words of visible text.

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