Skip to content
https://rhizome.org

Lighthouse Mobile

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

62

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
static.rhizome.org/media/cache/45/ca/45ca6b933a7d856f229d57f7fd0bd61a.jpg14400.0 s377.2 KiB
static.rhizome.org/media/cache/97/eb/97ebf826ddfbac2a4d03e5527c124638.png14400.0 s340.3 KiB
static.rhizome.org/media/cache/3b/ea/3beaebb5ee30d59ce369ecd485299187.jpg14400.0 s321.7 KiB
static.rhizome.org/media/cache/80/91/809111ac1f0f95f70bba8d9d8a129cf6.jpg14400.0 s236.8 KiB
static.rhizome.org/media/cache/c2/63/c263881b6f6d350df4c1002dab1b26a8.jpg14400.0 s145.3 KiB
static.rhizome.org/media/cache/0f/96/0f96a9eff25f31476fec8e0a210e8d69.jpg14400.0 s99.1 KiB
static.rhizome.org/media/cache/95/3c/953ca535f07573c29c2a954bd8426058.png14400.0 s91.7 KiB
static.rhizome.org/media/cache/0b/b0/0bb0ff5def0718d83deb6f554b23a7f6.jpg14400.0 s63.0 KiB
static.rhizome.org/static/fonts/u001-rhizome/U001-Bol-v2.4.woff14400.0 s60.8 KiB
static.rhizome.org/static/fonts/u001-rhizome/U001-Reg-v2.4.woff14400.0 s60.2 KiB
static.rhizome.org/media/cache/b6/f9/b6f9cffed3b489e03af89f87466e7ae7.jpg14400.0 s51.4 KiB
static.rhizome.org/media/cache/25/25/252569a759364e03d1f3ba383ec112a2.jpg14400.0 s46.5 KiB
static.rhizome.org/media/cache/7a/6e/7a6eae31a96ec3d04107ba5031e9baf0.jpg14400.0 s38.1 KiB
static.rhizome.org/static/css/style.e84c14f6.css14400.0 s26.7 KiB
static.rhizome.org/static/js/bundle.bb9e5a36.js14400.0 s18.8 KiB
rhizome.org/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?14400.0 s12.3 KiB
static.rhizome.org/static/css/index-module.4b6ff2ba.css14400.0 s10.6 KiB
rhizome.org/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js2873.0 s753 B
static.rhizome.org/static/js/loadfx.ded2b16e.js14400.0 s559 B

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.11512100000000003] map[score:0.004376] map[score:0.004354] map[score:0.004348] map[score:0.004347] map[score:0.00428]]

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
li > a.plain > figure > img li > a.plain > figure > img
static.rhizome.org/media/cache/97/eb/97ebf826ddfbac2a4d03e5527c124638.png339.7 KiB317.5 KiB
li > a.plain > figure > img li > a.plain > figure > img
static.rhizome.org/media/cache/45/ca/45ca6b933a7d856f229d57f7fd0bd61a.jpg376.6 KiB278.8 KiB
li > a.plain > figure > img li > a.plain > figure > img
static.rhizome.org/media/cache/3b/ea/3beaebb5ee30d59ce369ecd485299187.jpg321.2 KiB234.1 KiB
li > a.plain > figure > img li > a.plain > figure > img
static.rhizome.org/media/cache/80/91/809111ac1f0f95f70bba8d9d8a129cf6.jpg236.3 KiB184.0 KiB
li > a.plain > figure > img li > a.plain > figure > img
static.rhizome.org/media/cache/c2/63/c263881b6f6d350df4c1002dab1b26a8.jpg144.9 KiB101.3 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: li > a.plain > figure > img
path: 1,HTML,1,BODY,3,MAIN,0,UL,1,LI,0,A,0,FIGURE,0,IMG
selector: li > a.plain > figure > img
snippet: <img srcset="https://static.rhizome.org/media/cache/be/5e/be5e571aafa1b2f1016b3196ea02d…" sizes="(max-width: 500px) 80vw, 50vw" src="https://static.rhizome.org/media/cache/45/ca/45ca6b933a7d856f229d57f7fd0bd…" 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

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
static.rhizome.org/static/css/style.e84c14f6.css26.7 KiB1.2 s
static.rhizome.org/static/js/loadfx.ded2b16e.js559 B

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
static.rhizome.org/static/fonts/u001-rhizome/U001-Reg-v2.4.woff15 ms
static.rhizome.org/static/fonts/u001-rhizome/U001-Bol-v2.4.woff10 ms

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

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.

Layout shift score
0.004
0.004
0.004
0.004
0.004
0.004
0.004
0.004
0.004
0.004
0.004
0.004
0.004
0.004
0.004

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

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
Style & Layout1.1 s
Other1.0 s
Rendering613 ms
Script Evaluation472 ms
Parse HTML & CSS79 ms
Script Parsing & Compilation17 ms
Garbage Collection7.2 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 12.9 KiB
URLTransfer SizeEst Savings
static.rhizome.org/static/css/style.e84c14f6.css26.7 KiB8.9 KiB
static.rhizome.org/static/css/index-module.4b6ff2ba.css10.6 KiB4.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 35.4 KiB
URLTransfer SizeEst Savings
static.rhizome.org/static/css/style.e84c14f6.css26.5 KiB25.3 KiB
static.rhizome.org/static/css/index-module.4b6ff2ba.css10.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
li > a.plain > figure > img li > a.plain > figure > img
static.rhizome.org/media/cache/45/ca/45ca6b933a7d856f229d57f7fd0bd61a.jpg
li > a.plain > figure > img li > a.plain > figure > img
static.rhizome.org/media/cache/3b/ea/3beaebb5ee30d59ce369ecd485299187.jpg
li > a.plain > figure > img li > a.plain > figure > img
static.rhizome.org/media/cache/80/91/809111ac1f0f95f70bba8d9d8a129cf6.jpg
li > a.plain > figure > img li > a.plain > figure > img
static.rhizome.org/media/cache/c2/63/c263881b6f6d350df4c1002dab1b26a8.jpg
li > a.plain > figure > img li > a.plain > figure > img
static.rhizome.org/media/cache/97/eb/97ebf826ddfbac2a4d03e5527c124638.png

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

●Document request latency
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify JavaScript
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 2,014 KiB
●JavaScript execution time 0.5 s
●Avoid long main-thread tasks 5 long tasks found
●Avoid non-composited animations 50 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 260 ms
●Server Backend Latencies 260 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 260 ms
○INP breakdown
○User Timing marks and measures
90

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.landing > section.cta-container > div.cta > button.cta-close body.landing > section.cta-container > div.cta > button.cta-close

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
7x7 2026: Containment tr > td > div.title > a.plain
Online Conversation with Sam Lavigne tr > td > div.title > a.plain
Works from SCREENTIME tr > td > div.title > a.plain

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
2026-05-16 7x7 2026: Containment #Seven on Seven, #new museum, #7x7 ... 2026-04… div > section#index > table
○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Identical links have the same purpose.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○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
○`<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.
○Elements with visible text labels have matching accessible names.
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
SharedStorage
rhizome.org/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
rhizome.org/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge
rhizome.org/cdn-cgi/challenge-platform/scripts/jsd/main.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 DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
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