Skip to content
https://theweek.com

Lighthouse Desktop

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

80

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
bordeaux.futurecdn.net/bordeaux.js0.0 ms159.0 KiB
cdn.privacy-mgmt.com/Notice.8f529.js3600.0 s91.2 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=78421800.0 s64.7 KiB
cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js3600.0 s42.0 KiB
freyr.futurecdn.net/freyr.js0.0 ms22.3 KiB
sdk.mrf.io/statics/47bd3e88b6bda15c34ce.js3600.0 s24.4 KiB
champagne.futurecdn.net/champagne.js0.0 ms16.1 KiB
cdn.privacy-mgmt.com/Notice.30929.css3600.0 s6.7 KiB
sdk.mrf.io/statics/compass-multimedia-sdk.js?version=22603600.0 s4.3 KiB
uk-script.dotmetrics.net/Scripts/ncs-script.js?v=3620.0 ms2.9 KiB
sb.scorecardresearch.com/internal-cs/default/beacon.js86400.0 s6.7 KiB
cdn.mos.cms.futurecdn.net/flexiimages/qsgislpohy1687441729.svg0.0 ms2.5 KiB
cdn.privacy-mgmt.com/polyfills.01516.js3600.0 s2.3 KiB
/hit.gif?id=12390&url=https%3A%2F%2Ftheweek.com%2F&dom=th...86400.0 s1.1 KiB

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.203667] map[node:map[boundingRect:map[bottom:0 height:0 left:0 right:0 top:0 width:0] lhId:page-9-META nodeLabel:head > meta path:1,HTML,0,HEAD,2,META selector:head > meta snippet:<meta name="viewport" content="width=device-width,initial-scale=1"> type:node] score:0.203667]]

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:46.35 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.

URLResource SizeEst Savings
a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img
cdn.mos.cms.futurecdn.net/xxmmDLr9rzCMDCkRPgBNPF-11024-80.jpg.webp443.3 KiB416.0 KiB
a.listing__link > div.listing__image-layout > div.listing__image-wrapper > img.listing__image a.listing__link > div.listing__image-layout > div.listing__image-wrapper > img.listing__image
cdn.mos.cms.futurecdn.net/5kSDDVwuYp9BmoBiBVJJAV-1360-80.jpg.webp361.4 KiB347.5 KiB
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
cdn.mos.cms.futurecdn.net/7XrfJYwowSPnctHfP3frsh-2360-80.jpg.webp227.8 KiB219.1 KiB
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
cdn.mos.cms.futurecdn.net/pqVw3TMZvBezZrw4RRApiQ-2360-80.jpg.webp169.1 KiB162.6 KiB
a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img
cdn.mos.cms.futurecdn.net/oHTiFVQszJBRAzf945RZgY-1600-80.jpg.webp88.6 KiB86.2 KiB
https://cdn.mos.cms.futurecdn.net/flexiimages/jacafc5zvs1692883516.jpg div.navigation__burgerbar > a.vanilla-blueconic-header-wrapper > div#blueconic-header-theweek > img.vanilla-blueconic-header__img
cdn.mos.cms.futurecdn.net/flexiimages/jacafc5zvs1692883516.jpg63.9 KiB63.0 KiB
Add The Week to your weekly routine div.image-full-width-wrapper > div.image-widthsetter > p.vanilla-image-block > img#kxNqzHUDqKSCRhkHJhUyqi
cdn.mos.cms.futurecdn.net/kxNqzHUDqKSCRhkHJhUyqi.gif103.7 KiB47.7 KiB
a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img
cdn.mos.cms.futurecdn.net/L3TddgZL8WGq9kpWnnJaGh-1600-80.jpg.webp21.7 KiB21.1 KiB
Photo collage of a hand holding a Raspberry Pi and another hand with a doll han… div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
cdn.mos.cms.futurecdn.net/Fk6qPYBtGEoMWKNZm7U2Yo-360-80.jpg.webp21.8 KiB9.9 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: a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img
path: 1,HTML,1,BODY,5,DIV,0,DIV,0,DIV,2,UL,0,LI,0,A,0,DIV,0,DIV,0,IMG
selector: a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img
snippet: <img src="https://cdn.mos.cms.futurecdn.net/xxmmDLr9rzCMDCkRPgBNPF-11024-80.jpg.webp" class="v2-listing-image-img block-image-ads" srcset="https://cdn.mos.cms.futurecdn.net/xxmmDLr9rzCMDCkRPgBNPF-11920-80.jpg.webp…" sizes="(min-width: 1024px) 970px, 100vw" data-original-mos="https://cdn.mos.cms.futurecdn.net/xxmmDLr9rzCMDCkRPgBNPF-1920-80.jpg.webp" data-pin-media="https://cdn.mos.cms.futurecdn.net/xxmmDLr9rzCMDCkRPgBNPF-1920-80.jpg.webp" data-pin-nopin="true">

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

URLTransfer SizeDuration
search-api.fie.futurecdn.net/css/browser/master-f8e9977d/progressive.min.css10.6 KiB202 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.

ElementLayout shift score
head > meta head > meta
0.204

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

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: 100 ms 658.5 KiB
URLTransfer SizeEst Savings
bordeaux.futurecdn.net/bordeaux.js158.6 KiB90.1 KiB
vanilla.futurecdn.net/theweek/1610431/media/shared/js/bundle.connect.js138.1 KiB85.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-TBNNBVX9&gtm=4e64h1140.9 KiB80.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-WHLXGS3C&gtm=4e64h1166.1 KiB68.8 KiB
search-api.fie.futurecdn.net/js/w/es6/master-f8e9977d/progressive.js108.4 KiB66.9 KiB
www.googletagmanager.com/gtag/js?id=G-N7FFZKR5JW&cx=c&gtm=4e64h1163.9 KiB63.0 KiB
theweek.com/58.6 KiB49.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-WWBWRXL143.2 KiB47.2 KiB
vanilla.futurecdn.net/theweek/app.Cl0pY1ep.js89.7 KiB33.1 KiB
theweek.com/vite/assets/vendor-DH-HcC7C.js40.4 KiB27.8 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=784264.4 KiB24.0 KiB
sdk.mrf.io/statics/47bd3e88b6bda15c34ce.js23.9 KiB22.1 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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.

URLTransfer Size
cdn.mos.cms.futurecdn.net/xxmmDLr9rzCMDCkRPgBNPF-11024-80.jpg.webp444.2 KiB
cdn.mos.cms.futurecdn.net/5kSDDVwuYp9BmoBiBVJJAV-1360-80.jpg.webp362.3 KiB
theweek.com/233.1 KiB
cdn.mos.cms.futurecdn.net/7XrfJYwowSPnctHfP3frsh-2360-80.jpg.webp228.6 KiB
cdn.mos.cms.futurecdn.net/pqVw3TMZvBezZrw4RRApiQ-2360-80.jpg.webp169.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-WHLXGS3C&gtm=4e64h1166.2 KiB
www.googletagmanager.com/gtag/js?id=G-N7FFZKR5JW&cx=c&gtm=4e64h1164.0 KiB
bordeaux.futurecdn.net/bordeaux.js159.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-WWBWRXL143.5 KiB
search-api.fie.futurecdn.net/js/w/es6/master-f8e9977d/progressive.js142.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
https://cdn.mos.cms.futurecdn.net/flexiimages/jacafc5zvs1692883516.jpg div.navigation__burgerbar > a.vanilla-blueconic-header-wrapper > div#blueconic-header-theweek > img.vanilla-blueconic-header__img
cdn.mos.cms.futurecdn.net/flexiimages/jacafc5zvs1692883516.jpg
The Week a.logo__link > span.logo__svg > picture > img
cdn.mos.cms.futurecdn.net/flexiimages/qsgislpohy1687441729.svg
flag of US div.locale-selector > button.locale-selector__trigger > div.locale-selector__icon--flag > img
vanilla.futurecdn.net/theweek/media/shared/img/flags/nosize/US.svg

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

●Max Potential First Input Delay 90 ms
●Document request latency
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●User Timing marks and measures 29 user timings
●JavaScript execution time 0.6 s
●Minimizes main-thread work 1.3 s
●Avoid long main-thread tasks 3 long tasks found
●Network Requests
●Network Round Trip Times 50 ms
●Server Backend Latencies 40 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 0 ms
○INP breakdown
○Avoid non-composited animations
77

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
div.navigation__container > div.navigation__burgerbar > div.search > button.navigation__search div.navigation__container > div.navigation__burgerbar > div.search > button.navigation__search

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img
a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img
a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
a.listing__link > div.listing__image-layout > div.listing__image-wrapper > img.listing__image a.listing__link > div.listing__image-layout > div.listing__image-wrapper > img.listing__image
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.newsletter-form__container > section.newsletter-form__main-section > form.newsletter-form__form > input.form__email-input div.newsletter-form__container > section.newsletter-form__main-section > form.newsletter-form__form > input.form__email-input

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.navigation__topitem > div.social > li.social__item > a.newsletter div.navigation__topitem > div.social > li.social__item > a.newsletter

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
QUOTE OF THE DAY li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label
By submitting your information you agree to the Terms & Conditions and Privacy … div.newsletter-form__wrapper > div.newsletter-form__container > section.newsletter-form__main-section > footer.newsletter-form__footer

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.navigation__container > div.navigation__topitem > div.social > li.social__item div.navigation__container > div.navigation__topitem > div.social > li.social__item

These are opportunities to improve the experience of reading tabular or list data using 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
●Input buttons have discernible text.
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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>`).
●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
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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 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.
○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
○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.
77

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
Unload event listeners are deprecated and will be removed.
bordeaux.futurecdn.net/bordeaux.js line 31, col 6976

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.

SourceDescription
cache.pythia.futureplc.com/v1alpha1/decision-engine/match_all
Failed to load resource: the server responded with a status of 404 ()
vanilla.futurecdn.net/theweek/app.Cl0pY1ep.js line 11, col 8687
TypeError: Cannot read properties of undefined (reading 'length') at dd.generateCampaignsFromMatchAllResponse (https://vanilla.futurecdn.net/theweek/app.Cl0pY1ep.js:12:8688) at dd.<anonymous> (https://vanilla.futurecdn.net/theweek/app.Cl0pY1ep.js:12:8289) at Generator.next (<anonymous>) at i (https://vanilla.futurecdn.net/theweek/app.Cl0pY1ep.js:1:502)
●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 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
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
92

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img
a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img
a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img a.wdn-listv2-item-link > div.v2-listing-image-layout > div.v2-listing-image-wrapper > img.v2-listing-image-img
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
a.listing__link > div.listing__image-layout > div.listing__image-wrapper > img.listing__image a.listing__link > div.listing__image-layout > div.listing__image-wrapper > img.listing__image
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image
div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image div.listing__image-layout > div.listing__image-wrapper > picture > img.listing__image

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 have descriptive text
●Links are crawlable
●robots.txt is valid
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback