Website review, no card needed
luminiere.co website review
Visit site (opens in a new tab)Reviewed 11 November 202635 issues · 76 checks
This review found 35 issues worth fixing on luminiere.co, 19 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. 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
63D- #97,649 of 102,641 reviewed websitesbeats 4%
- #55,784 of 57,056 online storesbeats 2%
- #50,990 of 51,912 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
1.3 s · 671 KiBAbout 671 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
hcaptcha.com adds 1.6 s
1.6 shcaptcha.com costs a phone 1.6 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 12.6 s
A phone's processor spends 12.6 s on main-thread work while loading, 4.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,380 HTML elements
The page has 5,380 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
7 third-party services on the page
7 third-party services load with your homepage (hcaptcha.com, Shopify and nfcube.com and others), adding 3.2 MB and 2.2 s of main-thread time.
Render-blocking requests
900 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Shopify adds 535 ms
535 msShopify costs a phone 535 ms of main-thread work and 1.9 MB 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 487 ms. During a long task the page ignores taps.
Reduce unused CSS
360 ms · 125 KiBAbout 125 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 360 ms faster on a phone.
Use efficient cache lifetimes
130 KiB6 files are served with short cache lifetimes, so returning visitors download them again (130 KiB).
Legacy JavaScript
59 KiBPolyfills for old browsers add 59 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Improve image delivery
13 KiB1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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 CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 22.6 s
22.6 sYour largest element takes 22.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 34.7 s
34.7 sThe page becomes fully interactive after 34.7 s. Good is under 3.8 s.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.9 s
1.9 sScripts block taps and scrolling for 1.9 s in total while the page loads. Good is under 200 ms.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.8 MB in 380 requests
7.8 MBYour homepage downloads 7.8 MB in 380 requests on a phone: images 4.2 MB (105), scripts 2.1 MB (158) and other files 624 KiB (59). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (217 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.2 g of CO₂ per visit
2.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.21 g of CO₂e: 264.8 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
26 buttons without a name
26 buttons have no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
12 dropdowns have no label.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
23 links without text
23 visible links have no text or label, so screen readers cannot say where they go.
20 form fields without a label
20 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), 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. (1 element).
2 checks passed
Every image has alt text
All 66 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (9 characters)
Your title is only 9 characters: “Luminiere”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 5 problems
Structured data found (Organization and WebSite) but with 5 problems, for example “Organization: sameAs is not an absolute URL ("#")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
216 internal links, 0 external
The homepage links to 216 pages on luminiere.co and 0 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://luminiere.co/.
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://luminiere.co/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (2,122 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://luminiere.co/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://luminiere.co/collections/velas-clasicas, https://luminiere.co/collections/linea-aromatica, https://luminiere.co/collections/linea-color-sin-aroma, https://luminiere.co/collections/velas-candelabros, https://luminiere.co/collections/velas-por-coleccion and https://luminiere.co/collections/velas-arcangeles and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://luminiere.co/collections/velas-clasicas, https://luminiere.co/collections/linea-aromatica, https://luminiere.co/collections/linea-color-sin-aroma, https://luminiere.co/collections/velas-candelabros, https://luminiere.co/collections/velas-por-coleccion and https://luminiere.co/collections/velas-arcangeles and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 79 found) and read each the way a search engine does.
5 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.
2 checks passed
Tap targets are thumb-sized
12 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 2,056 words of copy
The homepage carries about 2,056 words of visible text.
1 checks passed
29 short forms
29 short forms (1 field at most) are right on the homepage.
Privacy and tracking
6 cookies set on arrival
6Opening the homepage sets 6 cookies, 1 of them by other companies (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.
14 other companies contacted
Loading the homepage contacts 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 luminiere.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Xo Builder · King Product Options · Production Builder · Forms · Xb Wishlist · nfcube.com
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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on luminiere.co, including 14 speed issues, 5 SEO issues and 5 conversion gaps. 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.