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
cdn-4.convertexperiments.com/js/1004924-1004851.js	300.0 s	104.8 KiB
widget.trustpilot.com/trustboxes/5406e65db0d04a09e042d5fc/main.js	86400.0 s	26.1 KiB
mbyoastbv.activehosted.com/f/embed.php?id=44	120.0 s	9.7 KiB
widget.trustpilot.com/trustboxes/54ad5defc6454f065c28af8b/main.js	86400.0 s	18.5 KiB
yoast.com/cdn-cgi/challenge-platform/h/g/scripts/jsd/fe6331af5207/main.js?	14400.0 s	10.8 KiB
widget.trustpilot.com/bootstrap/v5/tp.widget.bootstrap.min.js	86400.0 s	8.1 KiB
beacon-v2.helpscout.net/	120.0 s	863 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.201505] map[node:map[boundingRect:map[bottom:891 height:200 left:28 right:384 top:690 width:356] lhId:page-1-FIGURE nodeLabel:Load Wistia-inc video: Yoast Homepagevideo path:1,HTML,1,BODY,3,DIV,0,MAIN,0,DIV,0,DIV,6,FIGURE selector:main#content > div.wp-block-group > div.wp-block-group__inner-container > figure.wp-block-embed snippet:<figure class="wp-block-embed aligncenter is-style-yoast-styling is-type-video is-provid…"> type:node] score:0.124589] map[node:map[boundingRect:map[bottom:891 height:200 left:28 right:384 top:690 width:356] lhId:page-1-FIGURE nodeLabel:Load Wistia-inc video: Yoast Homepagevideo path:1,HTML,1,BODY,3,DIV,0,MAIN,0,DIV,0,DIV,6,FIGURE selector:main#content > div.wp-block-group > div.wp-block-group__inner-container > figure.wp-block-embed snippet:<figure class="wp-block-embed aligncenter is-style-yoast-styling is-type-video is-provid…"> type:node] score:0.076916 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:324 height:128 left:28 right:313 top:196 width:285] lhId:page-28-IMG nodeLabel:div.wp-block-group > div.wp-block-group__inner-container > figure.wp-block-image > img.content-visible path:1,HTML,1,BODY,3,DIV,0,MAIN,0,DIV,0,DIV,2,FIGURE,0,IMG selector:div.wp-block-group > div.wp-block-group__inner-container > figure.wp-block-image > img.content-visible snippet:<img decoding="async" src="https://yoast.com/app/uploads/2025/04/yoast_logo_2025_homepage.svg" alt="" class="content-visible wp-image-4082107" style="width:285px"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:7864 height:128 left:27 right:385 top:7736 width:358] lhId:page-6-IMG nodeLabel:Yoast SEO for Shopify path:1,HTML,1,BODY,3,DIV,0,MAIN,6,DIV,3,DIV,0,DIV,0,FIGURE,0,A,0,IMG selector:div.product-shop__card-top > figure.product-image > a > img snippet:<img src="https://yoast.com/cdn-cgi/image/width=672%2Cheight=240%2Cfit=crop%2Cf=auto…" srcset="https://yoast.com/cdn-cgi/image/width=672%2Cheight=240%2Cfit=crop%2Cf=auto…" sizes="auto, (min-width: 480px) 672px, (min-width: 1012px) 33vw" alt="Yoast SEO for Shopify" loading="lazy" fetchpriority="low" decoding="async" width="672" height="240"> type:node] score:0]]

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:18.697 source:map[column:616 line:26 type:source-location url:https://cdn-4.convertexperiments.com/js/1004924-1004851.js 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:15.871 source:map[column:12654 line:25 type:source-location url:https://cdn-4.convertexperiments.com/js/1004924-1004851.js urlProvider:network]] map[reflowTime:0.244 source:map[column:12751 line:25 type:source-location url:https://cdn-4.convertexperiments.com/js/1004924-1004851.js urlProvider:network]] map[reflowTime:0.557 source:map[column:12981 line:25 type:source-location url:https://cdn-4.convertexperiments.com/js/1004924-1004851.js urlProvider:network]] map[reflowTime:0.082 source:map[column:13402 line:25 type:source-location url:https://cdn-4.convertexperiments.com/js/1004924-1004851.js urlProvider:network]] map[reflowTime:1.799 source:map[column:13552 line:25 type:source-location url:https://cdn-4.convertexperiments.com/js/1004924-1004851.js urlProvider:network]] map[reflowTime:0.144 source:map[column:13670 line:25 type:source-location url:https://cdn-4.convertexperiments.com/js/1004924-1004851.js urlProvider:network]] map[reflowTime:2.024 source:map[column:14212 line:0 type:source-location url:https://yoast.com/app/themes/yoast-theme/js/yoast.min.js?ver=1770295121 urlProvider:network]] map[reflowTime:0.513 source:map[column:81423 line:1 type:source-location url:https://yoast.com/app/themes/yoast-theme/js/includes/jquery-3.5.1.min.js?ver=3.5.1 urlProvider:network]] map[reflowTime:8.189 source:map[column:10534 line:0 type:source-location url:https://widget.trustpilot.com/bootstrap/v5/tp.widget.bootstrap.min.js urlProvider:network]] map[reflowTime:0.045 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.video-player > div.video-seo-embed-loader > picture.post__hero > img `div.video-player > div.video-seo-embed-loader > picture.post__hero > img`	/deliveries/b2e1b3e866eb2e9e5a8bd7cff6c44d86.jpg?image_cr...	132.9 KiB	122.7 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-0-IMG

nodeLabel: div.video-player > div.video-seo-embed-loader > picture.post__hero > img

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

selector: div.video-player > div.video-seo-embed-loader > picture.post__hero > img

snippet: <img alt="" sizes="(max-width: 1280px) 100vw, 1280px" srcset="https://embed-ssl.wistia.com/deliveries/b2e1b3e866eb2e9e5a8bd7cff6c44d86.j…">

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
/css2?family=Inter%3Awght%40400%3B500%3B600&ver=1.14	1.2 KiB	871 ms
cdn-4.convertexperiments.com/js/1004924-1004851.js	104.8 KiB	2.0 s
/app/plugins/address-autocomplete/build/style-address-aut...	95 B
/app/plugins/yith-multi-currency-switcher-for-woocommerce...	11.8 KiB
/app/themes/yoast-theme/css/patterns/Layout/Webinar_Page/...	974 B
yoast.com/app/themes/yoast-com/assets/css/pages/page-wide.min.css?ver=1773742574	2.2 KiB
yoast.com/app/themes/yoast-com/assets/css/siteheader.min.css?ver=1774858901	637 B
yoast.com/app/plugins/woocommerce/assets/css/select2.css?ver=10.0.5	2.0 KiB
yoast.com/app/uploads/daexthefup_uploads/custom-1.css?ver=1.14	843 B
/app/plugins/yith-multi-currency-switcher-for-woocommerce...	3.4 KiB	150 ms
yoast.com/app/plugins/helpful-pro/public/assets/css/general.css?ver=1.14	1.0 KiB
yoast.com/app/themes/yoast-theme/js/includes/jquery-3.5.1.min.js?ver=3.5.1	30.6 KiB	300 ms
yoast.com/app/plugins/woocommerce/assets/css/brands.css?ver=10.0.5	784 B	150 ms
fonts.bunny.net/css?family=ibm-plex-sans:400,600	1.3 KiB	760 ms
/app/plugins/yith-woocommerce-affiliates-premium/assets/c...	5.6 KiB

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.

Element	Layout shift score
Load Wistia-inc video: Yoast Homepagevideo `main#content > div.wp-block-group > div.wp-block-group__inner-container > figure.wp-block-embed`	0.125
Load Wistia-inc video: Yoast Homepagevideo `main#content > div.wp-block-group > div.wp-block-group__inner-container > figure.wp-block-embed`	0.077
Yoast SEO for Shopify `div.product-shop__card-top > figure.product-image > a > img`	0.000

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: 510 ms 65.2 KiB

URL	Transfer Size	Est Savings
yoast.com/app/themes/yoast-theme/css/style.min.css?ver=1777465021	61.3 KiB	53.5 KiB
/app/plugins/yith-multi-currency-switcher-for-woocommerce...	11.7 KiB	11.7 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: 1.0 s 317.4 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-5HDJXYWBNB&cx=c&gtm=4e6562	170.4 KiB	86.2 KiB
www.googletagmanager.com/gtag/js?id=AW-16841659969&cx=c&gtm=4e6562	143.5 KiB	81.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-NHRB36F	182.5 KiB	68.0 KiB
cdn-4.convertexperiments.com/js/1004924-1004851.js	104.3 KiB	57.4 KiB
beacon-v2.helpscout.net/static/js/vendor.4969c740.js	24.7 KiB	24.6 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
yoast.com/	581 ms	50 ms	11 ms
cdn-4.convertexperiments.com/js/1004924-1004851.js	482 ms	348 ms	24 ms
Unattributable	433 ms	6.2 ms	0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-NHRB36F	356 ms	297 ms	46 ms
yoast.com/cdn-cgi/challenge-platform/scripts/jsd/main.js	212 ms	206 ms	1.6 ms
www.googletagmanager.com/gtag/js?id=G-5HDJXYWBNB&cx=c&gtm=4e6562	195 ms	156 ms	37 ms
www.googletagmanager.com/gtag/js?id=AW-16841659969&cx=c&gtm=4e6562	141 ms	111 ms	29 ms
yoast.com/app/themes/yoast-theme/js/includes/jquery-3.5.1.min.js?ver=3.5.1	96 ms	85 ms	6.4 ms
widget.trustpilot.com/bootstrap/v5/tp.widget.bootstrap.min.js	71 ms	30 ms	1.6 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.4 s
Other	582 ms
Style & Layout	391 ms
Script Parsing & Compilation	196 ms
Parse HTML & CSS	122 ms
Rendering	60 ms
Garbage Collection	19 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.

	URL
div.wp-block-group > div.wp-block-group__inner-container > figure.wp-block-image > img.content-visible `div.wp-block-group > div.wp-block-group__inner-container > figure.wp-block-image > img.content-visible`	yoast.com/app/uploads/2025/04/yoast_logo_2025_homepage.svg
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.content-visible `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.content-visible`	yoast.com/app/uploads/2023/03/results_usp_optm.svg
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.content-visible `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.content-visible`	yoast.com/app/uploads/2023/03/support_usp_optm.svg
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.content-visible `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.content-visible`	yoast.com/app/uploads/2023/03/content_usp_optm.svg
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.content-visible `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.content-visible`	yoast.com/app/uploads/2023/03/technical_usp_optm.svg

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

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●Avoid long main-thread tasks 12 long tasks found

●Avoid non-composited animations 18 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 80 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 20 ms

○INP breakdown

○User Timing marks and measures

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
USD ($) EUR (€) GBP (£) `div.grid--flex > div.curreny_switcher_container > label > select#currency`

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.row > ul.utility-menu > li.login > a.menu-account `div.row > ul.utility-menu > li.login > a.menu-account`

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.

○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

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

●Select elements have associated label elements.

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

●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

●Links are distinguishable without relying on color.

●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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

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

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

○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

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
SharedStorage	yoast.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	yoast.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	yoast.com/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

●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

○Use a strong HSTS policy

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

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
19	`Schemamap: https://yoast.com/wp-json/yoast/v1/schema-aggregator/get-xml`	`Unknown directive`

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

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`