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
new.drupal.org/VnPBBfwe/init.js	600.0 s	103.2 KiB
/assets/js/js_Bnl1LxYQkOQTHhf-OZmYyBUBpRZwvUBDpfPx9t3x4Mc...	0.0 ms	55.5 KiB
/assets/css/css_g_I9kM1JK9O0moSuEEF_oGMYXX6f7Q0GbfUvr0vgK...	0.0 ms	53.3 KiB
new.drupal.org/themes/contrib/bluecheese/fonts/ZT_Gatha/ZTGatha-Bold.woff2	0.0 ms	26.8 KiB
/themes/contrib/bluecheese/components/components/case_stu...	0.0 ms	26.5 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
new.drupal.org/themes/contrib/bluecheese/fonts/Noto_Sans/NotoSans-Italic.woff2	0.0 ms	13.8 KiB
new.drupal.org/themes/contrib/bluecheese/fonts/Noto_Sans/NotoSans-Light.woff2	0.0 ms	13.4 KiB
new.drupal.org/themes/contrib/bluecheese/fonts/Noto_Sans/NotoSans-Medium.woff2	0.0 ms	13.3 KiB
new.drupal.org/themes/contrib/bluecheese/fonts/Noto_Sans/NotoSans-Regular.woff2	0.0 ms	13.1 KiB
new.drupal.org/themes/contrib/bluecheese/fonts/Noto_Sans/NotoSans-Bold.woff2	0.0 ms	13.1 KiB
new.drupal.org/themes/contrib/bluecheese/images/socials/mastodon-logo.svg	0.0 ms	2.6 KiB
new.drupal.org/themes/contrib/bluecheese/images/socials/instagram-logo.svg	0.0 ms	2.6 KiB
new.drupal.org/themes/contrib/bluecheese/images/socials/linkedin-logo.svg	0.0 ms	2.5 KiB
new.drupal.org/themes/contrib/bluecheese/images/socials/youtube-logo.svg	0.0 ms	2.4 KiB
new.drupal.org/themes/contrib/bluecheese/images/drop-pattern.svg	0.0 ms	2.3 KiB
new.drupal.org/themes/contrib/bluecheese/images/socials/slack-logo.svg	0.0 ms	2.2 KiB
/themes/contrib/bluecheese/components/components/header/h...	0.0 ms	2.0 KiB
new.drupal.org/themes/contrib/bluecheese/images/user.svg	0.0 ms	2.0 KiB
new.drupal.org/themes/contrib/bluecheese/images/socials/facebook-logo.svg	0.0 ms	1.9 KiB
/themes/contrib/bluecheese/components/components/header/h...	0.0 ms	1.7 KiB
/assets/css/css_8366dzQuryqL_l2I-J1xXH_07Vcj98HEsF240BbKG...	0.0 ms	1.6 KiB
/themes/contrib/bluecheese/components/components/header/h...	0.0 ms	1.5 KiB
new.drupal.org/themes/contrib/bluecheese/images/tag1logo-n.svg	0.0 ms	1.2 KiB
new.drupal.org/modules/contrib/google_tag/js/gtag.js?tdtfzb	0.0 ms	780 B
/themes/contrib/bluecheese/components/components/comparis...	0.0 ms	760 B
new.drupal.org/modules/contrib/google_tag/js/gtm.js?tdtfzb	0.0 ms	730 B
/themes/contrib/bluecheese/components/components/case_stu...	0.0 ms	680 B
/themes/contrib/bluecheese/components/components/case_stu...	0.0 ms	624 B
/assets/js/js_GibRgfhrhI2yhKlrf20pkl5dJchn3HxS5VsmP92O1BU...	0.0 ms	545 B
/themes/contrib/bluecheese/components/components/header/h...	0.0 ms	311 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.146757] map[node:map[boundingRect:map[bottom:13136 height:13015 left:0 right:412 top:121 width:412] lhId:page-1-DIV nodeLabel:Search Drupal.org Menu Main menu Home The Web's Most Powerful Open Source CMS … path:1,HTML,1,BODY,3,DIV selector:body.drupalorg-site-main > div.dialog-off-canvas-main-canvas snippet:<div class="dialog-off-canvas-main-canvas" data-off-canvas-main-canvas=""> type:node] score:0.146757]]

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
/themes/contrib/bluecheese/components/branding/icons/Font...	485 ms
new.drupal.org/themes/contrib/bluecheese/fonts/ZT_Gatha/ZTGatha-Bold.woff2	15 ms
new.drupal.org/themes/contrib/bluecheese/fonts/Noto_Sans/NotoSans-Medium.woff2	10 ms
new.drupal.org/themes/contrib/bluecheese/fonts/Noto_Sans/NotoSans-Regular.woff2	10 ms
new.drupal.org/themes/contrib/bluecheese/fonts/Noto_Sans/NotoSans-Bold.woff2	5.0 ms

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

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
/assets/css/css_g_I9kM1JK9O0moSuEEF_oGMYXX6f7Q0GbfUvr0vgK...	53.3 KiB	300 ms
new.drupal.org/modules/contrib/google_tag/js/gtag.js?tdtfzb	780 B
/assets/js/js_GibRgfhrhI2yhKlrf20pkl5dJchn3HxS5VsmP92O1BU...	545 B
new.drupal.org/modules/contrib/google_tag/js/gtm.js?tdtfzb	730 B
/assets/css/css_8366dzQuryqL_l2I-J1xXH_07Vcj98HEsF240BbKG...	1.6 KiB

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

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: 4.7 s

URL	Time Spent
drupal.org/	750 ms
www.drupal.org/	3.2 s
www.drupal.org/	0.0 ms
new.drupal.org/	753 ms
new.drupal.org/	0.0 ms
new.drupal.org/home	0.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.

Element	Layout shift score
Search Drupal.org Menu Main menu Home The Web's Most Powerful Open Source CMS … `body.drupalorg-site-main > div.dialog-off-canvas-main-canvas`	0.147
	0.030
	0.030

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 41.2 KiB

URL	Transfer Size	Est Savings
/assets/css/css_g_I9kM1JK9O0moSuEEF_oGMYXX6f7Q0GbfUvr0vgK...	53.1 KiB	41.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.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	829 ms	128 ms	0.0 ms
new.drupal.org/home	707 ms	15 ms	1.6 ms
new.drupal.org/VnPBBfwe/init.js	372 ms	323 ms	19 ms
www.drupal.org/_fs-ch-1T1wmsGaOgGaSxcX/script.js?reload=true	222 ms	201 ms	5.4 ms
/assets/js/js_Bnl1LxYQkOQTHhf-OZmYyBUBpRZwvUBDpfPx9t3x4Mc...	209 ms	127 ms	18 ms
www.googletagmanager.com/gtag/js?id=G-DW13JY8ZWD&cx=c&_slc=1	202 ms	161 ms	40 ms
www.googletagmanager.com/gtm.js?id=GTM-W36H8DW	174 ms	134 ms	30 ms
new.drupal.org/_fs-ch-1T1wmsGaOgGaSxcX/script.js?reload=true	131 ms	118 ms	3.9 ms
www.google-analytics.com/analytics.js	63 ms	53 ms	4.2 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	1.3 s
Other	803 ms
Style & Layout	511 ms
Rendering	211 ms
Script Parsing & Compilation	127 ms
Parse HTML & CSS	61 ms
Garbage Collection	15 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.

Estimated savings: 0.0 ms 198.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-W36H8DW	129.4 KiB	64.6 KiB
www.googletagmanager.com/gtag/js?id=G-DW13JY8ZWD&cx=c&_slc=1	162.5 KiB	64.1 KiB
new.drupal.org/VnPBBfwe/init.js	102.8 KiB	40.1 KiB
/assets/js/js_Bnl1LxYQkOQTHhf-OZmYyBUBpRZwvUBDpfPx9t3x4Mc...	55.4 KiB	29.6 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
Tag1 logo `div.footer__secondary-section > div.footer__sponsorship > a.footer__sponsorship-logo > img`	new.drupal.org/themes/contrib/bluecheese/images/tag1logo-n.svg
facebook logo `ul.footer__social-menu > li.footer__social-menu-item > a > img`	new.drupal.org/themes/contrib/bluecheese/images/socials/facebook-logo.svg
instagram logo `ul.footer__social-menu > li.footer__social-menu-item > a > img`	new.drupal.org/themes/contrib/bluecheese/images/socials/instagram-logo.svg
linkedin logo `ul.footer__social-menu > li.footer__social-menu-item > a > img`	new.drupal.org/themes/contrib/bluecheese/images/socials/linkedin-logo.svg
mastodon logo `ul.footer__social-menu > li.footer__social-menu-item > a > img`	new.drupal.org/themes/contrib/bluecheese/images/socials/mastodon-logo.svg
youtube logo `ul.footer__social-menu > li.footer__social-menu-item > a > img`	new.drupal.org/themes/contrib/bluecheese/images/socials/youtube-logo.svg
slack logo `ul.footer__social-menu > li.footer__social-menu-item > a > img`	new.drupal.org/themes/contrib/bluecheese/images/socials/slack-logo.svg

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

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,325 KiB

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 13 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 120 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 530 ms

○INP breakdown

○LCP request discovery

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

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
Drupal `div.l-section-container > div.cta-section__primary > h2.cta-section__title > strong`

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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

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

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

○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

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.

Source	Description
new.drupal.org/	`Connecting to 'https://www.drupal.org/fastly/logo' violates the following Content Security Policy directive: "default-src 'self'". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback. The action has been blocked.`
/_fs-ch-1T1wmsGaOgGaSxcX/pat?token=AcSjYzglySrZfgGj6fYUZR...	`Failed to load resource: the server responded with a status of 401 ()`
/_fs-ch-1T1wmsGaOgGaSxcX/pat?token=AdXABjKGGno4tjxsy-LHKo...	`Failed to load resource: the server responded with a status of 401 ()`
www.drupal.org/fastly/logo	`Failed to load resource: the server responded with a status of 404 ()`
new.drupal.org/	`Loading the image 'https://www.drupal.org/favicon.ico' violates the following Content Security Policy directive: "img-src 'self' data:". The action has been blocked.`

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

●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

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