gloryhaus.com website review

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

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

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.

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

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

8 third-party services load with your homepage (faire.com, Shopify and Attentive and others), adding 1.6 MB and 682 ms of main-thread time.

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

faire.com costs a phone 287 ms of main-thread work and 805 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.

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

Shopify costs a phone 128 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.

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

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

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

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

49 KiB could be saved by minifying JavaScript.

11 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 13.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mobile Christmas website banner featuring a close-up of a w…”.

The layout shifts by 0.831 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Your homepage downloads 4.5 MB in 255 requests on a phone: images 1.9 MB (36), scripts 1.3 MB (102) and other files 739 KiB (90). Under 2 MB keeps phones on slow connections fast.

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

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

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

The homepage links to 311 pages on gloryhaus.com and 13 external pages.

There is no https://www.gloryhaus.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-bundler.nice-team.net/app/css/style.css?shop=gloryhaus.myshopify.com&has_volum…”.

Chrome logged issues while loading the page (“Cookie”).

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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