wavesplus.pk website review

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Snapchat and others), adding 947 KiB and 515 ms of main-thread time.

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

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

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

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

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

2 images could be 27 KiB 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.

9 files are served with short cache lifetimes, so returning visitors download them again (50 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.

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 13.7 s. Good is under 3.8 s.

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

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

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

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

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

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

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

Your homepage downloads 3.7 MB in 360 requests on a phone: images 1.2 MB (29), scripts 1.1 MB (109) and other files 1.1 MB (204). Under 2 MB keeps phones on slow connections fast.

washing-machine-banner-mobile.jpg 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.05 g of CO₂e: 126.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

11 buttons have no accessible name, so screen readers announce just “button”.

Certain ARIA roles must be contained by particular parents: 10 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

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

Some list items are not inside a list.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 6 elements on the page fail this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

The homepage links to 240 pages on wavesplus.pk and 4 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.wavesplus.pk/pages/contact, https://www.wavesplus.pk/collections/home-appliances, https://www.wavesplus.pk/collections/water-heaters, https://www.wavesplus.pk/collections/iron-steamer/Dawlance, https://www.wavesplus.pk/collections/washing-machine and https://www.wavesplus.pk/collections/vacuum-cleaner/Vacuum-Cleaner and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.wavesplus.pk/collections/iron-steamer/Dawlance, whose canonical is https://www.wavesplus.pk/collections/iron-steamer/dawlance. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.wavesplus.pk/pages/contact, https://www.wavesplus.pk/collections/home-appliances, https://www.wavesplus.pk/collections/water-heaters, https://www.wavesplus.pk/collections/instant-geyser, https://www.wavesplus.pk/collections/iron-steamer/Dawlance and https://www.wavesplus.pk/collections/washing-machine 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 99 found) and read each the way a search engine does.

25 of 72 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

1 error was logged to the browser console while the page loaded, for example “Unexpected token '-'”.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 106 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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