Website review, no card needed

cellcosmet.com logo

cellcosmet.com website review

Visit site (opens in a new tab)Reviewed 6 November 202642 issues · 92 checks

This review found 42 issues worth fixing on cellcosmet.com, 14 of them high impact, across 92 checks. The most urgent: font display. 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.6 s2.0 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.5 s
Jun 20, 20262.6 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.6 s
Jul 18, 20263.1 s
Jul 25, 20263.3 s
Aug 1, 20263.4 s
Aug 8, 20263.4 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20262.5 s
Sep 5, 20262.7 s
Sep 12, 20262.9 s
Sep 19, 20263.0 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.3 s
Oct 17, 20263.2 s
Oct 24, 20262.6 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
304 ms147 msMay 16Oct 31170 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026165 ms
May 23, 2026183 ms
May 30, 2026187 ms
Jun 6, 2026198 ms
Jun 13, 2026208 ms
Jun 20, 2026222 ms
Jun 27, 2026198 ms
Jul 4, 2026196 ms
Jul 11, 2026195 ms
Jul 18, 2026172 ms
Jul 25, 2026186 ms
Aug 1, 2026198 ms
Aug 8, 2026201 ms
Aug 15, 2026218 ms
Aug 22, 2026229 ms
Aug 29, 2026217 ms
Sep 5, 2026227 ms
Sep 12, 2026258 ms
Sep 19, 2026275 ms
Sep 26, 2026285 ms
Oct 3, 2026286 ms
Oct 10, 2026277 ms
Oct 17, 2026250 ms
Oct 24, 2026195 ms
Oct 31, 2026170 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 cellcosmet.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cellcosmet.com at 2.3 s2.3 s
  2. cellcosmet.com at 4.7 s4.7 s
  3. cellcosmet.com at 7.0 s7.0 s
  4. cellcosmet.com at 9.4 s9.4 s
  5. cellcosmet.com at 11.7 s11.7 s
  6. cellcosmet.com at 14.1 s14.1 s
  7. cellcosmet.com at 16.4 s16.4 s
  8. cellcosmet.com at 18.7 s18.7 s

Speed

15 to fix44
  • Font display

    3.0 s

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

  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 44

    44/100

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

  • Main-thread work: 9.0 s

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

  • 3,214 HTML elements

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

  • Reduce unused JavaScript

    2.0 MB

    About 2.0 MB of JavaScript is downloaded but never used on this page.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and rebuyengine.com and others), adding 3.6 MB and 1.1 s of main-thread time.

  • Improve image delivery

    846 KiB

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

  • Reduce unused CSS

    450 ms · 155 KiB

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

  • Shopify adds 317 ms

    317 ms

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

  • Google Tag Manager adds 249 ms

    249 ms

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

  • 20 long tasks on the main thread

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

  • rebuyengine.com adds 178 ms

    178 ms

    rebuyengine.com costs a phone 178 ms of main-thread work and 839 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.

  • monkcommerce.app adds 125 ms

    125 ms

    monkcommerce.app costs a phone 125 ms of main-thread work and 552 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.

  • Klaviyo adds 112 ms

    112 ms

    Klaviyo costs a phone 112 ms of main-thread work and 327 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

    150 ms · 177 KiB

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

  • Legacy JavaScript

    50 ms · 90 KiB

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

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 10 ms

    10 ms

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

Core Web Vitals

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

  • Speed Index: 24.4 s

    24.4 s

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

  • Time to Interactive: 38.6 s

    38.6 s

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

  • Largest Contentful Paint: 8.4 s

    8.4 s

    Your largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A Gift They’ll Reach for Daily”.

  • Total Blocking Time: 744 ms

    744 ms

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 251 ms

    251 ms

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • 33 images without width and height

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    +5%

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

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

    +11%

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

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

  • Real-user TTFB: 518 ms

    518 ms

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

  • Cumulative Layout Shift: 0.089

    0.089

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

Images and page weight

2 to fix63
  • Page weight: 7.2 MB in 407 requests

    7.2 MB

    Your homepage downloads 7.2 MB in 407 requests on a phone: scripts 4.1 MB (158), images 1.5 MB (61) and other files 968 KiB (132). Under 2 MB keeps phones on slow connections fast.

  • 10 images below the first screen load straight away

    10 images further down the page (372 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (50 KiB) is 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 2.0 g of CO₂ per visit

    2.04 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9194
  • 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.

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate 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 46 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 8589
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“My Cart” and “Cellcosmet”). One clear main headline is easier for people and search engines.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • 101 internal links, 11 external

    The homepage links to 101 pages on cellcosmet.com and 11 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Discover Cellcosmet’s luxury Swiss skincare, combining advanced science and nature for radiant, youthful skin. Tailored…”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Luxury Swiss Cellular Skincare | Cellcosmet Anti-Aging Solutions”.

  • Canonical URL set

    The canonical URL is https://www.cellcosmet.com/.

  • 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.cellcosmet.com/sitemap.xml.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    40%

    The HTML your server sends has 930 of the 2,334 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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.

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 42 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5488
  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

  • 2 third-party cookies

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “QRCode is not defined”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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 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 2,334 words of copy

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

6 checks passed
  • Clear next step on the first screen

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

  • 16 calls to action

    The homepage has 16 calls to action, for example “Shop Bestsellers”, “Shop What's New” and “Shop”.

  • 6 short forms

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

  • Social proof on the page

    Social proof on the homepage: 7 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 2 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.

  • 53 other companies contacted

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

Apps your storefront loads

Pandectes Gdpr · Intelligems A B Testing · Okendo · Wyllo Formerly Nofraud · Triplewhale · Impact Com · Rebuy Personalization Engine · Essential Announcer · Smart Seo · Minmaxify Order Limits · Klaviyo Email Marketing Sms · Gdpr Cookie Consent · Essential Announcement Bar · Genesis · Monk Free Gift With Purchase · Bestpush · gorgias.chat · cloudfront.net · kxcdn.com · 9gtb.com · rebuyengine.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 | Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on cellcosmet.com, including 25 speed issues, 3 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

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