metroactiv.com website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.7 s faster on a phone.

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, razorpay.com and Shopify and others), adding 2.5 MB and 2.0 s of main-thread time.

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

Google Tag Manager costs a phone 736 ms of main-thread work and 514 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.

razorpay.com costs a phone 455 ms of main-thread work and 928 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 97 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

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

3 KiB could be saved by minifying CSS.

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

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

Visually, the page fills in at 8.4 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 168 ms to 217 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.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.8 MB in 518 requests on a phone: images 3.6 MB (145), scripts 2.3 MB (86) and other files 1.4 MB (248). Under 2 MB keeps phones on slow connections fast.

NEW_ARRIVALS_MB_copy.webp 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).

3 images (560 KiB) 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 2.20 g of CO₂e: 264.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Scrollable region must have keyboard access: 20 elements on the page fail this check, rated serious by axe-core.

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

5 elements hidden from screen readers can still receive keyboard focus.

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

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

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

Your title is 73 characters, so Google will cut it off around 60: “Shop Metro Activ for Top Footwear & Sportswear Brands Online – MetroActiv”.

Your meta description is 164 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.

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

Your <h1> is empty.

The homepage links to 761 pages on metroactiv.com and 10 external pages.

https://www.metroactiv.com/pages/store-locator and https://www.metroactiv.com/apps/advanced-wishlist have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.metroactiv.com/pages/store-locator, https://www.metroactiv.com/pages/contact and https://www.metroactiv.com/apps/advanced-wishlist have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

Social proof on the homepage: 60 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 carries about 693 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and 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 15 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 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.