Programmable

Website review, no card needed

puraderma.co logo

puraderma.co website review

Visit site (opens in a new tab)Reviewed 12 November 202638 issues · 82 checks

This review found 38 issues worth fixing on puraderma.co, 11 of them high impact, across 82 checks. The most urgent: main-thread work: 6.6 s. 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

Site score

78C

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.9 s1.6 sMay 23Aug 291.8 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.7 s
Jul 18, 20261.8 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
295 ms136 msMay 23Aug 8253 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026162 ms
May 30, 2026154 ms
Jun 6, 2026173 ms
Jun 27, 2026204 ms
Jul 4, 2026214 ms
Jul 11, 2026222 ms
Jul 18, 2026239 ms
Jul 25, 2026277 ms
Aug 1, 2026251 ms
Aug 8, 2026253 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

www.puraderma.co (opens in a new tab)
Full-page screenshot of puraderma.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. puraderma.co at 0.5 s0.5 s
  2. puraderma.co at 0.9 s0.9 s
  3. puraderma.co at 1.4 s1.4 s
  4. puraderma.co at 1.8 s1.8 s
  5. puraderma.co at 2.3 s2.3 s
  6. puraderma.co at 2.8 s2.8 s
  7. puraderma.co at 3.2 s3.2 s
  8. puraderma.co at 3.7 s3.7 s

Speed

12 to fix64

  • Main-thread work: 6.6 s

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

  • 3,296 HTML elements

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

  • 8 third-party services on the page

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

  • Mobile performance score: 64

    64/100

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

  • Reduce unused JavaScript

    909 KiB

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

  • Render-blocking requests

    800 ms

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

  • Google Tag Manager adds 251 ms

    251 ms

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

    280 KiB

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

  • Facebook adds 252 ms

    252 ms

    Facebook costs a phone 252 ms of main-thread work and 247 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 201 ms

    201 ms

    Klaviyo costs a phone 201 ms of main-thread work and 510 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.

  • Shopify adds 172 ms

    172 ms

    Shopify costs a phone 172 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.

  • cloudfront.net adds 136 ms

    136 ms

    cloudfront.net costs a phone 136 ms of main-thread work and 387 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

    150 ms · 38 KiB

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

  • 14 long tasks on the main thread

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

  • Minify JavaScript

    58 KiB

    58 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    44 KiB

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

  • Legacy JavaScript

    42 KiB

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

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

    16 ms

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

Core Web Vitals

5 to fix62

  • Time to Interactive: 28.3 s

    28.3 s

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

  • Largest Contentful Paint: 6.6 s

    6.6 s

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

  • Speed Index: 6.5 s

    6.5 s

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

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

    +59%

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

  • Total Blocking Time: 315 ms

    315 ms

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

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

    +10%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed

  • First Contentful Paint: 1.4 s

    1.4 s

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

4 to fix52

  • Page weight: 5.9 MB in 426 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 426 requests on a phone: scripts 2.4 MB (150), images 1.8 MB (59) and other files 1.2 MB (154). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Copy_of_Olivia_Mobile_Banners_-_live_1.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 9 images below the first screen load straight away

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

  • 2 images far larger than shown

    64 KiB

    2 images are downloaded at several times the size a phone draws them, for example EtTNEBcaP_mid.jpg at 600 px wide, shown at 160 px. Resized copies would save about 64 KiB.

  • 2 images in older formats

    2 images (61 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.7 g of CO₂ per visit

    1.67 g

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

Accessibility

7 to fixGoogle 9192

  • 45 text elements with low contrast

    45 text elements don'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.

  • 6 images without alt text

    6 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (4 elements)

    All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Alternative text of images should not be repeated as text (5 elements)

    Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed

  • 52 automated accessibility rules passed

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

SEO

3 to fixGoogle 8578

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (9 characters)

    Your title is only 9 characters: “PuraDerma”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • One H1 headline

    Your <h1> is empty.

  • 121 internal links, 0 external

    The homepage links to 121 pages on puraderma.co and 0 external pages.

5 checks passed

  • Canonical URL set

    The canonical URL is https://www.puraderma.co/.

  • 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.puraderma.co/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 (2,115 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix83

  • 10 pages without a meta description

    https://www.puraderma.co/collections/all, https://www.puraderma.co/policies/shipping-policy, https://www.puraderma.co/collections/google, https://www.puraderma.co/pages/sobre-nosotros, https://www.puraderma.co/pages/faq and https://www.puraderma.co/pages/antes-y-despues and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.puraderma.co/products/puraderma%E2%84%A2-brocha-contorno-lymphglow and https://www.puraderma.co/products/puraderma%E2%84%A2-brocha-contorno-lymphglow-copy use the same meta description. A description written for each page earns more clicks.

  • 7 links to non-canonical URLs

    Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://www.puraderma.co/products/puraderma%E2%84%A2-brocha-contorno-lymphglow, whose canonical is https://www.puraderma.co/products/puraderma%e2%84%a2-brocha-contorno-lymphglow. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages without an H1

    https://www.puraderma.co/collections/all, https://www.puraderma.co/collections/google, https://www.puraderma.co/pages/sobre-nosotros, https://www.puraderma.co/pages/faq, https://www.puraderma.co/pages/antes-y-despues and https://www.puraderma.co/pages/contactanos-1 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 48 found) and read each the way a search engine does.

4 checks passed

  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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

1 to fixGoogle 9693

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://d1npnstlfekkfz.cloudfront.net/zipify-oneclickupsell-single.4cb211c36b98a5ce.css' f…”.

2 checks passed

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 1,375 words of copy

    The homepage carries about 1,375 words of visible text.

5 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more”.

  • 12 short forms

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

  • Social proof on the page

    Social proof on the homepage: 11 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix

  • 6 trackers load before any consent

    6

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

  • 19 cookies set on arrival

    19

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

  • 36 other companies contacted

    Loading the homepage contacts 36 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 puraderma.co, 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 12 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Bucks · Instant Ai Page Builder · Gempages Builder · Pagefly Ai Page Builder · Menulock Disable Right Click · Klaviyo Email Marketing Sms · Gdpr Cookie Consent · Kaching Subscriptions · Zipify Oneclickupsell · loox.io · wetracked.io

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 Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on puraderma.co, including 17 speed issues, 3 SEO issues 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