Website review, no card needed

illuco.com logo

illuco.com website review

Visit site (opens in a new tab)Reviewed 12 November 202626 issues · 73 checks

This review found 26 issues worth fixing on illuco.com, 5 of them high impact, across 73 checks. The most urgent: render-blocking requests. 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

Real-visitor load time (LCP)75th percentile, phones
2.9 s1.7 sMay 23Nov 72.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20262.1 s
Jun 13, 20262.3 s
Jun 20, 20262.4 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.5 s
Jul 18, 20262.6 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.7 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Oct 31, 20262.4 s
Nov 7, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
289 ms124 msMay 23Nov 7244 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026143 ms
May 30, 2026144 ms
Jun 6, 2026157 ms
Jun 13, 2026166 ms
Jun 20, 2026187 ms
Jun 27, 2026206 ms
Jul 4, 2026196 ms
Jul 11, 2026187 ms
Jul 18, 2026210 ms
Jul 25, 2026226 ms
Aug 1, 2026244 ms
Aug 8, 2026270 ms
Aug 15, 2026234 ms
Aug 22, 2026220 ms
Aug 29, 2026227 ms
Sep 5, 2026229 ms
Sep 12, 2026227 ms
Sep 19, 2026217 ms
Sep 26, 2026207 ms
Oct 3, 2026204 ms
Oct 10, 2026202 ms
Oct 17, 2026245 ms
Oct 24, 2026250 ms
Oct 31, 2026237 ms
Nov 7, 2026244 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

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

How it loaded on a phone

  1. illuco.com at 0.4 s0.4 s
  2. illuco.com at 0.8 s0.8 s
  3. illuco.com at 1.1 s1.1 s
  4. illuco.com at 1.5 s1.5 s
  5. illuco.com at 1.9 s1.9 s
  6. illuco.com at 2.3 s2.3 s
  7. illuco.com at 2.6 s2.6 s
  8. illuco.com at 3.0 s3.0 s

Speed

7 to fix79
  • Render-blocking requests

    1.0 s

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

  • Mobile performance score: 79

    79/100

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

  • Reduce unused CSS

    300 ms · 71 KiB

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

  • Reduce unused JavaScript

    351 KiB

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

  • Main-thread work: 2.4 s

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

  • 2,389 HTML elements

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

  • Shopify adds 124 ms

    124 ms

    Shopify costs a phone 124 ms of main-thread work and 783 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 third-party services on the page

    8 third-party services load with your homepage (Shopify, sealsubscriptions.com and shop.app and others), adding 932 KiB and 161 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Use efficient cache lifetimes

    38 KiB

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

  • Minify JavaScript

    33 KiB

    33 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    8 KiB

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

  • 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

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 22 ms

    22 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 5.3 s

    5.3 s

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

  • Time to Interactive: 8.3 s

    8.3 s

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

  • Tap response (INP) got 68% slower for real visitors

    +68%

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

  • Largest content (LCP) got 25% slower for real visitors

    +25%

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

  • Speed Index: 3.8 s

    3.8 s

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

6 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.8 s

    1.8 s

    Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

  • Total Blocking Time: 26 ms

    26 ms

    Scripts block the page for only 26 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix81
  • Page weight: 2.6 MB in 346 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 346 requests on a phone: scripts 1.0 MB (164), other files 782 KiB (100) and images 397 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    ergo-bn_mb.jpg 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).

  • About 0.7 g of CO₂ per visit

    0.74 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.74 g of CO₂e: 88.4 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

3 to fixGoogle 9596
  • 10 images without alt text

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

  • 14 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

1 to fixGoogle 9295
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Precision Loupes, Headlights & Dermatoscopes”). One clear main headline is easier for people and search engines.

  • 96 internal links, 16 external

    The homepage links to 96 pages on illuco.com and 16 external pages.

7 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Shop ILLUCO's precision loupes, headlights, and dermatoscopes for dental, surgical, and dermatology professionals. Kore…”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Dental & Surgical Loupes, Headlights, Dermatoscopes | ILLUCO”.

  • Canonical URL set

    The canonical URL is https://illuco.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://illuco.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,034 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix62
  • 1 page without a title

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

  • 1 linked page hidden from search

    https://illuco.com/customer_authentication/redirect 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://illuco.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://illuco.com/customer_authentication/redirect has 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 46 found) and read each the way a search engine does.

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

Best practices

1 to fixGoogle 9293
  • 7 small tap targets

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No analytics detected

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

  • A 9-field form

    Your longest form asks for 9 fields (7 required). Every extra field lowers completion.

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

    The homepage carries about 900 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “JOIN OUR EMAIL LIST FOR 10% OFF!” and “Shop Wireless →”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “JOIN OUR EMAIL LIST FOR 10% OFF!”, “Shop All Loupes” and “Shop Dermatoscopes”.

  • Social proof on the page

    Social proof on the homepage: 8 testimonial or review blocks, a star rating and 3 trust badges.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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.

  • 11 cookies set on arrival

    11

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

  • 27 other companies contacted

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

Apps your storefront loads

Inbox · Smart Seo · Judge Me Reviews · Forms · Elfsight Event Calendar · Affirm · Mailchimp · chimpstatic.com · affiliatly.com · amazonaws.com · sealsubscriptions.com · influencer-hero.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

Framework
Tailwind CSS
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 26 issues on illuco.com, including 12 speed issues, 1 SEO issue and 2 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