Skip to content
https://blog.jp

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.

90

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
pdn.adingo.jp/p.js600.0 s20.7 KiB
parts.blog.livedoor.jp/blog_portal/lite/img/v3/guide/ldapp.png604800.0 s77.7 KiB
parts.blog.livedoor.jp/blog_portal/lite/css/v3/main.css?v=20240325604800.0 s45.5 KiB
parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/iphone_02.png604800.0 s43.6 KiB
parts.blog.livedoor.jp/blog_portal/lite/img/v3/guide/ldapp_android.png604800.0 s11.4 KiB
parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/download_android.png604800.0 s5.5 KiB
parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/h2_bg.svg604800.0 s5.3 KiB
parts.blog.livedoor.jp/blog_portal/lite/img/v3/guide/ldapp_ios.png604800.0 s5.1 KiB
parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/download_ios.png604800.0 s4.2 KiB
parts.blog.livedoor.jp/img/common/logo_w.svg604800.0 s3.8 KiB
parts.blog.livedoor.jp/img/common/logo.svg604800.0 s3.6 KiB
parts.blog.livedoor.jp/img/common/logo_posted_app.png604800.0 s3.4 KiB
parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_07.svg604800.0 s3.2 KiB
parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_01.svg604800.0 s2.9 KiB
parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_04.svg604800.0 s2.5 KiB
parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_03.svg604800.0 s2.4 KiB
parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_02.svg604800.0 s1.8 KiB
parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_06.svg604800.0 s1.5 KiB
parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/parts_01.svg604800.0 s1.5 KiB
parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/icon_05.svg604800.0 s1.5 KiB
parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/parts_02.svg604800.0 s1.4 KiB

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.left > div.img_3 > span > img div.left > div.img_3 > span > img
parts.blog.livedoor.jp/blog_portal/lite/img/v3/guide/ldapp.png77.3 KiB59.8 KiB
div.right > div.download > span.img_6 > img div.right > div.download > span.img_6 > img
parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/iphone_02.png43.2 KiB33.2 KiB
div.ldapp > a > span.img > img div.ldapp > a > span.img > img
parts.blog.livedoor.jp/blog_portal/lite/img/v3/guide/ldapp_android.png11.1 KiB8.6 KiB
Google Playで手に入れよう div.download-inner > span > a > img
parts.blog.livedoor.jp/blog_portal/pc/img/v3/guide/download_android.png5.2 KiB4.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
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
parts.blog.livedoor.jp/blog_portal/lite/css/v3/main.css?v=2024032545.5 KiB1.1 s

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

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: 150 ms 44.0 KiB
URLTransfer SizeEst Savings
parts.blog.livedoor.jp/blog_portal/lite/css/v3/main.css?v=2024032545.2 KiB44.0 KiB

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

●Time to Interactive 3.2 s
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 271 KiB
●JavaScript execution time 0.1 s
●Minimizes main-thread work 0.5 s
●Avoid long main-thread tasks 1 long task found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 260 ms
●Server Backend Latencies 20 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 260 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
○Avoid large layout shifts
57

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
TOP div.guide-title > div.pan > span > a
blog.jp div.box > div.right > ul.list_1 > li
diary.to div.box > div.right > ul.list_1 > li
officialblog.jp div.box > div.right > ul.list_1 > li
livedoor div.sitemap > ul > li > a
© livedoor div.footer-inner > div.box > p.copy > small

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
TOP div.guide-title > div.pan > span > a

These are opportunities to improve the legibility of your content.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.ldapp > a > span.img > img div.ldapp > a > span.img > img

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.box > div.right > div.ldapp > a div.box > div.right > div.ldapp > a
div.box > div.right > div.ldapp > a div.box > div.right > div.ldapp > a

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

Best practices

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

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
livedoor div.sitemap > ul > li > a
利用規約 div.sitemap > ul > li > a
ガイドライン div.sitemap > ul > li > a
サイトマップ div.sitemap > ul > li > a
プライバシー div.sitemap > ul > li > a
ヘルプ div.sitemap > ul > li > a

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●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
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
div.ldapp > a > span.img > img div.ldapp > a > span.img > img
parts.blog.livedoor.jp/blog_portal/lite/img/v3/guide/ldapp_ios.png175 x 56 (3.13)524 x 193 (2.72)
●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
●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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
91

SEO

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.ldapp > a > span.img > img div.ldapp > a > span.img > img

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

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

Send Feedback