Website review, no card needed
idlife.com website review
Visit site (opens in a new tab)Reviewed 4 November 202640 issues · 83 checks
This review found 40 issues worth fixing on idlife.com, 7 of them high impact, across 83 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 80 ms |
| May 23, 2026 | 80 ms |
| May 30, 2026 | 85 ms |
| Jun 6, 2026 | 86 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 87 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 87 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 87 ms |
| Jul 25, 2026 | 87 ms |
| Aug 1, 2026 | 87 ms |
| Aug 8, 2026 | 91 ms |
| Aug 15, 2026 | 94 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 96 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 95 ms |
| Sep 19, 2026 | 95 ms |
| Sep 26, 2026 | 95 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 107 ms |
| Oct 17, 2026 | 120 ms |
| Oct 24, 2026 | 130 ms |
| Oct 31, 2026 | 139 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
Speed
Render-blocking requests
1.4 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
879 KiB12 images could be 879 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, website-files.com and hsappstatic.net and others), adding 2.2 MB and 577 ms of main-thread time.
Reduce unused CSS
550 ms · 90 KiBAbout 90 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 550 ms faster on a phone.
Reduce unused JavaScript
578 KiBAbout 578 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
513 KiB21 files are served with short cache lifetimes, so returning visitors download them again (513 KiB).
website-files.com adds 109 ms
109 mswebsite-files.com costs a phone 109 ms of main-thread work and 1.5 MB 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.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 189 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 21 KiB21 KiB could be saved by minifying CSS.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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: 133 ms
133 msYour server sent the HTML in 133 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 19.2 s
19.2 sThe page becomes fully interactive after 19.2 s. Good is under 3.8 s.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Woman in a sunny kitchen smiling at her phone, with IDLife …”.
Tap response (INP) got 68% slower for real visitors
+68%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 80 ms to 139 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 961 ms
961 msReal visitors wait 961 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 358 ms
358 msScripts block taps and scrolling for 358 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 144 ms
144 msReal visitors wait 144 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.5 MB in 114 requests
3.5 MBYour homepage downloads 3.5 MB in 114 requests on a phone: scripts 1.7 MB (35), images 1.3 MB (36) and fonts 330 KiB (6). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
172 KiB3 images are downloaded at several times the size a phone draws them, for example 6ab3cc598790457c77966fa4_No photo description available_-p-5 at 390 px wide, shown at 64 px. Resized copies would save about 172 KiB.
7 images below the first screen load straight away
7 images further down the page (451 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images in older formats
4 images (427 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 1.0 g of CO₂ per visit
0.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 119.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (58 elements)
All page content should be contained by landmarks: 58 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 checks passed
Every image has alt text
All 104 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (171 characters)
Your meta description is 171 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://idlife.com/sitemap.xml, so Google discovers your pages only by following links.
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.
118 internal links, 0 external
The homepage links to 118 pages on idlife.com and 0 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Millions of possibilities. Nutrition made for one. You.”.
Title: 42 characters
Your title is a healthy 42 characters: “IDLife | Nutrition built from your answers”.
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.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://idlife.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,293 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://idlife.com/shop and https://idlife.com/products/bioage have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://idlife.com/assessment, https://idlife.com/products/energy-03-1022, https://idlife.com/products/hydrate-15-1042, https://idlife.com/products/bioage, https://idlife.com/products/collagen and https://idlife.com/products/dna-bundle and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://idlife.com/assessment has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 28 found) and read each the way a search engine does.
5 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
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 401 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 659 words of copy
The homepage carries about 659 words of visible text.
5 checks passed
21 calls to action
The homepage has 21 calls to action, for example “Join IDLife”, “Shop All” and “Shop All Bestsellers”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 29 testimonial or review blocks, 3 customer or partner logos, a star rating and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel 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.
12 cookies set on arrival
12Opening 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.
38 other companies contacted
Loading the homepage contacts 38 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 idlife.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Webflow
- Analytics
- Google Tag Manager
- Hosting
- Exigo Epic
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on idlife.com, including 18 speed issues, 5 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.