saturnghc.com website review

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

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

About 470 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, Clarity and Shopify and others), adding 1.2 MB and 460 ms of main-thread time.

About 79 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 2.5 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

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

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

1 image could be 30 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

5 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.7 MB in 261 requests on a phone: scripts 1.1 MB (57), other files 1.1 MB (127) and images 242 KiB (57). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example App_Customer_Support.webp at 2,304 px wide, shown at 65 px. Resized copies would save about 150 KiB.

2 images (447 KiB) are 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.76 g of CO₂e: 91.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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.

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

Your meta description is only 60 characters: “Saturn by GHC is world's leading health and wellness company”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

The homepage links to 62 pages on saturnghc.com and 7 external pages.

https://saturnghc.com/collections/skin, https://saturnghc.com/collections/hair and https://saturnghc.com/collections/wellness have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 12 pages by a URL that isn't their canonical one, for example https://saturnghc.com/collections/skin/products/2-salicylic-acid-body-wash-250-ml, whose canonical is https://saturnghc.com/products/2-salicylic-acid-body-wash-250-ml. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://saturnghc.com/collections/skin, https://saturnghc.com/collections/hair and https://saturnghc.com/collections/wellness have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://saturnghc.com/cdn/shop/t/16/assets/theme.scss.liquid?v=800625199814639753617095591…”.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

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

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