hiboy.eu website review

22 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

About 119 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 650 ms faster on a phone.

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

5 third-party services load with your homepage (cloudfront.net, Shopify and oceanpayment.com and others), adding 600 KiB and 259 ms of main-thread time.

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

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

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

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

6 KiB could be saved by minifying JavaScript.

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

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.

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

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

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

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

2 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 188 ms to 164 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 images are downloaded at several times the size a phone draws them, for example Este_Es_el_MEJOR_Patinete_Electrico_de_2026_-_HiBoy_Max_Pro. at 1,280 px wide, shown at 297 px. Resized copies would save about 798 KiB.

Your homepage downloads 4.0 MB in 230 requests on a phone: images 2.6 MB (54), other files 775 KiB (103) and scripts 423 KiB (46). Under 2 MB keeps phones on slow connections fast.

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

hiboy-max-pro-autumn-portrait-base-800x1120.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).

By the Sustainable Web Design model, a visit to your homepage emits about 1.12 g of CO₂e: 135.0 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.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Your title is 76 characters, so Google will cut it off around 60: “Electric Scooters & Bikes | Shop Reliable Electric Vehicles Online – EUHIBOY”.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 60 pages on hiboy.eu and 16 external pages.

https://www.hiboy.eu/collections/parts, https://www.hiboy.eu/pages/about-us, https://www.hiboy.eu/pages/hiboy-affiliate and https://www.hiboy.eu/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.hiboy.eu/pages/contact-us, https://www.hiboy.eu/pages/hiboy-affiliate and https://www.hiboy.eu/apps/track123 have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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