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
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@6/webfonts/fa-solid-900.woff2	604800.0 s	154.9 KiB
/npm/@fortawesome/fontawesome-free@6/webfonts/fa-brands-4...	604800.0 s	116.3 KiB
cdn.jsdelivr.net/npm/@docsearch/js@3	604800.0 s	35.9 KiB
cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@6/css/all.min.css	604800.0 s	21.8 KiB
img.shields.io/github/forks/hexojs/hexo?style=social	1800.0 s	2.3 KiB
img.shields.io/github/stars/hexojs/hexo?style=social	1800.0 s	2.2 KiB
img.shields.io/npm/dm/hexo?logo=npm&style=social	7200.0 s	1.7 KiB
img.shields.io/twitter/follow/hexojs?style=social	86400.0 s	1.7 KiB
cdn.jsdelivr.net/docsearch.js/1/docsearch.min.css	604800.0 s	4.4 KiB
cdn.jsdelivr.net/npm/@docsearch/css@3	604800.0 s	3.4 KiB
cdn.jsdelivr.net/npm/js-cookie@2/src/js.cookie.min.js	604800.0 s	1.3 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

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.

URL	Transfer Size	Duration
cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@6/css/all.min.css	21.8 KiB	150 ms
cdn.jsdelivr.net/docsearch.js/1/docsearch.min.css	4.4 KiB
cdn.jsdelivr.net/npm/@docsearch/css@3	3.4 KiB	150 ms
cdn.jsdelivr.net/npm/typeface-lato@0.0.75/index.min.css	1013 B	753 ms
hexo.io/css/navy.css	5.2 KiB

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.

URL	Est Savings
cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@6/webfonts/fa-solid-900.woff2	15 ms
/npm/@fortawesome/fontawesome-free@6/webfonts/fa-brands-4...	15 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
div.inner > div.theme-thumbnail > div.theme-thumbnail-container > img `div.inner > div.theme-thumbnail > div.theme-thumbnail-container > img`	hexo.io/themes/screenshots/landscape.png	302.1 KiB	278.2 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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: 150 ms 21.4 KiB

URL	Transfer Size	Est Savings
cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@6/css/all.min.css	21.7 KiB	21.4 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: 150 ms 93.0 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-8VWFR61YDH&cx=c&_slc=1	147.0 KiB	63.4 KiB
cdn.jsdelivr.net/npm/@docsearch/js@3	35.5 KiB	29.6 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
div.inner > div.theme-thumbnail > div.theme-thumbnail-container > img `div.inner > div.theme-thumbnail > div.theme-thumbnail-container > img`	hexo.io/themes/screenshots/landscape.png
div.inner > div#footer-links > a.footer-link > img `div.inner > div#footer-links > a.footer-link > img`	www.netlify.com/img/global/badges/netlify-dark.svg

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 902 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.9 s

●Avoid long main-thread tasks 3 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 190 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 40 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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
Get started `div.wrapper > div.inner > div#intro-get-started-wrap > a#intro-get-started-link`

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.inner > div.theme-thumbnail > div.theme-thumbnail-container > img `div.inner > div.theme-thumbnail > div.theme-thumbnail-container > img`
div.inner > div#footer-links > a.footer-link > img `div.inner > div#footer-links > a.footer-link > img`

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English 正體中文简体中文 Русский 한국어 Português (Brasil) ภาษาไทย 日本語 Español `body > nav#mobile-nav > div#mobile-lang-select-wrap > select#mobile-lang-select`

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
header#banner > div.inner > div#banner-start > a#banner-start-link `header#banner > div.inner > div#banner-start > a#banner-start-link`
footer#footer > div.inner > div#footer-links > a.footer-link `footer#footer > div.inner > div#footer-links > a.footer-link`
footer#footer > div.inner > div#footer-links > a.footer-link `footer#footer > div.inner > div#footer-links > a.footer-link`
footer#footer > div.inner > div#footer-links > a.footer-link `footer#footer > div.inner > div#footer-links > a.footer-link`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Docs API News Plugins Themes About GitHub `body > nav#mobile-nav > div#mobile-nav-inner > ul#mobile-nav-list`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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-hidden="true"]` is not present on the document `<body>`

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

100

Best Practices

●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 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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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.inner > div.theme-thumbnail > div.theme-thumbnail-container > img `div.inner > div.theme-thumbnail > div.theme-thumbnail-container > img`
div.inner > div#footer-links > a.footer-link > img `div.inner > div#footer-links > a.footer-link > img`

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`