luminaryvitamins.com website review

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

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

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

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

6 third-party services load with your homepage (Shopify, luminaryvitamins.engineering and Yotpo and others), adding 1.2 MB and 567 ms of main-thread time.

77 KiB could be saved by minifying JavaScript.

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

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

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

luminaryvitamins.engineering costs a phone 145 ms of main-thread work and 371 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.

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

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

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

15 KiB JavaScript is shipped twice across bundles.

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

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Luminary Vitamins uses cookies to enhance your experience, …”.

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

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

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Scripts block taps and scrolling for 208 ms in total while the page loads. Good is under 200 ms.

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

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

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

Your homepage downloads 10.1 MB in 425 requests on a phone: media 6.4 MB (1), other files 1.4 MB (289) and scripts 1.2 MB (89). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example luminary_vitamins_create_for_men_gummies.png at 966 px wide, shown at 88 px. Resized copies would save about 263 KiB.

1 image (75 KiB) is 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 2.85 g of CO₂e: 342.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

Your title is 70 characters, so Google will cut it off around 60: “Doctor-Formulated Fertility & Prenatal Gummy Vitamins | Luminary Vitam”.

The homepage links to 101 pages on luminaryvitamins.com and 5 external pages.

https://www.luminaryvitamins.com/a/loop_subscriptions/customer has no <title>, so Google invents the link text in results.

https://www.luminaryvitamins.com/products/preconception-fertility-support-gummies and https://www.luminaryvitamins.com/products/luminary-vitamins-create all use the title “Preconception Gummies (CoQ10 + Iron + Folic Acid) | Luminary”, and 4 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.luminaryvitamins.com/a/loop_subscriptions/customer has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.luminaryvitamins.com/products/preconception-fertility-support-gummies and https://www.luminaryvitamins.com/products/luminary-vitamins-create use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.luminaryvitamins.com/products/luminary-vitamins-create, whose canonical is https://www.luminaryvitamins.com/products/preconception-fertility-support-gummies. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.luminaryvitamins.com/a/loop_subscriptions/customer has no <h1> headline, so visitors and search engines get no clear main topic.

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

Opening the homepage sets 8 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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.