welzo.com website review

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

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

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

Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (figpii.com, Clarity and Shopify and others), adding 777 KiB and 805 ms of main-thread time.

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

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

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

figpii.com costs a phone 378 ms of main-thread work and 83 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.

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

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

sealsubscriptions.com costs a phone 38 ms of main-thread work and 379 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.

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

28 KiB could be saved by minifying JavaScript.

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

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.

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

Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Test your body, optimise with targeted supplements, recover…”.

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

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

Your homepage downloads 3.4 MB in 341 requests on a phone: scripts 1.5 MB (75), other files 1.1 MB (190) and images 435 KiB (29). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.96 g of CO₂e: 115.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

4 elements use ARIA attributes their role does not allow, which confuses screen readers.

Elements must only use permitted ARIA attributes: 8 elements on the page fail this check, rated serious by axe-core.

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

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

6 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: 14 elements on the page fail this check, rated minor by axe-core.

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

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

The homepage links to 1,365 pages on welzo.com and 52 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.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187176104&tm=shpfy_ui&Ver=2&mid=21fec399-5f19-43e7-9ea8-3dee5d97f11f&bo=1&sid=ca42de00d8ee11f1bc88bbd730520bed&vid=ca431b10d8ee11f1885ab1fbebad75d5&vids=1&msclkid=N&pi.

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 “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

Large scripts ship without source maps.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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.

The homepage carries about 1,065 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Klaviyo and Microsoft Ads and 2 mores (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 33 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 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.