Skip to content
https://mprnews.org

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.

44

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.

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.

URLEst Savings
/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu...80 ms
/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu...50 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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:41.358 source:map[type:text value:[unattributed]]]]

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
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
value: No additional origins are good candidates for preconnecting

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
/signals/config/260753451121808?v=2.9.303&r=stable&domain...1200.0 s127.0 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
hls-chunk.stream.publicradio.org/nis-hls/6Dtbs7i7Nkpp-177689779-9984.aac300.0 s59.1 KiB
hls-chunk.stream.publicradio.org/nis-hls/9kQynPxHtSVp-177689780-9984.aac300.0 s59.0 KiB
/dcdn/settings.js?a=940895&settings_type=4&ts=1776873524&...1800.0 s14.3 KiB
static.chartbeat.com/js/chartbeat.js7200.0 s15.9 KiB
scripts.clarity.ms/0.8.59/clarity.js86400.0 s26.2 KiB
origin.acuityplatform.com/event/v2/pixel.js0.0 ms2.7 KiB
/web-push-notification.js0.0 ms2.3 KiB
rules.quantcount.com/rules-p-5WnH1bmrzt_S7.js3600.0 s1.1 KiB
/eHTcSTeHuP62xSyaTIYO4izNysr-TFqnBDKIIEWGBar7iGHlgSMIZ7qr...86400.0 s1.2 KiB
/v.gif?cd=0&a=940895&d=mprnews.org&u=D9A3C141A290E6A92402...43200.0 s147 B
/tr/?id=260753451121808&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms16 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.

URLResource SizeEst Savings
Report critical of Minneapolis police handling of Lussier death and Moturi shoo… a > div.home-featured-visual > picture > img
/7bb57f0f4741bb615ce6698f2474262b59d0c1e1/widescreen/82e8...21.9 KiB12.4 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: 1.1 s
URLTime Spent
mprnews.org/1.1 s
www.mprnews.org/0.0 ms

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 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 25.4 KiB
URLTransfer SizeEst Savings
.fc-consent-root .fc-dialog-container.fc-fullscreen { height: 100% !important; … } …16.3 KiB14.0 KiB
www.mprnews.org/_next/static/css/bf42abeacb47846f.css13.9 KiB11.4 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: 500 ms 746.8 KiB
URLTransfer SizeEst Savings
/pagead/managed/js/gpt/m202604160201/pubads_impl.js187.7 KiB129.7 KiB
www.mprnews.org/_next/static/chunks/5639-462b93cc1e76b5e6.js162.0 KiB126.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-W6G65JFZ&gtm=4e64k1133.7 KiB63.4 KiB
www.googletagmanager.com/gtag/js?id=G-XGZ99F1SED&cx=c&gtm=4e64k1146.5 KiB61.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-KTT2Z2158.2 KiB61.1 KiB
www.googletagmanager.com/gtag/js?id=G-64TYYEK8MV&cx=c&gtm=4e64k1177.7 KiB57.3 KiB
www.mprnews.org/_next/static/chunks/pages/_app-424c3fa0596f68e4.js112.4 KiB57.1 KiB
/signals/config/260753451121808?v=2.9.303&r=stable&domain...126.9 KiB36.0 KiB
fundingchoicesmessages.google.com/i/22546217694?ers=368.7 KiB35.5 KiB
www.mprnews.org/_next/static/chunks/framework-484ee0e91759f406.js65.0 KiB33.6 KiB
www.mprnews.org/_next/static/chunks/pages/weather-a790ce62c2eb08de.js34.1 KiB33.0 KiB
connect.facebook.net/en_US/fbevents.js96.5 KiB32.5 KiB
www.mprnews.org/_next/static/chunks/1725-775f5637bb4610af.js24.1 KiB20.1 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.

URLTotal CPU TimeScript EvaluationScript Parse
www.mprnews.org/2.6 s516 ms0.5 ms
Unattributable940 ms89 ms0.0 ms
www.mprnews.org/_next/static/chunks/framework-484ee0e91759f406.js670 ms515 ms17 ms
www.mprnews.org/_next/static/chunks/main-b6a758ad60535fcc.js551 ms373 ms138 ms
www.googletagmanager.com/gtag/js?id=G-64TYYEK8MV&cx=c&gtm=4e64k1433 ms366 ms63 ms
www.googletagmanager.com/gtm.js?id=GTM-KTT2Z2393 ms339 ms46 ms
/f/AGSKWxU2BwBFrvqYdBqABfxSQn4-oWK1BA18tBqRTw4oZXCF1Gt7dx...364 ms163 ms39 ms
/signals/config/260753451121808?v=2.9.303&r=stable&domain...301 ms266 ms35 ms
www.googletagmanager.com/gtag/js?id=G-XGZ99F1SED&cx=c&gtm=4e64k1288 ms194 ms32 ms
fundingchoicesmessages.google.com/i/22546217694?ers=3283 ms258 ms20 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js272 ms224 ms45 ms
scripts.clarity.ms/0.8.59/clarity.js222 ms187 ms7.7 ms
www.googletagmanager.com/gtm.js?id=GTM-W6G65JFZ&gtm=4e64k1184 ms148 ms34 ms
www.mprnews.org/_next/static/chunks/pages/_app-424c3fa0596f68e4.js132 ms95 ms30 ms
connect.facebook.net/en_US/fbevents.js120 ms91 ms28 ms
static.chartbeat.com/js/chartbeat.js83 ms77 ms3.7 ms
securepubads.g.doubleclick.net/tag/js/gpt.js74 ms64 ms9.1 ms
www.mprnews.org/_next/static/chunks/pages/index-20534c3fc997b967.js69 ms61 ms7.9 ms
a.omappapi.com/app/js/api.min.js58 ms49 ms4.7 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 Evaluation4.9 s
Other1.9 s
Style & Layout852 ms
Script Parsing & Compilation651 ms
Rendering484 ms
Garbage Collection150 ms
Parse HTML & CSS111 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
Pages with WebSocket cannot enter back/forward cache.Pending browser support

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.

URLTransfer Size
/pagead/managed/js/gpt/m202604160201/pubads_impl.js187.7 KiB
www.googletagmanager.com/gtag/js?id=G-64TYYEK8MV&cx=c&gtm=4e64k1177.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-KTT2Z2158.6 KiB
www.googletagmanager.com/gtag/js?id=G-XGZ99F1SED&cx=c&gtm=4e64k1146.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-W6G65JFZ&gtm=4e64k1133.8 KiB
/signals/config/260753451121808?v=2.9.303&r=stable&domain...127.0 KiB
www.mprnews.org/_next/data/vhQJdTABBPK6O2IJdsCiR/weather.json117.9 KiB
www.mprnews.org/_next/static/chunks/pages/_app-424c3fa0596f68e4.js112.9 KiB
connect.facebook.net/en_US/fbevents.js96.6 KiB
/cdn/edrv/va_gq-d728c477f0f4777c8be7f1f120d0c70b.br.js96.5 KiB

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

●Layout shift culprits
●Optimize DOM size
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 14 user timings
●Avoid long main-thread tasks 20 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 180 ms
●Server Backend Latencies 420 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 20 ms
●Avoid large layout shifts 4 layout shifts found
○INP breakdown
○Avoid non-composited animations
96

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.

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 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
●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 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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○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.
73

Best Practices

Trust and Safety

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source
www.gstatic.com/firebasejs/8.6.0/firebase-messaging.js

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
AttributionReporting
connect.facebook.net/en_US/fbevents.js line 279, col 769
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

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
/web-push-notification.js
Failed to get FCM Registration token! FirebaseError: Messaging: The notification permission was not granted and blocked instead. (messaging/permission-blocked). at rt.<anonymous> (https://www.gstatic.com/firebasejs/8.6.0/firebase-messaging.js:1:35846) at https://www.gstatic.com/firebasejs/8.6.0/firebase-messaging.js:1:2003 at Object.next (https://www.gstatic.com/firebasejs/8.6.0/firebase-messaging.js:1:2108) at r (https://www.gstatic.com/firebasejs/8.6.0/firebase-messaging.js:1:855)
/v1alpha/projects/-/apps/1:87843365608:web:86c4f523699328...
Failed to load resource: the server responded with a status of 404 ()
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation 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
●Page has valid source maps
○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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Sign in div.Auth_modalContainerRight__CB2pQ > div.Auth_supplementalTextBottom__76DiP > div > a
Forgot Password? div.Auth_modalContainerRight__CB2pQ > form > div.Auth_supplementalText__LpEPr > a
Sign up div.Auth_modalContainerRight__CB2pQ > div.Auth_supplementalTextBottom__76DiP > div > a

To appear in search results, crawlers need access to your app.

○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
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback