Website review, no card needed

dermyoung.com logo

dermyoung.com website review

Visit site (opens in a new tab)Reviewed 20 October 202624 issues · 74 checks

This review found 24 issues worth fixing on dermyoung.com, 8 of them high impact, across 74 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of dermyoung.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dermyoung.com at 3.7 s3.7 s
  2. dermyoung.com at 7.4 s7.4 s
  3. dermyoung.com at 11.2 s11.2 s
  4. dermyoung.com at 14.9 s14.9 s
  5. dermyoung.com at 18.6 s18.6 s
  6. dermyoung.com at 22.3 s22.3 s
  7. dermyoung.com at 26.0 s26.0 s
  8. dermyoung.com at 29.8 s29.8 s

Speed

6 to fix56
  • Use efficient cache lifetimes

    3.6 s · 824 KiB

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

  • Render-blocking requests

    2.4 s

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

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    450 ms · 84 KiB

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

  • Reduce unused JavaScript

    450 ms · 64 KiB

    About 64 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Improve image delivery

    312 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Facebook, GoDaddy and wpmucdn.com and others), adding 333 KiB and 236 ms of main-thread time.

  • Font display

    100 ms

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

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    26 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 87 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 556 ms of it running JavaScript. That is comfortably low.

  • Server response: 25 ms

    25 ms

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

Core Web Vitals

4 to fix66
  • Largest Contentful Paint: 10.5 s

    10.5 s

    Your largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “DermYoung skincare products and store fronts.”.

  • Speed Index: 23.2 s

    23.2 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Time to Interactive: 10.5 s

    10.5 s

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

  • 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
  • Total Blocking Time: 112 ms

    112 ms

    Scripts block the page for only 112 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix88
  • An image on the first screen is lazy-loaded

    DY-website-image_10-07-24-600x600.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).

  • 1 image far larger than shown

    39 KiB

    1 image is downloaded at several times the size a phone draws it, for example Youth-Essence-with-Box-scaled.jpg at 1,620 px wide, shown at 370 px. Resized copies would save about 39 KiB.

  • 3 images in older formats

    3 images (234 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.

  • 1 image below the first screen load straight away

    1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.5 g of CO₂ per visit

    0.52 g

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

1 checks passed
  • Page weight: 1.9 MB in 98 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 98 requests on a phone: images 805 KiB (15), scripts 524 KiB (41) and fonts 370 KiB (6). That is a lean page.

Accessibility

2 to fixGoogle 9396
  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious 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. (2 elements).

2 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 10092
  • No structured data

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

  • No XML sitemap

    No XML sitemap at https://dermyoung.com/sitemap.xml, so Google discovers your pages only by following links.

  • 39 internal links, 5 external

    The homepage links to 39 pages on dermyoung.com and 5 external pages.

6 checks passed
  • Meta description: 94 characters

    Your meta description is 94 characters: “Discover Anti-Aging Skincare at Derm Young. Transform your skin with science-backed solutions.”.

  • One H1 headline

    Your main headline reads: “THE I-GENESIS COLLECTION: CLINICAL SKINCARE FOR LONG-TERM SKIN HEALTH”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “Anti-Aging Skincare | Derm Young”.

  • Canonical URL set

    The canonical URL is https://dermyoung.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.

AI search readiness

1 to fix88
  • 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://dermyoung.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 (502 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 7 pages without a meta description

    https://dermyoung.com/product-category/face-and-body, https://dermyoung.com/product-category/gifts-and-travel-sets, https://dermyoung.com/product-category/beauty-tools, https://dermyoung.com/product-category/all-products, https://dermyoung.com/product/i-genesis-youth-essence and https://dermyoung.com/product/i-genesis-illumine-oil and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://dermyoung.com/skin-consultation has no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://dermyoung.com/shop-online, https://dermyoung.com/product-category/beauty-tools and https://dermyoung.com/contact-us have 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 18 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

2 to fixGoogle 9691
  • 8 small tap targets

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

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

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

  • Thin social proof

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 563 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” and “Toggle submenu for Shop”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop”, “Toggle submenu for Shop” and “Get Started”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Meta Pixel and Matomo.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Meta Pixel (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.

  • 13 cookies set on arrival

    13

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 dermyoung.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
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Matomo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on dermyoung.com, including 10 speed issues, 2 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