hiboy.ae website review

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

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

15 images could be 1.4 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.

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

8 third-party services load with your homepage (Clarity, cloudfront.net and Shopify and others), adding 2.9 MB and 671 ms of main-thread time.

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

Shopify costs a phone 165 ms of main-thread work and 2.2 MB 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.

cloudfront.net costs a phone 227 ms of main-thread work and 608 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.

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

About 63 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 122 ms. During a long task the page ignores taps.

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

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

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

4 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 33.5 MB in 502 requests on a phone: media 25.2 MB (4), images 5.4 MB (72) and other files 1.3 MB (259). Under 2 MB keeps phones on slow connections fast.

18 images are downloaded at several times the size a phone draws them, for example 1_1_2d0b4c15-dfa3-4a8c-b950-93c39a55af1d.jpg at 6,000 px wide, shown at 360 px. Resized copies would save about 2.3 MB.

1_1_2d0b4c15-dfa3-4a8c-b950-93c39a55af1d.jpg weighs 765 KiB. On a phone connection a single image that size takes seconds.

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

banner2MB.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 (155 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 9.49 g of CO₂e: 1139.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Some list items are not inside a list.

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

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

1 link inside paragraphs relies on colour alone to stand out.

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

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

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

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

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 69 pages on hiboy.ae and 34 external pages.

https://hiboy.ae/policies/shipping-policy, https://hiboy.ae/pages/sale, https://hiboy.ae/collections/accessories-1, https://hiboy.ae/collections/s2-accessories-1, https://hiboy.ae/collections/s2-pro-accessories-1 and https://hiboy.ae/collections/s2-max-accessories-1 and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://hiboy.ae/collections/all, https://hiboy.ae/pages/sale, https://hiboy.ae/collections/electric-scooter-for-kids, https://hiboy.ae/collections/accessories-1, https://hiboy.ae/collections/s2-accessories-1 and https://hiboy.ae/collections/s2-pro-accessories-1 and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 33 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.

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://d2zz0xvz7ly6wf.cloudfront.net/static/css/arco.22224e35.chunk.css' from origin 'htt…”.

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

Before a visitor clicks anything, the page loads Microsoft Clarity (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 5 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.