Skip to content
https://speakerdeck.com

Lighthouse Desktop

· 0 checks — Desktop 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.

93

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
cdn4.buysellads.net/pub/speakerdeck.js?17768070000003600.0 s163.0 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
c.amazon-adsystem.com/aax2/apstag.js3600.0 s91.0 KiB
/signals/config/2893765844191276?v=2.9.303&r=stable&domai...1200.0 s44.5 KiB
btloader.com/tag?o=5102648370397184&upapi=true300.0 s34.8 KiB
/k4snpx1b3nz0b7sn8en6bld3fw9g?response-content-dispositio...0.0 ms16.5 KiB
speakerdeck.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?14400.0 s12.6 KiB
secure.gravatar.com/avatar/e4f5d494ebdc9e7cce1aecf3ce3e8bc1?s=24300.0 s1.8 KiB
secure.gravatar.com/avatar/6b43aae026afebf1bb1b19fb1d5cfca7?s=24300.0 s1.6 KiB
secure.gravatar.com/avatar/4888c8378accd22acc2998ddf1414e7f?s=24300.0 s1.5 KiB
secure.gravatar.com/avatar/433acaea1012b25d97ae66da9b998dad?s=24300.0 s1.5 KiB
secure.gravatar.com/avatar/5f2da528927a2ec9ba4fec2069cbc958?s=24300.0 s1.4 KiB
secure.gravatar.com/avatar/2bf27e1a5632db8aba77510c78aaa9a2?s=24300.0 s1.4 KiB
secure.gravatar.com/avatar/245cee81a9c424266e5e401d844ea881?s=24300.0 s1.4 KiB
secure.gravatar.com/avatar/3ab1249be442027903e1180025340b3f?s=24300.0 s1.3 KiB
/tr/?id=2893765844191276&ev=PageView&dl=https%3A%2F%2Fspe...0.0 ms16 B

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
fonts.googleapis.com/css?family=Lato:400,700|Roboto+Slab:700&display=swap1.2 KiB273 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.

URLResource SizeEst Savings
Avatar for Kris div.col-lg-6 > div.hero-slide > div.d-flex > img.avatar
/k4snpx1b3nz0b7sn8en6bld3fw9g?response-content-dispositio...15.9 KiB15.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/c711731dd997437c90294769eafc273f/preview_s...49.4 KiB11.9 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/1bdfc578481d4d3fb7001ddd92a8906a/preview_s...42.7 KiB5.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

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: 40 ms 37.6 KiB
URLTransfer SizeEst Savings
/assets/application-0853bc215819f43b15391734b5a07d7d5da07...41.6 KiB37.6 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: 290 ms 689.1 KiB
URLTransfer SizeEst Savings
d1eu30co0ohy4w.cloudfront.net/assets/js/application-d48f03e9e9f1d7e7ef13.js213.8 KiB186.1 KiB
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...187.4 KiB140.9 KiB
cdn4.buysellads.net/pub/speakerdeck.js?1776807000000162.8 KiB108.6 KiB
c.amazon-adsystem.com/aax2/apstag.js90.6 KiB89.0 KiB
www.googletagmanager.com/gtag/js?id=G-8WD0LC0MP9&cx=c&gtm=4e64h1153.0 KiB65.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-TSP938CX123.7 KiB64.8 KiB
connect.facebook.net/en_US/fbevents.js96.5 KiB34.5 KiB

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

●Max Potential First Input Delay 80 ms
●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,674 KiB
●User Timing marks and measures 5 user timings
●JavaScript execution time 0.5 s
●Minimizes main-thread work 1.0 s
●Avoid long main-thread tasks 3 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 190 ms
●Server Backend Latencies 140 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 440 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
89

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
Kris Priemer · 42 slides · 3.2k views div.row > div.col-lg-6 > div.hero-slide > div.d-flex

These are opportunities to improve the legibility of your content.

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
malarkey div.card > div.deck-preview-meta > div.text-truncate > a
michielstock div.card > div.deck-preview-meta > div.text-truncate > a
szymonslowik div.card > div.deck-preview-meta > div.text-truncate > a
reverentgeek div.card > div.deck-preview-meta > div.text-truncate > a
ryanjones div.card > div.deck-preview-meta > div.text-truncate > a
lara div.card > div.deck-preview-meta > div.text-truncate > a
shpigford div.card > div.deck-preview-meta > div.text-truncate > a
kneath 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
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●`[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
●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
●Image elements do not have `[alt]` attributes that are redundant text.
○`[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
○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
○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 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
○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.
77

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

SourceDescription
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`

Send Feedback