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.

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
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
/signals/config/542017519474115?v=2.9.303&r=stable&domain...	1200.0 s	44.8 KiB
consent.cookiebot.com/uc.js	631.0 s	35.7 KiB
wisepops.net/loader.js?v=1&site=UkdKwSrMxb	1800.0 s	24.0 KiB
a.quora.com/qevents.js	14400.0 s	14.7 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.7 KiB
static.chartbeat.com/js/chartbeat.js	86400.0 s	15.9 KiB
static.chartbeat.com/js/subscriptions.js	86400.0 s	10.8 KiB
static.chartbeat.com/js/chartbeat_mab.js	86400.0 s	10.1 KiB
/consentconfig/3f5c049a-7407-416b-bc5a-861f63f9ab95/grist...	17915.0 s	2.3 KiB
cdn.userway.org/widget.js	3600.0 s	1.6 KiB
/collect?v=2&fmt=js&pid=4682305&time=1776819826196&url=ht...	0.0 ms	692 B
cdn.userway.org/styles/2026-04-14-10-40-20/widget_base.css?v=1776163220800	864000.0 s	5.4 KiB
/_/ad/10c4ac8cbc574efaa3c172168a566396/pixel?tag=ViewCont...	0.0 ms	346 B
/tr/?id=542017519474115&ev=PageView&dl=https%3A%2F%2Fgris...	0.0 ms	19 B

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.

URL	Est Savings
grist.org/wp-content/themes/grist/dist/fonts/GT-Super-Display-Bold.woff2	280 ms
fonts.gstatic.com/s/roboto/v51/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	75 ms
fonts.gstatic.com/s/roboto/v51/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	75 ms
grist.org/wp-content/themes/grist/dist/fonts/PolySansUS-Median.woff2	35 ms
fonts.gstatic.com/s/roboto/v51/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	35 ms
grist.org/wp-content/themes/grist/dist/fonts/GT-Super-Text-Book.woff2	30 ms
grist.org/wp-content/themes/grist/dist/fonts/basis-grotesque-regular-pro.woff2	25 ms
grist.org/wp-content/themes/grist/dist/fonts/basis-grotesque-bold-pro.woff2	20 ms
grist.org/wp-content/themes/grist/dist/fonts/GT-Super-Text-Bold.woff2	5.0 ms

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:80.245 source:map[type:text value:[unattributed]]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:3576.404 label:Time to first byte subpart:timeToFirstByte] map[duration:14.877 label:Resource load delay subpart:resourceLoadDelay] map[duration:374.378 label:Resource load duration subpart:resourceLoadDuration] map[duration:53.641 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: Leia Larsen

path: 1,HTML,1,BODY,13,DIV,1,DIV,0,MAIN,0,DIV,0,SECTION,0,DIV,0,DIV,0,ARTICLE,0,DIV,3,DIV,0,A,0,FIGURE,0,IMG

selector: div.hp-cover-story__art > a.tease-art > figure.tease-art__figure > img.tease-art__art

snippet: <img src="https://grist.org/wp-content/uploads/2026/04/260320_BALCONYSOLAR.03XX26_10…" alt="Leia Larsen" height="2333" width="3500" srcset="https://grist.org/wp-content/uploads/2026/04/260320_BALCONYSOLAR.03XX26_10…" sizes="(max-width: 1024px) 100vw, 1024px" class="tease-art__art js-modal-gallery__hidden" loading="eager" fetchpriority="high" decoding="async" pinger-seen="true" data-uw-rm-alt-original="" data-uw-rm-alt="CT">

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

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
/wp-content/plugins/wordpress-tooltips/js/qtip2/jquery.qt...	16.6 KiB	150 ms
grist.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	31.0 KiB	150 ms
grist.org/wp-content/themes/grist/dist/homePage.css?ver=0.16.28	39.7 KiB	301 ms
/wp-content/plugins/wordpress-tooltips/js/jdirectory/jque...	1.7 KiB
grist.org/wp-content/themes/grist/dist/userwayInit.js	598 B
grist.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.2 KiB
grist.org/wp-content/themes/grist/dist/abTestingFooterDonation.js?ver=0.16.28	1.3 KiB
grist.org/wp-content/themes/grist/dist/abTesting.js?ver=0.16.28	1.4 KiB
grist.org/wp-content/themes/grist/dist/cookieManager.js?ver=0.16.28	281 B
/wp-content/plugins/wordpress-tooltips/js/jdirectory/dire...	720 B
/wp-content/plugins/wordpress-tooltips/js/qtip2/jquery.qt...	2.4 KiB
/wp-content/plugins/grist-reveal-card/dist/grist-reveal-c...	1.3 KiB

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
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...	43.9 KiB	41.9 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...	24.8 KiB	23.7 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...	46.2 KiB	13.2 KiB

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 3.5 s

URL	Time Spent
grist.org/	3.6 s

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: 300 ms 46.6 KiB

URL	Transfer Size	Est Savings
grist.org/wp-content/themes/grist/dist/homePage.css?ver=0.16.28	39.5 KiB	35.0 KiB
	13.5 KiB	11.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: 600 ms 597.8 KiB

URL	Transfer Size	Est Savings
grist.org/wp-content/themes/grist/dist/vendor.js?ver=0.16.28	221.6 KiB	156.6 KiB
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB	107.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-WBDMG4S	159.1 KiB	76.8 KiB
www.googletagmanager.com/gtag/destination?id=AW-735548782&cx=c&gtm=4e64h1	134.1 KiB	66.5 KiB
www.googletagmanager.com/gtag/js?id=G-8L4CPT2Q80&cx=c&gtm=4e64h1	172.7 KiB	65.5 KiB
cdn.wisepops.com/shared/wisepops/WfBjvuM6AwWqxUtKeXDF/591370.js?v=1773340452545	111.8 KiB	40.1 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	33.8 KiB
cdn.userway.org/widgetapp/2026-04-14-10-40-20/widget_app_base_1776163220800.js	47.1 KiB	26.7 KiB
/3f5c049a-7407-416b-bc5a-861f63f9ab95/cc.js?renew=false&r...	110.9 KiB	24.4 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
grist.org/wp-content/themes/grist/dist/vendor.js?ver=0.16.28	5.8 s	1.6 s	48 ms
grist.org/	1.9 s	37 ms	17 ms
Unattributable	1.6 s	404 ms	0.0 ms
/remediation/2026-04-14-10-40-20/paid/remediation-tool.js...	1.2 s	1.1 s	10 ms
/3f5c049a-7407-416b-bc5a-861f63f9ab95/cc.js?renew=false&r...	501 ms	214 ms	29 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	479 ms	412 ms	40 ms
cdn.wisepops.com/shared/wisepops/WfBjvuM6AwWqxUtKeXDF/591370.js?v=1773340452545	439 ms	399 ms	30 ms
grist.org/wp-content/themes/grist/dist/app.js?ver=0.16.28	388 ms	303 ms	7.6 ms
consent.cookiebot.com/uc.js	339 ms	289 ms	13 ms
www.googletagmanager.com/gtag/js?id=G-8L4CPT2Q80&cx=c&gtm=4e64h1	291 ms	247 ms	39 ms
www.googletagmanager.com/gtm.js?id=GTM-WBDMG4S	233 ms	193 ms	37 ms
cdn.userway.org/widgetapp/2026-04-14-10-40-20/widget_app_base_1776163220800.js	142 ms	117 ms	11 ms
static.chartbeat.com/js/chartbeat.js	137 ms	128 ms	4.8 ms
www.googletagmanager.com/gtag/destination?id=AW-735548782&cx=c&gtm=4e64h1	131 ms	106 ms	25 ms
connect.facebook.net/en_US/fbevents.js	115 ms	88 ms	25 ms
/signals/config/542017519474115?v=2.9.303&r=stable&domain...	114 ms	101 ms	13 ms
loader.wisepops.com/get-loader.js?v=1&site=UkdKwSrMxb	89 ms	77 ms	6.0 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	62 ms	55 ms	7.1 ms
static.chartbeat.com/js/subscriptions.js	62 ms	58 ms	2.6 ms
snap.licdn.com/li.lms-analytics/insight.min.js	61 ms	46 ms	4.4 ms
static.ads-twitter.com/uwt.js	56 ms	52 ms	3.1 ms
grist.org/wp-content/themes/grist/dist/latest-slider.js	51 ms	28 ms	0.9 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	6.4 s
Other	4.1 s
Style & Layout	1.5 s
Rendering	1.5 s
Script Parsing & Compilation	423 ms
Parse HTML & CSS	422 ms
Garbage Collection	212 ms

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.

●Layout shift culprits

●Optimize DOM size

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,658 KiB

●User Timing marks and measures 9 user timings

●Avoid long main-thread tasks 20 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 380 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Avoid large layout shifts 1 layout shift found

○INP breakdown

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

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.

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
AttributionReporting	snap.licdn.com/li.lms-analytics/insight.min.js

●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

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`