siosystem.com website review

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

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

Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (alia-prod.com, Shopify and Accessibe Accessibility Overlay and others), adding 21.4 MB and 1.0 s of main-thread time.

Shopify costs a phone 215 ms of main-thread work and 20.0 MB 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.

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

Polyfills for old browsers add 50 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

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

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

alia-prod.com costs a phone 238 ms of main-thread work and 666 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.

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

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

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 could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 35.4 MB in 317 requests on a phone: media 31.4 MB (5), scripts 1.5 MB (96) and images 1,018 KiB (47). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example 5734883dc531cbb5.webp at 2,048 px wide, shown at 209 px. Resized copies would save about 125 KiB.

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

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 72 characters, so Google will cut it off around 60: “Skincare Clinically Proven To Reduce Appearance Of Wrinkles – SIO Beauty”.

There are 2 <h1> headlines (“” and “Overnight Results, Proven By Science”). One clear main headline is easier for people and search engines.

The homepage links to 107 pages on siosystem.com and 6 external pages.

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

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

https://www.siobeauty.com/pages/about and https://www.siobeauty.com/pages/the-science-old all use the title “About Us | Clinically Proven Science and Results | SiO Beauty – SIO B…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.siobeauty.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.siobeauty.com/pages/about and https://www.siobeauty.com/pages/the-science-old use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.siobeauty.com/pages/the-science-old, whose canonical is https://www.siobeauty.com/pages/about. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

https://www.siobeauty.com/customer_authentication/redirect took over 3 s to send its HTML from our server.

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

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

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 1,036 words of visible text.

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