glaxon.com website review

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

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

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

8 third-party services load with your homepage (route.com, Shopify and rechargecdn.com and others), adding 1,005 KiB and 623 ms of main-thread time.

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

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

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

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

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

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

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

6 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

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.9 MB in 216 requests on a phone: scripts 1.1 MB (59), images 911 KiB (17) and other files 858 KiB (130). Under 2 MB keeps phones on slow connections fast.

2 images further down the page (59 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

3 tap targets are too small or too close together to hit reliably with a finger.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 97 pages on glaxon.com and 13 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.glaxon.com/collections/products and https://www.glaxon.com/collections/all all use the title “Products”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.glaxon.com/collections/products, https://www.glaxon.com/collections/all, https://www.glaxon.com/collections/best-sellers, https://www.glaxon.com/collections/glaxon-pez%C2%AE, https://www.glaxon.com/collections/sports-nutrition and https://www.glaxon.com/collections/post-workout have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.glaxon.com/collections/glaxon-pez%C2%AE, whose canonical is https://www.glaxon.com/collections/glaxon-pez%c2%ae. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

7 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage carries about 489 words of visible text.

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