goholiglow.com website review

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

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

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

8 third-party services load with your homepage (monkcommerce.app, Shopify and Klaviyo and others), adding 1.1 MB and 313 ms of main-thread time.

monkcommerce.app costs a phone 115 ms of main-thread work and 548 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.

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

About 47 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 31 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

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

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 12.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 12.2 s. Good is under 3.8 s.

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

The first text or image appears after 1.9 s on a phone. Good is under 1.8 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 30.2 MB in 307 requests on a phone: media 26.4 MB (2), images 1.4 MB (33) and scripts 1.1 MB (85). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

2 images have no alt text, which hurts accessibility and image search.

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

Your title is 80 characters, so Google will cut it off around 60: “Giant Inflatable LED Christmas Ornaments | One-of-a-Kind | HoliGlow – GoHoliGlow”.

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

Your meta description is 306 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 49 pages on goholiglow.com and 3 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://goholiglow.com/collections/holiglow%C2%AE-bundle-packs, https://goholiglow.com/collections/holiglow-classic-vintage-starter-packs, https://goholiglow.com/collections/accessories-inflation, https://goholiglow.com/pages/contact and https://goholiglow.com/collections/best-sellers have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://goholiglow.com/collections/all-holiglow%C2%AE-christmas-ornaments, whose canonical is https://goholiglow.com/collections/all-holiglow%c2%ae-christmas-ornaments. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://goholiglow.com/pages/contact has no <h1> headline, so visitors and search engines get no clear main topic.

https://goholiglow.com/collections/holiglow%C2%AE-bundle-packs, https://goholiglow.com/collections/holiglow-classic-vintage-starter-packs, https://goholiglow.com/collections/accessories-inflation and https://goholiglow.com/pages/contact took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

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

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