luminas.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (Clarity, alia-prod.com and Shopify and others), adding 1.6 MB and 510 ms of main-thread time.

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

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

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

alia-prod.com costs a phone 138 ms of main-thread work and 370 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 KiB could be saved by minifying JavaScript.

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

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

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 18.4 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 20.0 s. Good is under 3.8 s.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.2 MB in 477 requests on a phone: images 1.8 MB (59), other files 1.5 MB (220) and scripts 1.3 MB (143). Under 2 MB keeps phones on slow connections fast.

hero-image-mobile.webp weighs 682 KiB. On a phone connection a single image that size takes seconds.

7 images (2.5 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.

9 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

hero-image-mobile.webp 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).

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

Your title is 77 characters, so Google will cut it off around 60: “LUMINAS: Clinically Backed, Long-Lasting Pain Relief Patches – LUMINAS Energy”.

There are 4 <h1> headlines (“LUMINAS Energy LUMINAS Energy”, “Real People. Real Relief.” and “Recommended by leading doctors and medical experts”). One clear main headline is easier for people and search engines.

1 link has no real href, so search engines can't follow it.

The homepage links to 34 pages on luminas.com and 9 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

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

https://luminas.com/customer_authentication/redirect, https://luminas.com/collections/luminas, https://luminas.com/collections/staminapro, https://luminas.com/pages/staminapro and https://luminas.com/collections/all-products have no meta description, so Google writes the search snippet from whatever text it finds.

https://luminas.com/products/pain-relief-tan-patches and https://luminas.com/products/pain-relief-patches use the same meta description. A description written for each page earns more clicks.

https://luminas.com/customer_authentication/redirect, https://luminas.com/collections/luminas, https://luminas.com/collections/staminapro and https://luminas.com/collections/all-products have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

4 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

The homepage carries about 1,552 words of visible text.

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