reebok.ca website review

The page goes through 2 redirects before it starts loading, costing about 5.1 s. Link and advertise the final URL directly.

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

reebok.com costs a phone 1.0 s of main-thread work and 3.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

Your mobile performance score is 26. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (reebok.com, Google Tag Manager and Klaviyo and others), adding 6.4 MB and 3.2 s of main-thread time.

45 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

20 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.

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

13 images could be 349 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 460 ms of main-thread work and 344 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 341 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.

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

Kameleoon costs a phone 356 ms of main-thread work and 57 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.

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

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

The HTML itself could arrive about 50 ms sooner: redirects, a slow server response or missing compression delay everything after it.

15 KiB could be saved by minifying JavaScript.

6 KiB could be saved by minifying CSS.

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.

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 13.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A person wearing a white headband, black zip-up jacket, and…”.

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

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

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

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

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 394 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

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

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

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

Your homepage downloads 9.6 MB in 524 requests on a phone: scripts 4.0 MB (238), images 3.4 MB (83) and other files 1.1 MB (148). Under 2 MB keeps phones on slow connections fast.

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

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

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

Structured data found (WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected ',' or ']' after array element in JSON at position )”.

Your <h1> is empty.

The homepage links to 514 pages on reebok.ca and 0 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://reebok.ca/collections/nano-offer, https://reebok.ca/collections/classics, https://reebok.ca/pages/faq, https://reebok.ca/collections/new-arrivals/Gender:-Women, https://reebok.ca/collections/matching-sets and https://reebok.ca/collections/sport-style have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://reebok.ca/collections/new-arrivals/Gender:-Women, whose canonical is https://reebok.ca/collections/new-arrivals/Gender:%20Women. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://reebok.ca/collections/gift-guide, https://reebok.ca/collections/nano-offer, https://reebok.ca/collections/classics, https://reebok.ca/collections/new-arrivals/Gender:-Women and https://reebok.ca/collections/retro-runners have no <h1> headline, so visitors and search engines get no clear main topic.

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

10 errors were logged to the browser console during Google's test (“Access to fetch at 'https://a.klaviyo.com/client/sessions/?company_id=WmQuMk' from origin 'https://…”).

Large scripts ship without source maps.

Social proof on the homepage: 45 testimonial or review blocks. 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.

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 2,963 words of visible text.