Skip to content
https://getpocket.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.

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.142452] map[node:map[boundingRect:map[bottom:1181 height:654 left:71 right:1279 top:527 width:1208] lhId:page-4-SECTION nodeLabel:Why has Pocket shut down? Pocket has helped millions save articles and discove… path:1,HTML,1,BODY,5,DIV,1,DIV,0,MAIN,1,SECTION selector:div#__next > div.css-ov321h > main.style-module__oJvAWa__base > section.page-container snippet:<section class="page-container"> type:node] score:0.071341] map[node:map[boundingRect:map[bottom:3122 height:3122 left:0 right:1350 top:0 width:1350] lhId:page-7-DIV nodeLabel:So long, farewell, Auf Wiedersehen... After careful consideration, we’ve made … path:1,HTML,1,BODY,5,DIV,1,DIV selector:body > div#__next > div.css-ov321h snippet:<div class="css-ov321h withBanner"> type:node] score:0.071111 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:478 height:310 left:715 right:1239 top:168 width:524] lhId:page-0-IMG nodeLabel:header > div.style-module__oJvAWa__headerContent > div.style-module__oJvAWa__media > img path:1,HTML,1,BODY,5,DIV,1,DIV,0,MAIN,0,HEADER,0,DIV,1,DIV,0,IMG selector:header > div.style-module__oJvAWa__headerContent > div.style-module__oJvAWa__media > img snippet:<img src="https://assets.getpocket.com/web-client/_next/static/media/pocket-list.48a…" alt=""> type:node]]] type:subitems]]]

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

URLEst Savings
/web-ui/assets/Doyle-Medium.eb6ee0eb205e8467cb3b0e6119121...40 ms
/web-ui/assets/Graphik-Regular-Web.e05a3b2ff4a3813954bcf8...25 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
header > div.style-module__oJvAWa__headerContent > div.style-module__oJvAWa__media > img header > div.style-module__oJvAWa__headerContent > div.style-module__oJvAWa__media > img
assets.getpocket.com/web-client/_next/static/media/pocket-list.48a5f724.png284.8 KiB258.4 KiB
main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img
assets.getpocket.com/web-client/_next/static/media/pocket-your-way.72256db6.png298.6 KiB252.4 KiB
main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img
assets.getpocket.com/web-client/_next/static/media/article-carousel.b0e94742.png246.3 KiB210.4 KiB
main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img
assets.getpocket.com/web-client/_next/static/media/reading-nook.95c44724.png31.8 KiB21.6 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-1-IMG
nodeLabel: main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img
path: 1,HTML,1,BODY,5,DIV,1,DIV,0,MAIN,1,SECTION,0,DIV,0,IMG
selector: main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img
snippet: <img src="https://assets.getpocket.com/web-client/_next/static/media/pocket-your-way…" alt="">

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

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
assets.getpocket.com/web-client/_next/static/chunks/f421bff56e9ba7e2.csshttp/1.1
assets.getpocket.com/web-client/_next/static/chunks/85b2c0276c955df5.csshttp/1.1
assets.getpocket.com/web-client/_next/static/chunks/dfec6f6a0df61587.jshttp/1.1
assets.getpocket.com/web-client/_next/static/chunks/c7f7bf439df278d3.jshttp/1.1
assets.getpocket.com/web-client/_next/static/chunks/77ad7628c1b6eb7e.jshttp/1.1
assets.getpocket.com/web-client/_next/static/chunks/6f8cb0c8d2ade47c.jshttp/1.1
assets.getpocket.com/web-client/_next/static/chunks/e088e458ab4f0efd.jshttp/1.1
/web-client/_next/static/chunks/turbopack-4d5a40aa852ef05...http/1.1
assets.getpocket.com/web-client/_next/static/chunks/a925f3dc4c63b2fa.jshttp/1.1
assets.getpocket.com/web-client/_next/static/chunks/ff79cce69b3b9117.jshttp/1.1
assets.getpocket.com/web-client/_next/static/chunks/76c9ff9f8653b887.jshttp/1.1
/web-client/_next/static/chunks/turbopack-22f9b95002bfc33...http/1.1
/web-client/_next/static/8k4-4Xw-VZLy-lEPIrEZw/_ssgManife...http/1.1
/web-client/_next/static/8k4-4Xw-VZLy-lEPIrEZw/_buildMani...http/1.1
assets.getpocket.com/web-client/_next/static/media/pocket-list.48a5f724.pnghttp/1.1
assets.getpocket.com/web-client/_next/static/media/pocket-your-way.72256db6.pnghttp/1.1
assets.getpocket.com/web-client/_next/static/media/reading-nook.95c44724.pnghttp/1.1
/web-client/_next/static/media/save-button-doodle.c7f4139...http/1.1
assets.getpocket.com/web-client/_next/static/media/article-carousel.b0e94742.pnghttp/1.1
/web-ui/assets/Graphik-Regular-Web.e05a3b2ff4a3813954bcf8...http/1.1
/web-ui/assets/Doyle-Medium.eb6ee0eb205e8467cb3b0e6119121...http/1.1
/web-client/_next/static/8k4-4Xw-VZLy-lEPIrEZw/_clientMid...http/1.1
/web-ui/assets/pocket-logo-light-mode.9a20614bbcbaf69b221...http/1.1

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

Diagnostics

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: 40 ms 146.0 KiB
URLTransfer SizeEst Savings
assets.getpocket.com/web-client/_next/static/chunks/ff79cce69b3b9117.js70.7 KiB70.5 KiB
assets.getpocket.com/web-client/_next/static/chunks/77ad7628c1b6eb7e.js65.1 KiB26.5 KiB
assets.getpocket.com/web-client/_next/static/chunks/6f8cb0c8d2ade47c.js70.4 KiB25.9 KiB
assets.getpocket.com/web-client/_next/static/chunks/76c9ff9f8653b887.js38.7 KiB23.0 KiB

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: 0.0 ms 10.0 KiB
URLTransfer SizeEst Savings
.css-1ia2h6h { box-sizing: content-box; margin: 0px auto; max-width: 1128px; … } …10.4 KiB10.0 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
main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img
assets.getpocket.com/web-client/_next/static/media/reading-nook.95c44724.png
main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img
assets.getpocket.com/web-client/_next/static/media/pocket-your-way.72256db6.png
main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img
assets.getpocket.com/web-client/_next/static/media/article-carousel.b0e94742.png
header > div.style-module__oJvAWa__headerContent > div.style-module__oJvAWa__media > img header > div.style-module__oJvAWa__headerContent > div.style-module__oJvAWa__media > img
assets.getpocket.com/web-client/_next/static/media/pocket-list.48a5f724.png
main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img main.style-module__oJvAWa__base > section.page-container > div.style-module__oJvAWa__media > img
/web-client/_next/static/media/save-button-doodle.c7f4139...

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 315 ms
URLTime Spent
getpocket.com/315 ms
getpocket.com/en/0.0 ms
getpocket.com/waypoint0.0 ms
getpocket.com/home0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Why has Pocket shut down? Pocket has helped millions save articles and discove… div#__next > div.css-ov321h > main.style-module__oJvAWa__base > section.page-container
0.071
So long, farewell, Auf Wiedersehen... After careful consideration, we’ve made … body > div#__next > div.css-ov321h
0.071
●Time to Interactive 1.4 s
●Use efficient cache lifetimes
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Render blocking requests
●Optimize viewport for mobile
●Max Potential First Input Delay 50 ms
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,360 KiB
●User Timing marks and measures 7 user timings
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.3 s
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 40 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 50 ms
○INP breakdown
○Avoid long main-thread tasks
○Avoid non-composited animations
86

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Why has Pocket shut down? main.style-module__oJvAWa__base > section.page-container > div > h3

These are opportunities to improve keyboard navigation in your application.

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

These items highlight common accessibility best practices.

Names and labels

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
Chinese (Taiwan) Chinese Dutch English French French (Canada) German Italian Ja… div.css-f221da > div.languages-wrapper > div.languages > select

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.

○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
●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 are distinguishable without relying on color.
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○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
○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
○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.
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
92

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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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