Website review, no card needed

infinitealoe.com logo

infinitealoe.com website review

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

This review found 31 issues worth fixing on infinitealoe.com, 9 of them high impact, across 82 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
1.9 s1.5 sMay 23Nov 71.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.7 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
168 ms125 msMay 23Nov 7161 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026132 ms
May 30, 2026133 ms
Jun 6, 2026136 ms
Jun 13, 2026130 ms
Jun 20, 2026137 ms
Jun 27, 2026145 ms
Jul 4, 2026149 ms
Jul 11, 2026156 ms
Jul 18, 2026156 ms
Jul 25, 2026154 ms
Aug 1, 2026152 ms
Aug 8, 2026144 ms
Aug 15, 2026145 ms
Aug 22, 2026142 ms
Aug 29, 2026147 ms
Sep 5, 2026156 ms
Sep 12, 2026158 ms
Sep 19, 2026162 ms
Sep 26, 2026157 ms
Oct 3, 2026156 ms
Oct 10, 2026163 ms
Oct 17, 2026163 ms
Oct 24, 2026163 ms
Oct 31, 2026163 ms
Nov 7, 2026161 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 infinitealoe.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix73
  • Render-blocking requests

    1.8 s

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

  • 4,540 HTML elements

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

  • Main-thread work: 4.1 s

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

  • Mobile performance score: 73

    73/100

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

  • Reduce unused JavaScript

    150 ms · 762 KiB

    About 762 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Clarity and Shopify and others), adding 1.4 MB and 652 ms of main-thread time.

  • Reduce unused CSS

    600 ms · 96 KiB

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

  • Klaviyo adds 156 ms

    156 ms

    Klaviyo costs a phone 156 ms of main-thread work and 388 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.

  • Shopify adds 106 ms

    106 ms

    Shopify costs a phone 106 ms of main-thread work and 397 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

    147 KiB

    4 images could be 147 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    102 KiB

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

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    40 KiB

    Polyfills for old browsers add 40 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.

1 checks passed
  • Server response: 13 ms

    13 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 17.5 s

    17.5 s

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

  • 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 “Three jars of InfiniteAloe Complete Skin Care: Original Sce…”.

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

    +22%

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

  • Speed Index: 4.5 s

    4.5 s

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

  • 1 image without width and height

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

10 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 LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 187 ms

    187 ms

    Real visitors wait 187 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.3 s

    1.3 s

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

  • Real-user TTFB: 549 ms

    549 ms

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

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

    -14%

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

  • Total Blocking Time: 116 ms

    116 ms

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

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 3.7 MB in 284 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 284 requests on a phone: scripts 1.5 MB (109), images 983 KiB (34) and other files 795 KiB (111). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    60 KiB

    1 image is downloaded at several times the size a phone draws it, for example organic_aloe_transparent-removebg-preview.png at 500 px wide, shown at 60 px. Resized copies would save about 60 KiB.

  • About 1.0 g of CO₂ per visit

    1.04 g

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

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

6 to fixGoogle 8192
  • ARIA roles used must conform to valid values (1 element)

    ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

    All page content should be contained by landmarks: 6 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.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 54 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • Meta description is long (199 characters)

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

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 98 internal links, 4 external

    The homepage links to 98 pages on infinitealoe.com and 4 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Never Have Dry Skin Again”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “InfiniteAloe® Official Store | The Aloe-First Skin Care Formula”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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://infinitealoe.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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,169 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

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

  • 1 linked page hidden from search

    https://infinitealoe.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://infinitealoe.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://infinitealoe.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 48 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

2 to fixGoogle 9687
  • 6 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-static.okendo.io/reviews-widget-plus/css/okendo-reviews-styles.ffe4027a.css' f…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • About 2,535 words of copy

    The homepage carries about 2,535 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop now” and “Shop Complete Skin Care”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Shop now”, “Shop by Product” and “Shop by Sets”.

  • 10 short forms

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

  • Social proof on the page

    Social proof on the homepage: 64 testimonial or review blocks, a star rating and “2.1M+ Customers”.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

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

  • Risk reducer mentioned

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, Meta Pixel, Microsoft Clarity and TikTok Pixel (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.

  • 18 cookies set on arrival

    18

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

  • 41 other companies contacted

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

Apps your storefront loads

Pandectes Gdpr · Instafeed · Eg Auto Add To Cart · Gorgias Live Chat Helpdesk · Uppromote Affiliate · Klaviyo Email Marketing Sms · Elevar Conversion Tracking · Okendo · Gdpr Cookie Consent · Pushowl · Affliate By Secomapp · rechargecdn.com · electricsms.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

Stack

Framework
SvelteKit
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Los Angeles

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 infinitealoe.com, including 14 speed issues and 2 SEO issues. 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