gatherlux.com website review

15 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

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

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

6 third-party services load with your homepage (Shopify, Clarity and Google Fonts and others), adding 2.6 MB and 321 ms of main-thread time.

Shopify costs a phone 210 ms of main-thread work and 2.4 MB 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.

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

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

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

2 KiB could be saved by minifying CSS.

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

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

8 KiB could be saved by minifying JavaScript.

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 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Journey Cushion Pressure Redistribution”.

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

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

The first text or image appears after 2.4 s on a phone. Good is under 1.8 s.

2 images have no width and height attributes, so the layout jumps as each one loads.

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.

12 images are downloaded at several times the size a phone draws them, for example journey-cushion-travel-seat-cushion-showcse-premium.webp at 1,536 px wide, shown at 320 px. Resized copies would save about 2.3 MB.

journey-cushion-travel-seat-cushion-showcse-premium.webp weighs 1.2 MB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.9 MB in 331 requests on a phone: images 1.6 MB (20), other files 1.0 MB (140) and scripts 739 KiB (106). Under 2 MB keeps phones on slow connections fast.

12 images (3.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

6 images further down the page (2.1 MB) 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 1.10 g of CO₂e: 132.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

Elements with visible text labels do not have matching accessible names. (5 elements).

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

There are 2 <h1> headlines (“” and “Arrive Ready. Not Sore, Stiff or Exhausted.”). One clear main headline is easier for people and search engines.

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

Structured data found (Organization and WebSite) but with 3 problems, for example “Organization: sameAs is not an absolute URL ("facebook.com/gatherlux")”.

The homepage links to 29 pages on gatherlux.com and 1 external page.

There is no https://gatherlux.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.

Your homepage links to https://gatherlux.com/instagram.com/gatherlux, which answers with an error. Visitors hit a dead end and search engines drop it.

https://gatherlux.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://gatherlux.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://gatherlux.com/collections/all, https://gatherlux.com/customer_authentication/redirect and https://gatherlux.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://gatherlux.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

The homepage carries about 966 words of visible text.

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