C — https://9to5mac.com | BeaverCheck Audit

Site Health

Score: 75 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

WordPress sites average 75

At average

Better than 50% of WordPress sites See full WordPress benchmark →

Adobe Fonts sites average 72

At average

Better than 75% of Adobe Fonts sites See full Adobe Fonts benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

1 button(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality

1 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility

1 image-only link(s) without alt text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2F9to5mac.com)](https://beavercheck.com/results/7272c3a7-6ca2-432a-b361-8515236520f9)

HTML

<a href="https://beavercheck.com/results/7272c3a7-6ca2-432a-b361-8515236520f9"><img src="https://beavercheck.com/badge?url=https%3A%2F%2F9to5mac.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2F9to5mac.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.

3 accessibility issues exclude users who rely on assistive technology.

Return on Investment

$550 investment → $3,688/month returns + USD 157,500 risk avoided

Payback period: < 1 month First-year ROI: +7947%

Investment

$550

6h · 5 findings

Monthly returns

$3,688 /mo

~$44,257 / year

Conversions recovered $3,688
Bandwidth savings $0.41

Regulatory risk avoided

USD 157,500

if kept compliant

ADA Title III USD 150,000
CCPA/CPRA USD 7,500

Payback period

0 12mo 24mo

$100 — 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.

Full methodology & sources

Estimated Remediation Cost

$550

5.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$100 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,125 / month at risk

~$157,505 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA

1 advertising/retargeting trackers detected
CCPA/CPRA: USD 2,500 – USD 7,500
5 of 6 <nav> elements are unlabeled
ADA Title III: USD 25,000 – USD 150,000
Multiple H1 headings (5 found)
ADA Title III: USD 25,000 – USD 150,000

+3 more

Bandwidth Waste

$0.41 /mo

5069.9 MB/mo × 0.080 USD/GB

Optimize transfer: save ~507 KB per page load
Saves $0.41/mo

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.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

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

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

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.

2.56 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

4.90 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

733 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.051

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

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

13.31 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
btloader.com/tag?h=9to5mac-com&upapi=true	300.0 s	29.9 KiB
cdn.onesignal.com/sdks/web/v16/OneSignalSDK.page.es6.js?v=160603	259200.0 s	42.2 KiB
onesignal.com/sdks/web/v16/OneSignalSDK.page.styles.css?v=160603	3600.0 s	7.5 KiB
/avatar/57682250b4cca117adc866947cd168039296d63a504baa888...	300.0 s	3.8 KiB
/avatar/af01c840dac8281fd5f1986a8504e54222700437fa19c3083...	300.0 s	3.6 KiB
/avatar/51c53e5c5859bfaa0037d265388173f156f15457a06350a06...	300.0 s	3.5 KiB
/avatar/bff64efa105c91e6f9c64ea73476006e59b7e460b60496788...	300.0 s	3.2 KiB
/avatar/bb78cec603180c1a17605af3930b21e40c59b276cb679e543...	300.0 s	3.1 KiB
/avatar/33905347f5390e65e6f7d6b3148b3c513dcf629e4a77f8a24...	300.0 s	2.9 KiB
/avatar/f197b1d9aee0cea92fec918d9c75e5d69c6d302fca699a00d...	300.0 s	2.8 KiB
api.onesignal.com/sync/3765d02d-bcb7-45e5-911c-d8b40e60dd5f/web?callback=__jp0	3600.0 s	2.5 KiB
/avatar/d8da06fcba2b80ec1f2d301d7376dae8e055ac48d88994a80...	300.0 s	2.0 KiB
9to5maccom.disqus.com/count.js	300.0 s	1.5 KiB
/5zJ1140IycMhvueUy25dPoqJu6-m230A8ON487evV-aEt73CBkjIEAJk...	86400.0 s	1.3 KiB
rules.quantcount.com/rules-p-18TTuBOnUhD7c.js	3600.0 s	632 B
/px/?rand=1776295414594&plid=256ef926-6084-4af8-a3d7-cfdd...	0.0 ms	229 B
cdn.onesignal.com/sdks/web/v16/OneSignalSDK.page.js	259200.0 s	901 B
sb.scorecardresearch.com/internal-c2/default/cs.js	86400.0 s	375 B
/p.css?s=1&k=rah1hlf&ht=tk&f=139.140.173.174.175.176&a=30...	604800.0 s	172 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.

URL	Est Savings
/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu...	45 ms
/af/0bd0af/00000000000000007758cf8e/31/l?primer=7cdcb44be...	30 ms
/af/6eb0e3/00000000000000007758cf8f/31/l?primer=7cdcb44be...	15 ms
/af/e37e5a/00000000000000007735e60d/31/l?primer=7cdcb44be...	5.0 ms
/af/d7ff92/00000000000000007735e609/31/l?primer=7cdcb44be...	5.0 ms
/af/5be242/00000000000000007735e603/31/l?primer=7cdcb44be...	5.0 ms

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:59.446 source:map[column:77561 line:2 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g 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:14.078 source:map[column:10165 line:0 type:source-location url:https://9to5mac.com/wp-content/mu-plugins/jetpack-15.5/_inc/build/infinite-scroll/infinity.min.js?m=1776195303g urlProvider:network]] map[reflowTime:20.042 source:map[column:78054 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:0.412 source:map[column:50872 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:0.838 source:map[column:51243 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:0.341 source:map[column:52245 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:8.481 source:map[column:62268 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:12.942 source:map[column:62477 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:16.39 source:map[column:58589 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:7.071 source:map[column:111 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:20.675 source:map[column:14029 line:0 type:source-location url:https://9to5mac.com/wp-content/plugins/crowdsignal-forms/build/poll.js?ver=47f4c5b7627e8b8b3c60 urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
iOS 26.5 public beta `article.article > figure.article__image > span.article__image-link > img.wp-post-image`	/9to5mac.com/wp-content/uploads/sites/6/2026/03/iOS-26.5-...	35.8 KiB	27.3 KiB
article.article > figure.article__image > span.article__image-link > img.wp-post-image `article.article > figure.article__image > span.article__image-link > img.wp-post-image`	/9to5mac.com/wp-content/uploads/sites/6/2026/04/fernando-...	29.8 KiB	22.8 KiB
article.article > figure.img-border > a.article__image-link > img.wp-post-image `article.article > figure.img-border > a.article__image-link > img.wp-post-image`	/9to5mac.com/wp-content/uploads/sites/6/2026/04/Google-On...	34.2 KiB	20.4 KiB
article.article > figure.img-border > a.article__image-link > img.wp-post-image `article.article > figure.img-border > a.article__image-link > img.wp-post-image`	/9to5mac.com/wp-content/uploads/sites/6/2025/02/Samsung-r...	27.6 KiB	16.4 KiB
Apple about to test iPhone 18 production ready for new split-launch plan \| Rend… `article.article > figure.article__image > span.article__image-link > img.wp-post-image`	/9to5mac.com/wp-content/uploads/sites/6/2025/11/iphone-18...	17.2 KiB	13.1 KiB
The past few days brought two encouraging signs for the new Siri \| Liquid Glass… `article.article > figure.img-border > a.article__image-link > img.wp-post-image`	/9to5mac.com/wp-content/uploads/sites/6/2025/09/siri-ios-...	20.9 KiB	12.5 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-2-IMG

nodeLabel: article.article > figure.img-border > a.article__image-link > img.wp-post-image

path: 1,HTML,1,BODY,10,MAIN,3,DIV,0,DIV,0,DIV,1,ARTICLE,0,FIGURE,0,A,0,IMG

selector: article.article > figure.img-border > a.article__image-link > img.wp-post-image

snippet: <img width="1600" height="800" src="https://i0.wp.com/9to5mac.com/wp-content/uploads/sites/6/2026/04/Google-On…" class=" wp-post-image" alt="" srcset="https://i0.wp.com/9to5mac.com/wp-content/uploads/sites/6/2026/04/Google-On…" loading="lazy" decoding="async">

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

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
use.typekit.net/rah1hlf.css?ver=a5420cfd953060a39214	1.1 KiB	753 ms
/p.css?s=1&k=rah1hlf&ht=tk&f=139.140.173.174.175.176&a=30...	172 B	753 ms
/_static/??-eJzTLy/QzcxLzilNSS3WzwKiwtLUokoopZebmaeXVayjj...	34.7 KiB	452 ms
/_static/??/wp-includes/css/dist/components/style.min.css...	17.7 KiB	151 ms
9to5mac.com/wp-content/themes/ninetofive/assets/js/adsbygoogle.js	398 B
9to5mac.com/wp-content/themes/ninetofive/dist/css/frontend.css?m=1775475071g	26.1 KiB	452 ms
/wp-content/themes/ninetofive/dist/css/critical.css?ver=a...	3.1 KiB
/wp-content/client-mu-plugins/9to5-core/dist/css/frontend...	643 B

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.

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 6.4 KiB

URL	Transfer Size	Est Savings
js.memberful.com/embed.js	26.9 KiB	6.4 KiB

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: 600 ms 50.8 KiB

URL	Transfer Size	Est Savings
9to5mac.com/wp-content/themes/ninetofive/dist/css/frontend.css?m=1775475071g	25.8 KiB	19.8 KiB
/_static/??/wp-includes/css/dist/components/style.min.css...	17.5 KiB	17.1 KiB
.fc-consent-root .fc-dialog-container.fc-fullscreen { height: 100% !important; … } …	16.2 KiB	13.9 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

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

Estimated savings: 150 ms 340.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-K5T6XC3	115.9 KiB	64.1 KiB
www.googletagmanager.com/gtag/js?id=G-J70SYZBTQ7&cx=c&gtm=4e64e1	153.7 KiB	61.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-M48W9J	141.7 KiB	61.7 KiB
9to5mac.com/wp-includes/js/dist/blocks.min.js?ver=57eca4d23daac7159d88	52.9 KiB	35.7 KiB
/f/AGSKWxWRVgQCrTV_0WPnzTWF3pp4HU_BShilvG1NAl0BI-0eVz8C-H...	68.7 KiB	33.7 KiB
9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g	61.0 KiB	32.9 KiB
cdn.onesignal.com/sdks/web/v16/OneSignalSDK.page.es6.js?v=160603	41.7 KiB	27.1 KiB
/_static/??-eJzTLy/QzcxLzilNSS3WzwKiwtLUokoopZebmaeXVayjj...	34.5 KiB	23.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.

URL	Total CPU Time	Script Evaluation	Script Parse
9to5mac.com/	1.9 s	216 ms	13 ms
Unattributable	606 ms	38 ms	0.0 ms
9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g	509 ms	204 ms	15 ms
/f/AGSKWxXg5PxvTPK-8dBE871sjCaY_GaiqZENxiyi206zm-8H0sGkQY...	270 ms	137 ms	33 ms
www.googletagmanager.com/gtag/js?id=G-J70SYZBTQ7&cx=c&gtm=4e64e1	257 ms	204 ms	51 ms
/f/AGSKWxWRVgQCrTV_0WPnzTWF3pp4HU_BShilvG1NAl0BI-0eVz8C-H...	254 ms	233 ms	16 ms
www.googletagmanager.com/gtm.js?id=GTM-M48W9J	224 ms	182 ms	38 ms
cdn.parsely.com/keys/9to5mac.com/p.js?ver=3.23.1	170 ms	138 ms	22 ms
/wp-content/plugins/crowdsignal-forms/build/poll.js?ver=4...	155 ms	69 ms	3.0 ms
cdn.onesignal.com/sdks/web/v16/OneSignalSDK.page.es6.js?v=160603	146 ms	106 ms	10 ms
www.googletagmanager.com/gtm.js?id=GTM-K5T6XC3	121 ms	90 ms	30 ms
9to5mac-com.videoplayerhub.com/gallery.js?ver=6.9.4	83 ms	74 ms	6.7 ms
/wp-content/mu-plugins/jetpack-15.5/_inc/build/infinite-s...	71 ms	10 ms	1.2 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.9 s
Style & Layout	1.5 s
Other	932 ms
Script Parsing & Compilation	312 ms
Rendering	274 ms
Parse HTML & CSS	205 ms
Garbage Collection	21 ms

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

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

●User Timing marks and measures 7 user timings

●Avoid long main-thread tasks 17 long tasks found

●Avoid non-composited animations 2 animated elements found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 110 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 510 ms

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Toggle search form `div.header-top > div.header-top__inner > div.header-right > button#js-search-toggle`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
body.home > div#onesignal-bell-container > div#onesignal-bell-launcher > button.onesignal-bell-launcher-button `body.home > div#onesignal-bell-container > div#onesignal-bell-launcher > button.onesignal-bell-launcher-button`

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.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.widget > div.cross-site-feed > h3.featured__blog-title > a `div.widget > div.cross-site-feed > h3.featured__blog-title > a`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.widget > div.cross-site-feed > h3.featured__blog-title > a `div.widget > div.cross-site-feed > h3.featured__blog-title > a`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.widget > div.cross-site-feed > h3.featured__blog-title > a `div.widget > div.cross-site-feed > h3.featured__blog-title > a`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.widget > div.cross-site-feed > h3.featured__blog-title > a `div.widget > div.cross-site-feed > h3.featured__blog-title > a`
div.widget > div.cross-site-feed > h3.featured__blog-title > a `div.widget > div.cross-site-feed > h3.featured__blog-title > a`

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
Learn more `div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label`
List of partners. `div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog`

These are opportunities to improve the legibility of your content.

○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 are valid and not misspelled

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

○`<frame>` or `<iframe>` elements have a title

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

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

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Specifying overflow: visible on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/shared-element-transitions/blob/main/debugging_overflow_on_images.md.	/_/mss/boq-content-ads-contributor/_/js/k=boq-content-ads... line 19, col 449

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●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

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 destination	Link Text
9to5google.com/2026/04/15/google-one-youtube-premium/#more-1048299	READ MORE

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

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.

700 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

944 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

18 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.014

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

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

2.45 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

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.

Why this matters

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.

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.

URL	Est Savings
/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu...	45 ms
/af/0bd0af/00000000000000007758cf8e/31/l?primer=7cdcb44be...	35 ms
/af/6eb0e3/00000000000000007758cf8f/31/l?primer=7cdcb44be...	10 ms
/af/d7ff92/00000000000000007735e609/31/l?primer=7cdcb44be...	5.0 ms
/af/5be242/00000000000000007735e603/31/l?primer=7cdcb44be...	5.0 ms

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:54.874 source:map[column:77561 line:2 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g 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:12.286 source:map[column:9888 line:0 type:source-location url:https://9to5mac.com/wp-content/mu-plugins/jetpack-15.5/_inc/build/infinite-scroll/infinity.min.js?m=1776195303g urlProvider:network]] map[reflowTime:0.874 source:map[column:15726 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:25.369 source:map[column:78054 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:0.42 source:map[column:50872 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:0.709 source:map[column:51243 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:0.294 source:map[column:52245 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:15.186 source:map[column:62477 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:12.896 source:map[column:58589 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:5.516 source:map[column:105786 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:0.359 source:map[column:147 line:1 type:source-location url:https://9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g urlProvider:network]] map[reflowTime:18.186 source:map[column:14029 line:0 type:source-location url:https://9to5mac.com/wp-content/plugins/crowdsignal-forms/build/poll.js?ver=47f4c5b7627e8b8b3c60 urlProvider:network]]]

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.

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

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
use.typekit.net/rah1hlf.css?ver=a5420cfd953060a39214	1.1 KiB	203 ms
/p.css?s=1&k=rah1hlf&ht=tk&f=139.140.173.174.175.176&a=30...	172 B	203 ms
/_static/??-eJzTLy/QzcxLzilNSS3WzwKiwtLUokoopZebmaeXVayjj...	34.7 KiB
9to5mac.com/wp-content/themes/ninetofive/assets/js/adsbygoogle.js	398 B
/_static/??/wp-includes/css/dist/components/style.min.css...	17.7 KiB	86 ms
/wp-content/client-mu-plugins/9to5-core/dist/css/frontend...	643 B
9to5mac.com/wp-content/themes/ninetofive/dist/css/frontend.css?m=1775475071g	26.1 KiB
/wp-content/themes/ninetofive/dist/css/critical.css?ver=a...	3.1 KiB

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
btloader.com/tag?h=9to5mac-com&upapi=true	300.0 s	29.8 KiB
cdn.onesignal.com/sdks/web/v16/OneSignalSDK.page.es6.js?v=160603	259200.0 s	42.0 KiB
onesignal.com/sdks/web/v16/OneSignalSDK.page.styles.css?v=160603	3600.0 s	7.5 KiB
/avatar/33905347f5390e65e6f7d6b3148b3c513dcf629e4a77f8a24...	300.0 s	2.9 KiB
/avatar/f197b1d9aee0cea92fec918d9c75e5d69c6d302fca699a00d...	300.0 s	2.8 KiB
api.onesignal.com/sync/3765d02d-bcb7-45e5-911c-d8b40e60dd5f/web?callback=__jp0	3600.0 s	2.4 KiB
/avatar/849428dccf7c6dfcf7f9eea24f9ddcab67f0eed8aedfb1862...	300.0 s	1.6 KiB
9to5maccom.disqus.com/count.js	300.0 s	1.5 KiB
/avatar/57682250b4cca117adc866947cd168039296d63a504baa888...	300.0 s	1.5 KiB
/avatar/51c53e5c5859bfaa0037d265388173f156f15457a06350a06...	300.0 s	1.4 KiB
/avatar/d8da06fcba2b80ec1f2d301d7376dae8e055ac48d88994a80...	300.0 s	1.4 KiB
/avatar/af01c840dac8281fd5f1986a8504e54222700437fa19c3083...	300.0 s	1.4 KiB
/avatar/bb78cec603180c1a17605af3930b21e40c59b276cb679e543...	300.0 s	1.4 KiB
/avatar/bff64efa105c91e6f9c64ea73476006e59b7e460b60496788...	300.0 s	1.4 KiB
/avatar/d785394ff4d89a4eb07e796e7fdf5cbf02e75451600b52725...	300.0 s	1.3 KiB
/5zJ1140IycMhvueUy25dPoqJu6-m230A8ON487evV-aEt73CBkjIEAJk...	86400.0 s	1.3 KiB
rules.quantcount.com/rules-p-18TTuBOnUhD7c.js	3600.0 s	632 B
/px/?rand=1776295437178&plid=46a466ec-94ed-43bd-bb96-9533...	0.0 ms	229 B
cdn.onesignal.com/sdks/web/v16/OneSignalSDK.page.js	259200.0 s	903 B
sb.scorecardresearch.com/internal-c2/default/cs.js	86400.0 s	375 B
/p.css?s=1&k=rah1hlf&ht=tk&f=139.140.173.174.175.176&a=30...	604800.0 s	172 B

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
iOS 26.5 public beta `article.article > figure.article__image > span.article__image-link > img.wp-post-image`	/9to5mac.com/wp-content/uploads/sites/6/2026/03/iOS-26.5-...	61.0 KiB	60.1 KiB
article.article > figure.img-border > a.article__image-link > img.wp-post-image `article.article > figure.img-border > a.article__image-link > img.wp-post-image`	/9to5mac.com/wp-content/uploads/sites/6/2026/04/Google-On...	56.6 KiB	53.9 KiB
article.article > figure.article__image > span.article__image-link > img.wp-post-image `article.article > figure.article__image > span.article__image-link > img.wp-post-image`	/9to5mac.com/wp-content/uploads/sites/6/2026/04/fernando-...	49.1 KiB	48.4 KiB
article.article > figure.img-border > a.article__image-link > img.wp-post-image `article.article > figure.img-border > a.article__image-link > img.wp-post-image`	/9to5mac.com/wp-content/uploads/sites/6/2025/02/Samsung-r...	49.4 KiB	38.2 KiB
article.article > figure.img-border > a.article__image-link > img.wp-post-image `article.article > figure.img-border > a.article__image-link > img.wp-post-image`	/9to5mac.com/wp-content/uploads/sites/6/2026/03/ios-26-4-...	42.1 KiB	32.6 KiB
Apple about to test iPhone 18 production ready for new split-launch plan \| Rend… `article.article > figure.article__image > span.article__image-link > img.wp-post-image`	/9to5mac.com/wp-content/uploads/sites/6/2025/11/iphone-18...	31.0 KiB	30.5 KiB
The past few days brought two encouraging signs for the new Siri \| Liquid Glass… `article.article > figure.img-border > a.article__image-link > img.wp-post-image`	/9to5mac.com/wp-content/uploads/sites/6/2025/09/siri-ios-...	38.5 KiB	29.8 KiB
Apple to finally let iPhone apps and games offer promo codes for in-app purchas… `article.article > figure.img-border > a.article__image-link > img.wp-post-image`	/9to5mac.com/wp-content/uploads/sites/6/2025/03/Apple-los...	20.3 KiB	15.7 KiB
A collage of books `article.article > figure.article__image > span.article__image-link > img`	/9to5toys.com/wp-content/uploads/sites/5/2026/04/Apple-Bo...	12.0 KiB	10.4 KiB
A group of treadmills with a screen `article.article > figure.article__image > span.article__image-link > img`	/connectthewatts.com/wp-content/uploads/sites/11/2025/10/...	8.3 KiB	6.5 KiB
Best 2026 Fitness Deals `article.article > figure.article__image > span.article__image-link > img`	/connectthewatts.com/wp-content/uploads/sites/11/2025/12/...	7.4 KiB	5.6 KiB
ChatPlayground AI `article.article > figure.article__image > span.article__image-link > img`	/9to5toys.com/wp-content/uploads/sites/5/2026/04/ChatPlay...	7.1 KiB	5.0 KiB
article.article > figure.article__image > span.article__image-link > img `article.article > figure.article__image > span.article__image-link > img`	/9to5toys.com/wp-content/uploads/sites/5/2025/01/Ninja-Sl...	6.1 KiB	4.8 KiB
A video game cover with a red square and a red square with a red sign with a ma… `article.article > figure.article__image > span.article__image-link > img`	/9to5toys.com/wp-content/uploads/sites/5/2026/04/StarFiel...	5.6 KiB	4.4 KiB

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

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 40 ms 6.4 KiB

URL	Transfer Size	Est Savings
js.memberful.com/embed.js	26.9 KiB	6.4 KiB

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: 80 ms 49.8 KiB

URL	Transfer Size	Est Savings
9to5mac.com/wp-content/themes/ninetofive/dist/css/frontend.css?m=1775475071g	25.8 KiB	18.8 KiB
/_static/??/wp-includes/css/dist/components/style.min.css...	17.5 KiB	17.1 KiB
.fc-consent-root .fc-dialog-container.fc-fullscreen { height: 100% !important; … } …	16.2 KiB	14.0 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 337.0 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-K5T6XC3	115.9 KiB	62.7 KiB
www.googletagmanager.com/gtag/js?id=G-J70SYZBTQ7&cx=c&gtm=4e64e1	153.7 KiB	61.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-M48W9J	141.7 KiB	60.4 KiB
9to5mac.com/wp-includes/js/dist/blocks.min.js?ver=57eca4d23daac7159d88	52.9 KiB	35.7 KiB
/f/AGSKWxWRVgQCrTV_0WPnzTWF3pp4HU_BShilvG1NAl0BI-0eVz8C-H...	68.7 KiB	33.8 KiB
9to5mac.com/wp-content/themes/ninetofive/dist/js/frontend.js?m=1770813487g	61.0 KiB	32.8 KiB
cdn.onesignal.com/sdks/web/v16/OneSignalSDK.page.es6.js?v=160603	41.5 KiB	26.9 KiB
/_static/??-eJzTLy/QzcxLzilNSS3WzwKiwtLUokoopZebmaeXVayjj...	34.5 KiB	23.4 KiB

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 709 ms

URL	Time Spent
9to5mac.com/	809 ms

●Time to Interactive 2.5 s

●Max Potential First Input Delay 70 ms

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

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

●User Timing marks and measures 7 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 1.3 s

●Avoid long main-thread tasks 2 long tasks found

●Avoid non-composited animations 2 animated elements found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 110 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

Accessibility

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Toggle search form `div.header-top > div.header-top__inner > div.header-right > button#js-search-toggle`
div.container > article.article > figure.article__image > a.article__image-link `div.container > article.article > figure.article__image > a.article__image-link`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
body.home > div#onesignal-bell-container > div#onesignal-bell-launcher > button.onesignal-bell-launcher-button `body.home > div#onesignal-bell-container > div#onesignal-bell-launcher > button.onesignal-bell-launcher-button`

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > article.article > figure.article__image > a.article__image-link `div.container > article.article > figure.article__image > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.widget > div.cross-site-feed > h3.featured__blog-title > a `div.widget > div.cross-site-feed > h3.featured__blog-title > a`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.widget > div.cross-site-feed > h3.featured__blog-title > a `div.widget > div.cross-site-feed > h3.featured__blog-title > a`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.widget > div.cross-site-feed > h3.featured__blog-title > a `div.widget > div.cross-site-feed > h3.featured__blog-title > a`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.container > article.article > figure.img-border > a.article__image-link `div.container > article.article > figure.img-border > a.article__image-link`
div.widget > div.cross-site-feed > h3.featured__blog-title > a `div.widget > div.cross-site-feed > h3.featured__blog-title > a`
div.widget > div.cross-site-feed > h3.featured__blog-title > a `div.widget > div.cross-site-feed > h3.featured__blog-title > a`

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
Justin Kahn `article.article > div.article__content > div.post-meta > span.author__link`
Justin Kahn `article.article > div.article__content > div.post-meta > span.author__link`
Justin Kahn `article.article > div.article__content > div.post-meta > span.author__link`
Donna Enzmann `article.article > div.article__content > div.post-meta > span.author__link`
Justin Kahn `article.article > div.article__content > div.post-meta > span.author__link`
Fred Lambert `article.article > div.article__content > div.post-meta > span.author__link`
Peter Johnson `article.article > div.article__content > div.post-meta > span.author__link`
Peter Johnson `article.article > div.article__content > div.post-meta > span.author__link`
Reinette LeJeune `article.article > div.article__content > div.post-meta > span.author__link`
Justin Kahn `article.article > div.article__content > div.post-meta > span.author__link`
Justin Kahn `article.article > div.article__content > div.post-meta > span.author__link`
Justin Kahn `article.article > div.article__content > div.post-meta > span.author__link`
Donna Enzmann `article.article > div.article__content > div.post-meta > span.author__link`
Justin Kahn `article.article > div.article__content > div.post-meta > span.author__link`
Learn more `div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label`
List of partners. `div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog`

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
Avatar for Justin Kahn `div.article__content > div.article__excerpt > div.post-meta > a.author__image-link`
Justin Kahn `div.article__excerpt > div.post-meta > span.author__link > a`
0 Comments `div.article__excerpt > div.post-meta > div.meta__comment-count > a.comments`
Avatar for Ben Lovejoy `div.article__content > div.article__excerpt > div.post-meta > a.author__image-link`
Ben Lovejoy `div.article__excerpt > div.post-meta > span.author__link > a`
1 Comment `div.article__excerpt > div.post-meta > div.meta__comment-count > a.comments`

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 are valid and not misspelled

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

○`<frame>` or `<iframe>` elements have a title

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

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

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Specifying overflow: visible on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/shared-element-transitions/blob/main/debugging_overflow_on_images.md.	/_/mss/boq-content-ads-contributor/_/js/k=boq-content-ads... line 19, col 449

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●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

SEO

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 destination	Link Text
9to5google.com/2026/04/15/google-one-youtube-premium/#more-1048299	READ MORE

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://9to5mac.com

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Names and labels

Contrast

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Names and labels

Contrast

Best practices

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts