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

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
fonts.googleapis.com/css?family=Lato:400,700\|Roboto+Slab:700&display=swap	1.2 KiB	814 ms

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
cdn4.buysellads.net/pub/speakerdeck.js?1776807000000	3600.0 s	163.0 KiB
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
c.amazon-adsystem.com/aax2/apstag.js	3600.0 s	91.0 KiB
/signals/config/2893765844191276?v=2.9.303&r=stable&domai...	1200.0 s	44.5 KiB
btloader.com/tag?o=5102648370397184&upapi=true	300.0 s	34.8 KiB
/k4snpx1b3nz0b7sn8en6bld3fw9g?response-content-dispositio...	0.0 ms	16.5 KiB
speakerdeck.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?	14400.0 s	13.1 KiB
/tr/?id=2893765844191276&ev=PageView&dl=https%3A%2F%2Fspe...	0.0 ms	16 B

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.card > a.deck-preview-link > div.deck-preview-image > div.deck-preview-background `div.card > a.deck-preview-link > div.deck-preview-image > div.deck-preview-background`	/presentations/cceb0dea99d74814a892a151f9ed9df0/preview_s...	55.3 KiB	17.8 KiB
div.card > a.deck-preview-link > div.deck-preview-image > div.deck-preview-background `div.card > a.deck-preview-link > div.deck-preview-image > div.deck-preview-background`	/presentations/ac0c8af05fc10130a2f822000a1c835e/preview_s...	59.8 KiB	9.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

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 38.0 KiB

URL	Transfer Size	Est Savings
/assets/application-0853bc215819f43b15391734b5a07d7d5da07...	41.6 KiB	38.0 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: 1.2 s 690.5 KiB

URL	Transfer Size	Est Savings
d1eu30co0ohy4w.cloudfront.net/assets/js/application-d48f03e9e9f1d7e7ef13.js	213.8 KiB	186.1 KiB
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB	142.6 KiB
cdn4.buysellads.net/pub/speakerdeck.js?1776807000000	162.8 KiB	108.6 KiB
c.amazon-adsystem.com/aax2/apstag.js	90.6 KiB	89.0 KiB
www.googletagmanager.com/gtag/js?id=G-8WD0LC0MP9&cx=c&gtm=4e64h1	153.0 KiB	65.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-TSP938CX	123.7 KiB	64.8 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	34.1 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
speakerdeck.com/	1.1 s	188 ms	4.8 ms
Unattributable	550 ms	65 ms	0.0 ms
speakerdeck.com/cdn-cgi/challenge-platform/scripts/jsd/main.js	336 ms	325 ms	3.8 ms
cdn4.buysellads.net/pub/speakerdeck.js?1776807000000	312 ms	220 ms	84 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	300 ms	218 ms	79 ms
www.googletagmanager.com/gtag/js?id=G-8WD0LC0MP9&cx=c&gtm=4e64h1	295 ms	233 ms	58 ms
d1eu30co0ohy4w.cloudfront.net/assets/js/application-d48f03e9e9f1d7e7ef13.js	212 ms	102 ms	97 ms
btloader.com/tag?o=5102648370397184&upapi=true	186 ms	162 ms	16 ms
www.googletagmanager.com/gtm.js?id=GTM-TSP938CX	181 ms	133 ms	46 ms
/signals/config/2893765844191276?v=2.9.303&r=stable&domai...	175 ms	145 ms	29 ms
connect.facebook.net/en_US/fbevents.js	171 ms	121 ms	47 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	112 ms	98 ms	14 ms
c.amazon-adsystem.com/aax2/apstag.js	74 ms	3.2 ms	71 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	2.0 s
Other	802 ms
Script Parsing & Compilation	550 ms
Style & Layout	462 ms
Rendering	145 ms
Parse HTML & CSS	53 ms
Garbage Collection	18 ms

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

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 15 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 120 ms

●Server Backend Latencies 150 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 400 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.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.d-flex > div.form-check > input#billingToggle `div.container > div.d-flex > div.form-check > input#billingToggle`

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

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
keithpitt `div.card > div.deck-preview-meta > div.text-truncate > a`
tonyrice `div.card > div.deck-preview-meta > div.text-truncate > a`
helenjbeal `div.card > div.deck-preview-meta > div.text-truncate > a`
eileencodes `div.card > div.deck-preview-meta > div.text-truncate > a`

○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

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

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

●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

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

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●ARIA IDs are unique

○`[accesskey]` values are unique

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

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

○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

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

○Identical links have the same purpose.

○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

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	speakerdeck.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	speakerdeck.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	speakerdeck.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
AttributionReporting	connect.facebook.net/en_US/fbevents.js line 279, col 769

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.

Source	Description
c.amazon-adsystem.com/aax2/apstag.js line 1, col 6076	`Uncaught Error: Unauthorized`

●Uses HTTPS

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

100

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.

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`