Skip to content
https://theinformation.com

Lighthouse Mobile

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

26

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
ti-assets.theinformation.com/packs/js/vendor-packages-fdbd8911d7fd8010b795.js14400.0 s840.7 KiB
js.stripe.com/acacia/stripe.js120.0 s220.2 KiB
ti-assets.theinformation.com/packs/js/897-6bbd6f9c8b09dca3e826.js14400.0 s189.7 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=52671800.0 s58.6 KiB
cdn.cookielaw.org/scripttemplates/202510.2.0/otBannerSdk.js86400.0 s124.3 KiB
cdn.p-n.io/pushly-sdk.min.js?domain_key=Wh0KRP2v2DPh4UPCgSrygixsTWBKP2XmUzDk300.0 s45.6 KiB
/signals/config/525402414304551?v=2.9.303&r=stable&domain...1200.0 s46.6 KiB
ti-assets.theinformation.com/packs/js/vendor-react-8519dd62207ba32d6207.js14400.0 s58.4 KiB
/analytics.js/v1/pBBV1c1b6TE22XZ2gQCmMx3vihrGNdPC/analyti...120.0 s28.8 KiB
ti-assets.theinformation.com/packs/css/446-3cd7427c.css14400.0 s28.9 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
utt.impactcdn.com/A6141635-34c3-4ac6-89de-710e23062de11.js900.0 s20.5 KiB
m.stripe.network/out-4.5.45.js300.0 s16.5 KiB
scripts.clarity.ms/0.8.59/clarity.js86400.0 s26.2 KiB
ti-assets.theinformation.com/packs/js/homepage-75828eb7dae88e3bb743.js14400.0 s14.1 KiB
cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js0.0 ms9.2 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...14400.0 s13.3 KiB
cdn.cookielaw.org/consent/018e806d-5784-74c9-9740-5aaf1d5dc546/OtAutoBlock.js86400.0 s21.1 KiB
pixel.byspotify.com/ping.min.js3600.0 s10.2 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/en_US/appleid.auth.js86400.0 s17.4 KiB
public.profitwell.com/js/profitwell.js?auth=null14400.0 s9.7 KiB
cdn.cookielaw.org/consent/018e806d-5784-74c9-9740-5aaf1d5dc546/otSDKStub.js86400.0 s12.1 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...86400.0 s10.7 KiB
ti-assets.theinformation.com/packs/js/535-ef24ec7a6ba3950b3b74.js14400.0 s5.8 KiB
/logos/8de75818-35ff-4a79-8fcd-fe7d20ffd525/018e806d-5784...86400.0 s8.7 KiB
/next-integrations/actions/google-ec-plugins/00b46d0899db...0.0 ms2.7 KiB
ti-assets.theinformation.com/packs/css/base_components-bfbb82a8.css14400.0 s3.9 KiB
alpharetargeting.com/source/arti.js0.0 ms2.1 KiB
ws.zoominfo.com/pixel/zMQorfj7aSSwrJ1oBwQx0.0 ms2.1 KiB
ti-assets.theinformation.com/packs/js/runtime-ad73b3f8e1d073df1807.js14400.0 s2.6 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.7 KiB
static-cdn.trackier.com/rtg/69c4cb49a8055b23cd23aca8.js3600.0 s1.0 KiB
/rp.gif?ts=1776888082419&id=t2_8l30jc1j&event=PageVisit&m...0.0 ms666 B
static-cdn.trackier.com/rtg/6997f17b5dc8e734c157cc89.js3600.0 s828 B
/collect?v=2&fmt=js&pid=8832882&time=1776888082392&li_ads...0.0 ms450 B
/tr/?id=525402414304551&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms16 B
/tr/?id=525402414304551&ev=impression&dl=https%3A%2F%2Fww...0.0 ms16 B

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.

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: How Tech M&A Is Filling AI Gaps
path: 1,HTML,1,BODY,3,DIV,2,SECTION,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,SECTION,1,DIV,0,ARTICLE,0,A,1,SPAN,0,IMG
selector: article.flex-1 > a.relative > span.h-full > img.h-auto
snippet: <img alt="How Tech M&amp;A Is Filling AI Gaps" class="h-auto w-full" loading="eager" sizes="(min-width: 480px) 600px, 400px" src="https://tii.imgix.net/production/articles/16974/c8bb2d75-1f6d-4456-8857-9e…" srcset="https://tii.imgix.net/production/articles/16974/c8bb2d75-1f6d-4456-8857-9e…">

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

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.

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
How Tech M&A Is Filling AI Gaps article.flex-1 > a.relative > span.h-full > img.h-auto
/production/articles/16974/c8bb2d75-1f6d-4456-8857-9e0ff5...71.7 KiB24.1 KiB

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

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.

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: 759 ms

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: 610 ms 106.5 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.

URLTotal CPU TimeScript EvaluationScript Parse
Unattributable1.3 s163 ms0.0 ms
www.theinformation.com/1.0 s400 ms36 ms
ti-assets.theinformation.com/packs/js/vendor-react-8519dd62207ba32d6207.js1.0 s958 ms24 ms
ti-assets.theinformation.com/packs/js/homepage-75828eb7dae88e3bb743.js742 ms715 ms10 ms
www.googletagmanager.com/gtm.js?id=GTM-MXFP3X735 ms615 ms66 ms
www.googletagmanager.com/gtag/js?id=G-LL334L9M32625 ms491 ms69 ms
sdk.mrf.io/statics/marfeel-sdk.js?id=5267530 ms510 ms1.7 ms
cdn.p-n.io/pushly-sdk.min.js?domain_key=Wh0KRP2v2DPh4UPCgSrygixsTWBKP2XmUzDk521 ms411 ms69 ms
www.theinformation.com/cdn-cgi/challenge-platform/scripts/jsd/main.js425 ms342 ms3.5 ms
scripts.clarity.ms/0.8.59/clarity.js391 ms352 ms10 ms
cdn.cookielaw.org/scripttemplates/202510.2.0/otBannerSdk.js390 ms304 ms61 ms
ti-assets.theinformation.com/packs/js/vendor-packages-fdbd8911d7fd8010b795.js389 ms24 ms363 ms
d712.theinformation.com/script.js371 ms310 ms17 ms
js.stripe.com/acacia/stripe.js298 ms166 ms131 ms
cdn.cookielaw.org/consent/018e806d-5784-74c9-9740-5aaf1d5dc546/OtAutoBlock.js253 ms182 ms57 ms
js-agent.newrelic.com/nr-spa-1.313.1.min.js214 ms173 ms12 ms
connect.facebook.net/en_US/fbevents.js177 ms133 ms43 ms
utt.impactcdn.com/A6141635-34c3-4ac6-89de-710e23062de11.js165 ms149 ms6.6 ms
/signals/config/525402414304551?v=2.9.303&r=stable&domain...164 ms139 ms24 ms
www.googletagmanager.com/gtag/js?id=AW-860455588&cx=c&gtm=4e64k0140 ms99 ms40 ms
cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js114 ms108 ms3.5 ms
ti-assets.theinformation.com/packs/js/897-6bbd6f9c8b09dca3e826.js105 ms2.1 ms103 ms
www.googletagmanager.com/gtag/js?id=G-LL334L9M32&cx=c&gtm=4e64k0100 ms33 ms67 ms
/next-integrations/integrations/vendor/commons.59560acdd6...99 ms86 ms8.3 ms
www.googletagmanager.com/gtag/destination?id=G-LL334L9M32&cx=c&gtm=4e64k094 ms31 ms62 ms
cdn.cookielaw.org/consent/018e806d-5784-74c9-9740-5aaf1d5dc546/otSDKStub.js91 ms62 ms4.4 ms
www.googletagmanager.com/gtag/js?id=AW-86045558870 ms26 ms44 ms
static.ads-twitter.com/uwt.js64 ms57 ms5.4 ms
accounts.google.com/gsi/client62 ms25 ms36 ms
theinformation.blueconic.net/DG/DEFAULT/cs?&callback=bc_json20160 ms52 ms0.3 ms
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...53 ms40 ms3.8 ms
www.redditstatic.com/ads/pixel.js52 ms35 ms8.1 ms
cdn.rollbar.com/rollbarjs/refs/tags/v2.26.1/rollbar.min.js51 ms20 ms9.5 ms
snap.licdn.com/li.lms-analytics/insight.min.js51 ms44 ms6.5 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.

CategoryTime Spent
Script Evaluation7.8 s
Script Parsing & Compilation1.5 s
Other1.4 s
Style & Layout443 ms
Garbage Collection237 ms
Parse HTML & CSS179 ms
Rendering41 ms

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

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
How Tech M&A Is Filling AI Gaps article.flex-1 > a.relative > span.h-full > img.h-auto
/production/articles/16974/c8bb2d75-1f6d-4456-8857-9e0ff5...

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 7 user timings
●Avoid long main-thread tasks 20 long tasks found
●Network Requests
●Network Round Trip Times 200 ms
●Server Backend Latencies 220 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 240 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
72

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
header#global-nav > div.flex > div.flex > button.border-none header#global-nav > div.flex > div.flex > button.border-none

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
body.namespaced-ti > div#ti-wrapper > img body.namespaced-ti > div#ti-wrapper > img
body.namespaced-ti > img body.namespaced-ti > img

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.mx-0 > div.w-full > article.flex-col > a.relative div.mx-0 > div.w-full > article.flex-col > a.relative
div.w-full > section > article.flex-col > a.relative div.w-full > section > article.flex-col > a.relative
div.w-full > section > article.flex-col > a.relative div.w-full > section > article.flex-col > a.relative
div.w-full > section > article.flex-col > a.relative div.w-full > section > article.flex-col > a.relative
div.w-full > section > article.flex-col > a.relative div.w-full > section > article.flex-col > a.relative
div.border-0 > div.flex > article.flex > a.relative div.border-0 > div.flex > article.flex > a.relative
div.border-0 > div.flex > article.flex > a.relative div.border-0 > div.flex > article.flex > a.relative
div.border-0 > div.flex > article.flex > a.relative div.border-0 > div.flex > article.flex > a.relative
div.w-full > section > article.flex-col > a.relative div.w-full > section > article.flex-col > a.relative
div.w-full > section > article.flex-col > a.relative div.w-full > section > article.flex-col > a.relative
div.border-0 > div.flex > article.flex > a.relative div.border-0 > div.flex > article.flex > a.relative
div.border-0 > div.flex > article.flex > a.relative div.border-0 > div.flex > article.flex > a.relative
div.w-full > section > article.flex-col > a.relative div.w-full > section > article.flex-col > a.relative
div.w-full > section > article.flex-col > a.relative div.w-full > section > article.flex-col > a.relative
div.w-full > section > article.flex-col > a.relative div.w-full > section > article.flex-col > a.relative
div.w-full > section > article.flex-col > a.relative div.w-full > section > article.flex-col > a.relative
div.w-full > section > article.flex-col > a.relative div.w-full > section > article.flex-col > a.relative
div.w-full > section > article.flex-col > a.relative div.w-full > section > article.flex-col > a.relative
div.w-full > section > article.flex-col > a.relative div.w-full > section > article.flex-col > a.relative
div.w-full > section > article.flex-col > a.relative div.w-full > section > article.flex-col > a.relative
div.w-full > section > article.flex-col > a.relative div.w-full > section > article.flex-col > a.relative

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
Subscribe div.flex > div.relative > div.group > a.z-1
Deep Research section > div.mx-0 > article.flex-1 > a.mb-4
Artificial Intelligence div.w-full > article.flex-col > div.ml-0 > a.mb-4
Exclusive div.w-full > article.flex-col > div.ml-0 > a.mb-4
The Information Finance section > article.flex-col > div.ml-0 > a.mb-4
AI Agenda section > article.flex-col > div.ml-0 > a.mb-4
The Briefing section > article.flex-col > div.ml-0 > a.mb-4
Dealmaker section > article.flex-col > div.ml-0 > a.mb-4
Every Wednesday (subscribers only) div.flex > article.flex > div.mt-8 > a.mb-4
Four times/week (subscribers only) div.flex > article.flex > div.mt-8 > a.mb-4
Five times/week div.flex > article.flex > div.mt-8 > a.mb-4
View all div.w-full > section > div.border-0 > a.inline-block
Exclusive section > article.flex-col > div.ml-0 > a.mb-4
Applied AI section > article.flex-col > div.ml-0 > a.mb-4
Exclusive div.flex > article.flex > div.mt-8 > a.mb-4
The Big Read div.flex > article.flex > div.mt-8 > a.mb-4
View all div.w-full > section > div.border-0 > a.inline-block
AI Agenda section > article.flex-col > div.ml-0 > a.mb-4
True Value section > article.flex-col > div.ml-0 > a.mb-4
Exclusive section > article.flex-col > div.ml-0 > a.mb-4
The Briefing section > article.flex-col > div.ml-0 > a.mb-4
Directory section > div.border-0 > p.mx-auto > a.text-primary-magenta
Exclusive section > article.flex-col > div.ml-0 > a.mb-4
AI Infrastructure section > article.flex-col > div.ml-0 > a.mb-4
AI Agenda section > article.flex-col > div.ml-0 > a.mb-4
Exclusive section > article.flex-col > div.ml-0 > a.mb-4
Read more div.w-full > section > div.px-16 > a.bg-transparent
Get started div > form.w-full > div.email-form > button.w-full
Already a subscriber? div > form.w-full > div.mt-8 > span.opacity-50
Sign in div > form.w-full > div.mt-8 > a.font-suisse-screen
Terms div.flex > div.mt-48 > div.mb-8 > a.mt-8
Privacy div.flex > div.mt-48 > div.mb-8 > a.mt-8
Help & Support div.flex > div.mt-48 > div.mb-8 > a.mt-8
© 2013–2026 The Information. All Rights Reserved. div.m-auto > div.flex > div.mt-48 > div.mt-8
Cookie Settings / Do Not Sell or Share My Info div.flex > div.mt-48 > div > a#ot-sdk-btn

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
Directory section > div.border-0 > p.mx-auto > a.text-primary-magenta

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
X Facebook LinkedIn Threads Instagram header#global-nav > div.fixed > nav.h-screen > ul.mt-40

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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.

○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
●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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Form elements have associated labels
●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
●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
●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 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.
○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.
73

Best Practices

Trust and Safety

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
Unload event listeners are deprecated and will be removed.
www.theinformation.com/ line 5, col 8711
AttributionReporting

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
www.theinformation.com/ line 5, col 8711
[object Object]
www.theinformation.com/ line 5, col 8711
[SERVER] [ReactOnRails Renderer]: setTimeout is not defined for VM. No-op for server rendering.
www.theinformation.com/ line 5, col 8711
[SERVER] at setTimeout (evalmachine.<anonymous>:3:19) at Query.scheduleGc (webpack://reader/./node_modules/react-query/es/core/queryClient.js_+_3_modules?:64:24) at new Query (webpack://reader/./node_modules/react-query/es/core/queryClient.js_+_3_modules?:40:10) at QueryCache.build (webpack://reader/./node_modules/react-query/es/core/queryClient.js_+_3_modules?:552:15) at QueryObserver.updateQuery (webpack://reader/./node_modules/react-query/es/react/index.js_+_14_modules?:749:45) at QueryObserver.setOptions (webpack://reader/./node_modules/react-query/es/react/index.js_+_14_modules?:370:10) at new QueryObserver (webpack://reader/./node_modules/react-query/es/react/index.js_+_14_modules?:312:11) at eval (webpack://reader/./node_modules/react-query/es/react/index.js_+_14_modules?:924:12) at vb (webpack://reader/./node_modules/react-dom/cjs/react-dom-server-legacy.node.production.min.js?:56:265)
Failed to load resource: net::ERR_INVALID_URL
Failed to load resource: net::ERR_INVALID_URL
Failed to load resource: the server responded with a status of 401 ()
Failed to load resource: the server responded with a status of 401 ()
Failed to load resource: the server responded with a status of 401 ()
Failed to load resource: the server responded with a status of 401 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Uncaught Error: Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #425; visit https://reactjs.org/docs/error-decoder.html?invariant=425 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation 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
83

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 destinationLink Text
www.theinformation.com/?page=2&view=recentRead more

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
body.namespaced-ti > div#ti-wrapper > img body.namespaced-ti > div#ti-wrapper > img
body.namespaced-ti > img body.namespaced-ti > img

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
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback