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.

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
jquery.com/wp-content/themes/jquery/lib/Cairo/Cairo-Bold.woff2	25 ms
jquery.com/wp-content/themes/jquery/lib/FontAwesome/fontawesome-webfont.woff2	25 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
code.jquery.com/jquery-4.0.0.min.js	27.2 KiB	900 ms
jquery.com/wp-content/themes/jquery/js/main.js?v=10baaffd	1.6 KiB
jquery.com/wp-content/themes/jquery.com/style.css?v=8acf125c	1.3 KiB
jquery.com/wp-content/themes/jquery/css/base.css?v=4a1b65ae	13.3 KiB	333 ms
/wp-content/themes/jquery/lib/typesense-minibar/typesense...	4.2 KiB

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
jquery.com/wp-content/themes/jquery/lib/Cairo/Cairo-Bold.woff2	1800.0 s	35.4 KiB
jquery.com/wp-content/themes/jquery/lib/FontAwesome/fontawesome-webfont.woff2	1800.0 s	23.2 KiB
jquery.com/wp-content/themes/jquery/content/books/jquery-in-action.jpg	86400.0 s	24.4 KiB
jquery.com/wp-content/themes/jquery.com/i/feature-sprites.png	86400.0 s	18.4 KiB
jquery.com/wp-content/themes/jquery/css/base.css?v=4a1b65ae	86400.0 s	13.3 KiB
jquery.com/wp-content/themes/jquery/content/books/learning-jquery-4th-ed.jpg	86400.0 s	6.9 KiB
jquery.com/wp-content/themes/jquery/images/logo-jquery.png	86400.0 s	4.5 KiB
/wp-content/themes/jquery/lib/typesense-minibar/typesense...	86400.0 s	4.2 KiB
jquery.com/wp-content/themes/jquery/content/books/jquery-succinctly.jpg	86400.0 s	3.6 KiB
jquery.com/wp-content/themes/jquery/images/dark-grey-tile.png	86400.0 s	2.8 KiB
/wp-content/themes/jquery/lib/typesense-minibar/typesense...	86400.0 s	2.2 KiB
jquery.com/wp-content/themes/jquery/js/main.js?v=10baaffd	86400.0 s	1.6 KiB
jquery.com/wp-content/themes/jquery/images/logo-wordpress.svg	1800.0 s	669 B
jquery.com/wp-content/themes/jquery.com/style.css?v=8acf125c	86400.0 s	1.3 KiB
jquery.com/wp-content/themes/jquery/images/logo-digitalocean.svg	1800.0 s	477 B
jquery.com/wp-content/themes/jquery.com/i/download.png	86400.0 s	484 B

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
jQuery in Action by Bear Bibeault, Yehuda Katz, and Aurelio De Rosa `ul.books > li > a > img`	jquery.com/wp-content/themes/jquery/content/books/jquery-in-action.jpg	24.3 KiB	22.6 KiB
div#banner-secondary > div.features-box > div.feature-box > div.feature-box-image `div#banner-secondary > div.features-box > div.feature-box > div.feature-box-image`	jquery.com/wp-content/themes/jquery.com/i/feature-sprites.png	18.3 KiB	11.3 KiB
Learning jQuery 4th Edition by Karl Swedberg and Jonathan Chaffer `ul.books > li > a > img`	jquery.com/wp-content/themes/jquery/content/books/learning-jquery-4th-ed.jpg	6.8 KiB	5.2 KiB

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

Diagnostics

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

URL	Transfer Size	Est Savings
jquery.com/wp-content/themes/jquery/css/base.css?v=4a1b65ae	13.3 KiB	4.2 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.7 s

●Max Potential First Input Delay 20 ms

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 180 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.4 s

●Avoid long main-thread tasks 1 long task found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 10 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 30 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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

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
nav#main > typesense-minibar > form.searchform > button.visuallyhidden `nav#main > typesense-minibar > form.searchform > button.visuallyhidden`

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.

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
herodevs.com `body.jquery > div#banner > a`
Navigation `div#container > nav#main > div.menu-top-container > button#menu-trigger`
v4.0.0 `a.button > span.download-button-content > span.download-message > span.download-version`
"button.continue" `div.container > div.line > code > span.hljs-string`
"Next Step..." `div.container > div.line > code > span.hljs-string`
"#banner-message" `div.container > div.line > code > span.hljs-string`
"#button-container button" `div.container > div.line > code > span.hljs-string`
"click" `div.container > div.line > code > span.hljs-string`
url `div.container > div.line > code > span.hljs-attr`
"/api/getWeather" `div.container > div.line > code > span.hljs-string`
data `div.container > div.line > code > span.hljs-attr`
zipcode `div.container > div.line > code > span.hljs-attr`
97201 `div.container > div.line > code > span.hljs-number`
success `div.container > div.line > code > span.hljs-attr`
"#weather-temp" `div.container > div.line > code > span.hljs-string`
"<strong>" `div.container > div.line > code > span.hljs-string`
"</strong> degrees" `div.container > div.line > code > span.hljs-string`

These are opportunities to improve the legibility of your content.

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
Discover Support Options `div#banner-secondary > div.download > div.download-options > a`
View Source on GitHub → `div#banner-secondary > div.download > div.download-options > a`
How jQuery Works → `div#banner-secondary > div.download > div.download-options > a`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js `html.js`

These items highlight common accessibility best practices.

○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

●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

●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

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

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

○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

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
jQuery Succinctly by Cody Lindley `ul.books > li > a > img`	jquery.com/wp-content/themes/jquery/content/books/jquery-succinctly.jpg	90 x 112 (0.80)	124 x 166 (0.75)

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
jquery.com/ line 347, col 0	`Applying inline speculation rules violates the following Content Security Policy directive 'script-src 'self' 'nonce-db04281fedbe392c' code.jquery.com'. Either the 'unsafe-inline' keyword, a hash ('sha256-hZhXKqL3V9mpohqAHCc0GmfFPvqrhP8tP/zBKtvjXmg='), or a nonce ('nonce-...') is required to enable inline execution. The action has been blocked.`
jquery.com/ line 26, col 0	`Applying inline style violates the following Content Security Policy directive 'style-src 'self' 'nonce-db04281fedbe392c' code.jquery.com'. Either the 'unsafe-inline' keyword, a hash ('sha256-UIcrKzPURWyA4TnwsGBP76F3UAtE9ZnoB43rgcG+OVw='), or a nonce ('nonce-...') is required to enable inline execution. 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

●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

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
/2021/10/07/jquery-maintainers-update-and-transition-jque...	Learn more
/2021/10/jquery-maintainers-continue-modernization-initia...	Learn more

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

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`