Skip to content
https://forbes.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.

36

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
cdn.ketchjs.com/ketchtag/stable/v2.12/ketch-sdk.js1200.0 s257.2 KiB
js.datadome.co/tags.js3600.0 s39.4 KiB
/specials-images/imageserve/69a745fe59f179efca2abcea/0x0....86400.0 s23.4 KiB
/specials-images/imageserve/69dc6098e89b3b9e5fcef75e/0x0....86400.0 s17.4 KiB
/specials-images/imageserve/699607a995c6ee056f34a273/0x0....86400.0 s15.7 KiB
/specials-images/imageserve/69d71386fa3a0a4fff474789/0x0....86400.0 s14.7 KiB
/specials-images/imageserve/698bd4a8a1f16a65d7d5138c/0x0....86400.0 s14.0 KiB
/specials-images/imageserve/69dfb1a075b9dba04e574a4c/0x0....86400.0 s10.1 KiB
/specials-images/imageserve/69e010c11ab9bc714d2e2d1c/0x0....86400.0 s10.0 KiB
/specials-images/imageserve/69dfa84e9751715040aa0963/0x0....86400.0 s9.7 KiB
/specials-images/imageserve/69c1936b9cb752432044a594/0x0....86400.0 s6.8 KiB
/specials-images/imageserve/69de9d2c2c72e6d68c9bbf03/0x0....86400.0 s6.0 KiB
cdn.ketchjs.com/plugins/v1/tcf/stub.js1200.0 s1.1 KiB
/specials-images/imageserve/5e8b62cfc095010007bffea0/0x0....86400.0 s1.3 KiB
global.ketchcdn.com/web/v2/config/forbes/website_smart_tag/boot.js604800.0 s5.0 KiB
/specials-images/imageserve/62d700cd6094d2c180f269b9/0x0....86400.0 s1.2 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:32.453 source:map[column:207127 line:1 type:source-location url:https://i.forbesimg.com/simple-site/_next/static/chunks/framework-f30cbadcebab7629.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:13.893 source:map[column:85073 line:0 type:source-location url:https://i.forbesimg.com/simple-site/_next/static/chunks/3297-bf079039fbe7ee2e.js urlProvider:network]] map[reflowTime:18.56 source:map[column:467 line:71 type:source-location url:https://i.forbesimg.com/simple-site/_next/static/chunks/9946-46abaea941fcbcfe.js urlProvider:network]]]

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:361.469 label:Time to first byte subpart:timeToFirstByte] map[duration:17.23 label:Resource load delay subpart:resourceLoadDelay] map[duration:29.74 label:Resource load duration subpart:resourceLoadDuration] map[duration:2124.066 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: Shoemaker Allbirds Suddenly Says It’s An AI Company—And Stock Jumps 800%
path: 1,HTML,1,BODY,1,DIV,1,DIV,0,DIV,1,DIV,3,DIV,0,DIV,1,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,A,0,IMG
selector: div.oN01vaYs > div.m62t0vmy > a.qGitkxSR > img.aFPbmUqY
snippet: <img loading="eager" class="aFPbmUqY" src="https://imageio.forbes.com/specials-images/imageserve/69dfb1a075b9dba04e57…" alt="Shoemaker Allbirds Suddenly Says It’s An AI Company—And Stock Jumps 800%" data-testid="article-image" fetchpriority="high">

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.

URLTransfer SizeDuration
cdn.ketchjs.com/plugins/v1/tcf/stub.js1.1 KiB754 ms

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.

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.

URLEst Savings
i.forbesimg.com/assets/fonts/highlander/highlander-bold.woff25.0 ms

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
From Makers Of Weight-Loss Pills To Anti-Wrinkle Shots, Meet South Korea’s Lab-… div.oN01vaYs > div.m62t0vmy > a.qGitkxSR > img.aFPbmUqY
/specials-images/imageserve/69dc6098e89b3b9e5fcef75e/0x0....16.7 KiB8.4 KiB
Unwind And Behold div.OsZHSqaf > div.Qa0cWwjz > a > img.jCXrjekI
/specials-images/imageserve/69a745fe59f179efca2abcea/0x0....22.7 KiB8.1 KiB

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

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: 752 ms
URLTime Spent
forbes.com/752 ms
www.forbes.com/0.0 ms

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 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.8 s 279.9 KiB
URLTransfer SizeEst Savings
cdn.ketchjs.com/ketchtag/stable/v2.12/ketch-sdk.js257.0 KiB110.4 KiB
i.forbesimg.com/simple-site/dist/js/nextJS-1963499c3b82ccfdd62e.js97.0 KiB64.3 KiB
i.forbesimg.com/simple-site/_next/static/chunks/6cdf2dfb-feb8d9c97c521f8c.js49.2 KiB42.4 KiB
i.forbesimg.com/simple-site/_next/static/chunks/framework-f30cbadcebab7629.js74.0 KiB38.3 KiB
i.forbesimg.com/simple-site/_next/static/chunks/3297-bf079039fbe7ee2e.js65.8 KiB24.4 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
www.forbes.com/15.4 s27 ms2.6 ms
i.forbesimg.com/simple-site/_next/static/chunks/3297-bf079039fbe7ee2e.js10.5 s1.4 s13 ms
Unattributable1.6 s150 ms0.0 ms
i.forbesimg.com/simple-site/_next/static/chunks/framework-f30cbadcebab7629.js1.2 s659 ms16 ms
js.datadome.co/tags.js756 ms713 ms8.7 ms
cdn.ketchjs.com/ketchtag/stable/v2.12/ketch-sdk.js470 ms342 ms124 ms
i.forbesimg.com/simple-site/dist/js/nextJS-1963499c3b82ccfdd62e.js165 ms138 ms23 ms
/simple-site/_next/static/chunks/pages/homepage-cd26c3085...104 ms101 ms2.2 ms
i.forbesimg.com/simple-site/_next/static/chunks/main-a6004c5457d0f87b.js51 ms41 ms8.8 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
Style & Layout10.4 s
Other8.2 s
Rendering7.6 s
Script Evaluation3.6 s
Garbage Collection252 ms
Script Parsing & Compilation243 ms
Parse HTML & CSS89 ms

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: 0.0 ms 19.2 KiB
URLTransfer SizeEst Savings
22.1 KiB19.2 KiB

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

●Layout shift culprits
●Optimize DOM size
●LCP request discovery
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,522 KiB
●User Timing marks and measures 5 user timings
●Avoid long main-thread tasks 15 long tasks found
●Avoid non-composited animations 3 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 110 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 340 ms
○INP breakdown
○Avoid large layout shifts
87

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.jwg6t > div.oVlcb > div._1ZEg_ > button.Kw_Z2 div.jwg6t > div.oVlcb > div._1ZEg_ > button.Kw_Z2
div.jwg6t > div.oVlcb > div._1ZEg_ > button.Kw_Z2 div.jwg6t > div.oVlcb > div._1ZEg_ > button.Kw_Z2

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Shoemaker Allbirds Suddenly Says It’s An AI Company—And Stock Jumps 800% div.m62t0vmy > div.oIAs-U61 > div.uUkCnU2P > h3
Berkshire Hathaway div._9-I7-GeA > div.EwA-8rSS > a.YiD-O5P- > h4.fy-R13n6
Unscramble The Anagram To Reveal The Phrase. div.t88Q2 > div.km6IHox8 > div.fyCO-ZAO > h4._4xN2GEvG
Guess The Category div.t88Q2 > div.qqiUF-0E > div._6J8LylxM > h4.lxOc5nJf
Crown Each Region div.t88Q2 > div.qqiUF-0E > div._6J8LylxM > h4.lxOc5nJf
Unlock A Trivia Ladder div.t88Q2 > div.qqiUF-0E > div._6J8LylxM > h4.lxOc5nJf

These are opportunities to improve keyboard navigation in your application.

Contrast

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
Learn More. div._9N3rK > div.NwLQu > div._2N3up > a._fjVO

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Leadership footer.McL2WvD5 > div.WWE9FB01 > div.kQelIt33 > a.jxJ5WfZR
Money footer.McL2WvD5 > div.WWE9FB01 > div.kQelIt33 > a.jxJ5WfZR
Business footer.McL2WvD5 > div.WWE9FB01 > div.kQelIt33 > a.jxJ5WfZR
Vetted footer.McL2WvD5 > div.WWE9FB01 > div.kQelIt33 > a.jxJ5WfZR
Real Estate footer.McL2WvD5 > div.WWE9FB01 > div.kQelIt33 > a.jxJ5WfZR
Lists footer.McL2WvD5 > div.WWE9FB01 > div.kQelIt33 > a.jxJ5WfZR

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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.
○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.
○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.
96

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
/simple-site/_next/static/chunks/pages/homepage-cd26c3085...
error while fetching trending articles SyntaxError: Unexpected token '<', "<html lang"... is not valid JSON
www.forbes.com/blaize/profile
Failed to load resource: the server responded with a status of 401 ()
www.forbes.com/blaize/account
Failed to load resource: the server responded with a status of 401 ()
/simple-data/trending-picks?microsec=1776293940000&isXLRe...
Failed to load resource: the server responded with a status of 403 ()
www.forbes.com/genai-flowapi/videos?start=0&limit=500
Failed to load resource: the server responded with a status of 403 ()
i.forbesimg.com/simple-site/dist/js/nextJS-1963499c3b82ccfdd62e.js line 1, col 200188
ServiceWorker registration failed: SecurityError: Failed to register a ServiceWorker for scope ('https://www.forbes.com/') with script ('https://www.forbes.com/service-worker.js'): The script resource is behind a redirect, which is disallowed.
The script resource is behind a redirect, which is disallowed.
i.forbesimg.com/simple-site/_next/static/chunks/9006-413a79a03178c12c.js
YouTube Shorts data fetch error: Error: Error: 403 at s (https://i.forbesimg.com/simple-site/_next/static/chunks/9006-413a79a03178c12c.js:1:36049) at async Promise.all (index 0) at async Object.<anonymous> (https://i.forbesimg.com/simple-site/_next/static/chunks/pages/homepage-cd26c30859d12f8e.js:1:20169)
●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 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
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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Fashion ul.collapsed > li.QpfB0oZe > div.suOjX7vq > a
Electronics ul.collapsed > li.QpfB0oZe > div.suOjX7vq > a
Sportswear & Gear ul.collapsed > li.QpfB0oZe > div.suOjX7vq > a
Mattress & Sleep ul.collapsed > li.QpfB0oZe > div.suOjX7vq > a
Travel ul.collapsed > li.QpfB0oZe > div.suOjX7vq > a
Home & Garden ul.collapsed > li.QpfB0oZe > div.suOjX7vq > a
Forbes Magazine ul.collapsed > li.QpfB0oZe > div.suOjX7vq > a

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
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback