Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
tagan.adlightning.com/rawstory/op.js	1800.0 s	14.8 KiB
static.chartbeat.com/js/chartbeat.js	7200.0 s	15.9 KiB
static.chartbeat.com/js/chartbeat_mab.js	7200.0 s	10.1 KiB
sb.scorecardresearch.com/internal-cs/default/beacon-and.js	86400.0 s	7.8 KiB
/6a56b78e-3a46-44df-a7c1-3b9d4052c2fb/launchpad-liveramp.js	0.0 ms	1.7 KiB

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.

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:22006.644 label:Time to first byte subpart:timeToFirstByte] map[duration:520.815 label:Resource load delay subpart:resourceLoadDelay] map[duration:25.06 label:Resource load duration subpart:resourceLoadDuration] map[duration:103.36 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-DIV

nodeLabel: Republican denies 'unsubstantiated' abuse allegations amid nasty divorce

path: 2,HTML,1,BODY,4,DIV,0,DIV,71,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,ARTICLE,0,DIV,0,DIV,0,DIV,0,A,0,DIV

selector: div.rm-col-center > div.widget__head > a.rm-stats-tracked > div.widget__image

snippet: <div class="widget__image crop-3x2" role="img" aria-label="Republican denies 'unsubstantiated' abuse allegations amid nasty divorce" data-runner-img-hd="https://www.rawstory.com/media-library/u-s-congressman-max-miller-speaking…" data-runner-img-md="https://www.rawstory.com/media-library/u-s-congressman-max-miller-speaking…" data-runner-img-sd="https://www.rawstory.com/media-library/u-s-congressman-max-miller-speaking…" data-runner-style="padding-bottom: 66.66666666666666%;" style="padding-bottom: 66.6667%; background-image: url("https://www.rawstory.com/…");" …>

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-DIV

nodeLabel: Republican denies 'unsubstantiated' abuse allegations amid nasty divorce

path: 2,HTML,1,BODY,4,DIV,0,DIV,71,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,ARTICLE,0,DIV,0,DIV,0,DIV,0,A,0,DIV

selector: div.rm-col-center > div.widget__head > a.rm-stats-tracked > div.widget__image

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

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
tagan.adlightning.com/rawstory/op.js	14.8 KiB	918 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
RawStory `div#sTop_Bar_0_0_8_0_0_0_0_20_0_0 > div#sTop_Bar_0_0_8_0_0_0_0_20_0_0_2 > a.display-block > img.image-element__img`	assets.rbl.ms/33391448/origin.png	30.5 KiB	26.5 KiB
div#sside-bar-homepage_0_0_10_0_0_0_5 > div#sside-bar-homepage_0_0_10_0_0_0_5_0 > a#sside-bar-homepage_0_0_10_0_0_0_5_0_0 > img.image-element__img `div#sside-bar-homepage_0_0_10_0_0_0_5 > div#sside-bar-homepage_0_0_10_0_0_0_5_0 > a#sside-bar-homepage_0_0_10_0_0_0_5_0_0 > img.image-element__img`	/media-library/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpb...	14.5 KiB	13.9 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 858 ms

URL	Time Spent
rawstory.com/	858 ms
www.rawstory.com/	0.0 ms

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: 21.8 s

URL	Time Spent
www.rawstory.com/	21.9 s

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 17.7 KiB

URL	Transfer Size	Est Savings
launchpad.privacymanager.io/latest/launchpad.bundle.js	40.3 KiB	12.7 KiB
inline: // Wait for TCF consent before …	8.1 KiB	2.7 KiB
inline: window.REBELMOUSE_TASKS_QUEUE.…	4.8 KiB	2.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 300 ms 47.7 KiB

URL	Transfer Size	Est Savings
/ats-modules/7aa6d770-a3f3-49fb-acde-4783d74486db/ats.js	41.1 KiB	24.3 KiB
tagan.adlightning.com/rawstory/b-682065e-3b86f1db.js	31.3 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 minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.6 s
Other	756 ms
Style & Layout	271 ms
Parse HTML & CSS	141 ms
Script Parsing & Compilation	112 ms
Rendering	46 ms
Garbage Collection	39 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
The page has an unload handler in a sub frame.	Actionable
The page did not finish loading before navigating away.	Not actionable

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 12.3 KiB

URL	Transfer Size	Est Savings
@layer tokens,themes,utilities,elements;.rm-embed-container{position:relative;} …	17.6 KiB	12.3 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/media-library/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpb...	2.3 MiB
www.rawstory.com/	95.8 KiB
tagan.adlightning.com/rawstory/bl-0d6ee0c-0e633374.js	59.7 KiB
launchpad.privacymanager.io/latest/launchpad.bundle.js	40.7 KiB
tagan.adlightning.com/rawstory/b-682065e-3b86f1db.js	31.8 KiB
fonts.gstatic.com/s/oswald/v36/TK3iWkUHHAIjg752GT8G.woff2	31.0 KiB
assets.rbl.ms/33391448/origin.png	30.9 KiB
/media-library/u-s-president-donald-trump-speaks-with-rep...	24.7 KiB
/media-library/u-s-congressman-max-miller-speaking-with-a...	22.7 KiB
assets.rbl.ms/24986931/origin.png	22.7 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.


RawStory `div#mySidenav > div.search-logo > a.search-logo > img`

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●JavaScript execution time 1.0 s

●Avoid long main-thread tasks 10 long tasks found

●Network Requests

●Network Round Trip Times 70 ms

●Server Backend Latencies 70 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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.

Best practices

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.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

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

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●Links have a discernible name

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

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

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
www.rawstory.com/ line 367, col 55	`SyntaxError: Unexpected token ')'`
www.rawstory.com/ line 4147, col 75	`TypeError: Cannot read properties of null (reading 'insertAdjacentHTML') at https://www.rawstory.com/:4148:76`
www.rawstory.com/ line 4532, col 75	`TypeError: Cannot read properties of null (reading 'insertAdjacentHTML') at https://www.rawstory.com/:4533:76`

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

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

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

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`