lebent.ca website review

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

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

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

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

8 third-party services load with your homepage (Klaviyo, boostcommerce.io and Shopify and others), adding 1.0 MB and 435 ms of main-thread time.

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

Shopify costs a phone 74 ms of main-thread work and 315 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 80 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.

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

About 198 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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.

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

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Le Bent CA”.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.5 MB in 291 requests on a phone: images 2.1 MB (54), scripts 953 KiB (97) and other files 948 KiB (104). Under 2 MB keeps phones on slow connections fast.

59756158-89e9-46d7-9cc6-8f1f00ea4a5e.png weighs 1.2 MB. On a phone connection a single image that size takes seconds.

1 image (1.2 MB) 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.

Base_Layer_CAT.jpg 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).

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

Your hreflang tags are invalid, so Google may show the wrong language version.

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

Your <h1> is empty.

The homepage links to 231 pages on lebent.ca and 17 external pages.

There is no https://www.lebent.ca/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.lebent.ca/blogs/news has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lebent.ca/pages/contact-us, https://www.lebent.ca/collections/socks-snow and https://www.lebent.ca/collections/socks-all-season have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Boost > [ERROR] Cart icon selector not found in matched config”.

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.

The homepage carries about 572 words of visible text.

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