micro-mobility.com website review

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

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

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

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

5 third-party services load with your homepage (Google Tag Manager, Cookiebot and Google Analytics and others), adding 706 KiB and 503 ms of main-thread time.

Google Tag Manager costs a phone 423 ms of main-thread work and 513 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 60 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

11 KiB could be saved by minifying CSS.

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

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

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

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 wait 4.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 6.1 MB in 133 requests on a phone: images 4.9 MB (78), scripts 998 KiB (33) and fonts 145 KiB (2). Under 2 MB keeps phones on slow connections fast.

5 images are downloaded at several times the size a phone draws them, for example png-mixed_-micro-sprite-eco-led-mini-micro-deluxe-foldable-e at 2,813 px wide, shown at 195 px. Resized copies would save about 4.0 MB.

png-mixed_-micro-sprite-eco-led-mini-micro-deluxe-foldable-e weighs 3.4 MB. On a phone connection a single image that size takes seconds.

5 images further down the page (4.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (3.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.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

All page content should be contained by landmarks: 24 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

7 links have no real href, so search engines can't follow them.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 147 pages on micro-mobility.com and 11 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.

https://www.micro-mobility.com/en, https://www.micro-mobility.com/home and https://www.micro-mobility.com/en/home all use the title “Micro Mobility Scooter Worldwide - micro-mobility.com”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.micro-mobility.com/en/products, https://www.micro-mobility.com/en/products/age-groups, https://www.micro-mobility.com/en/products/age-groups/1-3-years, https://www.micro-mobility.com/en/products/age-groups/3-5-years, https://www.micro-mobility.com/en/products/age-groups/5-12-years and https://www.micro-mobility.com/en/products/age-groups/teens and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.micro-mobility.com/home and https://www.micro-mobility.com/en/home use the same meta description. A description written for each page earns more clicks.

https://www.micro-mobility.com/home, https://www.micro-mobility.com/en/home, https://www.micro-mobility.com/en/products, https://www.micro-mobility.com/en/products/age-groups, https://www.micro-mobility.com/en/products/age-groups/1-3-years and https://www.micro-mobility.com/en/products/age-groups/3-5-years and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.micro-mobility.com/home, https://www.micro-mobility.com/en/products, https://www.micro-mobility.com/en/products/age-groups, https://www.micro-mobility.com/en/products/age-groups/3-5-years and https://www.micro-mobility.com/en/products/age-groups/5-12-years took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

Social proof on the homepage: 17 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 has only about 145 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

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