rotorbike.com website review

21 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

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

Your mobile performance score is 52 (desktop: 71). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Cookiebot and others), adding 1.1 MB and 815 ms of main-thread time.

The page goes through 1 redirect before it starts loading, costing about 756 ms. Link and advertise the final URL directly.

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

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

Google Tag Manager costs a phone 444 ms of main-thread work and 540 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 4.0 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

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

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

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

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.

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

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

Your largest element takes 18.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ontvang GRATIS premium CRONO-fietsschoenen”.

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

Visually, the page fills in at 10.4 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.

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

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

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

9 images 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 3.3 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.7 MB in 295 requests on a phone: images 1.9 MB (39), scripts 1.6 MB (231) and stylesheets 96 KiB (1). Under 2 MB keeps phones on slow connections fast.

11 images (1.6 MB) are 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.

Slider-header-ROTOR-UNO_mobile-02.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).

1 image is downloaded at several times the size a phone draws it, for example DM-12s-Chainrings-home-desktop.jpg at 1,248 px wide, shown at 340 px. Resized copies would save about 59 KiB.

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

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

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

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

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is only 21 characters: “ROTOR Bike Components”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://rotorbike.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at rotorbike.com/robots.txt, the first file search crawlers ask for.

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

The homepage links to 83 pages on rotorbike.com and 10 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.

There is no https://rotorbike.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.

https://rotorbike.com/en-us/groupsets, https://rotorbike.com/en-us/powermeters, https://rotorbike.com/en-us/cassettes, https://rotorbike.com/en-us/accessories and https://rotorbike.com/en-us/clothing have no meta description, so Google writes the search snippet from whatever text it finds.

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

19 of 49 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: the server responded with a status of 400 ()”.

6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

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

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: 2 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.

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.

The homepage carries about 321 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar 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 18 cookies (measured from a US location before any click).

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