Website review, no card needed
omniluxmedical.com website review
Visit site (opens in a new tab)Reviewed 19 November 202642 issues · 90 checks
This review found 42 issues worth fixing on omniluxmedical.com, 14 of them high impact, across 90 checks. The most urgent: main-thread work: 17.0 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71C- #99,792 of 123,808 reviewed websitesbeats 17%
- #61,061 of 69,682 online storesbeats 10%
- #56,668 of 63,388 Shopify storesbeats 9%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.4 s |
| Oct 31, 2026 | 3.3 s |
| Nov 7, 2026 | 3.3 s |
| Nov 14, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 186 ms |
| Jun 6, 2026 | 196 ms |
| Jun 13, 2026 | 206 ms |
| Jun 20, 2026 | 215 ms |
| Jun 27, 2026 | 221 ms |
| Jul 4, 2026 | 225 ms |
| Jul 11, 2026 | 227 ms |
| Jul 18, 2026 | 226 ms |
| Jul 25, 2026 | 228 ms |
| Aug 1, 2026 | 228 ms |
| Aug 8, 2026 | 228 ms |
| Aug 15, 2026 | 229 ms |
| Aug 22, 2026 | 236 ms |
| Aug 29, 2026 | 237 ms |
| Sep 5, 2026 | 230 ms |
| Sep 12, 2026 | 223 ms |
| Sep 19, 2026 | 220 ms |
| Sep 26, 2026 | 220 ms |
| Oct 3, 2026 | 230 ms |
| Oct 10, 2026 | 237 ms |
| Oct 17, 2026 | 243 ms |
| Oct 24, 2026 | 239 ms |
| Oct 31, 2026 | 234 ms |
| Nov 7, 2026 | 230 ms |
| Nov 14, 2026 | 227 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
4.3 s
8.7 s
13.0 s
17.4 s
21.7 s
26.1 s
30.4 s
34.7 s
Speed
Main-thread work: 17.0 s
A phone's processor spends 17.0 s on main-thread work while loading, 9.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.6 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
12,608 HTML elements
The page has 12,608 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 31
31/100Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and cloudfront.net and others), adding 3.3 MB and 3.6 s of main-thread time.
Reduce unused JavaScript
1.8 MBAbout 1.8 MB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
550 ms · 1.1 MB56 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Google Tag Manager adds 814 ms
814 msGoogle Tag Manager costs a phone 814 ms of main-thread work and 1,023 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.
Improve image delivery
50 ms · 806 KiB16 images could be 806 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
Shopify adds 512 ms
512 msShopify costs a phone 512 ms of main-thread work and 770 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.
Klaviyo adds 449 ms
449 msKlaviyo costs a phone 449 ms of main-thread work and 751 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 adds 459 ms
459 msalia-prod.com costs a phone 459 ms of main-thread work and 574 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.
cloudfront.net adds 507 ms
507 mscloudfront.net costs a phone 507 ms of main-thread work and 94 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 326 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 126 KiBAbout 126 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.
Legacy JavaScript
90 KiBPolyfills for old browsers add 90 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
20 KiB20 KiB JavaScript is shipped twice across bundles.
Minify CSS
7 KiB7 KiB could be saved by minifying CSS.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 28 ms
28 msYour server sent the HTML in 28 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Speed Index: 20.5 s
20.5 sVisually, the page fills in at 20.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 55.4 s
55.4 sThe page becomes fully interactive after 55.4 s. Good is under 3.8 s.
Largest Contentful Paint: 9.2 s
9.2 sYour largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Total Blocking Time: 2.0 s
2.0 sScripts block taps and scrolling for 2.0 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 186 ms to 227 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 198 ms
198 msReal visitors wait 198 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 589 ms
589 msReal visitors wait 589 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.019
0.019The layout barely moves while loading (CLS 0.019, good is under 0.1).
Images and page weight
Page weight: 9.3 MB in 793 requests
9.3 MBYour homepage downloads 9.3 MB in 793 requests on a phone: scripts 4.7 MB (279), other files 1.8 MB (369) and images 1.6 MB (84). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (309 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.
About 2.6 g of CO₂ per visit
2.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.63 g of CO₂e: 315.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
176 images without alt text
176 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (21 elements)
All page content should be contained by landmarks: 21 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Omnilux Black Friday | Save Up To $300 On Medical Grade LED Devices”.
2 H1 headlines
There are 2 <h1> headlines (“Our Best Black Friday: SAVE UP TO $300” and “My cart (0)”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/OmniLux_Logo.png")”.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
436 internal links, 9 external
The homepage links to 436 pages on omniluxmedical.com and 9 external pages.
4 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Shop the Omnilux Black Friday Sale. Save up to 300. Discover FDA-cleared LED devices backed by 40+ peer-reviewed studie…”.
Canonical URL set
The canonical URL is https://omniluxled.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://omniluxled.com/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (4,976 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://omniluxled.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://omniluxled.com/collections/exclusive-bundles is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://omniluxled.com/collections/hydrocolloid-refills has no meta description, so Google writes the search snippet from whatever text it finds.
9 pages without an H1
https://omniluxled.com/collections/all-products, https://omniluxled.com/collections/best-sellers, https://omniluxled.com/collections/all-devices, https://omniluxled.com/collections/skin-care, https://omniluxled.com/collections/anti-aging-topicals and https://omniluxled.com/collections/blemish-topicals and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://omniluxled.com/collections/anti-aging-topicals, https://omniluxled.com/collections/blemish-topicals and https://omniluxled.com/products/age-renewal-led-bundle took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=137030122&Ver=2&mid=3a471b72-99e2-4c27-b7c6-12edcecb6a54&bo=4&sid=e68e5f10e46311f18563ebc684d7ba88&vid=e68e7780e46311f1abbbafb7f574faab&vids=1&msclkid=N&pi=918639831&l.
6 small tap targets
6 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Identifier 'trapFocusHandlers' has already been declared”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,086 words of copy
The homepage carries about 1,086 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP THE SALE”.
30 calls to action
The homepage has 30 calls to action, for example “Shop Black Friday Sale”, “Shop All Topical Skincare” and “Shop All Products”.
121 short forms
121 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 218 testimonial or review blocks, 4 customer or partner logos, a star rating, 17 trust badges and “700,000+ customers”.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and Hotjar.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Tag Manager, Hotjar, Klaviyo, Microsoft Ads and Microsoft Clarity and 3 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.
49 cookies set on arrival
49Opening the homepage sets 49 cookies (measured from a US location before any click).
No consent tool detected
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.
94 other companies contacted
Loading the homepage contacts 94 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at omniluxmedical.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Glen Ellen
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on omniluxmedical.com, including 23 speed issues, 3 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.