Website review, no card needed

cosmedix.com logo

cosmedix.com website review

Visit site (opens in a new tab)Reviewed 4 November 202633 issues · 81 checks

This review found 33 issues worth fixing on cosmedix.com, 14 of them high impact, across 81 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
1.7 s1.4 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.6 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.6 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
187 ms120 msMay 16Oct 31161 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026128 ms
May 23, 2026130 ms
May 30, 2026137 ms
Jun 6, 2026138 ms
Jun 13, 2026145 ms
Jun 20, 2026152 ms
Jun 27, 2026155 ms
Jul 4, 2026157 ms
Jul 11, 2026162 ms
Jul 18, 2026164 ms
Jul 25, 2026162 ms
Aug 1, 2026155 ms
Aug 8, 2026153 ms
Aug 15, 2026146 ms
Aug 22, 2026154 ms
Aug 29, 2026169 ms
Sep 5, 2026171 ms
Sep 12, 2026179 ms
Sep 19, 2026179 ms
Sep 26, 2026171 ms
Oct 3, 2026163 ms
Oct 10, 2026163 ms
Oct 17, 2026158 ms
Oct 24, 2026156 ms
Oct 31, 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 cosmedix.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cosmedix.com at 1.1 s1.1 s
  2. cosmedix.com at 2.1 s2.1 s
  3. cosmedix.com at 3.2 s3.2 s
  4. cosmedix.com at 4.2 s4.2 s
  5. cosmedix.com at 5.3 s5.3 s
  6. cosmedix.com at 6.3 s6.3 s
  7. cosmedix.com at 7.4 s7.4 s
  8. cosmedix.com at 8.4 s8.4 s

Speed

13 to fix39
  • Reduce unused JavaScript

    4.4 s · 887 KiB

    About 887 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.4 s faster on a phone.

  • Use efficient cache lifetimes

    1.6 s · 283 KiB

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

  • Main-thread work: 14.3 s

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 39

    39/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Clarity and Google Tag Manager and others), adding 2.2 MB and 2.4 s of main-thread time.

  • Shopify adds 895 ms

    895 ms

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

  • 19 long tasks on the main thread

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

  • Clarity adds 592 ms

    592 ms

    Clarity costs a phone 592 ms of main-thread work and 32 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 231 ms

    231 ms

    Google Tag Manager costs a phone 231 ms of main-thread work and 399 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 193 ms

    193 ms

    Klaviyo costs a phone 193 ms of main-thread work and 360 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 139 ms

    139 ms

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

  • 1,871 HTML elements

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

  • Reduce unused CSS

    290 ms · 89 KiB

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

  • Improve image delivery

    150 ms · 17 KiB

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

  • Legacy JavaScript

    39 KiB

    Polyfills for old browsers add 39 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: 11 ms

    11 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 29.8 s

    29.8 s

    Your largest element takes 29.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “READY TO ELEVATE YOUR SKIN HEALTH? .​ 20% OFF . Plus, Free …”.

  • Time to Interactive: 30.0 s

    30.0 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Speed Index: 8.9 s

    8.9 s

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

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

    +23%

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

  • Real-user TTFB: 826 ms

    826 ms

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

  • 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.5 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 179 ms

    179 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • 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

3 to fix45
  • 1 image over 500 KB

    opti-crystal-liquid-crystal-eye-serum-5133035.webp weighs 5.5 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 5.1 MB in 521 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 521 requests on a phone: scripts 2.4 MB (160), other files 1.7 MB (304) and images 579 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (6.2 MB) 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.4 g of CO₂ per visit

    1.44 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.44 g of CO₂e: 172.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 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 9498
  • Scrollable region must have keyboard access (3 elements)

    Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 33 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 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9295
  • Meta description is short (59 characters)

    Your meta description is only 59 characters: “Transformative Results with a Luxurious Skincare Experience”. 70 to 160 characters is enough to sell the click.

  • 202 internal links, 7 external

    The homepage links to 202 pages on cosmedix.com and 7 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Cosmedix - Professional Skincare Brand, Powered by Precision”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “COSMEDIX | Clean. Clinical. Luxurious. – C O S M E D I X”.

  • Canonical URL set

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

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.cosmedix.com/collections/holiday-kits-2026 has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.cosmedix.com/collections/limited-a, https://www.cosmedix.com/collections/holiday-kits-2026, https://www.cosmedix.com/collections and https://www.cosmedix.com/pages/cosmedix-elite 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 78 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 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7770
  • 1 broken image

    1 image failed to load on a phone, for example https://d3k81ch9hvuctc.cloudfront.net/company/VAhF6M/images/d170985f-1285-4938-ad25-8424e552ef08.png.

  • 30 small tap targets

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

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://a.klaviyo.com/client/sessions/?company_id=VAhF6M' from origin 'https://www.cosmedix.com' ha…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • 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 983 words of copy

    The homepage carries about 983 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 HOLIDAY KITS”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “SHOP”, “SHOP BY SKIN TYPE” and “Contact Us”.

  • 4 short forms

    4 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 8 testimonial or review blocks and 4 customer or partner logos.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • 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
  • 9 trackers load before any consent

    9

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

  • 25 cookies set on arrival

    25

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

  • 59 other companies contacted

    Loading the homepage contacts 59 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 cosmedix.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Hiring

Hiring
3 open roles
Job board
paylocity

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 cosmedix.com, including 20 speed issues, 1 SEO issue and 1 conversion gap. 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