rigidlightstore.com website review

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

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

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

Shopify costs a phone 204 ms of main-thread work and 475 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.

5 third-party services load with your homepage (Shopify, Klaviyo and govx.com and others), adding 757 KiB and 380 ms of main-thread time.

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

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

About 119 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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 9.1 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.4 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.

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

Your homepage downloads 2.3 MB in 254 requests on a phone: other files 684 KiB (77), scripts 641 KiB (126) and images 569 KiB (11). Under 2 MB keeps phones on slow connections fast.

2 images (82 KiB) 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.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings skip levels (h2 → h4), 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.

There is no <h1>, so neither visitors nor Google get a clear main headline.

The homepage links to 51 pages on rigidlightstore.com and 8 external pages.

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

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

https://rigidlightstore.com/collections/all, https://rigidlightstore.com/policies/shipping-policy, https://rigidlightstore.com/customer_authentication/redirect, https://rigidlightstore.com/collections/rigid-industries-light-bars, https://rigidlightstore.com/collections/rigid-light-kits and https://rigidlightstore.com/collections/rigid-industries-oem-harnesses and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://rigidlightstore.com/collections/all, https://rigidlightstore.com/customer_authentication/redirect, https://rigidlightstore.com/collections/rigid-pod-lights, https://rigidlightstore.com/collections/rigid-industries-light-bars, https://rigidlightstore.com/collections/rigid-light-kits and https://rigidlightstore.com/collections/rigid-industries-oem-harnesses and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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

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