welzo.qa website review

10 images could be 268 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

Google Tag Manager costs a phone 281 ms of main-thread work and 408 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 2,081 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Shopify costs a phone 25 ms of main-thread work and 306 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 (Google Tag Manager, Shopify and Google/Doubleclick Ads and others), adding 724 KiB and 308 ms of main-thread time.

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

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

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

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

3 KiB JavaScript is shipped twice across bundles.

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

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

Your homepage downloads 2.3 MB in 203 requests on a phone: other files 740 KiB (86), scripts 679 KiB (66) and images 629 KiB (25). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example The_Daily_Mirror_logo.png at 390 px wide, shown at 72 px. Resized copies would save about 34 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.65 g of CO₂e: 77.9 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: 2 elements on the page fail this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

Headings skip levels (h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 301 pages on welzo.qa and 11 external pages.

https://welzo.ae/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://welzo.ae/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://welzo.ae/customer_authentication/redirect, https://welzo.ae/collections/beyond-raw, https://welzo.ae/collections/bodydynamix, https://welzo.ae/collections/codeage, https://welzo.ae/collections/ghost and https://welzo.ae/collections/gnc and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://welzo.ae/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://welzo.ae/collections/laperva took over 3 s to send its HTML from our server.

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

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 498 words of visible text.

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