Website review, no card needed

reebok.eu logo

reebok.eu website review

Visit site (opens in a new tab)Reviewed 4 November 202633 issues · 86 checks

This review found 33 issues worth fixing on reebok.eu, 6 of them high impact, across 86 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.4 s2.0 sMay 16Oct 315.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.5 s
Jun 6, 20262.6 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.9 s
Jul 25, 20263.0 s
Aug 1, 20263.1 s
Aug 8, 20263.3 s
Aug 15, 20263.4 s
Aug 22, 20263.7 s
Aug 29, 20264.0 s
Sep 5, 20264.1 s
Sep 12, 20264.1 s
Sep 19, 20264.2 s
Sep 26, 20264.1 s
Oct 3, 20264.0 s
Oct 10, 20264.3 s
Oct 17, 20264.7 s
Oct 24, 20264.9 s
Oct 31, 20265.0 s
Real-visitor tap response (INP)75th percentile, phones
188 ms137 msMay 16Oct 31182 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026143 ms
May 23, 2026145 ms
May 30, 2026153 ms
Jun 6, 2026158 ms
Jun 13, 2026162 ms
Jun 20, 2026160 ms
Jun 27, 2026156 ms
Jul 4, 2026152 ms
Jul 11, 2026152 ms
Jul 18, 2026155 ms
Jul 25, 2026158 ms
Aug 1, 2026163 ms
Aug 8, 2026162 ms
Aug 15, 2026160 ms
Aug 22, 2026160 ms
Aug 29, 2026162 ms
Sep 5, 2026166 ms
Sep 12, 2026166 ms
Sep 19, 2026164 ms
Sep 26, 2026166 ms
Oct 3, 2026166 ms
Oct 10, 2026172 ms
Oct 17, 2026178 ms
Oct 24, 2026179 ms
Oct 31, 2026182 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of reebok.eu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. reebok.eu at 0.6 s0.6 s
  2. reebok.eu at 1.3 s1.3 s
  3. reebok.eu at 1.9 s1.9 s
  4. reebok.eu at 2.6 s2.6 s
  5. reebok.eu at 3.2 s3.2 s
  6. reebok.eu at 3.9 s3.9 s
  7. reebok.eu at 4.5 s4.5 s
  8. reebok.eu at 5.2 s5.2 s

Speed

8 to fix74
  • Mobile performance score: 74

    74/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, TikTok and Klaviyo and others), adding 1.2 MB and 827 ms of main-thread time.

  • Render-blocking requests

    800 ms

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

  • Improve image delivery

    790 KiB

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

  • Main-thread work: 4.0 s

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

  • Reduce unused JavaScript

    327 KiB

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

  • 2,216 HTML elements

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

  • Shopify adds 115 ms

    115 ms

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

  • Use efficient cache lifetimes

    238 KiB

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

  • 11 long tasks on the main thread

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

  • Legacy JavaScript

    40 KiB

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

  • Reduce unused CSS

    19 KiB

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

  • Minify JavaScript

    18 KiB

    18 KiB could be saved by minifying JavaScript.

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 11 ms

    11 ms

    Your server sent the HTML in 11 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Time to Interactive: 15.5 s

    15.5 s

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

  • Largest Contentful Paint: 4.1 s

    4.1 s

    Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Introducing the LTD Collection. A playground for creative e…”.

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Tap response (INP) got 25% slower for real visitors

    +25%

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

  • Largest content (LCP) got 109% slower for real visitors

    +109%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 885 ms

    885 ms

    Real visitors wait 885 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 398 ms

    398 ms

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

  • Speed Index: 4.6 s

    4.6 s

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

4 checks passed
  • Real-user INP: 151 ms

    151 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 4.1 MB in 264 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 264 requests on a phone: images 1.3 MB (57), scripts 1.3 MB (80) and other files 1.1 MB (107). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    389 KiB

    4 images are downloaded at several times the size a phone draws them, for example DSC04983.jpg at 750 px wide, shown at 165 px. Resized copies would save about 389 KiB.

  • 1 image in older formats

    1 image (146 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.

  • About 1.2 g of CO₂ per visit

    1.16 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 9196
  • All page content should be contained by landmarks (19 elements)

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

    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.

  • 8 links without text

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

  • 3 form fields without a label

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 108 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10086
  • No H1 headline

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("//www.reebok.eu/cdn/shop/files/reebok-logo.svg?v=174058…”.

  • 408 internal links, 11 external

    The homepage links to 408 pages on reebok.eu and 11 external pages.

6 checks passed
  • Meta description: 97 characters

    Your meta description is 97 characters: “Shop a range of Reebok sneakers, apparel and accessories, at the official Reebok EU online store.”.

  • Title: 31 characters

    Your title is a healthy 31 characters: “Reebok EU | Sport Is Everything”.

  • Canonical URL set

    The canonical URL is https://www.reebok.eu/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.reebok.eu/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.reebok.eu/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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,502 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 1 page slow to respond

    https://www.reebok.eu/collections/f45-training took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    4 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 4 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 4 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=9e6eeea3-8990-4602-a66c-d0a003d1e6cd&referrer=&landingpage=https%3A%2F%2Fwww.reebok.eu%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%2017_.

  • 32 small tap targets

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

  • 2 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • Local business without LocalBusiness data

    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.

  • No phone number on the homepage

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

  • Thin social proof

    Social proof on the homepage: 24 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

  • No map or directions link

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 432 words of copy

    The homepage carries about 432 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop now” and “40% OFF F45 TRAINING | SHOP NOW”.

  • 77 calls to action

    The homepage has 77 calls to action, for example “40% OFF F45 TRAINING | SHOP NOW”, “30% OFF TRAINING ESSENTIALS | SHOP NOW” and “JUST DROPPED: REEBOK X ROUJE | SHOP NOW”.

  • 30 short forms

    30 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel, Microsoft Clarity and TikTok Pixel.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Klaviyo and Meta Pixel and 2 mores (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.

  • 27 cookies set on arrival

    27

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

  • No consent tool detected

    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.

  • 30 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at reebok.eu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

E-commerce
Shopify
Analytics
Google Analytics | Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on reebok.eu, including 18 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25