Skip to content
https://grist.org

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.

94

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 forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:75.525 source:map[type:text value:[unattributed]]]]

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
A group of sheep stand in a field in front of an array of solar panels. div.tease__art > a.tease-art > figure.tease-art__figure > img.tease-art__art
/wp-content/uploads/2026/04/Select-1JB04614_XMIT.jpg?resi...96.1 KiB85.6 KiB
A computer generated rendering of a planned export terminal for liquid natural … article.small-tease > a.tease-art > figure.tease-art__figure > img.tease-art__art
/wp-content/uploads/2026/04/Louisiana-LNG-computer-genera...86.8 KiB79.3 KiB
The skylines of the future will be made of wood article.small-tease > a.tease-art > figure.tease-art__figure > img.tease-art__art
/wp-content/uploads/2026/04/1-Credit-Michael-Elkan-Photog...83.6 KiB76.4 KiB
Photo of someone holding a grocery receipt over a cart full of food article.small-tease > a.tease-art > figure.tease-art__figure > img.tease-art__art
/wp-content/uploads/2026/04/grocery-cart-reciept.jpg?resi...40.6 KiB39.2 KiB
div.tease__art > a.tease-art > figure.tease-art__figure > img.tease-art__art div.tease__art > a.tease-art > figure.tease-art__figure > img.tease-art__art
/wp-content/uploads/2026/04/GettyImages-453802918.jpeg?re...43.6 KiB38.8 KiB
At the UN, Indigenous leaders tackle how to enforce global climate court rulings article.small-tease > a.tease-art > figure.tease-art__figure > img.tease-art__art
/wp-content/uploads/2026/04/250423_UNPFII81.jpg?resize=12...40.1 KiB38.8 KiB
An illustration of an Earth surrounded by symbols like a wind turbine, a stetho… article.small-tease > a.tease-art > figure.tease-art__figure > img.tease-art__art
/wp-content/uploads/2026/04/grist-50-earth-month.jpg?resi...39.2 KiB37.9 KiB
Leia Larsen div.hp-cover-story__art > a.tease-art > figure.tease-art__figure > img.tease-art__art
/wp-content/uploads/2026/04/260320_BALCONYSOLAR.03XX26_10...53.1 KiB32.6 KiB
The Afsluitdijk, a causeway between Friesland and North Holland, is seen in an … div.tease__art > a.tease-art > figure.tease-art__figure > img.tease-art__art
/wp-content/uploads/2026/04/Afsluitdijk-climate-change-re...23.9 KiB21.3 KiB
Collage of graduate wearing red cap and gown, looking out toward hurricane imag… div.tease__art > a.tease-art > figure.tease-art__figure > img.tease-art__art
/wp-content/uploads/2026/04/climate-future-advice.jpg?res...21.5 KiB19.2 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
value: No additional origins are good candidates for preconnecting

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 44.9 KiB
URLTransfer SizeEst Savings
grist.org/wp-content/themes/grist/dist/homePage.css?ver=0.16.2839.5 KiB34.7 KiB
13.5 KiB10.2 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.

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.

CategoryTime Spent
Script Evaluation1.9 s
Other1.1 s
Style & Layout406 ms
Rendering375 ms
Script Parsing & Compilation112 ms
Parse HTML & CSS106 ms
Garbage Collection79 ms

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.

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.

div.fix__featured > a.fix__featured-link > figure > img.fix__featured-headshot div.fix__featured > a.fix__featured-link > figure > img.fix__featured-headshot

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

Max Potential First Input Delay 130 ms
Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 9 user timings
Avoid long main-thread tasks 4 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 180 ms
Server Backend Latencies 160 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 0 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
Avoid non-composited animations
93

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Play video div.large-tease__art-wrapper > div.tease-art > figure.tease-art__figure > a.play-button
Play video article.small-tease > div.tease-art > figure.tease-art__figure > a.play-button
Play video article.small-tease > div.tease-art > figure.tease-art__figure > a.play-button
Play video article.small-tease > div.tease-art > figure.tease-art__figure > a.play-button
Play video article.small-tease > div.tease-art > figure.tease-art__figure > a.play-button

These are opportunities to improve the usage of ARIA in your application which 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
Privacy Policy div#CybotCookiebotDialogBodyContentText > p > a > span
Show details div#CybotCookiebotDialogBody > div.CybotCookiebotDialogBodyBottomWrapper > div#CybotCookiebotDialogBodyEdgeMoreDetails > a#CybotCookiebotDialogBodyEdgeMoreDetailsLink
Donate ul.nav__items > li.nav__item > a.button > span
Get Grist's Free Weekly Newsletter div.hp-topper__subscription > div.hp-topper-newsletter > h2.subsection-header > span
Support Grist div.footer__cta-wrapper > div.footer__cta > a.button > span

These are opportunities to improve the legibility of your content.

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 with `role="dialog"` or `role="alertdialog"` have accessible names.
`[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.
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
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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
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
Select elements have associated label elements.
Skip links are focusable.
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.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Image elements do not have `[alt]` attributes that are redundant text.
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.
81

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
AttributionReporting
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 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 clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
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.

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
Play video div.large-tease__art-wrapper > div.tease-art > figure.tease-art__figure > a.play-button
Play video article.small-tease > div.tease-art > figure.tease-art__figure > a.play-button
Play video article.small-tease > div.tease-art > figure.tease-art__figure > a.play-button
Play video article.small-tease > div.tease-art > figure.tease-art__figure > a.play-button
Play video article.small-tease > div.tease-art > figure.tease-art__figure > a.play-button

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

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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback