probikeshop.ch website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and fastbundle.co and others), adding 2.3 MB and 1.1 s of main-thread time.

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

Shopify costs a phone 412 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.

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

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

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

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

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

34 KiB could be saved by minifying JavaScript.

34 KiB JavaScript is shipped twice across bundles.

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

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.

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.

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

Your largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Équipez-vous au meilleur prix C'EST PARTI”.

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

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

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

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

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

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

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

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

Your homepage downloads 5.4 MB in 575 requests on a phone: scripts 2.2 MB (124), other files 1.4 MB (307) and images 1.2 MB (80). Under 2 MB keeps phones on slow connections fast.

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

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

4 tap targets are too small or too close together to hit reliably with a finger.

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

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

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

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

Structured data found (OnlineStore, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://probikeshop.fr)”.

The homepage links to 664 pages on probikeshop.ch and 8 external pages.

https://probikeshop.ch/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://probikeshop.ch/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://probikeshop.ch/customer_authentication/redirect and https://probikeshop.ch/collections/black-friday have no meta description, so Google writes the search snippet from whatever text it finds.

https://probikeshop.ch/collections/all, https://probikeshop.ch/customer_authentication/redirect, https://probikeshop.ch/collections/black-friday, https://probikeshop.ch/collections/vtt-cassettes, https://probikeshop.ch/collections/vtt-chaines-attaches-rapides and https://probikeshop.ch/collections/vtt-derailleurs and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://probikeshop.ch/customer_authentication/redirect, https://probikeshop.ch/collections/vtt-boitiers-pedalier-roulements, https://probikeshop.ch/collections/vtt-pedaliers, https://probikeshop.ch/collections/vtt-plateaux, https://probikeshop.ch/collections/vtt-groupes-complets and https://probikeshop.ch/collections/vtt-pieces-transmission-electrique took over 3 s to send their HTML from our server.

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

6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'event')”.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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.

Opening the homepage sets 24 cookies, 3 of them by other companies (measured from a US location before any click).

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.

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