glosenstore.com website review

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

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

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

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

a2rev.com costs a phone 80 ms of main-thread work and 322 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.

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

8 third-party services load with your homepage (Shopify, a2rev.com and omnisnippet1.com and others), adding 834 KiB and 186 ms of main-thread time.

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

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

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

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

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 layout shifts by 0.633 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your largest element takes 6.2 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 9.5 s. Good is under 3.8 s.

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

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.3 MB in 186 requests on a phone: scripts 980 KiB (84), images 596 KiB (25) and other files 573 KiB (41). Under 2 MB keeps phones on slow connections fast.

1695a5f0885249489ab95814153d4ea7_tplv-aphluv4xwc-origin-jpeg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

1 element hidden from screen readers can still receive keyboard focus.

1 tap target is too small or too close together to hit reliably with a finger.

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

11 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 6 characters: “Glosen”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (Organization and WebSite) but with 5 problems, for example “Organization: sameAs is not an absolute URL ("#")”.

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 184 pages on glosenstore.com and 1 external page.

https://glosenstore.com/collections/all, https://glosenstore.com/collections/frontpage, https://glosenstore.com/policies/shipping-policy, https://glosenstore.com/collections/first-aid-box, https://glosenstore.com/collections/pill-box and https://glosenstore.com/collections/cash-box and 6 others 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://glosenstore.com/pages/%E6%89%B9%E5%8F%91%E7%99%BB%E8%AE%B0, whose canonical is https://glosenstore.com/pages/%e6%89%b9%e5%8f%91%e7%99%bb%e8%ae%b0. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://glosenstore.com/collections/all, https://glosenstore.com/collections/frontpage, https://glosenstore.com/collections/first-aid-box and https://glosenstore.com/collections/all-collections have no <h1> headline, so visitors and search engines get no clear main topic.

https://glosenstore.com/collections/frontpage, https://glosenstore.com/policies/shipping-policy and https://glosenstore.com/collections/first-aid-box took over 3 s to send their HTML from our server.

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

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.

The homepage carries about 712 words of visible text.

Before a visitor clicks anything, the page loads 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 10 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.