lacolombe.com website review

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

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

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

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

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

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

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

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

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

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

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

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

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

18 KiB JavaScript is shipped twice across bundles.

11 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.

2 KiB could be saved by minifying CSS.

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

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

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

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

The layout shifts by 0.119 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Scripts block taps and scrolling for 230 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' largest content (lcp) went from 1.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 16.5 MB in 462 requests on a phone: media 10.8 MB (2), images 2.4 MB (83) and scripts 1.8 MB (146). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example PDPAlt1_TAN_12OZ_BOX_ALLDARK.png at 800 px wide, shown at 184 px. Resized copies would save about 81 KiB.

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

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

There are 2 <h1> headlines (“Peppermint Mocha is Home for the Holidays” and “Bestsellers”). One clear main headline is easier for people and search engines.

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

2 links have no real href, so search engines can't follow them.

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

The homepage links to 196 pages on lacolombe.com and 19 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.lacolombe.com/collections/member-pricing has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lacolombe.com/collections/coffee, https://www.lacolombe.com/collections/coffee/coffee-blends, https://www.lacolombe.com/collections/coffee/decaf, https://www.lacolombe.com/collections/coffee/organic, https://www.lacolombe.com/collections/coffee/single-origin-coffee and https://www.lacolombe.com/collections/coffee/dark and 2 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.lacolombe.com/collections/all-products/NewArrival, whose canonical is https://www.lacolombe.com/collections/all-products/newarrival. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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

Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 34 cookies (measured from a US location before any click).

Loading the homepage contacts 63 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.