Website review, no card needed

karammdskin.com logo

karammdskin.com website review

Visit site (opens in a new tab)Reviewed 12 November 202632 issues · 68 checks

This review found 32 issues worth fixing on karammdskin.com, 9 of them high impact, across 68 checks. The most urgent: main-thread work: 17.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

Real-visitor load time (LCP)75th percentile, phones
5.4 s1.8 sMay 23Nov 72.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.5 s
Jun 20, 20262.7 s
Jun 27, 20263.7 s
Jul 4, 20264.6 s
Jul 11, 20264.7 s
Jul 18, 20265.0 s
Jul 25, 20264.8 s
Aug 1, 20264.0 s
Aug 8, 20263.8 s
Aug 15, 20263.6 s
Aug 22, 20263.3 s
Aug 29, 20263.1 s
Sep 5, 20263.1 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20263.1 s
Oct 3, 20263.0 s
Oct 10, 20263.0 s
Oct 17, 20262.9 s
Oct 24, 20262.7 s
Oct 31, 20262.5 s
Nov 7, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
332 ms149 msMay 23Nov 7224 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026170 ms
May 30, 2026186 ms
Jun 6, 2026209 ms
Jun 13, 2026202 ms
Jun 20, 2026212 ms
Jun 27, 2026277 ms
Jul 4, 2026311 ms
Jul 11, 2026301 ms
Jul 18, 2026301 ms
Jul 25, 2026247 ms
Aug 1, 2026198 ms
Aug 8, 2026210 ms
Aug 15, 2026214 ms
Aug 22, 2026219 ms
Aug 29, 2026235 ms
Sep 5, 2026248 ms
Sep 12, 2026253 ms
Sep 19, 2026260 ms
Sep 26, 2026271 ms
Oct 3, 2026260 ms
Oct 10, 2026261 ms
Oct 17, 2026255 ms
Oct 24, 2026229 ms
Oct 31, 2026220 ms
Nov 7, 2026224 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 karammdskin.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. karammdskin.com at 1.8 s1.8 s
  2. karammdskin.com at 3.7 s3.7 s
  3. karammdskin.com at 5.5 s5.5 s
  4. karammdskin.com at 7.3 s7.3 s
  5. karammdskin.com at 9.2 s9.2 s
  6. karammdskin.com at 11.0 s11.0 s
  7. karammdskin.com at 12.9 s12.9 s
  8. karammdskin.com at 14.7 s14.7 s

Speed

13 to fix42
  • Main-thread work: 17.6 s

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

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and Facebook and others), adding 2.4 MB and 4.1 s of main-thread time.

  • Reduce unused JavaScript

    1.0 MB

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

  • Render-blocking requests

    950 ms

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

  • Google Tag Manager adds 796 ms

    796 ms

    Google Tag Manager costs a phone 796 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.

  • alia-prod.com adds 730 ms

    730 ms

    alia-prod.com costs a phone 730 ms of main-thread work and 465 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 708 ms. During a long task the page ignores taps.

  • Facebook adds 590 ms

    590 ms

    Facebook costs a phone 590 ms of main-thread work and 229 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 525 ms

    525 ms

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

  • ContentSquare adds 469 ms

    469 ms

    ContentSquare costs a phone 469 ms of main-thread work and 187 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

    479 KiB

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

  • 2,586 HTML elements

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

  • Reduce unused CSS

    150 ms · 49 KiB

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

  • Legacy JavaScript

    72 KiB

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

  • Improve image delivery

    12 KiB

    1 image could be 12 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 39 ms

    39 ms

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

Core Web Vitals

8 to fix67
  • 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.

  • Time to Interactive: 28.7 s

    28.7 s

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

  • Speed Index: 14.3 s

    14.3 s

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

  • Total Blocking Time: 2.9 s

    2.9 s

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

  • Largest Contentful Paint: 5.0 s

    5.0 s

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

  • Real-user INP: 238 ms

    238 ms

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

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

    +25%

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

6 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 763 ms

    763 ms

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

  • First Contentful Paint: 1.6 s

    1.6 s

    The first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix0
  • Page weight: 7.1 MB in 460 requests

    7.1 MB

    Your homepage downloads 7.1 MB in 460 requests on a phone: scripts 2.9 MB (216), media 2.0 MB (1) and other files 949 KiB (179). Under 2 MB keeps phones on slow connections fast.

  • About 2.0 g of CO₂ per visit

    2.00 g

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

Accessibility

2 to fix100
  • 8 images without alt text

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

  • 3 links without text

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

SEO

3 to fixGoogle 10087
  • 2 H1 headlines

    There are 2 <h1> headlines (“KaramMD Skin” and “A New Standard In Anti-Aging SkincareA New Standa…”). One clear main headline is easier for people and search engines.

  • Meta description is long (251 characters)

    Your meta description is 251 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 133 internal links, 6 external

    The homepage links to 133 pages on karammdskin.com and 6 external pages.

5 checks passed
  • Title: 48 characters

    Your title is a healthy 48 characters: “Premium Skincare By Dr Amir Karam | KaramMD Skin”.

  • Canonical URL set

    The canonical URL is https://karammdskin.com/.

  • Structured data in place

    Structured data found: OnlineStore.

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

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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://karammdskin.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 5 pages without a meta description

    https://karammdskin.com/collections/bestsellers, https://karammdskin.com/collections/anti-aging, https://karammdskin.com/collections/barrier-support, https://karammdskin.com/collections/travel-collection and https://karammdskin.com/collections/sunscreen have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://karammdskin.com/products/karammd-trifecta, https://karammdskin.com/products/quench-vitamin-c-serum, https://karammdskin.com/products/illuminate-anti-aging-cream, https://karammdskin.com/products/enrich-breathable-barrier-balm, https://karammdskin.com/products/polish-enzymatic-exfoliator and https://karammdskin.com/collections/bestsellers and 9 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 37 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

1 to fixGoogle 9693
  • 10 console errors

    10 errors were logged to the browser console during Google's test (“Access to fetch at 'https://shdid.me/api/cbc/identify' from origin 'https://karammdskin.com' has be…”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • 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 3,043 words of copy

    The homepage carries about 3,043 words of visible text.

4 checks passed
  • 19 calls to action

    The homepage has 19 calls to action, for example “Shop Bestsellers”, “Shop Anti-Aging” and “Shop Barrier Support”.

  • 9 short forms

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

  • Social proof on the page

    Social proof on the homepage: 32 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

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 karammdskin.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 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Videowise Connect · Elevar Conversion Tracking · Checkmate · Triplewhale · Eg Auto Add To Cart · Klaviyo Email Marketing Sms · Powerful Form Builder · Contentsquare Analytics · Okendo · Microsoft Clarity · Loop Returns · rechargecdn.com · wickedreports.com · tncapp.com · herokuapp.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

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Company

Headquarters
San Diego

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on karammdskin.com, including 21 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