quadlockcase.ca website review

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 19.2 MB and 1.5 s of main-thread time.

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

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

Google Tag Manager costs a phone 817 ms of main-thread work and 771 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 466 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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

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

2 KiB could be saved by minifying JavaScript.

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

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

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

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

Your largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website uses cookies to ensure you get the best experi…”. Most of its time is element render delay (2.4 s).

46 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' tap response (inp) went from 140 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 21.3 MB in 315 requests on a phone: media 17.6 MB (2), scripts 1.6 MB (72) and other files 1.2 MB (189). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example QL-WEB-0186_HomePageHype-Brand_Introduction_Reel_16x9_v2.00_ at 1,920 px wide, shown at 390 px. Resized copies would save about 91 KiB.

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

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

<svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

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

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

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

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

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

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

The homepage links to 213 pages on quadlockcase.ca and 27 external pages.

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

https://www.quadlockcase.ca/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.quadlockcase.ca/customer_authentication/redirect and https://www.quadlockcase.ca/collections/bundles have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.quadlockcase.ca/customer_authentication/redirect, https://www.quadlockcase.ca/products/cases-airpods, https://www.quadlockcase.ca/products/iphone-colored-cases, https://www.quadlockcase.ca/fr, https://www.quadlockcase.ca/collections/shop-marine and https://www.quadlockcase.ca/collections/shop-aviation have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://www.quadlockcase.ca/.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

4 images are served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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 26 cookies, 3 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.