outlight.us website review

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

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

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

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

Klaviyo costs a phone 200 ms of main-thread work and 423 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 2.2 s on main-thread work while loading, 840 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Google Fonts costs a phone 1 ms of main-thread work and 310 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 third-party services load with your homepage (Klaviyo, Clarity and Shopify and others), adding 899 KiB and 383 ms of main-thread time.

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

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.

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

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

6 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 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A modern glass house at dusk with Outlight floor lamps glow…”.

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

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

The first text or image appears after 1.8 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 90 ms to 92 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.4 MB in 283 requests on a phone: images 1.4 MB (24), other files 988 KiB (169) and scripts 654 KiB (75). Under 2 MB keeps phones on slow connections fast.

custom_nano-banana-2_1774064541159.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

2 images are downloaded at several times the size a phone draws them, for example custom_nano-banana-2_1774342531115.png at 1,264 px wide, shown at 350 px. Resized copies would save about 118 KiB.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 68 pages on outlight.us and 1 external page.

The HTML your server sends has 388 of the 802 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://outlight.us/collections/best-sellers, https://outlight.us/pages/about-us, https://outlight.us/pages/support-center, https://outlight.us/pages/trade-program-application and https://outlight.us/collections/indoor-wall-lights have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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