microkickboard.com website review

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

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

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

8 third-party services load with your homepage (widgetic.com, Shopify and Clarity and others), adding 930 KiB and 588 ms of main-thread time.

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

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

Shopify costs a phone 144 ms of main-thread work and 544 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 65 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.

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

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

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.

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.

Your largest element takes 28.4 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 34.0 s. Good is under 3.8 s.

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

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

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

For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 138 ms to 204 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 1.6 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

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

The layout shifts by 0.14 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 8.5 MB in 647 requests on a phone: images 6.0 MB (405), scripts 1.1 MB (81) and other files 826 KiB (130). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

Your title is only 15 characters: “Micro Kickboard”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 843 pages on microkickboard.com and 1 external page.

https://microkickboard.com/products/mini-foldable-led-scooter and https://microkickboard.com/products/micro-mini-foldable-eco-led-scooter all use the title “Micro Mini Foldable LED Scooter – Micro Kickboard”. Search engines can't tell which page to show for a search, so each competes with the others.

https://microkickboard.com/pages/shop-by-age, https://microkickboard.com/collections/children-ages-1-2, https://microkickboard.com/collections/ride-on-scooters, https://microkickboard.com/products/mini-rock-and-go-led-scooter, https://microkickboard.com/products/mini-3in1-scooter and https://microkickboard.com/products/micro-balance-bike and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://flagcdn.com/w40/an.png.

5 of 24 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 “TypeError: Cannot read properties of null (reading 'getAttribute')”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 230 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, Google Tag Manager, Klaviyo and Microsoft Ads and 3 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 19 cookies (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 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.