Website review, no card needed

perpetua.life logo

perpetua.life website review

Visit site (opens in a new tab)Reviewed 8 November 202633 issues · 85 checks

This review found 33 issues worth fixing on perpetua.life, 8 of them high impact, across 85 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
3.3 s1.6 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.4 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.9 s
Jun 20, 20263.0 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20262.9 s
Jul 18, 20262.6 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.8 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
201 ms129 msMay 16Oct 31137 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026164 ms
May 23, 2026166 ms
May 30, 2026171 ms
Jun 6, 2026164 ms
Jun 13, 2026175 ms
Jun 20, 2026181 ms
Jun 27, 2026185 ms
Jul 4, 2026193 ms
Jul 11, 2026177 ms
Jul 18, 2026161 ms
Jul 25, 2026151 ms
Aug 1, 2026149 ms
Aug 8, 2026154 ms
Aug 15, 2026153 ms
Aug 22, 2026151 ms
Aug 29, 2026140 ms
Sep 5, 2026138 ms
Sep 12, 2026146 ms
Sep 19, 2026151 ms
Sep 26, 2026153 ms
Oct 3, 2026156 ms
Oct 10, 2026154 ms
Oct 17, 2026153 ms
Oct 24, 2026143 ms
Oct 31, 2026137 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 perpetua.life (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. perpetua.life at 0.7 s0.7 s
  2. perpetua.life at 1.5 s1.5 s
  3. perpetua.life at 2.2 s2.2 s
  4. perpetua.life at 3.0 s3.0 s
  5. perpetua.life at 3.7 s3.7 s
  6. perpetua.life at 4.5 s4.5 s
  7. perpetua.life at 5.2 s5.2 s
  8. perpetua.life at 6.0 s6.0 s

Speed

11 to fix58
  • Main-thread work: 8.4 s

    A phone's processor spends 8.4 s on main-thread work while loading, 3.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 (Google Tag Manager, Shopify and loox.io and others), adding 1.4 MB and 2.6 s of main-thread time.

  • Mobile performance score: 58

    58/100

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

  • Google Tag Manager adds 909 ms

    909 ms

    Google Tag Manager costs a phone 909 ms of main-thread work and 484 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.

  • Render-blocking requests

    650 ms

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

  • Reduce unused JavaScript

    507 KiB

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

  • 20 long tasks on the main thread

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

  • Shopify adds 415 ms

    415 ms

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

  • 2,808 HTML elements

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

  • TikTok adds 255 ms

    255 ms

    TikTok costs a phone 255 ms of main-thread work and 157 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.

  • loox.io adds 256 ms

    256 ms

    loox.io costs a phone 256 ms of main-thread work and 28 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.

  • Use efficient cache lifetimes

    230 KiB

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

  • Improve image delivery

    100 ms · 33 KiB

    2 images could be 33 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

  • Duplicated JavaScript

    100 ms · 11 KiB

    11 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.

  • Legacy JavaScript

    22 KiB

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

  • Reduce unused CSS

    14 KiB

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

  • Minify JavaScript

    8 KiB

    8 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: 19 ms

    19 ms

    Your server sent the HTML in 19 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: 18.3 s

    18.3 s

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

  • Total Blocking Time: 2.5 s

    2.5 s

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

  • Real-user TTFB: 977 ms

    977 ms

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

  • Largest Contentful Paint: 3.8 s

    3.8 s

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

  • Speed Index: 3.5 s

    3.5 s

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

8 checks passed
  • 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: 112 ms

    112 ms

    Real visitors wait 112 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.6 s

    1.6 s

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

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

    -15%

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

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

    -27%

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

  • First Contentful Paint: 1.6 s

    1.6 s

    The first text or image appears after 1.6 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

1 to fix85
  • Page weight: 3.1 MB in 355 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 355 requests on a phone: scripts 1.5 MB (144), other files 891 KiB (146) and images 262 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.88 g

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

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

  • Images are sized for phones

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

Accessibility

1 to fixGoogle 9598
  • 8 text elements with low contrast

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 10090
  • Meta description is long (256 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 47 internal links, 13 external

    The homepage links to 47 pages on perpetua.life and 13 external pages.

6 checks passed
  • Title: 50 characters

    Your title is a healthy 50 characters: “Best Anti-Aging Supplement AEON – Perpetualife.bio”.

  • Canonical URL set

    The canonical URL is https://perpetualife.bio/.

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

  • llms.txt published

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

Other pages

4 to fix81
  • 1 linked page hidden from search

    https://perpetualife.bio/apps/subscriptions/cp/getmagiclink is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://perpetualife.bio/apps/subscriptions/cp/getmagiclink, https://perpetualife.bio/policies/refund-policy and https://perpetualife.bio/policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://perpetualife.bio/products/nad-liposomal-anti-aging-supplement-complex-aeon-black-white-bundle and https://perpetualife.bio/products/nad-liposomal-anti-aging-supplement-complex-aeon-white-with-curcumin-and-akg use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://perpetualife.bio/apps/subscriptions/cp/getmagiclink 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 18 found) and read each the way a search engine does.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 3 broken images

    3 images failed to load on a phone, for example https://d.adroll.com/uev/ABMFN5NXPFFOTOU2UHICTF/XJZO3KNBFNDLHP37P7DX2I/?adroll_tpc=lx3%3Dlex-875dcf7e-8824-4efd-8dd5-36b3b8e5e127&af0=0fe6f973&adroll_fpc=12b2e5cf9f350d36f151dea8d10b1dc7-1794159373674.

  • 6 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    16 of 16 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix56
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 495 words of visible text.

3 checks passed
  • 4 calls to action

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

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 24 cookies set on arrival

    24

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

  • 54 other companies contacted

    Loading the homepage contacts 54 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 perpetua.life, 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 21 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Google Ads Pixel By Nabu · Geo Redirect · Uppromote Affiliate · Judge Me Reviews · Product Blocker Ageo · Pixel X Facebook Tiktok Ga4 · Ecomposer Builder · Simprosys Google Shopping Feed · Bm Country Blocker Ip Blocker · Affliate By Secomapp · Boostymark Regionblock · Social Widget · Aftersell · Appstle Bundles · loox.io · zooomyapps.com · adroll.com · csell.co · cloudfront.net · dm-holdings.online · archive-digger.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
jQuery
E-commerce
Shopify
Analytics
Google Analytics
Hosting
AWS

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 perpetua.life, including 17 speed issues, 2 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

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