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
/bEKlywPj/jetpack-awareness-video-2024-full_mov.thumbgrid...	2188295.0 s	410.1 KiB
jetpack.com/wp-content/uploads/2024/04/contacts_transactions-1.png?w=768	2094234.0 s	298.4 KiB

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:1.243 source:map[column:27 line:174 type:source-location url:https://jetpack.com/_static/??-eJylkN1OwzAMRl+IxAowrTeIZ3FT07pzfhR76+uTTYpAu0NcxYl8zucYjupiyUbZoMp15awQyywlXhRefZh8cMqpCrlGN/8OC6vB/tPkpOBCzSfOftcX+OWzjRIp4BRhJ6sYL4lcpuOOb/SgngjhGboVe9p6JVVqTg+2uFGDUbiDl5Vs9I3n/6isYVZB45L1L5+IRQSr8iz0jI1d3nihAtjzTe/I4z7O2vpgjr8adidW7pLP9BHO57fpFMJp2r8BanSZdg== urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:24.865 source:map[column:3537 line:0 type:source-location url:https://v0.wordpress.com/js/next/videopress-iframe.js?m=1770107250 urlProvider:network]] map[reflowTime:45.019 source:map[column:3764 line:0 type:source-location url:https://v0.wordpress.com/js/next/videopress-iframe.js?m=1770107250 urlProvider:network]] map[reflowTime:29.825 source:map[column:3270 line:0 type:source-location url:https://stats.wp.com/w.js?ver=202617 urlProvider:network]] map[reflowTime:0.22 source:map[column:674 line:496 type:source-location url:https://jetpack.com/_static/??-eJyVzEsOwjAMRdENkVqtkMwEsZYSDI3zVWwpZfekM9RZpn73GFoxNielpMACNagpNe/fieUCf5tuFElgvVlg0rJaH8kkagdi6Vn2joZQOdf9+Ha7ae6Vm0zRpZF3hwwueaoj6hnyp/ePeJ8Rr/OCCyL/AJeVY3w= urlProvider:network]] map[reflowTime:1.243 source:map[column:50 line:185 type:source-location url:https://jetpack.com/_static/??-eJylkN1OwzAMRl+IxAowrTeIZ3FT07pzfhR76+uTTYpAu0NcxYl8zucYjupiyUbZoMp15awQyywlXhRefZh8cMqpCrlGN/8OC6vB/tPkpOBCzSfOftcX+OWzjRIp4BRhJ6sYL4lcpuOOb/SgngjhGboVe9p6JVVqTg+2uFGDUbiDl5Vs9I3n/6isYVZB45L1L5+IRQSr8iz0jI1d3nihAtjzTe/I4z7O2vpgjr8adidW7pLP9BHO57fpFMJp2r8BanSZdg== urlProvider:network]] map[reflowTime:0.263 source:map[column:15 line:215 type:source-location url:https://jetpack.com/_static/??-eJylkN1OwzAMRl+IxAowrTeIZ3FT07pzfhR76+uTTYpAu0NcxYl8zucYjupiyUbZoMp15awQyywlXhRefZh8cMqpCrlGN/8OC6vB/tPkpOBCzSfOftcX+OWzjRIp4BRhJ6sYL4lcpuOOb/SgngjhGboVe9p6JVVqTg+2uFGDUbiDl5Vs9I3n/6isYVZB45L1L5+IRQSr8iz0jI1d3nihAtjzTe/I4z7O2vpgjr8adidW7pLP9BHO57fpFMJp2r8BanSZdg== urlProvider:network]] map[reflowTime:2.243 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.

	URL	Resource Size	Est Savings
div.wp-block-group > div.wp-block-media-text > figure.wp-block-media-text__media > img.wp-image-292584 `div.wp-block-group > div.wp-block-media-text > figure.wp-block-media-text__media > img.wp-image-292584`	jetpack.com/wp-content/uploads/2024/04/contacts_transactions-1.png?w=768	298.1 KiB	279.3 KiB
div.wp-block-group > div.wp-block-media-text > figure.wp-block-media-text__media > img.wp-image-292585 `div.wp-block-group > div.wp-block-media-text > figure.wp-block-media-text__media > img.wp-image-292585`	jetpack.com/wp-content/uploads/2024/04/performance-and-ux-1.png?w=768	68.5 KiB	56.9 KiB
div.home-hero-visual > div.home-hero-visual__container > picture > img.home-hero-visual__img `div.home-hero-visual > div.home-hero-visual__container > picture > img.home-hero-visual__img`	/wp-content/themes/a8c/jetpackme-new/images/home/hero-jc-...	26.3 KiB	22.6 KiB
div.wp-block-group > div.wp-block-media-text > figure.wp-block-media-text__media > img.wp-image-292586 `div.wp-block-group > div.wp-block-media-text > figure.wp-block-media-text__media > img.wp-image-292586`	jetpack.com/wp-content/uploads/2024/04/security_new-2x.webp?w=768	21.0 KiB	16.7 KiB

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:335.093 label:Time to first byte subpart:timeToFirstByte] map[duration:170.713 label:Resource load delay subpart:resourceLoadDelay] map[duration:20.103 label:Resource load duration subpart:resourceLoadDuration] map[duration:1999.455 label:Element render delay subpart:elementRenderDelay]]

lhId: page-2-IMG

nodeLabel: div.home-hero-visual > div.home-hero-visual__container > picture > img.home-hero-visual__img

path: 6,HTML,2,BODY,3,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,DIV,1,DIV,0,PICTURE,1,IMG

selector: div.home-hero-visual > div.home-hero-visual__container > picture > img.home-hero-visual__img

snippet: <img class="home-hero-visual__img" srcset="https://s0.wp.com/wp-content/themes/a8c/jetpackme-new/images/home/hero-jc-…" src="https://s0.wp.com/wp-content/themes/a8c/jetpackme-new/images/home/hero-jc-…" alt="">

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-2-IMG

nodeLabel: div.home-hero-visual > div.home-hero-visual__container > picture > img.home-hero-visual__img

path: 6,HTML,2,BODY,3,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,DIV,1,DIV,0,PICTURE,1,IMG

selector: div.home-hero-visual > div.home-hero-visual__container > picture > img.home-hero-visual__img

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.

URL	Transfer Size	Duration
v0.wordpress.com/js/videojs/videopress-iframe-api.js?ver=7.0-RC2-62212	2.5 KiB	753 ms
/_static/??-eJyVzEsOwjAMRdENkVqtkMwEsZYSDI3zVWwpZfekM9RZp...	6.4 KiB
/_static/??-eJyVj80KAjEMhF/IGnYR6kV8lrbGbjX9oclSfHu7yIKyH...	82.0 KiB	1.5 s
s0.wp.com/?custom-css=1&csblog=1moTy&cscache=6&csrev=505	3.1 KiB	752 ms
/_static/??-eJx9TttqwzAM/aHJWkpZt4exTxmKLRonlm0iuV3/fi403...	16.6 KiB
/_static/??-eJyNjMEKgzAQBX+o9hGQBg/FTxFdF0lMdoOb4O9Loe3Z4...	6.5 KiB	150 ms
jetpack.com/wp-content/themes/h4/global.css?m=1420737423i&cssminify=yes	621 B

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

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: 130 ms 11.1 KiB

URL	Transfer Size	Est Savings
/_static/??-eJyVj80KAjEMhF/IGnYR6kV8lrbGbjX9oclSfHu7yIKyH...	82.0 KiB	11.1 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: 270 ms 91.1 KiB

URL	Transfer Size	Est Savings
/_static/??-eJyVj80KAjEMhF/IGnYR6kV8lrbGbjX9oclSfHu7yIKyH...	81.7 KiB	75.9 KiB
/_static/??-eJx9TttqwzAM/aHJWkpZt4exTxmKLRonlm0iuV3/fi403...	16.3 KiB	15.3 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/bEKlywPj/jetpack-awareness-video-2024-full_mov_hd_1080p.mp4	1.6 MiB
/bEKlywPj/jetpack-awareness-video-2024-full_mov.thumbgrid...	410.1 KiB
jetpack.com/wp-content/uploads/2024/04/contacts_transactions-1.png?w=768	298.4 KiB
/wp-content/plugins/video/assets/js/videojs/videopress-ro...	239.7 KiB
/bEKlywPj/jetpack-awareness-video-2024-full_mov_hd_1080p....	122.1 KiB
s0.wp.com/i/fonts/inter/Inter-Italic.woff2?v=3.19	104.7 KiB
s0.wp.com/i/fonts/inter/Inter-Bold.woff2?v=3.19	104.0 KiB
s0.wp.com/i/fonts/inter/Inter-Medium.woff2?v=3.19	103.8 KiB
s0.wp.com/i/fonts/inter/Inter-SemiBold.woff2?v=3.19	103.7 KiB
s0.wp.com/i/fonts/inter/Inter-Regular.woff2?v=3.19	96.9 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.


Automattic `ul.a8c-footer__link-list > li.a8c-footer__home > a.a8c-footer__home-link > img.a8c-footer__a8c-logo`

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

●Max Potential First Input Delay 100 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●Reduce unused JavaScript

●JavaScript execution time 0.3 s

●Minimizes main-thread work 1.6 s

●Avoid long main-thread tasks 6 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 180 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 330 ms

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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
per month for the first year, billed yearly `div.jetpack-product-card__heading-wrapper > div.jetpack-product-card__price > div.plan-price__values > span.jetpack-product-card__billing-time-frame`
per month for the first year, billed yearly `div.jetpack-product-card__heading-wrapper > div.jetpack-product-card__price > div.plan-price__values > span.jetpack-product-card__billing-time-frame`
per month for the first year, billed yearly `div.jetpack-product-card__heading-wrapper > div.jetpack-product-card__price > div.plan-price__values > span.jetpack-product-card__billing-time-frame`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
storage limit `div.jetpack-product-card > div.jetpack-product-card__body > p.jetpack-product-card__disclaimer > a`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wp-block-group > div.wp-block-group > figure.wp-block-image > a `div.wp-block-group > div.wp-block-group > figure.wp-block-image > a`
div.wp-block-group > div.wp-block-group > figure.wp-block-image > a `div.wp-block-group > div.wp-block-group > figure.wp-block-image > a`

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to main content `header.mast > header#jetpack-header > nav.header__content > a.header__skip`

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
Jetpack X account (formerly known as Twitter) `li.sitemap__category > ul.sitemap__link-list > li > a.sitemap__link`
Jetpack Facebook page `li.sitemap__category > ul.sitemap__link-list > li > a.sitemap__link`
Jetpack LinkedIn page `li.sitemap__category > ul.sitemap__link-list > li > a.sitemap__link`
Jetpack Youtube channel `li.sitemap__category > ul.sitemap__link-list > li > a.sitemap__link`

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

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Author / Investor / Podcaster `figure > figcaption.testimonial-block__caption > span.testimonial-block__author-position > a`
EN `div.jetpack-footer__content > div.jetpack-footer__head > div.jetpack-footer__language > button.language-toggle`

○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

●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

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Heading elements appear in a sequentially-descending order

●Identical links have the same purpose.

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

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

○No element has a `[tabindex]` value greater than 0

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

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

100

Best Practices

●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

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●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

○Use a strong HSTS policy

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