Website review, no card needed

illumefragrance.com logo

illumefragrance.com website review

Visit site (opens in a new tab)Reviewed 10 November 202631 issues · 72 checks

This review found 31 issues worth fixing on illumefragrance.com, 11 of them high impact, across 72 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of illumefragrance.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. illumefragrance.com at 0.8 s0.8 s
  2. illumefragrance.com at 1.6 s1.6 s
  3. illumefragrance.com at 2.3 s2.3 s
  4. illumefragrance.com at 3.1 s3.1 s
  5. illumefragrance.com at 3.9 s3.9 s
  6. illumefragrance.com at 4.7 s4.7 s
  7. illumefragrance.com at 5.5 s5.5 s
  8. illumefragrance.com at 6.2 s6.2 s

Speed

6 to fix52
  • Improve image delivery

    1.2 s · 2.2 MB

    61 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

  • Main-thread work: 4.1 s

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

  • 3,249 HTML elements

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

  • Mobile performance score: 52

    52/100

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

  • Render-blocking requests

    450 ms

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

  • 6 long tasks on the main thread

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Accessibe Accessibility Overlay, Yotpo and Attentive and others), adding 642 KiB and 361 ms of main-thread time.

  • Use efficient cache lifetimes

    222 KiB

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

  • Reduce unused JavaScript

    190 KiB

    About 190 KiB of JavaScript is downloaded but never used on this page.

  • Font display

    50 ms

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

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

  • 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.

1 checks passed
  • Server response: 8 ms

    8 ms

    Your server sent the HTML in 8 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix42
  • Largest Contentful Paint: 6.7 s

    6.7 s

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

  • Time to Interactive: 11.4 s

    11.4 s

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

  • Cumulative Layout Shift: 0.323

    0.323

    The layout shifts by 0.323 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 4.7 s

    4.7 s

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

  • Total Blocking Time: 259 ms

    259 ms

    Scripts block taps and scrolling for 259 ms 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.

1 checks passed
  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix70
  • Page weight: 21.1 MB in 316 requests

    21.1 MB

    Your homepage downloads 21.1 MB in 316 requests on a phone: media 15.2 MB (2), images 4.1 MB (74) and other files 755 KiB (150). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

    2 images further down the page (96 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.0 g of CO₂ per visit

    5.99 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8491
  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 26 images without alt text

    26 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (4 elements)

    All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 41 links without text

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

  • Alternative text of images should not be repeated as text (2 elements)

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

  • Headings skip levels

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

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8579
  • Title is short (24 characters)

    Your title is only 24 characters: “ILLUME® – Illume Candles”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Canonical points to another host

    Your canonical URL points to illumecandles.com, not illumefragrance.com, so Google may credit that host instead.

  • Meta description is long (213 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 239 internal links, 42 external

    The homepage links to 239 pages on illumefragrance.com and 42 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Set the season aglow”.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://illumefragrance.com/sitemap.xml.

AI search readiness

100
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 (1,248 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://illumefragrance.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 14 pages without an H1

    https://illumefragrance.com/collections/new-arrivals, https://illumefragrance.com/collections/on-sale, https://illumefragrance.com/collections/artist-series, https://illumefragrance.com/collections/bath-and-beauty, https://illumefragrance.com/collections/beautifully-done and https://illumefragrance.com/collections/noble-autumn and 8 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 88 found) and read each the way a search engine does.

6 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 9687
  • 28 small tap targets

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

  • 2 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 627 words of copy

    The homepage carries about 627 words of visible text.

2 checks passed
  • 16 calls to action

    The homepage has 16 calls to action, for example “Contact”, “Contact Us” and “Shop Now”.

  • 38 short forms

    38 short forms (2 fields at most) are right on the homepage, asking for an email.

Privacy and tracking

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 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.

  • 12 other companies contacted

    Loading the homepage contacts 12 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 illumefragrance.com, 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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Yotpo Product Reviews · Instafeed · nfcube.com · attn.tv

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 31 issues on illumefragrance.com, including 11 speed issues, 5 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25