popular.lighting website review

10 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

Shopify costs a phone 155 ms of main-thread work and 457 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 (Shopify, loox.io and omnisnippet1.com and others), adding 842 KiB and 429 ms of main-thread time.

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

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

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

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

21 KiB JavaScript is shipped twice across bundles.

Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

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.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Your homepage downloads 5.5 MB in 332 requests on a phone: images 3.4 MB (22), other files 991 KiB (168) and scripts 732 KiB (117). Under 2 MB keeps phones on slow connections fast.

4 images (157 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.

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

8 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: 11 elements on the page fail this check, rated moderate by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

Your <h1> is empty.

The homepage links to 100 pages on popular.lighting and 8 external pages.

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

/ and https://popular.lighting/apps/parcelpanel all use the title “Popular Lighting”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://popular.lighting/collections/motion-sensor-lighting, https://popular.lighting/collections/table-lamps, https://popular.lighting/collections/wall-lights, https://popular.lighting/collections/childrens-lights, https://popular.lighting/pages/contact and https://popular.lighting/apps/parcelpanel and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://popular.lighting/products/brilliance and https://popular.lighting/collections/the-best-sellers/products/brilliance use the same meta description. A description written for each page earns more clicks.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://popular.lighting/collections/the-best-sellers/products/sensa-motion-light, whose canonical is https://popular.lighting/products/sensa-motion-light. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://popular.lighting/collections/motion-sensor-lighting, https://popular.lighting/collections/table-lamps, https://popular.lighting/collections/wall-lights, https://popular.lighting/collections/childrens-lights, https://popular.lighting/apps/parcelpanel and https://popular.lighting/collections/the-best-sellers have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The homepage carries about 344 words of visible text.

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