rollover.com.pk website review

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

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

Your mobile performance score is 77 (desktop: 93). Pages that score under 90 lose visitors before the first paint.

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

8 third-party services load with your homepage (yango.tech, Clarity and yango.com and others), adding 538 KiB and 499 ms of main-thread time.

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

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

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

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

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

About 13 KiB of CSS is downloaded but never applied on this page.

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

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

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.

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

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

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

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

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

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

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

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

Your homepage downloads 3.5 MB in 341 requests on a phone: images 1.7 MB (59), other files 835 KiB (168) and scripts 616 KiB (72). Under 2 MB keeps phones on slow connections fast.

NEW-MOBILE-BANNER-SIZE_4_850c497a-c868-4209-b16e-94362396ff6 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).

7 images (420 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 1.00 g of CO₂e: 119.8 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.

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

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your <h1> is empty.

The homepage links to 272 pages on rollover.com.pk and 14 external pages.

https://rollover.com.pk/collections/new-arrivals-2, https://rollover.com.pk/collections/volume-1, https://rollover.com.pk/pages/mommy-me-coord-sets-1, https://rollover.com.pk/collections/bundles, https://rollover.com.pk/collections/infant-dresses and https://rollover.com.pk/collections/infants-bottoms have no meta description, so Google writes the search snippet from whatever text it finds.

https://rollover.com.pk/pages/lookbook, https://rollover.com.pk/collections/accessories, https://rollover.com.pk/collections/new-arrivals-2, https://rollover.com.pk/collections/volume-1, https://rollover.com.pk/pages/mommy-me-coord-sets-1 and https://rollover.com.pk/collections/bundles and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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 20 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.