Website review, no card needed

igniton.com logo

igniton.com website review

Visit site (opens in a new tab)Reviewed 10 November 202633 issues · 95 checks

This review found 33 issues worth fixing on igniton.com, 8 of them high impact, across 95 checks. The most urgent: fails Core Web Vitals for real visitors. 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
1.7 s880 msMay 23Nov 71.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.3 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.2 s
Aug 8, 20261.1 s
Aug 15, 20261.3 s
Aug 22, 20261.5 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.5 s
Oct 10, 2026979 ms
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Nov 7, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
237 ms100 msMay 23Nov 7138 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026202 ms
May 30, 2026217 ms
Jun 6, 2026221 ms
Jun 13, 2026203 ms
Jun 20, 2026168 ms
Jun 27, 2026144 ms
Jul 4, 2026144 ms
Jul 11, 2026152 ms
Jul 18, 2026162 ms
Jul 25, 2026152 ms
Aug 1, 2026145 ms
Aug 8, 2026135 ms
Aug 15, 2026134 ms
Aug 22, 2026145 ms
Aug 29, 2026158 ms
Sep 5, 2026174 ms
Sep 12, 2026183 ms
Sep 19, 2026180 ms
Sep 26, 2026159 ms
Oct 3, 2026138 ms
Oct 10, 2026116 ms
Oct 17, 2026127 ms
Oct 24, 2026128 ms
Oct 31, 2026131 ms
Nov 7, 2026138 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 igniton.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. igniton.com at 0.7 s0.7 s
  2. igniton.com at 1.3 s1.3 s
  3. igniton.com at 2.0 s2.0 s
  4. igniton.com at 2.6 s2.6 s
  5. igniton.com at 3.3 s3.3 s
  6. igniton.com at 4.0 s4.0 s
  7. igniton.com at 4.6 s4.6 s
  8. igniton.com at 5.3 s5.3 s

igniton.com does not allow embedding, so this is Google's rendering of the page.

Speed

9 to fix86
  • Main-thread work: 4.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (alia-prod.com, Cloudflare CDN and Facebook and others), adding 1.8 MB and 1.0 s of main-thread time.

  • Mobile performance score: 86

    86/100

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

  • Use efficient cache lifetimes

    150 ms · 687 KiB

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

  • Render-blocking requests

    750 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

  • Reduce unused JavaScript

    505 KiB

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

  • alia-prod.com adds 360 ms

    360 ms

    alia-prod.com costs a phone 360 ms of main-thread work and 365 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.

  • 1,539 HTML elements

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

  • Shopify adds 29 ms

    29 ms

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

  • 3 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    50 KiB

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

  • Reduce unused CSS

    29 KiB

    About 29 KiB of CSS is downloaded but never applied on this page.

  • Improve image delivery

    17 KiB

    1 image could be 17 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.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

6 to fix100
  • 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.

  • Time to Interactive: 20.4 s

    20.4 s

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

  • Speed Index: 8.3 s

    8.3 s

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

  • Real-user TTFB: 825 ms

    825 ms

    Real visitors wait 825 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 202 ms

    202 ms

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

  • 6 images without width and height

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

9 checks passed
  • Real-user LCP: 1.1 s

    1.1 s

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

  • Real-user INP: 138 ms

    138 ms

    Real visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

    1.1 s

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

  • Tap response (INP) got 36% faster for real visitors

    -36%

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

  • Largest content (LCP) got 24% faster for real visitors

    -24%

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

  • Cumulative Layout Shift: 0.08

    0.08

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

  • Largest Contentful Paint: 2.1 s

    2.1 s

    Your largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.

  • First Contentful Paint: 1.2 s

    1.2 s

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

Images and page weight

1 to fix33
  • Page weight: 4.0 MB in 459 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 459 requests on a phone: scripts 1.6 MB (116), other files 1.5 MB (269) and fonts 422 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.15 g

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

Accessibility

4 to fixGoogle 9790
  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

  • 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 42 images in the HTML carry an alt attribute.

  • 20 automated accessibility rules passed

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

SEO

2 to fixGoogle 10090
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Think quickly. Age better. Feel the difference.”). One clear main headline is easier for people and search engines.

  • Meta description is long (202 characters)

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

  • 87 internal links, 17 external

    The homepage links to 87 pages on igniton.com and 17 external pages.

6 checks passed
  • Title: 49 characters

    Your title is a healthy 49 characters: “Igniton – Quantum Brain and Longevity Supplements”.

  • Canonical URL set

    The canonical URL is https://www.igniton.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://www.igniton.com/sitemap.xml.

AI search readiness

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

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

  • llms.txt published

    The site publishes /llms.txt (11 KiB, 2 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 1 page without a title

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

  • 1 linked page hidden from search

    /customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 8 pages without a meta description

    /collections/all, /customer_authentication/redirect, /policies/shipping-policy, /pages/bf-2026, /pages/cyber-monday and /pages/gift-of-glow and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    /collections/all and /customer_authentication/redirect 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 30 found) and read each the way a search engine does.

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

Best practices

1 to fixGoogle 9292
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

  • 6 low-resolution images

    6 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • 1 link through redirect chains

    1 link go through two or more redirects, for example https://www.igniton.com/customer_authentication/redirect?locale=en&region_country=US.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (igniton.com).

  • Valid certificate (72 days left)

    The certificate from Let's Encrypt · YE2 verifies for igniton.com and is valid for another 72 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://igniton.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 41 links work

    All 41 links checked from your homepage (32 internal, 9 external) answered without errors.

Domain and trust

  • DNSSEC is off

    igniton.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

3 checks passed
  • Domain is 21 years old

    21 years

    igniton.com was registered in Dec 2004 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

  • Certificate issuers are restricted

    CAA records allow only digicert.com, globalsign.com, letsencrypt.org and pki.goog to issue certificates for igniton.com, so a mis-issued certificate from anyone else is refused.

  • Registered until Dec 2031

    igniton.com is registered until Dec 2031.

Content and conversion

4 to fix69
  • 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: 123 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • Only about 10 words

    The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.

4 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Apply”, “Shop early access” and “Shop the sale”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Email authentication

2 to fix65
  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be igniton.com is still delivered. Add a report address, check the reports, then move to quarantine.

  • No DKIM key on the usual selectors

    We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

  • Email authentication score: 65/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

1 checks passed
  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:spf.protection.outlook.com -all”.

Privacy and tracking

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

  • 2 other companies contacted

    Loading the homepage contacts 2 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).

Apps on your store

Your storefront loads 9 apps. Each one is code from another company running for your shoppers.

None of the apps your storefront loads is on the list of apps with a known security problem.

Apps your storefront loads

Intelligems A B Testing · Impact Com · Judge Me Reviews · Klaviyo Email Marketing Sms · Videowise Connect · Applovin Shop Integration · Simple Bundle · superfiliate-cdn.com · cloudfront.net

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

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on igniton.com, including 15 speed issues, 2 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