Skip to content
Audit Complete

Results for https://isweb.co.kr

Visit site
KR · KRW (₩) · Estimated Applicable regulations: PIPA Dev cost: ₩70,000/hr How jurisdiction is detected
Spain Spain · Madrid Completed: Apr 22, 2026 20:34 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C73

Site Health

Score: 73 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Missing signals may be hurting your search visibility.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

AngularJS · 366 peers
You 73
·
Avg 73
At average
0 50 100
Better than 45% of AngularJS sites See full AngularJS benchmark →
Cloudflare Turnstile · 375 peers
You 73
·
Avg 73
At average
0 50 100
Better than 43% of Cloudflare Turnstile sites See full Cloudflare Turnstile benchmark →

Top Priorities (5)

1

/.git/HEAD is publicly accessible

Security gaps expose your site and users to attacks, eroding trust.

Security › Information Leakage
2

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
4

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
5

Page weighs 16.2 MB (11.6 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

4

High impact, low effort — start here.

Strategic

1

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fisweb.co.kr)](https://beavercheck.com/results/4ea6b775-8dde-48ed-affb-a9574ea210ce)
<a href="https://beavercheck.com/results/4ea6b775-8dde-48ed-affb-a9574ea210ce"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fisweb.co.kr" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fisweb.co.kr

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 8.0s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

4 security gaps detected — browsers may warn visitors about your site.
Your LCP is 8.0s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

2 critical 6 warning

8 barrier(s) likely increasing bounce by ~30%.

Speed (2)

Page takes 8.0s to load

+12% bounce

Users abandon at ~3s — you're 5.5s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 791ms

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

₩280,000 investment → ₩1,803,594/month returns

Payback period: < 1 month First-year ROI: +7630%

Investment

₩280,000

4h · 5 findings

Monthly returns

₩1,803,594 /mo

~₩21,643,128 / year

  • Conversions recovered ₩1,799,666
  • Bandwidth savings ₩3,928

Regulatory risk avoided

No applicable regulations in this jurisdiction

Payback period

0 12mo 24mo

₩140,000 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

₩280,000

4.0 developer hours at ₩70000/hr

Based on South Korea rates (₩70000/hr)

Quick wins
₩140,000 4 fixes in ~120 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

₩3,928 / month at risk

~₩47,141 / year if left unfixed

Bandwidth Waste

₩3,928 /mo

36337.7 MB/mo × 108.108 KRW/GB

  • Optimize transfer: save ~3.6 MB per page load
    Saves ₩3,928/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

37
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
67
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

6.47 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

8.03 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

791 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

11.96 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

54.55 s

Detailed Report

Audit breakdown by category with detailed findings.

37

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
isweb.co.kr/file/renew/font/Pretendard-Bold.woff14400.0 s1.1 MiB
isweb.co.kr/file/renew/font/Pretendard-SemiBold.woff14400.0 s1.1 MiB
isweb.co.kr/file/renew/font/Pretendard-Medium.woff14400.0 s1.1 MiB
isweb.co.kr/file/renew/images/K-006.png14400.0 s1.1 MiB
isweb.co.kr/file/renew/font/Pretendard-Regular.woff14400.0 s1.1 MiB
isweb.co.kr/file/renew/images/K-007.png14400.0 s1.0 MiB
isweb.co.kr/file/renew/images/K-002.png14400.0 s912.9 KiB
isweb.co.kr/file/renew/images/K-001.png14400.0 s779.2 KiB
isweb.co.kr/file/renew/images/K-003.png14400.0 s774.3 KiB
isweb.co.kr/file/renew/images/K-005.png14400.0 s572.5 KiB
isweb.co.kr/file/plugin/froala/js/froala_editor.pkgd.min.js14400.0 s128.7 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
isweb.co.kr/file/plugin/jquery.ui/jquery-ui.js14400.0 s113.8 KiB
isweb.co.kr/file/renew/images/icon_footer_on_02.png14400.0 s79.5 KiB
isweb.co.kr/file/renew/images/icon_footer_on_01.png14400.0 s79.2 KiB
/signals/config/1484898934979788?v=2.9.303&r=stable&domai...1200.0 s44.7 KiB
cdn.datamanager.co.kr/0/tcsdm.js?eid=1h823ex6u2ypg1h823ex6u0.0 ms31.4 KiB
isweb.co.kr/file/renew/images/img_main_order_01.png14400.0 s37.4 KiB
isweb.co.kr/file/renew/js/swiper.min.js14400.0 s35.4 KiB
isweb.co.kr/file/js/jQuery.js14400.0 s33.9 KiB
isweb.co.kr/file/renew/images/img_main_order_03.png14400.0 s33.5 KiB
isweb.co.kr/file/renew/images/img_main_order_02.png14400.0 s26.2 KiB
t1.daumcdn.net/adfit/static/kp.js1270.0 s19.1 KiB
ssl.pstatic.net/melona/libs/gfp-nac-module/synchronizer.js1258.0 s18.2 KiB
isweb.co.kr/file/renew/css/base.css14400.0 s18.1 KiB
cdn.onetag.co.kr/0/tcs.js?eid=1h823ex6u2ypg1h823ex6u0.0 ms11.8 KiB
wcs.pstatic.net/wcslog.js200.0 s10.4 KiB
isweb.co.kr/file/plugin/bootstrap/js/bootstrap.js14400.0 s14.2 KiB
isweb.co.kr/file/plugin/jquery.file.upload/js/jquery.fileupload.js14400.0 s13.8 KiB
isweb.co.kr/file/renew/images/logo.png14400.0 s13.6 KiB
isweb.co.kr/file/css/custom.css?v=2023080914400.0 s12.9 KiB
isweb.co.kr/file/plugin/jquery.bxslider/jquery.bxslider.js14400.0 s12.3 KiB
isweb.co.kr/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?14400.0 s11.4 KiB
isweb.co.kr/file/renew/css/common.css?v=2024062114400.0 s10.7 KiB
isweb.co.kr/file/plugin/froala/css/froala_editor.pkgd.css14400.0 s8.8 KiB
isweb.co.kr/file/plugin/jquery.ui/jquery-ui.css14400.0 s8.3 KiB
isweb.co.kr/file/plugin/ionicons/css/ionicons.css14400.0 s8.1 KiB
isweb.co.kr/file/plugin/font_awsome/css/font-awesome.css14400.0 s6.8 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...86400.0 s10.7 KiB
cdn.megadata.co.kr/dist/prod/utilKit.js?adverId=wemento0.0 ms3.9 KiB
isweb.co.kr/file/css/custom.s.css?version=20230721_14400.0 s4.4 KiB
isweb.co.kr/file/plugin/froala/js/languages/ko.js14400.0 s3.6 KiB
isweb.co.kr/file/renew/css/swiper.min.css14400.0 s3.1 KiB
isweb.co.kr/file/plugin/froala/css/froala_style.css14400.0 s1.8 KiB
isweb.co.kr/file/css/common.css?v=2024062114400.0 s1.7 KiB
isweb.co.kr/file/renew/images/icon_footer_consult.png14400.0 s1.6 KiB
isweb.co.kr/file/renew/images/icon_footer_kakao.png14400.0 s1.6 KiB
isweb.co.kr/file/renew/js/common.js?a=114400.0 s1.5 KiB
isweb.co.kr/file/plugin/jquery.bxslider/jquery.bxslider.css14400.0 s1.2 KiB
isweb.co.kr/file/renew/images/icon_footer_bottom.png14400.0 s1.0 KiB
isweb.co.kr/file/renew/images/icon_footer_top.png14400.0 s1007 B
isweb.co.kr/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js2868.0 s758 B
isweb.co.kr/file/js/common.js?v=2023081714400.0 s829 B
isweb.co.kr/file/renew/images/icon_guide.png14400.0 s820 B
isweb.co.kr/file/renew/images/icon_login_more.png14400.0 s682 B
rum.beusable.net/script/b190718e140010u538/030056e5be3600.0 s561 B
isweb.co.kr/file/renew/images/icon_close_w.png14400.0 s653 B
isweb.co.kr/file/renew/images/icon_more.png14400.0 s611 B
isweb.co.kr/file/css/custom.m.css?version=20230721_14400.0 s466 B
/script/checker/b190718e140010u538/030056e5be?url=https%3...600.0 s336 B
isweb.co.kr/file/renew/images/icon_menu.png14400.0 s437 B
isweb.co.kr/file/css/custom.xs.css?version=20230721_14400.0 s90 B
/tr/?id=1484898934979788&ev=PageView&dl=https%3A%2F%2Fisw...0.0 ms16 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:35.602 source:map[column:29825 line:4 type:source-location url:https://isweb.co.kr/file/js/jQuery.js urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:1117.973 label:Time to first byte subpart:timeToFirstByte] map[duration:2284.848 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-DIV
nodeLabel: 나만의 홈페이지 만들기
path: 1,HTML,1,BODY,0,DIV,3,SECTION,0,DIV,0,DIV,1,H2,0,DIV
selector: div.main-box > div.main-text > h2 > div.container
snippet: <div class="container">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
isweb.co.kr/file/plugin/froala/js/froala_editor.pkgd.min.js128.7 KiB666 ms
isweb.co.kr/file/plugin/froala/css/froala_style.css1.8 KiB
isweb.co.kr/file/plugin/froala/css/froala_editor.pkgd.css8.8 KiB166 ms
isweb.co.kr/file/renew/css/common.css?v=2024062110.7 KiB166 ms
isweb.co.kr/file/plugin/jquery.ui/jquery-ui.js113.8 KiB1.2 s
isweb.co.kr/file/js/common.js?v=20230817829 B
isweb.co.kr/file/css/custom.s.css?version=20230721_4.4 KiB166 ms
isweb.co.kr/file/plugin/jquery.bxslider/jquery.bxslider.css1.2 KiB166 ms
isweb.co.kr/file/css/custom.xs.css?version=20230721_90 B
isweb.co.kr/file/js/jQuery.js33.9 KiB333 ms
isweb.co.kr/file/plugin/jquery.file.upload/js/jquery.fileupload.js13.8 KiB166 ms
isweb.co.kr/file/css/custom.css?v=2023080912.9 KiB499 ms
isweb.co.kr/file/plugin/font_awsome/css/font-awesome.css6.8 KiB
isweb.co.kr/file/renew/css/base.css18.1 KiB499 ms
isweb.co.kr/file/plugin/ionicons/css/ionicons.css8.1 KiB
isweb.co.kr/file/renew/js/swiper.min.js35.4 KiB166 ms
isweb.co.kr/file/renew/js/common.js?a=11.5 KiB
isweb.co.kr/file/css/common.css?v=202406211.7 KiB
isweb.co.kr/file/plugin/jquery.bxslider/jquery.bxslider.js12.3 KiB166 ms
isweb.co.kr/file/renew/css/swiper.min.css3.1 KiB166 ms
isweb.co.kr/file/plugin/bootstrap/js/bootstrap.js14.2 KiB166 ms
isweb.co.kr/file/css/custom.m.css?version=20230721_466 B
isweb.co.kr/file/plugin/jquery.ui/jquery-ui.css8.3 KiB
isweb.co.kr/file/plugin/froala/js/languages/ko.js3.6 KiB166 ms
fonts.googleapis.com/earlyaccess/notosanskr.css204.4 KiB2.3 s
fonts.googleapis.com/css2?family=Jua&display=swap11.7 KiB940 ms
wcs.pstatic.net/wcslog.js10.4 KiB911 ms
t1.daumcdn.net/adfit/static/kp.js19.1 KiB1.2 s
cdn.jsdelivr.net/gh/moonspam/NanumBarunGothic@1.0/nanumbarungothicsubset.css685 B752 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
isweb.co.kr/file/renew/images/K-006.png1.1 MiB1.0 MiB
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
isweb.co.kr/file/renew/images/K-007.png1.0 MiB1007.1 KiB
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
isweb.co.kr/file/renew/images/K-002.png912.5 KiB857.9 KiB
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
isweb.co.kr/file/renew/images/K-001.png778.8 KiB724.3 KiB
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
isweb.co.kr/file/renew/images/K-003.png773.9 KiB719.3 KiB
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
isweb.co.kr/file/renew/images/K-005.png572.2 KiB517.6 KiB
div.container > ul > li > img div.container > ul > li > img
isweb.co.kr/file/renew/images/img_main_order_01.png37.2 KiB36.7 KiB
div.container > ul > li > img div.container > ul > li > img
isweb.co.kr/file/renew/images/img_main_order_03.png33.2 KiB32.8 KiB
div.container > ul > li > img div.container > ul > li > img
isweb.co.kr/file/renew/images/img_main_order_02.png25.9 KiB25.7 KiB
div.header-logo > h1 > a > img div.header-logo > h1 > a > img
isweb.co.kr/file/renew/images/logo.png13.4 KiB13.4 KiB
ul > li.consult > a > ::after ul > li.consult > a > ::after
isweb.co.kr/file/renew/images/icon_footer_on_01.png78.9 KiB11.2 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 973 ms
URLTime Spent
isweb.co.kr/1.1 s

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 300 ms 22.9 KiB
URLTransfer SizeEst Savings
fonts.googleapis.com/earlyaccess/notosanskr.css204.4 KiB20.9 KiB
isweb.co.kr/file/css/custom.css?v=2023080912.9 KiB2.0 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.5 s
Other734 ms
Style & Layout542 ms
Script Parsing & Compilation397 ms
Parse HTML & CSS137 ms
Rendering45 ms
Garbage Collection32 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.container > ul > li > img div.container > ul > li > img
isweb.co.kr/file/renew/images/img_main_order_02.png
div.container > ul > li > img div.container > ul > li > img
isweb.co.kr/file/renew/images/img_main_order_01.png
div.container > ul > li > img div.container > ul > li > img
isweb.co.kr/file/renew/images/img_main_order_03.png
div.header-logo > h1 > a > img div.header-logo > h1 > a > img
isweb.co.kr/file/renew/images/logo.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Optimize DOM size
Font display
Modern HTTP
Optimize viewport for mobile
User Timing marks and measures 10 user timings
Avoid long main-thread tasks 18 long tasks found
Network Requests
Network Round Trip Times 290 ms
Server Backend Latencies 830 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
INP breakdown
LCP request discovery
Avoid non-composited animations
Avoid large layout shifts
67

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
무료로 시작하기 div.main-button > div.container > div.button-box > a.btn

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header-logo > h1 > a > img div.header-logo > h1 > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
div.container > ul > li > img div.container > ul > li > img
div.container > ul > li > img div.container > ul > li > img
div.container > ul > li > img div.container > ul > li > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.header-logo > h1 > a div.container > div.header-logo > h1 > a
div.template-box > ul.list > li.list-item > a div.template-box > ul.list > li.list-item > a
div.template-box > ul.list > li.list-item > a div.template-box > ul.list > li.list-item > a
div.template-box > ul.list > li.list-item > a div.template-box > ul.list > li.list-item > a
div.template-box > ul.list > li.list-item > a div.template-box > ul.list > li.list-item > a
div.template-box > ul.list > li.list-item > a div.template-box > ul.list > li.list-item > a
div.template-box > ul.list > li.list-item > a div.template-box > ul.list > li.list-item > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
Buttons have an accessible name
Form elements have associated labels
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
All heading elements contain content.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
AttributionReporting
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header-logo > h1 > a > img div.header-logo > h1 > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
div.container > ul > li > img div.container > ul > li > img
div.container > ul > li > img div.container > ul > li > img
div.container > ul > li > img div.container > ul > li > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

79
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
64
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.45 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.22 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.002

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.37 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

2.22 s

Detailed Report

Audit breakdown by category with detailed findings.

79

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
isweb.co.kr/file/renew/font/Pretendard-Bold.woff14400.0 s1.1 MiB
isweb.co.kr/file/renew/font/Pretendard-SemiBold.woff14400.0 s1.1 MiB
isweb.co.kr/file/renew/font/Pretendard-Medium.woff14400.0 s1.1 MiB
isweb.co.kr/file/renew/images/K-006.png14400.0 s1.1 MiB
isweb.co.kr/file/renew/font/Pretendard-Regular.woff14400.0 s1.1 MiB
isweb.co.kr/file/renew/images/K-007.png14400.0 s1.0 MiB
isweb.co.kr/file/renew/images/K-002.png14400.0 s912.9 KiB
isweb.co.kr/file/renew/images/K-001.png14400.0 s779.2 KiB
isweb.co.kr/file/renew/images/K-003.png14400.0 s774.3 KiB
isweb.co.kr/file/renew/images/K-005.png14400.0 s572.5 KiB
isweb.co.kr/file/plugin/froala/js/froala_editor.pkgd.min.js14400.0 s128.7 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
isweb.co.kr/file/plugin/jquery.ui/jquery-ui.js14400.0 s113.8 KiB
isweb.co.kr/file/renew/images/icon_footer_on_02.png14400.0 s79.5 KiB
isweb.co.kr/file/renew/images/icon_footer_on_01.png14400.0 s79.2 KiB
/signals/config/1484898934979788?v=2.9.303&r=stable&domai...1200.0 s44.7 KiB
cdn.datamanager.co.kr/0/tcsdm.js?eid=1h823ex6u2ypg1h823ex6u0.0 ms31.4 KiB
isweb.co.kr/file/renew/images/img_main_order_01.png14400.0 s37.4 KiB
isweb.co.kr/file/renew/js/swiper.min.js14400.0 s35.5 KiB
isweb.co.kr/file/js/jQuery.js14400.0 s33.9 KiB
isweb.co.kr/file/renew/images/img_main_order_03.png14400.0 s33.5 KiB
isweb.co.kr/file/renew/images/img_main_order_02.png14400.0 s26.2 KiB
t1.daumcdn.net/adfit/static/kp.js1246.0 s19.1 KiB
ssl.pstatic.net/melona/libs/gfp-nac-module/synchronizer.js1236.0 s18.2 KiB
isweb.co.kr/file/renew/css/base.css14400.0 s18.2 KiB
cdn.onetag.co.kr/0/tcs.js?eid=1h823ex6u2ypg1h823ex6u0.0 ms11.8 KiB
wcs.pstatic.net/wcslog.js176.0 s10.4 KiB
isweb.co.kr/file/plugin/bootstrap/js/bootstrap.js14400.0 s14.3 KiB
isweb.co.kr/file/plugin/jquery.file.upload/js/jquery.fileupload.js14400.0 s14.0 KiB
isweb.co.kr/file/renew/images/logo.png14400.0 s13.7 KiB
isweb.co.kr/file/css/custom.css?v=2023080914400.0 s13.1 KiB
isweb.co.kr/file/plugin/jquery.bxslider/jquery.bxslider.js14400.0 s12.5 KiB
isweb.co.kr/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?14400.0 s12.3 KiB
isweb.co.kr/file/renew/css/common.css?v=2024062114400.0 s10.8 KiB
isweb.co.kr/file/plugin/froala/css/froala_editor.pkgd.css14400.0 s9.0 KiB
isweb.co.kr/file/plugin/jquery.ui/jquery-ui.css14400.0 s8.4 KiB
isweb.co.kr/file/plugin/ionicons/css/ionicons.css14400.0 s8.3 KiB
isweb.co.kr/file/plugin/font_awsome/css/font-awesome.css14400.0 s6.9 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...86400.0 s10.7 KiB
cdn.megadata.co.kr/dist/prod/utilKit.js?adverId=wemento0.0 ms3.9 KiB
isweb.co.kr/file/css/custom.s.css?version=20230721_14400.0 s4.6 KiB
isweb.co.kr/file/plugin/froala/js/languages/ko.js14400.0 s3.7 KiB
isweb.co.kr/file/renew/images/icon_device_02.png14400.0 s3.6 KiB
isweb.co.kr/file/renew/images/icon_device_03.png14400.0 s3.5 KiB
isweb.co.kr/file/renew/images/icon_device_01_on.png14400.0 s3.3 KiB
isweb.co.kr/file/renew/css/swiper.min.css14400.0 s3.3 KiB
isweb.co.kr/file/plugin/froala/css/froala_style.css14400.0 s2.0 KiB
isweb.co.kr/file/css/common.css?v=2024062114400.0 s1.8 KiB
isweb.co.kr/file/renew/js/common.js?a=114400.0 s1.7 KiB
isweb.co.kr/file/renew/images/icon_footer_consult.png14400.0 s1.6 KiB
isweb.co.kr/file/renew/images/icon_footer_kakao.png14400.0 s1.6 KiB
isweb.co.kr/file/plugin/jquery.bxslider/jquery.bxslider.css14400.0 s1.3 KiB
isweb.co.kr/file/renew/images/icon_footer_bottom.png14400.0 s1021 B
isweb.co.kr/file/renew/images/icon_footer_top.png14400.0 s1004 B
isweb.co.kr/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js2874.0 s758 B
isweb.co.kr/file/js/common.js?v=2023081714400.0 s889 B
isweb.co.kr/file/renew/images/icon_guide.png14400.0 s817 B
rum.beusable.net/script/b190718e140010u538/030056e5be3600.0 s561 B
isweb.co.kr/file/renew/images/icon_close_w.png14400.0 s650 B
isweb.co.kr/file/css/custom.m.css?version=20230721_14400.0 s599 B
/script/checker/b190718e140010u538/030056e5be?url=https%3...600.0 s336 B
isweb.co.kr/file/css/custom.xs.css?version=20230721_14400.0 s222 B
/tr/?id=1484898934979788&ev=PageView&dl=https%3A%2F%2Fisw...0.0 ms16 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:32.547 source:map[column:29825 line:4 type:source-location url:https://isweb.co.kr/file/js/jQuery.js urlProvider:network]] map[reflowTime:1.65 source:map[column:1222 line:0 type:source-location url:https://wcs.pstatic.net/wcslog.js urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
isweb.co.kr/file/renew/images/K-006.png1.1 MiB1.1 MiB
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
isweb.co.kr/file/renew/images/K-007.png1.0 MiB1.0 MiB
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
isweb.co.kr/file/renew/images/K-002.png912.5 KiB891.7 KiB
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
isweb.co.kr/file/renew/images/K-001.png778.8 KiB758.0 KiB
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
isweb.co.kr/file/renew/images/K-003.png773.9 KiB753.1 KiB
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
isweb.co.kr/file/renew/images/K-005.png572.2 KiB551.3 KiB
div.container > ul > li > img div.container > ul > li > img
isweb.co.kr/file/renew/images/img_main_order_01.png37.2 KiB36.7 KiB
div.container > ul > li > img div.container > ul > li > img
isweb.co.kr/file/renew/images/img_main_order_03.png33.2 KiB32.7 KiB
div.container > ul > li > img div.container > ul > li > img
isweb.co.kr/file/renew/images/img_main_order_02.png25.9 KiB25.6 KiB
div.header-logo > h1 > a > img div.header-logo > h1 > a > img
isweb.co.kr/file/renew/images/logo.png13.4 KiB13.4 KiB
ul > li.consult > a > ::after ul > li.consult > a > ::after
isweb.co.kr/file/renew/images/icon_footer_on_01.png78.9 KiB11.2 KiB

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
fonts.googleapis.com/earlyaccess/notosanskr.css204.0 KiB617 ms
isweb.co.kr/file/plugin/froala/js/froala_editor.pkgd.min.js128.7 KiB743 ms
isweb.co.kr/file/plugin/jquery.ui/jquery-ui.js113.8 KiB805 ms
t1.daumcdn.net/adfit/static/kp.js19.1 KiB285 ms
isweb.co.kr/file/js/jQuery.js33.9 KiB437 ms
fonts.googleapis.com/css2?family=Jua&display=swap12.2 KiB339 ms
isweb.co.kr/file/renew/js/swiper.min.js35.5 KiB376 ms
isweb.co.kr/file/renew/js/common.js?a=11.7 KiB192 ms
isweb.co.kr/file/plugin/jquery.file.upload/js/jquery.fileupload.js14.0 KiB254 ms
isweb.co.kr/file/plugin/bootstrap/js/bootstrap.js14.3 KiB315 ms
isweb.co.kr/file/plugin/jquery.bxslider/jquery.bxslider.js12.5 KiB254 ms
isweb.co.kr/file/renew/css/base.css18.2 KiB315 ms
isweb.co.kr/file/css/custom.css?v=2023080913.1 KiB254 ms
isweb.co.kr/file/renew/css/common.css?v=2024062110.8 KiB254 ms
isweb.co.kr/file/plugin/ionicons/css/ionicons.css8.3 KiB254 ms
wcs.pstatic.net/wcslog.js10.4 KiB273 ms
isweb.co.kr/file/plugin/jquery.ui/jquery-ui.css8.4 KiB254 ms
isweb.co.kr/file/plugin/froala/css/froala_editor.pkgd.css9.0 KiB254 ms
isweb.co.kr/file/plugin/froala/js/languages/ko.js3.7 KiB192 ms
isweb.co.kr/file/renew/css/swiper.min.css3.3 KiB192 ms
isweb.co.kr/file/plugin/font_awsome/css/font-awesome.css6.9 KiB70 ms
isweb.co.kr/file/js/common.js?v=20230817889 B192 ms
isweb.co.kr/file/css/common.css?v=202406211.8 KiB192 ms
isweb.co.kr/file/plugin/froala/css/froala_style.css2.0 KiB192 ms
isweb.co.kr/file/plugin/jquery.bxslider/jquery.bxslider.css1.3 KiB192 ms
cdn.jsdelivr.net/gh/moonspam/NanumBarunGothic@1.0/nanumbarungothicsubset.css686 B230 ms

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 22.9 KiB
URLTransfer SizeEst Savings
fonts.googleapis.com/earlyaccess/notosanskr.css204.0 KiB20.8 KiB
isweb.co.kr/file/css/custom.css?v=2023080913.1 KiB2.1 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.container > ul > li > img div.container > ul > li > img
isweb.co.kr/file/renew/images/img_main_order_02.png
div.container > ul > li > img div.container > ul > li > img
isweb.co.kr/file/renew/images/img_main_order_01.png
div.container > ul > li > img div.container > ul > li > img
isweb.co.kr/file/renew/images/img_main_order_03.png
div.header-logo > h1 > a > img div.header-logo > h1 > a > img
isweb.co.kr/file/renew/images/logo.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 635 ms
URLTime Spent
isweb.co.kr/735 ms
Time to Interactive 2.2 s
Layout shift culprits
Optimize DOM size
Font display
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 50 ms
User Timing marks and measures 10 user timings
JavaScript execution time 0.3 s
Minimizes main-thread work 0.9 s
Network Requests
Network Round Trip Times 290 ms
Server Backend Latencies 300 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Avoid large layout shifts 2 layout shifts found
INP breakdown
LCP request discovery
Avoid long main-thread tasks
Avoid non-composited animations
64

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
무료로 시작하기 div.list > ul > li.link > a

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header-logo > h1 > a > img div.header-logo > h1 > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
div.container > ul > li > img div.container > ul > li > img
div.container > ul > li > img div.container > ul > li > img
div.container > ul > li > img div.container > ul > li > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.header-logo > h1 > a div.container > div.header-logo > h1 > a
div.template-box > ul.list > li.list-item > a div.template-box > ul.list > li.list-item > a
div.template-box > ul.list > li.list-item > a div.template-box > ul.list > li.list-item > a
div.template-box > ul.list > li.list-item > a div.template-box > ul.list > li.list-item > a
div.template-box > ul.list > li.list-item > a div.template-box > ul.list > li.list-item > a
div.template-box > ul.list > li.list-item > a div.template-box > ul.list > li.list-item > a
div.template-box > ul.list > li.list-item > a div.template-box > ul.list > li.list-item > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
Form elements have associated labels
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
All heading elements contain content.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
AttributionReporting
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header-logo > h1 > a > img div.header-logo > h1 > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
ul.list > li.list-item > a > img ul.list > li.list-item > a > img
div.container > ul > li > img div.container > ul > li > img
div.container > ul > li > img div.container > ul > li > img
div.container > ul > li > img div.container > ul > li > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback