Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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

Performance issues directly impact user engagement and conversion rates.

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.

Request	Cache TTL	Transfer Size
ntm.pstatic.net/scripts/ntm_d26044233161.js	380.0 s	74.2 KiB
ntm.pstatic.net/ex/nlog.js	630.0 s	47.4 KiB
feblog.pstatic.net/real/mobile/2026.04.08/js/vendor.4cb4e8bee0d02e92cbe3.js	1402938.0 s	316.1 KiB
feblog.pstatic.net/real/mobile/2026.04.08/js/main.3b65a088125b5fdd4276.js	1402938.0 s	151.6 KiB
feblog.pstatic.net/real/mobile/2026.04.08/js/lottie-web.06b5e1309e7adfd2a7ae.js	1402939.0 s	75.0 KiB
feblog.pstatic.net/real/mobile/2026.04.08/js/react.9ab79fee18f8f6832d78.js	1402939.0 s	68.6 KiB
/MjAyNjA0MjFfNTEg/MDAxNzc2NzY1MDc5OTI5.jh6HpIKhDPEirlM8aB...	2585740.0 s	43.4 KiB
/real/mobile/2026.04.08/css/mobile-pages-DiscoverPage.18b...	1402963.0 s	38.6 KiB
/real/mobile/2026.04.08/js/mobile-pages-DiscoverPage.2f5a...	1402948.0 s	33.4 KiB
/MjAyNjA0MjBfMTc0/MDAxNzc2NjY2Nzg1MTI5.xMe6q0XX43JeNO0yOg...	2532527.0 s	26.3 KiB
feblog.pstatic.net/real/mobile/2026.04.08/css/main.7deae71e1b278c5891b1.css	1402939.0 s	11.2 KiB
/MjAyNjA0MTdfNyAg/MDAxNzc2MzkxNTU3ODQ0.3TiCMhC40s-XbvB4xL...	2578096.0 s	10.6 KiB
feblog.pstatic.net/real/mobile/2026.04.08/css/1355.ac9115d1f08ec7927941.css	1402939.0 s	8.7 KiB
feblog.pstatic.net/real/mobile/2026.04.08/js/8421.b5f807b8423b7d1d6f60.js	1402942.0 s	7.6 KiB
ssl.pstatic.net/static/blog/ico_comments_54x54_2.png	91128.0 s	1.5 KiB
/MjAyMDA2MTBfMjM2/MDAxNTkxNzY5NTc2MTE4.RkKi0ir_DpSIETXx-D...	512768.0 s	3.7 KiB
feblog.pstatic.net/real/mobile/2026.04.08/js/bootstrap.962ad38300ead7991f11.js	1402941.0 s	4.8 KiB
feblog.pstatic.net/real/mobile/2026.04.08/js/7238.cec7faef05a1348d91a4.js	1402939.0 s	4.7 KiB
/MjAyMjA3MjZfMjQ0/MDAxNjU4ODA3NzMwMDQ2.JWY2m_bHbnupp_lj-C...	1741689.0 s	4.3 KiB
feblog.pstatic.net/real/mobile/2026.04.08/js/1355.1f73ab98915cadd556d3.js	1402939.0 s	4.0 KiB
/MjAyNjA0MDlfMjQ0/MDAxNzc1NzIxODAzODgz.wH5gxPbu17RyNBBBp1...	1527587.0 s	3.9 KiB
/MjAyNjA0MjFfMjc5/MDAxNzc2NzY1NTU4MjUy.WpRk1SBebzMAV9gTUX...	2556017.0 s	3.9 KiB
feblog.pstatic.net/real/mobile/2026.04.08/js/1730.eb016aceec404407afe4.js	1402939.0 s	2.8 KiB
feblog.pstatic.net/real/mobile/2026.04.08/js/541.873f9023edd716e134d3.js	1402939.0 s	770 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:40.987 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.

	URL	Resource Size	Est Savings
썸네일 `li.item__Mfnij > a.link__rlnCZ > div.thumb_area__JRGMt > img.thumb__kHm2j`	/MjAyNjA0MjFfNTEg/MDAxNzc2NzY1MDc5OTI5.jh6HpIKhDPEirlM8aB...	43.1 KiB	39.1 KiB
썸네일 `li.item__Mfnij > a.link__rlnCZ > div.thumb_area__JRGMt > img.thumb__kHm2j`	/MjAyNjA0MjFfMTgz/MDAxNzc2NzY0NDczMDcw.Ipl_bcPAt9tDMNLsYu...	49.9 KiB	35.2 KiB
썸네일 `li.item__Mfnij > a.link__rlnCZ > div.thumb_area__JRGMt > img.thumb__kHm2j`	/MjAyNjA0MjFfNCAg/MDAxNzc2NzYzMzUyNTU3.S5NpQ03Pvu3X0roUza...	34.5 KiB	30.5 KiB
썸네일 `li.item__Mfnij > a.link__rlnCZ > div.thumb_area__JRGMt > img.thumb__kHm2j`	/MjAyNjA0MjBfMjU4/MDAxNzc2Njc5ODY2MjY3.rKSlF6C16Q0Pw46P1I...	30.8 KiB	26.7 KiB
썸네일 `li.item__Mfnij > a.link__rlnCZ > div.thumb_area__JRGMt > img.thumb__kHm2j`	/MjAyNjA0MjBfMTc0/MDAxNzc2NjY2Nzg1MTI5.xMe6q0XX43JeNO0yOg...	26.0 KiB	11.3 KiB
프로필 `div.info_wrap__pCJq2 > a.profile__MSJ0k > span.thumb_area__JRGMt > img.thumb__kHm2j`	/MjAyNjA0MTdfNyAg/MDAxNzc2MzkxNTU3ODQ0.3TiCMhC40s-XbvB4xL...	10.3 KiB	10.1 KiB

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:1004.3150009765625 label:Time to first byte subpart:timeToFirstByte] map[duration:9.9359990234375 label:Resource load delay subpart:resourceLoadDelay] map[duration:66.236 label:Resource load duration subpart:resourceLoadDuration] map[duration:2664.487 label:Element render delay subpart:elementRenderDelay]]

lhId: page-4-IMG

nodeLabel: 썸네일

path: 1,HTML,1,BODY,0,DIV,1,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,UL,0,LI,0,A,0,DIV,0,IMG

selector: li.item__Mfnij > a.link__rlnCZ > div.thumb_area__JRGMt > img.thumb__kHm2j

snippet: <img class="thumb__kHm2j lazyload opacity__zbNuA" alt="썸네일" data-src="https://mblogthumb-phinf.pstatic.net/MjAyNjA0MjBfMTc0/MDAxNzc2NjY2Nzg1MTI5…" data-toggle-class="opacity__zbNuA" src="https://mblogthumb-phinf.pstatic.net/MjAyNjA0MjBfMTc0/MDAxNzc2NjY2Nzg1MTI5…" data-loaded="true">

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

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: 3.4 s

URL	Time Spent
blog.naver.com/	1.0 s
section.blog.naver.com/	630 ms
section.blog.naver.com/	726 ms
m.blog.naver.com/?proxyReferer=&noTrackingCode=true	1.1 s
m.blog.naver.com/Recommendation.naver	0.0 ms

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: 595 ms

URL	Time Spent
m.blog.naver.com/Recommendation.naver	695 ms

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

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: 300 ms 33.8 KiB

URL	Transfer Size	Est Savings
/real/mobile/2026.04.08/css/mobile-pages-DiscoverPage.18b...	38.4 KiB	33.8 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

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.1 s 414.0 KiB

URL	Transfer Size	Est Savings
feblog.pstatic.net/real/mobile/2026.04.08/js/vendor.4cb4e8bee0d02e92cbe3.js	315.8 KiB	219.9 KiB
feblog.pstatic.net/real/mobile/2026.04.08/js/main.3b65a088125b5fdd4276.js	149.3 KiB	72.8 KiB
feblog.pstatic.net/real/mobile/2026.04.08/js/lottie-web.06b5e1309e7adfd2a7ae.js	74.8 KiB	47.4 KiB
feblog.pstatic.net/real/mobile/2026.04.08/js/react.9ab79fee18f8f6832d78.js	68.4 KiB	26.7 KiB
ntm.pstatic.net/scripts/ntm_d26044233161.js	73.3 KiB	24.7 KiB
ntm.pstatic.net/ex/nlog.js	47.2 KiB	22.6 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
feblog.pstatic.net/real/mobile/2026.04.08/js/vendor.4cb4e8bee0d02e92cbe3.js	2.2 s	1.2 s	86 ms
m.blog.naver.com/Recommendation.naver	747 ms	4.7 ms	9.1 ms
feblog.pstatic.net/real/mobile/2026.04.08/js/main.3b65a088125b5fdd4276.js	489 ms	441 ms	40 ms
Unattributable	323 ms	12 ms	0.0 ms
ntm.pstatic.net/scripts/ntm_d26044233161.js	142 ms	111 ms	30 ms
ntm.pstatic.net/ex/nlog.js	58 ms	45 ms	13 ms
feblog.pstatic.net/real/mobile/2026.04.08/js/lottie-web.06b5e1309e7adfd2a7ae.js	58 ms	31 ms	27 ms

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.

Category	Time Spent
Script Evaluation	1.9 s
Other	897 ms
Style & Layout	744 ms
Rendering	272 ms
Script Parsing & Compilation	239 ms
Garbage Collection	42 ms
Parse HTML & CSS	39 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 reason	Failure 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

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

●LCP request discovery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,138 KiB

●Avoid long main-thread tasks 12 long tasks found

●Avoid non-composited animations 1 animated element found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 290 ms

●Server Backend Latencies 350 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

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 > div.trend_keyword__ie_R8 > h3.title__trMmQ > span.highlight___jgpD`
트렌드 키워드 `div > div.trend_keyword__ie_R8 > button.refresh_btn__APuVg > span.strong__qGvhA`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
지금 뜨고 있는 트렌드 키워드 ⭐ `div.virtual-column > div > div.trend_keyword__ie_R8 > h3.title__trMmQ`

These are opportunities to improve keyboard navigation in your application.

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

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

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-*]` 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

●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

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

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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

○`<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

○Form elements have associated labels

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

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URL	Request Resolution
section.blog.naver.com/	Allowed

●Avoids deprecated APIs

●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

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.

Crawling and Indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
`head > meta`

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
362	`D`	`Syntax not understood`

To appear in search results, crawlers need access to your app.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

○Structured data is valid

●Document has a `<title>` element

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`