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

31

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
media.reviewjournal.com/media/projects/header-bidding/prebid-10.25.0.js0.0 ms323.8 KiB
engage.reviewjournal.com/prod/review-journal/t8y9347t.min.js?202632186400.0 s291.9 KiB
d3plfjw9uod7ab.cloudfront.net/3b1c0b02-a34a-4a2e-9feb-655ccef0fe86.js7200.0 s65.6 KiB
d3plfjw9uod7ab.cloudfront.net/ad/3b1c0b02-a34a-4a2e-9feb-655ccef0fe86.js7200.0 s33.5 KiB
engage.reviewjournal.com/prod/review-journal/t8y9347t.min.css?202632186400.0 s50.3 KiB
g2i.reviewjournal.com/prod/review-journal/g2i.min.js?202632186400.0 s44.1 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
cmp.osano.com/lHFYjdHC7m/0330e02a-add0-459d-b255-bf8ace1f3c7c/osano-ui.js86400.0 s31.1 KiB
fp.reviewjournal.com/prod/review-journal/fp.min.js?202632186400.0 s22.8 KiB
connext-fd-gnbrate4fjhjb3f7.z01.azurefd.net/index.js86400.0 s2.6 KiB
paywall-ad-bucket.s3.amazonaws.com/ad_300_250.jpg0.0 ms1.0 KiB
/p.css?s=1&k=msl8qnj&ht=tk&f=22660.22665.22668.22669.3664...604800.0 s172 B
d3plfjw9uod7ab.cloudfront.net/ad/3b1c0b02-a34a-4a2e-9feb-655ccef0fe86.js7200.0 s0 B
d3plfjw9uod7ab.cloudfront.net/ad/3b1c0b02-a34a-4a2e-9feb-655ccef0fe86.js7200.0 s0 B
d3plfjw9uod7ab.cloudfront.net/ad/3b1c0b02-a34a-4a2e-9feb-655ccef0fe86.js7200.0 s0 B
d3plfjw9uod7ab.cloudfront.net/ad/3b1c0b02-a34a-4a2e-9feb-655ccef0fe86.js7200.0 s0 B
d3plfjw9uod7ab.cloudfront.net/ad/3b1c0b02-a34a-4a2e-9feb-655ccef0fe86.js7200.0 s0 B
d3plfjw9uod7ab.cloudfront.net/ad/3b1c0b02-a34a-4a2e-9feb-655ccef0fe86.js7200.0 s0 B
d3plfjw9uod7ab.cloudfront.net/ad/3b1c0b02-a34a-4a2e-9feb-655ccef0fe86.js7200.0 s0 B
d3plfjw9uod7ab.cloudfront.net/ad/3b1c0b02-a34a-4a2e-9feb-655ccef0fe86.js7200.0 s0 B

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.

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
7@7 FrontPage Channel div.field-col > div.rj-fuel-77 > div.rj-fuel > img.rj-fuel-thumb
/review-journal/image/upload/f_auto,q_auto,c_scale,w_560/...906.6 KiB877.9 KiB
Las Vegas News div.rj-logo > h1.h1 > a > img.rj-lazy-load
www.reviewjournal.com/wp-content/uploads/2020/07/rj_logo_black2.png8.5 KiB5.5 KiB

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.

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.

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: 954 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: 629 ms
URLTime Spent
www.reviewjournal.com/729 ms

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 5.5 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: 450 ms 49.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

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.

URLTotal CPU TimeScript EvaluationScript Parse
cmp.osano.com/lHFYjdHC7m/0330e02a-add0-459d-b255-bf8ace1f3c7c/osano.js2.6 s2.4 s23 ms
www.reviewjournal.com/1.5 s443 ms37 ms
d3plfjw9uod7ab.cloudfront.net/3b1c0b02-a34a-4a2e-9feb-655ccef0fe86.js1.4 s1.3 s20 ms
Unattributable869 ms129 ms0.0 ms
mp.mmvideocdn.com/mini-player/prod/voltax_mp.js611 ms497 ms98 ms
engage.reviewjournal.com/prod/review-journal/t8y9347t.min.js?2026321561 ms427 ms128 ms
d3plfjw9uod7ab.cloudfront.net/ad/3b1c0b02-a34a-4a2e-9feb-655ccef0fe86.js542 ms417 ms90 ms
www.googletagmanager.com/gtag/js?id=G-R6YZBPFWW8&cx=c&gtm=4e64h1h1320 ms269 ms45 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js278 ms225 ms49 ms
www.googletagmanager.com/gtag/js?id=AW-17087148146&cx=c&gtm=4e64h1h1271 ms232 ms37 ms
media.reviewjournal.com/media/projects/header-bidding/prebid-10.25.0.js253 ms221 ms27 ms
www.reviewjournal.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1250 ms155 ms6.6 ms
fundingchoicesmessages.google.com/i/104590658?ers=3250 ms218 ms17 ms
connext-fd-gnbrate4fjhjb3f7.z01.azurefd.net/index.js206 ms194 ms2.8 ms
www.googletagmanager.com/gtm.js?id=GTM-5ZBPF7G&l=MG2DL185 ms147 ms37 ms
www.googletagmanager.com/gtm.js?id=GTM-WJQX3C160 ms118 ms41 ms
fp.reviewjournal.com/prod/review-journal/fp.min.js?2026321123 ms40 ms5.6 ms
g2i.reviewjournal.com/prod/review-journal/g2i.min.js?2026321108 ms91 ms16 ms
cmp.osano.com/lHFYjdHC7m/0330e02a-add0-459d-b255-bf8ace1f3c7c/osano-ui.js83 ms39 ms13 ms
securepubads.g.doubleclick.net/tag/js/gpt.js75 ms65 ms9.8 ms
/wp-content/plugins/rj/public/js/ad-tags_bid/ad-tags-fron...57 ms15 ms2.7 ms
/f/AGSKWxXhjp7jVURwuVaCer2hP5JHc5TbHeB9CSnFugcDDKQxaEKWWJ...56 ms23 ms33 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation7.7 s
Other943 ms
Style & Layout898 ms
Script Parsing & Compilation749 ms
Garbage Collection167 ms
Parse HTML & CSS150 ms
Rendering134 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 reasonFailure type
The page has an unload handler in the main frame.Actionable

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
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify JavaScript
●User Timing marks and measures 5 user timings
●Avoid long main-thread tasks 20 long tasks found
●Avoid non-composited animations 2 animated elements found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 90 ms
●Server Backend Latencies 310 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid large layout shifts 4 layout shifts found
○INP breakdown
○LCP request discovery
92

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > img#06db9294 body.home > img#06db9294

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
Storage Preferences div#12ed7297-2404-458a-a455-99e6d8c59b69 > div.osano-cm-dialog__content > p.osano-cm-content__drawer-links > a.osano-cm-drawer-links__link
Third Parties div#12ed7297-2404-458a-a455-99e6d8c59b69 > div.osano-cm-dialog__content > p.osano-cm-content__drawer-links > a.osano-cm-drawer-links__link

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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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
●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
●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
●ARIA IDs are unique
●Identical links have the same purpose.
○`[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
○`[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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○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
Unload event listeners are deprecated and will be removed.
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.

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.

Description
TypeError: Cannot read properties of undefined (reading 'postbox') at <anonymous>:1:72

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●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
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > img#06db9294 body.home > img#06db9294

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 have descriptive text
●Links are crawlable
●robots.txt is valid
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback