kombisports.com website review

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

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

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

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

Google Tag Manager costs a phone 286 ms of main-thread work and 367 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.

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

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Facebook and others), adding 747 KiB and 475 ms of main-thread time.

Polyfills for old browsers add 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

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

For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.

Scripts block taps and scrolling for 320 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' tap response (inp) went from 128 ms to 148 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.5 MB in 101 requests on a phone: scripts 1,001 KiB (58), images 628 KiB (18) and fonts 445 KiB (1). Under 2 MB keeps phones on slow connections fast.

65cd222b2eaaaadbe78777d12df0c92cbbe155a8-2500x1667.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 0.69 g of CO₂e: 83.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 dropdown has no label.

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

All page content should be contained by landmarks: 4 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.

3 form fields have 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.

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

There are 2 <h1> headlines (“Cold out? Bring it on!” and “Snow's deep. So is our lineup.”). One clear main headline is easier for people and search engines.

Structured data found (OnlineStore and WebSite) but with 1 problem, for example “WebSite: missing name”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 78 pages on kombisports.com and 8 external pages.

https://www.kombicanada.com/collections/best-sellers-women, https://www.kombicanada.com/collections/new-arrivals-men and https://www.kombicanada.com/collections/best-sellers-men have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kombicanada.com/pages/collection-climate-series-women and https://www.kombicanada.com/pages/collection-climate-series-men have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.kombicanada.com/collections/new-arrivals-men and https://www.kombicanada.com/collections/men-headwear-balaclavas-and-face-masks took over 3 s to send their HTML from our server.

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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

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

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

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