Skip to content
https://social-plugins.line.me

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

29

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.

RequestCache TTLTransfer Size
developers.line.biz/_nuxt/prkPQDO6.js300.0 s420.0 KiB
developers.line.biz/images/top/as2.webp300.0 s79.7 KiB
developers.line.biz/_nuxt/_Fv01iQh.js300.0 s79.4 KiB
developers.line.biz/images/top/as1.webp300.0 s77.2 KiB
developers.line.biz/_nuxt/Cxi3vQKm.js300.0 s67.3 KiB
developers.line.biz/_nuxt/entry.XU__DSq0.css300.0 s49.8 KiB
developers.line.biz/_nuxt/CrbTXa04.js300.0 s47.1 KiB
/line-developers/docs/assets/fonts/line-seed-sans/WOFF/LI...300.0 s17.3 KiB
/line-developers/docs/assets/fonts/line-seed-sans/WOFF/LI...300.0 s16.7 KiB
developers.line.biz/_nuxt/szH1qBxF.js300.0 s13.3 KiB
developers.line.biz/_nuxt/Lt0PaMvO.js300.0 s13.0 KiB
developers.line.biz/images/common/logo-black.svg300.0 s11.2 KiB
developers.line.biz/images/common/logo-white.svg300.0 s11.2 KiB
developers.line.biz/_nuxt/BaseLayout.DryLLHoQ.css300.0 s9.0 KiB
developers.line.biz/_nuxt/B5eCqZVY.js300.0 s8.2 KiB
developers.line.biz/_nuxt/BYT-zroz.js300.0 s5.6 KiB
developers.line.biz/_nuxt/BTUmY--6.js300.0 s5.4 KiB
developers.line.biz/images/icons/products/light/msg.svg300.0 s4.4 KiB
developers.line.biz/images/icons/products/light/blockchain.svg300.0 s4.4 KiB
developers.line.biz/_nuxt/C-4GxZT9.js300.0 s4.2 KiB
developers.line.biz/images/icons/products/light/pay.svg300.0 s3.9 KiB
developers.line.biz/images/icons/products/light/login.svg300.0 s3.8 KiB
developers.line.biz/_nuxt/J5eZBgOb.js300.0 s3.2 KiB
developers.line.biz/images/icons/products/light/liff.svg300.0 s2.8 KiB
developers.line.biz/_nuxt/BDornkwx.js300.0 s2.6 KiB
developers.line.biz/_nuxt/Dbv2QMgT.js300.0 s2.6 KiB
developers.line.biz/_nuxt/BT3Jz119.js300.0 s2.4 KiB
developers.line.biz/_nuxt/DajjyPL4.js300.0 s2.3 KiB
developers.line.biz/_nuxt/index.BInUqC-a.css300.0 s2.1 KiB
developers.line.biz/_nuxt/DYgwRWPV.js300.0 s2.0 KiB
developers.line.biz/_nuxt/BYPZXu6Y.js300.0 s2.0 KiB
developers.line.biz/_nuxt/r0vVXu-3.js300.0 s2.0 KiB
developers.line.biz/_nuxt/D5ODQtHp.js300.0 s2.0 KiB
developers.line.biz/_nuxt/CLNKnlQW.js300.0 s1.6 KiB
developers.line.biz/images/icons/products/light/mini.svg300.0 s1.4 KiB
developers.line.biz/_nuxt/DUQ2EZlW.js300.0 s1.4 KiB
developers.line.biz/_nuxt/82OPCwt4.js300.0 s1.4 KiB
developers.line.biz/_nuxt/CCtt_pXX.js300.0 s1.4 KiB
developers.line.biz/_nuxt/m58zcBu5.js300.0 s1.4 KiB
developers.line.biz/_nuxt/X3wbroe1.js300.0 s1.3 KiB
developers.line.biz/_nuxt/CeqTCCIG.js300.0 s1.3 KiB
developers.line.biz/_nuxt/PUSqk0tl.js300.0 s1.2 KiB
developers.line.biz/_nuxt/ChDTfRIv.js300.0 s1.1 KiB
developers.line.biz/_nuxt/0TrngcGz.js300.0 s1.1 KiB
developers.line.biz/_nuxt/ClvyDXd8.js300.0 s1.0 KiB
developers.line.biz/_nuxt/DMeU8Xgk.js300.0 s1.0 KiB
developers.line.biz/_nuxt/BLGoNbmR.js300.0 s1.0 KiB
developers.line.biz/_nuxt/Bgms0fH8.js300.0 s1.0 KiB
developers.line.biz/_nuxt/XASAm_8K.js300.0 s1022 B
developers.line.biz/_nuxt/ZRAsEBTi.js300.0 s1005 B
developers.line.biz/_nuxt/Bnn1cFqM.js300.0 s940 B
developers.line.biz/_nuxt/DWBlcy01.js300.0 s909 B
developers.line.biz/_nuxt/CoB336W2.js300.0 s893 B
developers.line.biz/_nuxt/BrD0XtG_.js300.0 s877 B
developers.line.biz/_nuxt/BheWnx7M.js300.0 s870 B
developers.line.biz/_nuxt/B_Ejc2wA.js300.0 s845 B
developers.line.biz/_nuxt/YXuVqr5m.js300.0 s823 B
developers.line.biz/_nuxt/D_EM6cAh.js300.0 s805 B
developers.line.biz/_nuxt/DpXBMKwh.js300.0 s802 B
developers.line.biz/_nuxt/BVx47BmE.js300.0 s794 B
developers.line.biz/_nuxt/h9uDRzKI.js300.0 s785 B
developers.line.biz/_nuxt/MOeAtZ1q.js300.0 s783 B
developers.line.biz/_nuxt/D2IU_SR4.js300.0 s759 B
developers.line.biz/_nuxt/BADamYcw.js300.0 s751 B
developers.line.biz/_nuxt/BffxFq_0.js300.0 s750 B
developers.line.biz/_nuxt/DPxYUU_D.js300.0 s742 B
developers.line.biz/_nuxt/BKXe4xp_.js300.0 s719 B
developers.line.biz/_nuxt/DlAUqK2U.js300.0 s717 B
developers.line.biz/_nuxt/TransitionExpand.C7MR6gY2.css300.0 s702 B
developers.line.biz/_nuxt/VGDL7mTD.js300.0 s690 B
developers.line.biz/_nuxt/BFu_P-Ux.js300.0 s683 B
developers.line.biz/_nuxt/NewBadge.SwHpl8c9.css300.0 s674 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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
/line-developers/docs/assets/fonts/line-seed-sans/WOFF/LI...300 ms
/line-developers/docs/assets/fonts/line-seed-sans/WOFF/LI...275 ms
/laicon/edge/latest/fonts/laicon-extrabold-5c38942e.woff2...20 ms
/laicon/edge/latest/fonts/laicon-regular-5c38942e.woff2?1...15 ms
static.line-scdn.net/laicon/edge/latest/fonts/laicon-solid-5c38942e.woff2?18b1b315 ms

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:149.681 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
div.absolute > div#bg-top-img-1 > picture > img.h-full div.absolute > div#bg-top-img-1 > picture > img.h-full
developers.line.biz/images/top/as2.webp79.0 KiB32.7 KiB
div.absolute > div#bg-top-img-2 > picture > img.h-full div.absolute > div#bg-top-img-2 > picture > img.h-full
developers.line.biz/images/top/as1.webp76.5 KiB30.3 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:1025.179 label:Time to first byte subpart:timeToFirstByte] map[duration:257.377 label:Resource load delay subpart:resourceLoadDelay] map[duration:1342.976 label:Resource load duration subpart:resourceLoadDuration] map[duration:158.529 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: div.absolute > div#bg-top-img-1 > picture > img.h-full
path: 1,HTML,1,BODY,0,DIV,8,DIV,2,DIV,3,DIV,1,DIV,0,DIV,1,DIV,0,PICTURE,1,IMG
selector: div.absolute > div#bg-top-img-1 > picture > img.h-full
snippet: <img src="https://developers.line.biz/images/top/as2.webp" alt="" class="h-full w-full object-none sm:object-cover" style="object-position:65% 50%;" data-v-fdc6867a="">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: div.absolute > div#bg-top-img-1 > picture > img.h-full
path: 1,HTML,1,BODY,0,DIV,8,DIV,2,DIV,3,DIV,1,DIV,0,DIV,1,DIV,0,PICTURE,1,IMG
selector: div.absolute > div#bg-top-img-1 > picture > img.h-full
snippet: <img src="https://developers.line.biz/images/top/as2.webp" alt="" class="h-full w-full object-none sm:object-cover" style="object-position:65% 50%;" data-v-fdc6867a="">

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

URLTransfer SizeDuration
developers.line.biz/_nuxt/entry.XU__DSq0.css49.8 KiB793 ms
developers.line.biz/_nuxt/index.BInUqC-a.css2.1 KiB
fonts.googleapis.com/css2?family=LINE+Seed+JP:wght@400;700;800&display=swap89.0 KiB921 ms
developers.line.biz/_nuxt/TransitionExpand.C7MR6gY2.css702 B
developers.line.biz/_nuxt/NewBadge.SwHpl8c9.css674 B
developers.line.biz/_nuxt/BaseLayout.DryLLHoQ.css9.0 KiB396 ms
fonts.googleapis.com/css2?family=Noto+Sans+JP&display=swap30.2 KiB1.1 s
static.line-scdn.net/laicon/edge/latest/laicon.min.css6.6 KiB768 ms

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

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.

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.0 s
URLTime Spent
social-plugins.line.me/1.0 s
developers.line.biz/?r=/docs/line-social-plugins/0.0 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

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: 790 ms 118.7 KiB
URLTransfer SizeEst Savings
fonts.googleapis.com/css2?family=LINE+Seed+JP:wght@400;700;800&display=swap88.9 KiB88.9 KiB
fonts.googleapis.com/css2?family=Noto+Sans+JP&display=swap29.8 KiB29.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: 400 ms 157.5 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-K94RFW73WS156.8 KiB64.0 KiB
developers.line.biz/_nuxt/Cxi3vQKm.js66.7 KiB38.1 KiB
developers.line.biz/_nuxt/prkPQDO6.js332.9 KiB32.2 KiB
developers.line.biz/_nuxt/CrbTXa04.js46.5 KiB23.3 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.

URLTotal CPU TimeScript EvaluationScript Parse
Unattributable13.0 s11.1 s0.0 ms
developers.line.biz/?r=/docs/line-social-plugins/2.1 s472 ms3.9 ms
developers.line.biz/_nuxt/CLNKnlQW.js656 ms544 ms0.1 ms
www.googletagmanager.com/gtag/js?id=G-K94RFW73WS557 ms440 ms103 ms
developers.line.biz/_nuxt/CrbTXa04.js530 ms455 ms1.1 ms
developers.line.biz/_nuxt/prkPQDO6.js52 ms28 ms7.4 ms
developers.line.biz/_nuxt/entry.XU__DSq0.css51 ms0.0 ms0.0 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.

CategoryTime Spent
Script Evaluation13.0 s
Other2.5 s
Style & Layout919 ms
Garbage Collection233 ms
Rendering198 ms
Parse HTML & CSS167 ms
Script Parsing & Compilation126 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
Internal error.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 12.2 KiB
URLTransfer SizeEst Savings
fonts.googleapis.com/css2?family=LINE+Seed+JP:wght@400;700;800&display=swap89.0 KiB9.2 KiB
fonts.googleapis.com/css2?family=Noto+Sans+JP&display=swap30.2 KiB3.1 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
/__nuxt_content/docs/sql_dump.txt?v=v3.5.0--Dhx_kIlIFv5E4...2.8 MiB
developers.line.biz/_nuxt/sqlite3.DBpDb1lf.wasm838.1 KiB
/__nuxt_content/dynamic/sql_dump.txt?v=v3.5.0--NxmyunDx7H...670.5 KiB
developers.line.biz/_nuxt/prkPQDO6.js420.0 KiB
www.googletagmanager.com/gtag/js?id=G-K94RFW73WS157.1 KiB
fonts.googleapis.com/css2?family=LINE+Seed+JP:wght@400;700;800&display=swap89.0 KiB
developers.line.biz/images/top/as2.webp79.7 KiB
developers.line.biz/_nuxt/_Fv01iQh.js79.4 KiB
developers.line.biz/images/top/as1.webp77.2 KiB
developers.line.biz/_nuxt/Cxi3vQKm.js67.3 KiB

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

●Layout shift culprits
●Optimize DOM size
●Modern HTTP
●Optimize viewport for mobile
●Minify JavaScript
●User Timing marks and measures 7 user timings
●Avoid long main-thread tasks 20 long tasks found
●Avoid non-composited animations 2 animated elements found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 250 ms
●Server Backend Latencies 280 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 250 ms
●Avoid large layout shifts 15 layout shifts found
○INP breakdown
83

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flex > div.h-full > div.flex > button.custom div.flex > div.h-full > div.flex > button.custom

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > iframe body > iframe

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.flex > div.flex > div.flex > a.custom div.flex > div.flex > div.flex > a.custom

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flex > div.h-full > div.flex > button.rounded-md div.flex > div.h-full > div.flex > button.rounded-md
div.h-full > div.flex > button.rounded-md > div.vp-toggle-sidebar-button div.h-full > div.flex > button.rounded-md > div.vp-toggle-sidebar-button

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.light html.light

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
●Image elements have `[alt]` attributes
●`[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
●Background and foreground colors have a sufficient contrast ratio
●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
●No element has a `[tabindex]` value greater than 0
●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 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
○`<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.
○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

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
developers.line.biz/api/v1/session
Failed to load resource: the server responded with a status of 401 ()

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.

URL
developers.line.biz/_nuxt/sqlite3.DBpDb1lf.wasm
developers.line.biz/_nuxt/prkPQDO6.js
●Uses HTTPS
●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 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
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
75

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

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.

Canonical links suggest which URL to show in search results. Learn more about canonical links.

Why this matters

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

Source: MDN Permissions-Policy

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

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
More div.flex > div#navlinks-wrapper > div#navlinks > a.nav-link

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

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Page has successful HTTP status code
●Links have descriptive text
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○robots.txt is valid

Send Feedback