reflexlighting.com website review

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

6 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 1.3 s faster on a phone.

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

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

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

Your mobile performance score is 54 (desktop: 59). Pages that score under 90 lose visitors before the first paint.

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

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

5 third-party services load with your homepage (Hubspot, Google Tag Manager and lighting.exchange and others), adding 1.1 MB and 138 ms of main-thread time.

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

Amazon Web Services costs a phone 0 ms of main-thread work and 777 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.

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

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

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.

3 KiB could be saved by minifying CSS.

Your largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our website uses cookies to enhance your browsing experienc…”.

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

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

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

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

Your homepage downloads 4.2 MB in 135 requests on a phone: images 2.5 MB (27), scripts 860 KiB (45) and fonts 513 KiB (8). Under 2 MB keeps phones on slow connections fast.

3 images (710 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.

1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

3 elements use ARIA attributes their role does not allow, which confuses screen readers.

4 tap targets are too small or too close together to hit reliably with a finger.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://reflexlighting.com/wp-content/uploads/sites/211/2025/08/Reflex_Orange_Hor…”.

6 links have no real href, so search engines can't follow them.

The homepage links to 124 pages on reflexlighting.com and 12 external pages.

https://reflexlighting.com/power-technology, https://reflexlighting.com/projects/safari, https://reflexlighting.com/projects/orig3n, https://reflexlighting.com/projects/harvard-pilgrim and https://reflexlighting.com/projects/martignetti-campanies are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://reflexlighting.com/linecard/eastern-ma-rhode-island, https://reflexlighting.com/linecard/connecticut-western-ma, https://reflexlighting.com/education-eastern-ma-rhode-island, https://reflexlighting.com/education-connecticut-western-ma and https://reflexlighting.com/education-maine-new-hampshire-vermont have no meta description, so Google writes the search snippet from whatever text it finds.

https://reflexlighting.com/eastern-ma-rhode-island and https://reflexlighting.com/contact-maine-new-hampshire-vermont use the same meta description. A description written for each page earns more clicks.

https://reflexlighting.com/eastern-ma-rhode-island, https://reflexlighting.com/connecticut-western-ma, https://reflexlighting.com/contact-maine-new-hampshire-vermont, https://reflexlighting.com/projects/safari, https://reflexlighting.com/projects/orig3n and https://reflexlighting.com/projects/harvard-pilgrim and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.lighting.exchange/spotlight_css/base.css' from origin 'https://reflexlighting.…”.

Large scripts ship without source maps.

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.

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

Before a visitor clicks anything, the page loads Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 6 cookies (measured from a US location before any click).

Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.