Website review, no card needed

lifelineskincare.com logo

lifelineskincare.com website review

Visit site (opens in a new tab)Reviewed 8 November 202651 issues · 87 checks

This review found 51 issues worth fixing on lifelineskincare.com, 20 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
6.7 s4.8 sMay 16Oct 316.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.3 s
May 23, 20265.2 s
May 30, 20265.0 s
Jun 6, 20265.2 s
Jun 13, 20265.2 s
Jun 20, 20265.2 s
Jun 27, 20265.3 s
Jul 4, 20265.2 s
Jul 11, 20265.3 s
Jul 18, 20265.5 s
Jul 25, 20265.6 s
Aug 1, 20265.7 s
Aug 8, 20265.7 s
Aug 15, 20265.8 s
Aug 22, 20265.8 s
Aug 29, 20265.8 s
Sep 5, 20265.8 s
Sep 12, 20265.7 s
Sep 19, 20265.7 s
Sep 26, 20265.7 s
Oct 3, 20265.7 s
Oct 10, 20265.7 s
Oct 17, 20265.9 s
Oct 24, 20266.2 s
Oct 31, 20266.4 s
Real-visitor tap response (INP)75th percentile, phones
522 ms142 msMay 16Oct 31450 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026194 ms
May 23, 2026186 ms
May 30, 2026209 ms
Jun 6, 2026216 ms
Jun 13, 2026245 ms
Jun 20, 2026258 ms
Jun 27, 2026258 ms
Jul 4, 2026261 ms
Jul 11, 2026288 ms
Jul 18, 2026298 ms
Jul 25, 2026359 ms
Aug 1, 2026412 ms
Aug 8, 2026429 ms
Aug 15, 2026450 ms
Aug 22, 2026447 ms
Aug 29, 2026467 ms
Sep 5, 2026478 ms
Sep 12, 2026473 ms
Sep 19, 2026476 ms
Sep 26, 2026447 ms
Oct 3, 2026434 ms
Oct 10, 2026426 ms
Oct 17, 2026430 ms
Oct 24, 2026445 ms
Oct 31, 2026450 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 lifelineskincare.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lifelineskincare.com at 0.9 s0.9 s
  2. lifelineskincare.com at 1.8 s1.8 s
  3. lifelineskincare.com at 2.6 s2.6 s
  4. lifelineskincare.com at 3.5 s3.5 s
  5. lifelineskincare.com at 4.4 s4.4 s
  6. lifelineskincare.com at 5.3 s5.3 s
  7. lifelineskincare.com at 6.2 s6.2 s
  8. lifelineskincare.com at 7.1 s7.1 s

Speed

15 to fix42
  • Reduce unused JavaScript

    9.7 s · 1.7 MB

    About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.7 s faster on a phone.

  • Use efficient cache lifetimes

    7.2 s · 1.3 MB

    23 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

  • Duplicated JavaScript

    2.4 s · 485 KiB

    485 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 2.4 s faster on a phone.

  • Mobile performance score: 42

    42/100

    Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.9 s

    A phone's processor spends 4.9 s on main-thread work while loading, 2.2 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 (route.com, YouTube and growave.io and others), adding 3.2 MB and 1.4 s of main-thread time.

  • Improve image delivery

    600 ms · 163 KiB

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

  • Render-blocking requests

    600 ms

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

  • route.com adds 426 ms

    426 ms

    route.com costs a phone 426 ms of main-thread work and 1.1 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.

  • YouTube adds 402 ms

    402 ms

    YouTube costs a phone 402 ms of main-thread work and 1,004 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.

  • Reduce unused CSS

    300 ms · 174 KiB

    About 174 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.

  • Legacy JavaScript

    400 ms · 69 KiB

    Polyfills for old browsers add 69 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

  • 2,583 HTML elements

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

  • 11 long tasks on the main thread

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

  • Shopify adds 105 ms

    105 ms

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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: 6 ms

    6 ms

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

Core Web Vitals

12 to fix33
  • 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.

  • Real-user LCP: 7.9 s

    7.9 s

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

  • Real-user FCP: 3.3 s

    3.3 s

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

  • Real-user TTFB: 2.0 s

    2.0 s

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

  • First Contentful Paint: 8.6 s

    8.6 s

    The first text or image appears after 8.6 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 32.2 s

    32.2 s

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

  • Time to Interactive: 32.3 s

    32.3 s

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

  • Speed Index: 14.9 s

    14.9 s

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

  • Real-user INP: 459 ms

    459 ms

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

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

    +136%

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

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

    +21%

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

  • Total Blocking Time: 530 ms

    530 ms

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

2 checks passed
  • Real-user CLS: 0.10

    0.10

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 5.5 MB in 453 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 453 requests on a phone: scripts 3.4 MB (148), other files 1.4 MB (223) and images 360 KiB (28). Under 2 MB keeps phones on slow connections fast.

  • About 1.6 g of CO₂ per visit

    1.55 g

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

6 to fixGoogle 9492
  • [role="img"] and [role="image"] elements must have alternative text (11 elements)

    [role="img"] and [role="image"] elements must have alternative text: 11 elements on the page fail this check, rated serious by axe-core.

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

  • 16 links without text

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

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 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

4 to fixGoogle 9281
  • Title is short (18 characters)

    Your title is only 18 characters: “Lifeline Skin Care”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (320 characters)

    Your meta description is 320 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.

  • One H1 headline

    Your <h1> is empty.

  • 54 internal links, 7 external

    The homepage links to 54 pages on lifelineskincare.com and 7 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://lifelineskincare.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://lifelineskincare.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,320 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

5 to fix60
  • 1 page without a title

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

  • 1 linked page hidden from search

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

  • 2 pages share a title

    https://lifelineskincare.com/pages/the-science and https://lifelineskincare.com/pages/about-us all use the title “. – Lifeline Skin Care”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://lifelineskincare.com/collections/fine-lines-and-wrinkles, https://lifelineskincare.com/collections/acne-scarring, https://lifelineskincare.com/collections/elasticity-loss, https://lifelineskincare.com/collections/sun-damage, https://lifelineskincare.com/pages/results and https://lifelineskincare.com/blogs/blog and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://lifelineskincare.com/pages/lifeline-skin-care-products, https://lifelineskincare.com/collections/fine-lines-and-wrinkles, https://lifelineskincare.com/collections/acne-scarring, https://lifelineskincare.com/collections/elasticity-loss, https://lifelineskincare.com/collections/sun-damage and https://lifelineskincare.com/pages/results and 4 others 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 25 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

4 to fixGoogle 6970
  • 3 broken images

    3 images failed to load on a phone, for example https://forms.soundestlink.com/image/form/popup/5f3c4c8317f6734050123572.

  • 5 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to fetch”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Requests the notification permission on page load

    Requests the notification permission on page load.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 60 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

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

    The homepage carries about 689 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW” and “Learn More”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop By Skin Concern”, “SHOP NOW” and “Learn More”.

  • 3 short forms

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

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Amplitude, Criteo, Google Ads, Google Analytics and Google Tag Manager and 4 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.

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 cookies, 4 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.

  • 50 other companies contacted

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

Apps your storefront loads

Inbox · Blocky Fraud Blocker · Route Protection Tracking · Eg Auto Add To Cart · Omnisend · Growave Loyalty Wishlist · nofraud.com · trafficmanager.net · nfcube.com · googleapis.com · pepperjam.com · rechargecdn.com · revenuehunt.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
Hosting
Shopify

Company

Headquarters
Carlsbad

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on lifelineskincare.com, including 27 speed issues, 4 SEO issues and 3 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