glytone.com website review

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

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

8 third-party services load with your homepage (alia-prod.com, posthog.com and Shopify and others), adding 1.6 MB and 2.5 s of main-thread time.

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

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

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

posthog.com costs a phone 456 ms of main-thread work and 177 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.

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

Shopify costs a phone 357 ms of main-thread work and 331 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 354 ms. During a long task the page ignores taps.

Yotpo costs a phone 317 ms of main-thread work and 260 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.

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

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

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

42 KiB could be saved by minifying JavaScript.

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

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

12 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

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

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' tap response (inp) went from 121 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 3.5 MB in 301 requests on a phone: scripts 1.8 MB (116), other files 826 KiB (123) and images 661 KiB (44). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 button has no accessible name, so screen readers announce just “button”.

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

2 elements hidden from screen readers can still receive keyboard focus.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

1 link has no real href, so search engines can't follow it.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 199 pages on glytone.com and 5 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.

https://glytone.com/collections/body-care, https://glytone.com/collections/last-chance and https://glytone.com/collections/acne-prone-skin-1 have no meta description, so Google writes the search snippet from whatever text it finds.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-app.sealsubscriptions.com/shopify/public/css/style.css?shop=glytone1.myshopify…”.

Requests the notification permission on page load.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The page uses urgency cues (a countdown or limited-time wording).

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