United Stated · New York Completed: Apr 22, 2026 20:02 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 72 / 100
Based on 8 categories, 0 sections
Room to improve — your 28.0s load time is above Google's 2.5s 'Good' threshold.
Several missing protections leave your users and data exposed.
Mostly accessible, but some users still face barriers.
Missing signals may be hurting your search visibility.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Missing metadata means poor previews on social media and search.
Heavier than average — reducing page weight saves energy and bandwidth.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
Page weighs 13.9 MB (4.0 MB transferred)
Performance issues directly impact user engagement and conversion rates.
180 third-party resources (100% of weight)
Performance issues directly impact user engagement and conversion rates.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/581d14d7-eacd-4ca1-85f0-3cf25e906d97)<a href="https://beavercheck.com/results/581d14d7-eacd-4ca1-85f0-3cf25e906d97"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ftheinformation.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Ftheinformation.comThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 28.0s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. Addressing the critical issues below would have the most immediate impact on your user trust.
9 barrier(s) likely increasing bounce by ~31%.
Page takes 28.0s to load
+12% bounceUsers abandon at ~3s — you're 25.5s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 3.5s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
No Open Graph tags
+2% bounceLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
Fix: Add og:title, og:description, og:image, og:url to the page head
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
Thin content
+3% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
Content is hard to read
+2% bounceGraduate-level reading difficulty — limits the addressable audience for product or blog pages
Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$550 investment → $1.01/month returns + USD 150,000 risk avoided
$550
6h · 5 findings
$1.01 /mo
~$12 / year
USD 150,000
if kept compliant
$150 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
5.5 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$12,501 / month at risk
~$150,012 / year if left unfixed
$150,000
$1.01 /mo
12619.1 MB/mo × 0.080 USD/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 4 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
13.48 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
27.99 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
3.52 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
13.48 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
31.46 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
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.
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.
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
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est 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 KiB | 24.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.
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| theinformation.com/ | 759 ms |
| www.theinformation.com/ | 0.0 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /assets/mobile-a5707796fd5dd484efc069704d84737bb3c7783981... | 59.6 KiB | 59.1 KiB |
| ti-assets.theinformation.com/packs/css/446-3cd7427c.css | 28.7 KiB | 26.0 KiB |
| 21.8 KiB | 21.3 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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
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.
Performance issues directly impact user engagement and conversion rates.
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 7.8 s |
| Script Parsing & Compilation | 1.5 s |
| Other | 1.4 s |
| Style & Layout | 443 ms |
| Garbage Collection | 237 ms |
| Parse HTML & CSS | 179 ms |
| Rendering | 41 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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
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.
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.
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.
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.
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.
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
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.
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.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
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.
Performance issues directly impact user engagement and conversion rates.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| 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 | connect.facebook.net/en_US/fbevents.js line 279, col 769 |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
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 () | |
ti-assets.theinformation.com/packs/js/vendor-react-8519dd62207ba32d6207.js line 1, col 191974 | 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. |
ti-assets.theinformation.com/packs/js/vendor-react-8519dd62207ba32d6207.js line 1, col 113994 | 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. |
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| www.theinformation.com/?page=2&view=recent | Read 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.
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
262 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
819 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
48 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.001
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
342 ms
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
819 ms
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| /beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312... | 86400.0 s | 10.7 KiB |
| challenges.cloudflare.com/cdn-cgi/challenge-platform/h/b/cmg/1 | 0.0 ms | 208 B |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages that use WebXR are not currently eligible for back/forward cache. | Actionable |
| Only pages with a status code of 2XX can be cached. | Not actionable |
More information about the performance of your application. These numbers don't directly affect the Performance score.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| theinformation.com/ | 208 ms |
| theinformation.com/ | 0.0 ms |
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.
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () | |
Failed to load resource: the server responded with a status of 403 () |
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.
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Performance issues directly impact user engagement and conversion rates.
| Blocking Directive Source |
|---|
head > meta |
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Performance issues directly impact user engagement and conversion rates.
To appear in search results, crawlers need access to your app.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback