Skip to content
Audit Complete

Results for https://koreatimes.co.kr

Visit site
KR · KRW (₩) · Estimated Applicable regulations: PIPA Dev cost: ₩70,000/hr How jurisdiction is detected
Spain Spain · Madrid Completed: Apr 15, 2026 23:21 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)
D66

Site Health

Score: 66 / 100

Based on 8 categories, 0 sections

Room to improve — your 22.5s load time is above Google's 2.5s 'Good' threshold.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

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

Amazon ELB sites average 70
At average
Azure DNS sites average 68
At average

Top Priorities (5)

1

Content-Security-Policy header is missing

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

Security › Security Headers
2

HSTS header is missing

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

Security › Security Headers
3

No Content-Security-Policy header found

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

Security › Content Security Policy
4

Page weighs 12.5 MB (6.3 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

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%2Fkoreatimes.co.kr)](https://beavercheck.com/results/bd628205-0b2c-42ae-a9e5-9309b37c9543)
<a href="https://beavercheck.com/results/bd628205-0b2c-42ae-a9e5-9309b37c9543"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fkoreatimes.co.kr" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fkoreatimes.co.kr

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 22.5s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
Your LCP is 22.5s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
1 accessibility issue excludes users who rely on assistive technology.
C
Could reach Estimate based on resolving critical issues

Return on Investment

₩350,000 investment → ₩2,134/month returns + KRW 3,000,000,000 risk avoided

Payback period: > 2 years First-year ROI: -93%

Investment

₩350,000

5h · 5 findings

Monthly returns

₩2,134 /mo

~₩25,607 / year

  • Bandwidth savings ₩2,134

Regulatory risk avoided

KRW 3,000,000,000

if kept compliant

  • PIPA KRW 3,000,000,000

₩105,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

₩350,000

5.0 developer hours at ₩70000/hr

Based on South Korea rates (₩70000/hr)

Quick wins
₩105,000 3 fixes in ~90 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

₩250,002,134 / month at risk

~₩3,000,025,607 / year if left unfixed

Compliance Risk

₩3,000,000,000

PIPA
  • No privacy policy link detected
    PIPA: KRW 1,000,000 – KRW 3,000,000,000
  • Trackers detected but no cookie policy found
    PIPA: KRW 1,000,000 – KRW 3,000,000,000
  • Trackers detected but no privacy policy found
    PIPA: KRW 1,000,000 – KRW 3,000,000,000

+1 more

Bandwidth Waste

₩2,134 /mo

19738.6 MB/mo × 108.108 KRW/GB

  • Optimize transfer: save ~2.0 MB per page load
    Saves ₩2,134/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.

19
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
95
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
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.

7.56 s

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

22.51 s

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

1.67 s

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

0.205

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

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

35.98 s

Detailed Report

Audit breakdown by category with detailed findings.

19

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.000817] map[node:map[boundingRect:map[bottom:180 height:74 left:16 right:396 top:106 width:380] lhId:page-8-H2 nodeLabel:From bombs to economic warfare: US pivots on Iran path:1,HTML,1,BODY,3,DIV,5,DIV,0,DIV,0,ARTICLE,0,DIV,0,DIV,0,A,0,H2 selector:div.Top1Module_article__zeI2k > div.Top1Module_left-wrap__LWx54 > a.Top1Module_link__MiOlj > h2.Top1Module_title__Ho8pF snippet:<h2 class="Top1Module_title__Ho8pF"> type:node] score:0.000817 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://www.koreatimes.co.kr/_next/static/media/119cf01b445a4dc3-s.woff2]] map[cause:Web font extra:map[type:url value:https://www.koreatimes.co.kr/_next/static/media/14ca4067a94f5022-s.woff2]]] type:subitems]]]
headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.204658] map[node:map[boundingRect:map[bottom:1494 height:1408 left:0 right:412 top:86 width:412] lhId:page-13-DIV nodeLabel:From bombs to economic warfare: US pivots on Iran WASHINGTON — If the U.S. and… path:1,HTML,1,BODY,3,DIV,5,DIV selector:body.__variable_def9a7 > div.Wrapper_wrap__YfhIp > div.Top1Module_wrap__ps0_s snippet:<div class="Top1Module_wrap__ps0_s"> type:node] score:0.104496] map[node:map[boundingRect:map[bottom:1470 height:585 left:16 right:396 top:884 width:380] lhId:page-10-ARTICLE nodeLabel:US reaction backs South Korea jail term for American streamer SEATTLE — Online… path:1,HTML,1,BODY,3,DIV,5,DIV,0,DIV,1,ARTICLE selector:div.Wrapper_wrap__YfhIp > div.Top1Module_wrap__ps0_s > div.Top1Module_multi-layout__AC977 > article.Top1Module_article-wrap__Im_A1 snippet:<article class="Top1Module_article-wrap__Im_A1 Top1Module_sub-article-wrap__l6JGt"> type:node] score:0.100162]]

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:46.228 source:map[type:text value:[unattributed]]]]

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
4 Korean books shortlisted for 2026 Locus Awards thumbnail article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/15/f589498b-8069-44ff-932f-14a5bf9fa351.jpg?w=768174.5 KiB110.6 KiB
Iran says 26 million have volunteered to do military service thumbnail article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/16/93d3b698-d115-4b27-9a25-8f9cd02dc0bb.jpg?w=768121.6 KiB73.6 KiB
Wage, safety violations against migrant workers uncovered in South Jeolla Provi… article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/15/f465b2d8-cf57-4ac4-aea8-57de33692efc.jpeg?w=76878.1 KiB30.1 KiB
thumbnail article.Top1Module_article-wrap__Im_A1 > a.Top1Module_article__zeI2k > div.Top1Module_figure__8D34T > img
/2026/04/15/62e92a7e-0a77-46e0-8749-e27d1c5f9118.jpeg?w=76873.9 KiB26.0 KiB
US stocks hit all-time high on Middle East optimism thumbnail article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/16/74ad542a-e20e-47fa-9dec-f4cbfaa8c9b1.jpg?w=76869.6 KiB21.6 KiB
Korea has no plans to pay Iran for passage of stranded ships in Strait of Hormu… article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/15/f385e797-e003-42d1-a99a-0d7182de7a7d.jpg?w=76863.9 KiB16.0 KiB
From bombs to economic warfare: US pivots on Iran thumbnail article.Top1Module_article-wrap__Im_A1 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/16/46d80f0d-5d67-4281-b5e4-8e884304dd70.jpg?w=76859.2 KiB14.8 KiB
KOSPI settles above 6,000 as hope grows for second US-Iran truce talks thumbnail article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/15/cd07f718-a3d5-442c-af69-146a9fc1d3d3.jpg?w=76854.0 KiB12.6 KiB
/2026/04/15/e2b23ddf-a13d-4af7-8c54-9b75d10fd116.jpeg?w=76848.1 KiB12.0 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
value: No additional origins are good candidates for preconnecting

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.

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 3.9 s

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
From bombs to economic warfare: US pivots on Iran WASHINGTON — If the U.S. and… body.__variable_def9a7 > div.Wrapper_wrap__YfhIp > div.Top1Module_wrap__ps0_s
0.104
US reaction backs South Korea jail term for American streamer SEATTLE — Online… div.Wrapper_wrap__YfhIp > div.Top1Module_wrap__ps0_s > div.Top1Module_multi-layout__AC977 > article.Top1Module_article-wrap__Im_A1
0.100
From bombs to economic warfare: US pivots on Iran div.Top1Module_article__zeI2k > div.Top1Module_left-wrap__LWx54 > a.Top1Module_link__MiOlj > h2.Top1Module_title__Ho8pF
0.001

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

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.

Estimated savings: 170 ms 23.1 KiB

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 Evaluation5.9 s
Other2.2 s
Style & Layout1.3 s
Script Parsing & Compilation786 ms
Rendering321 ms
Garbage Collection299 ms
Parse HTML & CSS229 ms

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.

Estimated savings: 0.0 ms 2.1 KiB
URLTransfer SizeEst Savings
www.koreatimes.co.kr/initlib/ktet.js8.7 KiB2.1 KiB

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

Document request latency
Optimize DOM size
Font display
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 13 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 280 ms
Server Backend Latencies 230 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 320 ms
INP breakdown
Avoid non-composited animations
95

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
REVIEW div.HomeSectionArticle_text-area__Z8EXH > a.HomeSectionArticle_link__G2ROE > h3.HomeSectionArticle_title__DQEhd > span.Tag_wrap__cbdDh
By Sho Chang-young li.Opinion_item__kCEoe > a.Opinion_link__g7ypC > div.Opinion_info__A7Px9 > p.Opinion_name__rSiXA
By Gwynne Dyer li.Opinion_item__kCEoe > a.Opinion_link__g7ypC > div.Opinion_info__A7Px9 > p.Opinion_name__rSiXA

These are opportunities to improve the legibility of your content.

Best practices

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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
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
Deprecated ARIA roles were not used
ARIA IDs are unique
Identical links have the same purpose.
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
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
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
The page contains a heading, skip link, or landmark region
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>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
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.
96

Best Practices

Trust and Safety

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.

Why this matters

Performance issues directly impact user engagement and conversion rates.

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation 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
Redirects HTTP traffic to HTTPS
100

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.

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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

56
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
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.

2.74 s

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

4.88 s

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

139 ms

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

0.031

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

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

8.47 s

Detailed Report

Audit breakdown by category with detailed findings.

56

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
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s73.1 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=92911800.0 s58.4 KiB
cdn.id5-sync.com/api/1.0/esp.js3600.0 s34.7 KiB
sdk.mrf.io/statics/0639f9e9af1a7496d5c3.js3600.0 s24.0 KiB
t1.kakaocdn.net/kakao_js_sdk/2.7.4/kakao.min.js14782.0 s26.8 KiB
ssl.pstatic.net/melona/libs/gfp-nac-module/synchronizer.js1926.0 s18.2 KiB
scripts.clarity.ms/0.8.59/clarity.js86400.0 s26.2 KiB
wcs.naver.net/wcslog.js172.0 s10.5 KiB
connectid.analytics.yahoo.com/connectId-gpt.js3600.0 s9.0 KiB
static.criteo.net/js/ld/publishertag.ids.js86400.0 s14.8 KiB
tags.crwdcntrl.net/lt/c/16589/sync.min.js86400.0 s13.2 KiB
sdk.mrf.io/statics/compass-multimedia-sdk.js?version=22583600.0 s4.3 KiB
invstatic101.creativecdn.com/encrypted-signals/encrypted-tag-g.js0.0 ms2.9 KiB
dmp.im-apps.net/secure-signal/provider.js3600.0 s2.5 KiB
cdn.mgaru.dev/static/myGaruStandalone.js14400.0 s2.1 KiB
ads.pubmatic.com/AdServer/js/google-esp.js107205.0 s3.4 KiB
/pagead/js/r20260414/r20110914/client/window_focus_fy2021.js1209600.0 s1.2 KiB
cdn.jsdelivr.net/gh/prebid/shared-id/pubcid.js/docs/pubcid.min.js604800.0 s698 B
/a?v=3&t=l&pid=1972357757&rv=64e1&tag_exp=0~115938466~115...0.0 ms11 B
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s0 B
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s0 B
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s0 B
/pagead/js/r20260414/r20110914/client/window_focus_fy2021.js1209600.0 s0 B
/pagead/js/r20260414/r20110914/client/window_focus_fy2021.js1209600.0 s0 B
/pagead/js/r20260414/r20110914/client/window_focus_fy2021.js1209600.0 s0 B

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:87.937 source:map[type:text value:[unattributed]]]]

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
4 Korean books shortlisted for 2026 Locus Awards thumbnail article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/15/f589498b-8069-44ff-932f-14a5bf9fa351.jpg?w=1024282.5 KiB216.6 KiB
Iran says 26 million have volunteered to do military service thumbnail article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/16/93d3b698-d115-4b27-9a25-8f9cd02dc0bb.jpg?w=1024203.9 KiB175.2 KiB
thumbnail article.Top1Module_article-wrap__Im_A1 > a.Top1Module_article__zeI2k > div.Top1Module_figure__8D34T > img
/2026/04/15/62e92a7e-0a77-46e0-8749-e27d1c5f9118.jpeg?w=1024126.7 KiB117.0 KiB
/2026/04/15/c0b9aeb3-8794-4cc3-bc34-9469d0a4b9d8.jpeg?w=1024125.7 KiB97.0 KiB
Wage, safety violations against migrant workers uncovered in South Jeolla Provi… article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/15/f465b2d8-cf57-4ac4-aea8-57de33692efc.jpeg?w=1024119.0 KiB90.3 KiB
US stocks hit all-time high on Middle East optimism thumbnail article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/16/74ad542a-e20e-47fa-9dec-f4cbfaa8c9b1.jpg?w=1024110.5 KiB82.7 KiB
Korea has no plans to pay Iran for passage of stranded ships in Strait of Hormu… article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/15/f385e797-e003-42d1-a99a-0d7182de7a7d.jpg?w=1024101.3 KiB75.8 KiB
From bombs to economic warfare: US pivots on Iran thumbnail article.Top1Module_article-wrap__Im_A1 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/16/46d80f0d-5d67-4281-b5e4-8e884304dd70.jpg?w=102495.3 KiB71.5 KiB
KOSPI settles above 6,000 as hope grows for second US-Iran truce talks thumbnail article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/15/cd07f718-a3d5-442c-af69-146a9fc1d3d3.jpg?w=102487.9 KiB65.3 KiB
/2026/04/15/73aa5218-db74-43f7-beb6-7a159c9d288b.jpg?w=102471.5 KiB53.5 KiB
BOK chief nominee apologizes over asset, nationality controversies at hearing t… article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/15/74241b08-7f93-47a4-bafa-cb852a5509ee.jpg?w=102470.9 KiB53.0 KiB
/2026/04/16/899402f6-8cd6-4635-a91e-528ee2498af8.jpg?w=102468.4 KiB48.6 KiB
/2026/04/16/9c302228-7476-48a1-a294-597bf5e6362d.jpg?w=102471.6 KiB47.7 KiB
S. Korea required to make ironclad nonproliferation guarantee over nuclear subm… article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/15/a9a311c6-8248-4c03-8135-f9732d59c612.jpg?w=102463.7 KiB47.7 KiB
Trump posts image of himself with Jesus as his pope criticism continues thumbna… article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/16/913298ae-2412-4371-9c56-c83ffe57d3be.jpeg?w=102459.7 KiB43.3 KiB
body > div#google_image_div > a#aw0 > img.img_ad body > div#google_image_div > a#aw0 > img.img_ad
tpc.googlesyndication.com/simgad/343067856909921923740.1 KiB35.2 KiB
body > div#google_image_div > a#aw0 > img.img_ad body > div#google_image_div > a#aw0 > img.img_ad
tpc.googlesyndication.com/simgad/1806933678016957972138.0 KiB27.3 KiB
US says 9 vessels turned back in 48 hours of Iran port blockade thumbnail article.Top1Module_multi-layout__AC977 > div.Top1Module_article__zeI2k > a.Top1Module_figure__8D34T > img
/2026/04/16/a42a4ef7-02fa-4ed6-b0a6-0181a7d88406.jpg?w=102447.0 KiB27.3 KiB
body > div#google_image_div > a#aw0 > img.img_ad body > div#google_image_div > a#aw0 > img.img_ad
tpc.googlesyndication.com/simgad/510638643501226769331.2 KiB26.4 KiB
body > div#google_image_div > a#aw0 > img.img_ad body > div#google_image_div > a#aw0 > img.img_ad
tpc.googlesyndication.com/simgad/1769250030760132438318.8 KiB13.9 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
value: No additional origins are good candidates for preconnecting

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.

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.6 s

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

Diagnostics

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 reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 Evaluation2.2 s
Other839 ms
Style & Layout395 ms
Script Parsing & Compilation238 ms
Rendering147 ms
Garbage Collection115 ms
Parse HTML & CSS71 ms

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.

Estimated savings: 0.0 ms 2.1 KiB
URLTransfer SizeEst Savings
www.koreatimes.co.kr/initlib/ktet.js8.7 KiB2.1 KiB

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.

Estimated savings: 0.0 ms 22.6 KiB

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

Max Potential First Input Delay 120 ms
Layout shift culprits
Document request latency
Optimize DOM size
Font display
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 86 user timings
Avoid long main-thread tasks 11 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 270 ms
Server Backend Latencies 240 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 20 ms
Avoid large layout shifts 6 layout shifts found
INP breakdown
Avoid non-composited animations
96

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
INTERNATIONAL div.SettingBar_inner__uBjFU > div.SettingBar_main-edition__NNWnf > span.SettingBar_label-wrap__nnD1H > label
REVIEW article.SectionList_article-item__J_plF > a.SectionList_link__5GLzd > h4.SectionList_headline__qnXNy > span.Tag_wrap__cbdDh

These are opportunities to improve the legibility of your content.

Best practices

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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
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
The page contains a heading, skip link, or landmark region
ARIA IDs are unique
No form fields have multiple labels
`<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.
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>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
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.
96

Best Practices

Trust and Safety

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.

Why this matters

Performance issues directly impact user engagement and conversion rates.

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation 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
Redirects HTTP traffic to HTTPS
100

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.

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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback