myebikes.com website review

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

46 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

8 third-party services load with your homepage (Clarity, Klaviyo and Shopify and others), adding 1.7 MB and 470 ms of main-thread time.

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

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

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

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

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

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

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

26 KiB JavaScript is shipped twice across bundles.

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.

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

Your largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

Your homepage downloads 6.9 MB in 383 requests on a phone: images 3.7 MB (85), scripts 1.9 MB (136) and other files 864 KiB (132). Under 2 MB keeps phones on slow connections fast.

DSC9245.png 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 Vecocraft-logo.webp at 1,785 px wide, shown at 130 px. Resized copies would save about 97 KiB.

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

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

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

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

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

Your meta description is 168 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 162 pages on myebikes.com and 6 external pages.

https://myebikes.com/pages/pre-black-friday, https://myebikes.com/pages/compare-models, https://myebikes.com/collections/combo-sale-product, https://myebikes.com/collections/fahrrader, https://myebikes.com/collections/zubehor and https://myebikes.com/pages/kontaktformular have no meta description, so Google writes the search snippet from whatever text it finds.

https://myebikes.com/en, https://myebikes.com/pages/pre-black-friday and https://myebikes.com/pages/kontaktformular have no <h1> headline, so visitors and search engines get no clear main topic.

https://myebikes.com/en, https://myebikes.com/collections/all-e-bikes, https://myebikes.com/products/commuter-plus and https://myebikes.com/products/comfort took over 3 s to send their HTML from our server.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, 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.

Opening the homepage sets 21 cookies, 2 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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.