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.

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.

URL	Transfer Size	Duration
lichess1.org/assets/css/lobby.ad862683.css	7.2 KiB	805 ms
lichess1.org/assets/css/site.5a923922.css	10.5 KiB	964 ms
lichess1.org/assets/css/lib.theme.all.1689358c.css	5.8 KiB	805 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
Woman looking through magnifying glass `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`	/display?fmt=webp&h=250&op=thumbnail&path=LaMJfBLx3j96.we...	12.3 KiB	9.2 KiB
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`	/display?fmt=webp&h=250&op=thumbnail&path=ZODj-wMq0_B8.we...	9.0 KiB	6.8 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

Diagnostics

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 WebSocket cannot enter back/forward cache.	Pending browser support
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because WebSocket has been used.	Not actionable

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

●Use efficient cache lifetimes

●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 30 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 571 KiB

●JavaScript execution time 0.2 s

●Minimizes main-thread work 1.3 s

●Avoid long main-thread tasks 5 long tasks found

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

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 50 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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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
main.lobby > div.lobby__blog > div.carousel__controls > button.carousel__prev `main.lobby > div.lobby__blog > div.carousel__controls > button.carousel__prev`
main.lobby > div.lobby__blog > div.carousel__controls > button.carousel__next `main.lobby > div.lobby__blog > div.carousel__controls > button.carousel__next`

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.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`

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.

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
REGISTER `header#top > div.site-buttons > div.signin-or-signup > a.button`
31 hours ago `div.daily-feed__update > div > a.daily-feed__update__day > time.set`
45 hours ago `div.daily-feed__update > div > a.daily-feed__update__day > time.set`
2 days ago `div.daily-feed__update > div > a.daily-feed__update__day > time.set`
2 days ago `div.daily-feed__update > div > a.daily-feed__update__day > time.set`
3 days ago `div.daily-feed__update > div > a.daily-feed__update__day > time.set`
3 days ago `div.daily-feed__update > div > a.daily-feed__update__day > time.set`
4 days ago `div.daily-feed__update > div > a.daily-feed__update__day > time.set`
All updates » `div.daily-feed__updates > div.daily-feed__update > div > a.daily-feed__update__day`
≤2000 Bullet `tbody > tr > td > a.text`
Hourly SuperBlitz `tbody > tr > td > a.text`
Hourly HyperBullet `tbody > tr > td > a.text`
Hourly Blitz `tbody > tr > td > a.text`
≤1500 Blitz `tbody > tr > td > a.text`

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
Chess Digital League Final `div.daily-feed__update > div > p > a`
UAE Chess Federation `div.daily-feed__update > div > p > a`
Watch the interview on YouTube `div.daily-feed__update > div > p > a`
Roman Dehtiarov `div.daily-feed__update > div > p > a`
European Individual Chess Championship 2026 `div.daily-feed__update > div > p > a`
@GlasnostPerestroika `div.daily-feed__update > div > p > a`
2026 Spring Marathon `div.daily-feed__update > div > p > a`
Dimitrios Makridis `div.daily-feed__update > div > p > a`
next Marathon `div.daily-feed__update > div > p > a`
Watch the interview on YouTube `div.daily-feed__update > div > p > a`
YouTube `div.daily-feed__update > div > p > a`
Twitch `div.daily-feed__update > div > p > a`

These are opportunities to improve the legibility of your content.

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
Streamers » `main.lobby > div.lobby__side > section.lobby__streams > a.more`

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Philidor Defense Rapid 1h 57m 165 ≤2000 Bullet 27m 130 Hourly Atomic 27m … `div.lobby__tournaments-simuls > div.lobby__tournaments > div.lobby__box__content > table.tournaments`

○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

●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

●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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`[accesskey]` values are unique

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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 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
header#top > div.site-buttons > div#clinput > a.link `header#top > div.site-buttons > div#clinput > a.link`

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

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.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image `div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image`

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

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`