Skip to content
https://cybernews.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

55

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:46.451 source:map[type:text value:[unattributed]]] map[reflowTime:7.247 source:map[column:8404 line:1 type:source-location url:https://cybernews.com/js//data/builds/adtech-projects/cybernews/cmsbase-6c62435a69dc911f32c7.js urlProvider:network]] map[reflowTime:0.763 source:map[column:2581 line:4 type:source-location url:https://cybernews.com/js//data/builds/adtech-projects/cybernews/cmsbase-6c62435a69dc911f32c7.js urlProvider:network]] map[reflowTime:14.111 source:map[column:21572 line:0 type:source-location url:https://cdn-cookieyes.com/client_data/4cd5bb6c9ab3d688a1a45a20/banner.js urlProvider:network]] map[reflowTime:0.756 source:map[column:22454 line:0 type:source-location url:https://cdn-cookieyes.com/client_data/4cd5bb6c9ab3d688a1a45a20/banner.js urlProvider:network]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: Anthropic Mythos Preview
path: 1,HTML,1,BODY,8,MAIN,0,SECTION,0,DIV,0,DIV,0,DIV,2,FIGURE,0,A,0,IMG
selector: div.cells__item > figure.thumbnail > a > img.image
snippet: <img class="image image_wide image_lazy lazyloaded" width="750" height="375" alt="Anthropic Mythos Preview" src="https://media.cybernews.com/images/featured/2026/04/mythospreview.jpg" data-src="https://media.cybernews.com/images/featured/2026/04/mythospreview.jpg" pinger-seen="true">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Anthropic Mythos Preview div.cells__item > figure.thumbnail > a > img.image
media.cybernews.com/images/featured/2026/04/mythospreview.jpg45.4 KiB33.7 KiB
body > aside.ad-campaign__aside > div.ad-campaign > a.ad-campaign__container body > aside.ad-campaign__aside > div.ad-campaign > a.ad-campaign__container
cybernews.com/images/campaign/nordlayer-top.png194.5 KiB24.1 KiB
A hand holding a remote control directed to a smart TV, map of Kentucky behind … div.space > a.cells > div.cells__item > img.image
/images/thumbnail_small/2026/04/kentucky-smart-tv-screens...6.0 KiB4.9 KiB
coinmarketcap div.space > a.cells > div.cells__item > img.image
media.cybernews.com/images/thumbnail_small/2026/04/coinmarketcap.jpg5.7 KiB4.6 KiB

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

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation2.0 s
Style & Layout897 ms
Other863 ms
Script Parsing & Compilation272 ms
Rendering197 ms
Garbage Collection114 ms
Parse HTML & CSS93 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
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 2,609 KiB
●User Timing marks and measures 5 user timings
●Avoid long main-thread tasks 18 long tasks 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 100 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 60 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○Avoid non-composited animations
93

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

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
body > aside.ad-campaign__aside > div.ad-campaign > a.ad-campaign__container body > aside.ad-campaign__aside > div.ad-campaign > a.ad-campaign__container

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.

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
SECURITY div.cells__item > figure.thumbnail > figcaption.thumbnail__caption > a.category-tag
PRIVACY article.cells__item > figure.thumbnail > figcaption.thumbnail__caption > a.category-tag
SECURITY article.cells__item > figure.thumbnail > figcaption.thumbnail__caption > a.category-tag
AI NEWS article.cells__item > figure.thumbnail > figcaption.thumbnail__caption > a.category-tag
HOSTING HUB article.cells__item > figure.thumbnail > figcaption.thumbnail__caption > a.category-tag
HOSTING HUB article.cells__item > figure.thumbnail > figcaption.thumbnail__caption > a.category-tag
HOSTING HUB article.cells__item > figure.thumbnail > figcaption.thumbnail__caption > a.category-tag
TECH div.sticky-sidebar > figure.thumbnail > figcaption.thumbnail__caption > a.category-tag
About Us nav.footer__bottom-line-nav > ul.footer__bottom-line-nav-list > li.footer__bottom-line-nav-item > a.footer__bottom-line-nav-link
Contact nav.footer__bottom-line-nav > ul.footer__bottom-line-nav-list > li.footer__bottom-line-nav-item > a.footer__bottom-line-nav-link
Send Us a Tip nav.footer__bottom-line-nav > ul.footer__bottom-line-nav-list > li.footer__bottom-line-nav-item > a.footer__bottom-line-nav-link
Privacy Policy nav.footer__bottom-line-nav > ul.footer__bottom-line-nav-list > li.footer__bottom-line-nav-item > a.footer__bottom-line-nav-link
Terms & Conditions nav.footer__bottom-line-nav > ul.footer__bottom-line-nav-list > li.footer__bottom-line-nav-item > a.footer__bottom-line-nav-link
Advertising and Sponsorship Policy nav.footer__bottom-line-nav > ul.footer__bottom-line-nav-list > li.footer__bottom-line-nav-item > a.footer__bottom-line-nav-link
Vulnerability Disclosure nav.footer__bottom-line-nav > ul.footer__bottom-line-nav-list > li.footer__bottom-line-nav-item > a.footer__bottom-line-nav-link
Cookie Preferences nav.footer__bottom-line-nav > ul.footer__bottom-line-nav-list > li.footer__bottom-line-nav-item > a.content__tag_unstyled

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●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
●All heading elements contain content.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
77

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
A bad HTTP response code (403) was received when fetching the script.
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 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Manifest fetch from https://cybernews.com/manifest.json failed, code 403
Manifest fetch from https://cybernews.com/manifest.json failed, code 403
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
100

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.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback