aiwo.com website review

About 406 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

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

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

8 third-party services load with your homepage (Clarity, Facebook and Google Tag Manager and others), adding 1.1 MB and 562 ms of main-thread time.

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

About 36 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.

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

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

47 KiB could be saved by minifying JavaScript.

15 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Desktop scores 83 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

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

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

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

Your homepage downloads 3.1 MB in 257 requests on a phone: scripts 1.4 MB (107), other files 795 KiB (109) and images 651 KiB (21). Under 2 MB keeps phones on slow connections fast.

1 image (36 KiB) is 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 0.89 g of CO₂e: 106.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

5 images have no alt text, which hurts accessibility and image search.

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

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

The homepage links to 115 pages on aiwo.com and 6 external pages.

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

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

/customer_authentication/redirect, /pages/aiwo-longevity-path, /collections/products-supplements, /pages/healthcation, /pages/sleepcation and /pages/posture-screening-service have no meta description, so Google writes the search snippet from whatever text it finds.

/customer_authentication/redirect, /pages/aiwo-longevity-path, /collections/products-supplements, /pages/aiwo-aesthetics, /pages/aiwo-aesthetics-sculpting and /pages/contact-aiwo-chennai and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/contact-aiwo-chennai has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

3 links go through two or more redirects, for example https://aiwo.com/customer_authentication/redirect?locale=en&region_country=IN.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

aiwo.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

aiwo.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 1 customer or partner logo. 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.

There is no form on the homepage, so every lead has to click through to another page first.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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