Website review, no card needed

drpelo.co.kr logo

drpelo.co.kr website review

Visit site (opens in a new tab)Reviewed 6 November 202644 issues · 85 checks

This review found 44 issues worth fixing on drpelo.co.kr, 19 of them high impact, across 85 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

Full-page screenshot of drpelo.co.kr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. drpelo.co.kr at 1.2 s1.2 s
  2. drpelo.co.kr at 2.3 s2.3 s
  3. drpelo.co.kr at 3.5 s3.5 s
  4. drpelo.co.kr at 4.7 s4.7 s
  5. drpelo.co.kr at 5.9 s5.9 s
  6. drpelo.co.kr at 7.0 s7.0 s
  7. drpelo.co.kr at 8.2 s8.2 s
  8. drpelo.co.kr at 9.4 s9.4 s

Speed

12 to fix43
  • Reduce unused JavaScript

    1.1 s · 1.1 MB

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

  • Render-blocking requests

    2.1 s

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

  • YouTube adds 1.1 s

    1.1 s

    YouTube costs a phone 1.1 s of main-thread work and 1,015 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 43

    43/100

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

  • Main-thread work: 8.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, POWr and powrcdn.com and others), adding 2.1 MB and 2.6 s of main-thread time.

  • Use efficient cache lifetimes

    500 ms · 334 KiB

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

  • POWr adds 634 ms

    634 ms

    POWr costs a phone 634 ms of main-thread work and 59 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.

  • Improve image delivery

    150 ms · 445 KiB

    4 images could be 445 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.

  • Reduce unused CSS

    150 ms · 260 KiB

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

  • powrcdn.com adds 339 ms

    339 ms

    powrcdn.com costs a phone 339 ms of main-thread work and 609 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 252 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    150 ms · 19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 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).

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

    5 ms

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

Core Web Vitals

5 to fix42
  • Time to Interactive: 21.3 s

    21.3 s

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

  • Speed Index: 10.6 s

    10.6 s

    Visually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 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.

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • 29 images without width and height

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

  • 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
  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.9 s

    0.9 s

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

Images and page weight

3 to fix60
  • 1 image over 500 KB

    13_720x.gif weighs 2.5 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.8 MB in 150 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 150 requests on a phone: scripts 2.0 MB (51), images 633 KiB (13) and other files 614 KiB (68). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (2.5 MB) is 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.1 g of CO₂ per visit

    1.06 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 127.7 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

9 to fixGoogle 7385
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Certain ARIA roles must be contained by particular parents (1 element)

    Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.

  • Hidden but focusable

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 4 links without text

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

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 35 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

4 to fixGoogle 9288
  • No structured data

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

  • Meta description is long (194 characters)

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 37 internal links, 3 external

    The homepage links to 37 pages on drpelo.co.kr and 3 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Dr. Pelo”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Innovative Hair & Skin Care Products I Dr. Pelo”.

  • Canonical URL set

    The canonical URL is https://www.drpelo.co.kr/.

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

  • llms.txt published

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

Other pages

2 to fix90
  • 6 pages without a meta description

    https://www.drpelo.co.kr/collections/all, https://www.drpelo.co.kr/collections/hair-care, https://www.drpelo.co.kr/collections/treatment, https://www.drpelo.co.kr/collections/scalp-care, https://www.drpelo.co.kr/pages/science and https://www.drpelo.co.kr/collections/dr-pelo-collection-all have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.drpelo.co.kr/pages/science has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://www.drpelo.co.kr/collections/hair-care, https://www.drpelo.co.kr/collections/treatment, https://www.drpelo.co.kr/collections/scalp-care and https://www.drpelo.co.kr/collections/dr-pelo-collection-all 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 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

5 to fixGoogle 5469
  • 2 broken images

    2 images failed to load on a phone, for example https://www.drpelo.co.kr/.

  • 5 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “[Weglot] Cannot load Weglot because the project has been deleted”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

    The homepage carries about 799 words of visible text.

3 checks passed
  • Clear next step on the first screen

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

  • 4 calls to action

    The homepage has 4 calls to action, for example “Learn More”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 9 cookies set on arrival

    9

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

  • 25 other companies contacted

    Loading the homepage contacts 25 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 drpelo.co.kr, 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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Tms Prod V 71ff83e · nfcube.com · tkdigital.dev · weglot.com · powr.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

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on drpelo.co.kr, including 17 speed issues, 4 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