Website review, no card needed

medpeel.com logo

medpeel.com website review

Visit site (opens in a new tab)Reviewed 11 November 202629 issues · 89 checks

This review found 29 issues worth fixing on medpeel.com, 7 of them high impact, across 89 checks. The most urgent: render-blocking requests. 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
2.1 s1.7 sMay 23Nov 71.7 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20261.9 s
Aug 15, 20261.8 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.7 s
Nov 7, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
211 ms149 msMay 23Nov 7188 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026169 ms
May 30, 2026156 ms
Jun 6, 2026163 ms
Jun 13, 2026162 ms
Jun 20, 2026164 ms
Jun 27, 2026171 ms
Jul 4, 2026178 ms
Jul 11, 2026180 ms
Jul 18, 2026187 ms
Jul 25, 2026196 ms
Aug 1, 2026193 ms
Aug 8, 2026182 ms
Aug 15, 2026186 ms
Aug 22, 2026187 ms
Aug 29, 2026191 ms
Sep 5, 2026196 ms
Sep 12, 2026202 ms
Sep 19, 2026204 ms
Sep 26, 2026191 ms
Oct 3, 2026193 ms
Oct 10, 2026192 ms
Oct 17, 2026194 ms
Oct 24, 2026196 ms
Oct 31, 2026188 ms
Nov 7, 2026188 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 medpeel.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. medpeel.com at 0.6 s0.6 s
  2. medpeel.com at 1.1 s1.1 s
  3. medpeel.com at 1.7 s1.7 s
  4. medpeel.com at 2.2 s2.2 s
  5. medpeel.com at 2.8 s2.8 s
  6. medpeel.com at 3.4 s3.4 s
  7. medpeel.com at 3.9 s3.9 s
  8. medpeel.com at 4.5 s4.5 s

Speed

5 to fix73
  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 73

    73/100

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

  • Reduce unused JavaScript

    450 ms · 326 KiB

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

  • ZenDesk adds 324 ms

    324 ms

    ZenDesk costs a phone 324 ms of main-thread work and 431 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,650 HTML elements

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (ZenDesk, Google CDN and shgcdn3.com and others), adding 653 KiB and 481 ms of main-thread time.

  • 6 long tasks on the main thread

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

  • Use efficient cache lifetimes

    100 ms · 39 KiB

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

  • Improve image delivery

    100 ms · 23 KiB

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

  • Reduce unused CSS

    77 KiB

    About 77 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    50 ms · 17 KiB

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

  • Font display

    50 ms

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

  • Duplicated JavaScript

    6 KiB

    6 KiB JavaScript is shipped twice across bundles.

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

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 27 ms

    27 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 5.1 s

    5.1 s

    Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “chemical peels and skincare”.

  • Time to Interactive: 8.0 s

    8.0 s

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

  • Total Blocking Time: 301 ms

    301 ms

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

  • Speed Index: 3.4 s

    3.4 s

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

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

    +16%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 163 ms

    163 ms

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

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

    1.4 s

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

  • Real-user TTFB: 631 ms

    631 ms

    Real visitors wait 631 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

    0

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.38 g

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

4 checks passed
  • Page weight: 1.3 MB in 82 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 82 requests on a phone: scripts 811 KiB (34), images 284 KiB (19) and HTML 156 KiB (1). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

7 to fixGoogle 8891
  • Hidden but focusable

    12 elements hidden from screen readers can still receive keyboard focus.

  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 11 form fields without a label

    11 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

2 checks passed
  • Every image has alt text

    All 42 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

3 to fixGoogle 7781
  • No meta description

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

  • Title is short (8 characters)

    Your title is only 8 characters: “icons/43”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 17 links crawlers can't follow

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

  • 122 internal links, 12 external

    The homepage links to 122 pages on medpeel.com and 12 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Medpeel”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: 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://medpeel.com/sitemap.xml.

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.

3 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 (422 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

6 to fix60
  • 2 pages without a title

    https://medpeel.com/pages/new-products and https://medpeel.com/customer_authentication/redirect have no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://medpeel.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 14 pages share a title

    /, https://medpeel.com/collections/best-sellers, https://medpeel.com/collections/gifts, https://medpeel.com/pages/skin-quiz, https://medpeel.com/pages/skincare and https://medpeel.com/pages/chemical-peels and 8 others all use the title “icons/43”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://medpeel.com/pages/new-products, https://medpeel.com/collections/best-sellers, https://medpeel.com/pages/chemical-peels, https://medpeel.com/pages/about-us and https://medpeel.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages share a meta description

    https://medpeel.com/collections/gifts, https://medpeel.com/pages/skin-quiz, https://medpeel.com/pages/skincare, https://medpeel.com/blogs/news, https://medpeel.com/collections/serums-moisturizers-1 and https://medpeel.com/collections/cleansers-masks and 4 others use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://medpeel.com/pages/new-products, https://medpeel.com/collections/best-sellers, https://medpeel.com/collections/gifts, https://medpeel.com/pages/skin-quiz, https://medpeel.com/pages/skincare and https://medpeel.com/pages/chemical-peels and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages with very little text

    https://medpeel.com/collections/best-sellers, https://medpeel.com/collections/gifts, https://medpeel.com/pages/about-us, https://medpeel.com/collections/serums-moisturizers-1, https://medpeel.com/collections/cleansers-masks and https://medpeel.com/collections/exfoliators-scrubs and 3 others 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.

  • 2 pages slow to respond

    https://medpeel.com/customer_authentication/redirect and https://medpeel.com/collections/bundles took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

Best practices

2 to fixGoogle 9291
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    72 of 77 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • About 292 words of copy

    The homepage carries about 292 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 PROFESSIONAL PEELS” and “APPLY FOR A PROFESSIONAL ACCOUNT”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “SHOP BY CATEGORY”, “SHOP BY CONCERN” and “Shop Professional Peels”.

  • 13 short forms

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

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

  • 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
  • 1 tracker load before any consent

    1

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

  • 8 cookies set on arrival

    8

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

  • 8 other companies contacted

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

Apps your storefront loads

Hulk Form Builder · Powerful Form Builder · Selly Promotion Pricing · Klaviyo Email Marketing Sms · Oxi Social Login Wishlist · Smart Menu · cloudfront.net · trafficmanager.net · oxiapps.com · optimonk.com · revenuehunt.com · bogos.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 | Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on medpeel.com, including 9 speed issues and 3 SEO issues. 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