simplon.com website review

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

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

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

6 third-party services load with your homepage (Google Tag Manager, Cookiebot and Facebook and others), adding 841 KiB and 1.3 s of main-thread time.

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

Cookiebot costs a phone 362 ms of main-thread work and 41 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 350 ms).

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

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

Facebook costs a phone 275 ms of main-thread work and 283 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.

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 200 ms.

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

Your largest element takes 15.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “YOUR RIDE. YOUR BIKE.”.

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

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

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 4.5 MB in 64 requests on a phone: images 1.8 MB (32), scripts 1.7 MB (14) and other files 626 KiB (12). Under 2 MB keeps phones on slow connections fast.

skinfit_gardasee_patricksteiner_494.webp 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.29 g of CO₂e: 154.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Some list items are not inside a list.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

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

Structured data found (Organization 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 125 pages on simplon.com and 6 external pages.

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

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.simplon.com/en/Bikes, whose canonical is https://www.simplon.com/en/Bikes/All-models. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.simplon.com/en/Bikes, https://www.simplon.com/en/Bikes/Roadbikes, https://www.simplon.com/en/Bikes/Roadbikes/Kiaro_b_915184, https://www.simplon.com/en/Bikes/Roadbikes/Pavo_b_674043, https://www.simplon.com/en/Bikes/Roadbikes/Pride_b_292366 and https://www.simplon.com/en/Bikes/Gravel-Bikes and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.simplon.com/en/Bikes, https://www.simplon.com/en/Bikes/Roadbikes, https://www.simplon.com/en/Bikes/Roadbikes/Kiaro_b_915184, https://www.simplon.com/en/Bikes/Roadbikes/Pavo_b_674043, https://www.simplon.com/en/Bikes/Roadbikes/Pride_b_292366 and https://www.simplon.com/en/Bikes/Gravel-Bikes and 9 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Content security policy”).

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

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 1,044 words of visible text.

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

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

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