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
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	170.2 KiB
/public/latest-news/l994ar/picture315486350/alternates/LA...	4059.0 s	144.1 KiB
/public/latest-news/nkbc1d/picture315496377/alternates/LA...	40052.0 s	157.8 KiB
c.amazon-adsystem.com/aax2/apstag.js	3600.0 s	90.8 KiB
www.charlotteobserver.com/zloysinb-o/escenic.prod1776882958719.js	900.0 s	77.9 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	67.0 KiB
/public/latest-news/k3l43v/picture257458758/alternates/LA...	14067.0 s	95.0 KiB
/public/latest-news/4nqzp4/picture306510711/alternates/LA...	38537.0 s	110.6 KiB
/awMxVZLpNW6K6EG6WC5S8oR_a68/gpt_and_prebid/config.js	900.0 s	65.8 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	3600.0 s	73.1 KiB
www.charlotteobserver.com/zloysinb-o/engagement.prod1776882958719.js	900.0 s	65.4 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=5315	1800.0 s	60.1 KiB
/public/latest-news/9xrr3p/picture315435886/alternates/LA...	43200.0 s	90.6 KiB
/public/incoming/4uxj8/picture314609962/alternates/LANDSC...	24180.0 s	71.8 KiB
cdn.amplitude.com/engagement-browser/prod/split/index.js	60.0 s	40.1 KiB
/public/sports/u12jh1/picture315258868/alternates/LANDSCA...	17834.0 s	58.5 KiB
www.charlotteobserver.com/zloysinb-o/charlotteobservercore.js	212.0 s	36.9 KiB
js.matheranalytics.com/static/ltm/ma12095/all/33/ml.br.js	3600.0 s	42.4 KiB
ml314.com/tag.aspx?223	3600.0 s	38.7 KiB
01.cdn.mediatradecraft.com/charlotteobserver/main/main.js?template=homepage	7800.0 s	40.6 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	25.8 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	21.6 KiB
www.charlotteobserver.com/zloysinb-o/danelei.prod1776882958719.js	900.0 s	23.3 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	20.9 KiB
/wps/build/webpack/videoLoader.bundle-eb4e8a1ef2763bfaff1...	123035.0 s	56.9 KiB
sdk.mrf.io/statics/47bd3e88b6bda15c34ce.js	3600.0 s	24.4 KiB
b-code.liadm.com/a-01du	86400.0 s	46.3 KiB
d-code.liadm.com/did-008d.min.js	86400.0 s	45.9 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	16.5 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	13.5 KiB
www.charlotteobserver.com/zloysinb-o/netdale.prod1776882958719.js	900.0 s	14.9 KiB
cmp.osano.com/16A0CuTCdGtXx3A1C/ec63760f-40b0-4c2c-b76a-e71dda7f148e/osano-ui.js	86400.0 s	29.1 KiB
/wps/build/webpack/css/mi-styles.c759c39774ad6d697a46.css	267482.0 s	44.7 KiB
cdn.pdst.fm/ping.min.js	3600.0 s	10.3 KiB
www.charlotteobserver.com/zloysinb-o/quarantine.prod1776882958719.js	900.0 s	9.1 KiB
tags.srv.stackadapt.com/events.js	5.0 s	7.7 KiB
www.charlotteobserver.com/akam/13/6017e660	21600.0 s	9.6 KiB
www.charlotteobserver.com/zloysinb-o/hanealneh.prod1776882958719.js	604727.0 s	55.6 KiB
www.charlotteobserver.com/zloysinb-o/dahdeyah.prod1776882958719.js	604738.0 s	49.4 KiB
s.go-mpulse.net/boomerang/BEXGD-N4AW4-E276A-B6EUP-YDH2Y	604800.0 s	45.9 KiB
www.charlotteobserver.com/wps/source/images/mcm-logo.png	49185.0 s	9.0 KiB
www.charlotteobserver.com/zloysinb-o/performance.prod1776882958719.js	900.0 s	4.8 KiB
www.charlotteobserver.com/zloysinb-o/domkut.prod1776882958719.js	900.0 s	4.6 KiB
www.charlotteobserver.com/zloysinb-o/woldoni.prod1776882958719.js	900.0 s	4.2 KiB
sdk.mrf.io/statics/compass-multimedia-sdk.js?version=2262	3600.0 s	4.3 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	3.4 KiB
www.charlotteobserver.com/zloysinb-o/suggestedContent.prod1776882958719.js	900.0 s	3.7 KiB
www.charlotteobserver.com/zloysinb-o/cnx.prod1776882958719.js	900.0 s	3.3 KiB
www.charlotteobserver.com/static/hi/experiences/index.js	300.0 s	3.0 KiB
sb.scorecardresearch.com/beacon.js	86400.0 s	6.7 KiB
www.charlotteobserver.com/zloysinb-o/acuity.prod1776882958719.js	900.0 s	2.8 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	2.4 KiB
www.charlotteobserver.com/static/hi/experiences/lib/Zones.js	300.0 s	2.4 KiB
01.cdn.mediatradecraft.com/charlotteobserver/main/main.css	7800.0 s	2.8 KiB
www.charlotteobserver.com/zloysinb-o/modals.prod1776882958719.js	900.0 s	2.3 KiB
www.charlotteobserver.com/zloysinb-o/marfeel.prod1776882958719.js	900.0 s	2.2 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	1.9 KiB
/static/hi/2024/mcc-big-4-editorial/reality-check/images/...	236.0 s	1.9 KiB
www.charlotteobserver.com/static/hi/experiences/lib/Elements.js	300.0 s	1.9 KiB
/1563813/trc/3/json?tim=1776892280696&data=%7B%22id%22%3A...	0.0 ms	1.8 KiB
rules.quantcount.com/rules-p-6QaZPu1ys1b0b.js	3600.0 s	2.0 KiB
cdn.keywee.co/dist/analytics-1.5.12.min.js	259200.0 s	7.8 KiB
www.charlotteobserver.com/zloysinb-o/iterate.prod1776882958719.js	900.0 s	1.4 KiB
www.charlotteobserver.com/zloysinb-o/zones.prod1776882958719.js	604800.0 s	10.1 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	1.0 KiB
config.aps.amazon-adsystem.com/configs/10f892c4-b76d-4f37-b1fd-0ae5d74780b5	3600.0 s	1.2 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	1012 B
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	970 B
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	948 B
www.charlotteobserver.com/zloysinb-o/pageLoad.prod1776882958719.js	900.0 s	1.0 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	913 B
pagead2.googlesyndication.com/pagead/js/r20260421/r20110914/abg_lite_fy2021.js	1209600.0 s	8.4 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	60.0 s	672 B
/wps/build/images/newLogos/charlotteobserver/logo-mobile.svg	177966.0 s	2.1 KiB
sli.charlotteobserver.com/baker?dtstmp=1776892281016	0.0 ms	546 B
sli.charlotteobserver.com/baker?dtstmp=1776892280769	0.0 ms	546 B
www.charlotteobserver.com/wps/build/images/newLogos/charlotteobserver/logo.svg	377218.0 s	2.4 KiB
/usersync/liveintent/?cb=%2F%2Fi.liadm.com%2Fs%2F35004%3F...	0.0 ms	405 B
www.charlotteobserver.com/zloysinb-o/naeliya.prod1776882958719.js	604777.0 s	2.6 KiB
/i?e=pv&page=ml&hier=_HomePage&ptype=homepage&pubname=The...	0.0 ms	245 B
/i?e=ue&ue_na=Ad%20Impression&ue_px=eyJlYWlkIjoiNzI4NTI2M...	0.0 ms	245 B
/i?e=ue&ue_na=Ad%20Impression&ue_px=eyJlYWlkIjoiNzI4NTI2M...	0.0 ms	245 B
/i?e=ue&ue_na=Ad%20Impression&ue_px=eyJlYWlkIjoiNzI4NTI2M...	0.0 ms	245 B
cdn.keywee.co/config/3005.js	86400.0 s	576 B
/zloysinb-o/pdp.gif?i=eyJpZCI6Im1pX3RpX2NsdF8wNTI0YzY1Ni0...	86400.0 s	548 B
/track/cmf/generic?ttd_pid=liveintent&ttd_tpi=1&gdpr=0&us...	0.0 ms	149 B
/pagead/js/r20260421/r20110914/client/window_focus_fy2021.js	1209600.0 s	1.2 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	3600.0 s	0 B
/pagead/managed/js/activeview/current/ufs_web_display.js	3600.0 s	0 B
pagead2.googlesyndication.com/pagead/js/r20260421/r20110914/abg_lite_fy2021.js	1209600.0 s	0 B
pagead2.googlesyndication.com/pagead/js/r20260421/r20110914/abg_lite_fy2021.js	1209600.0 s	0 B
rules.quantcount.com/rules-p-6QaZPu1ys1b0b.js	3600.0 s	0 B
/pagead/js/r20260421/r20110914/client/window_focus_fy2021.js	1209600.0 s	0 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.

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: Charlotte gets an ‘F’ from the American Lung Association, Asheville an ‘A’

path: 1,HTML,1,BODY,5,SECTION,0,DIV,0,ARTICLE,1,FIGURE,0,A,0,IMG

selector: article#primary-content > figure > a.image-link-macro > img

snippet: <img src="https://www.charlotteobserver.com/public/latest-news/nkbc1d/picture3154963…" width="350" height="200" alt="Charlotte gets an ‘F’ from the American Lung Association, Asheville an ‘A’" loading="lazy" data-tb-thumbnail="">

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

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
cmp.osano.com/16A0CuTCdGtXx3A1C/ec63760f-40b0-4c2c-b76a-e71dda7f148e/osano.js	100.7 KiB
/css2?family=Noto+Sans:ital,wght@0,100..900;1,100..900&fa...	1.8 KiB	831 ms
www.charlotteobserver.com/zloysinb-o/charlotteobservercore.js	36.9 KiB	451 ms
/wps/build/webpack/css/mi-styles.c759c39774ad6d697a46.css	44.7 KiB	602 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
body.jar > div#google_image_div > a#aw0 > img.img_ad `body.jar > div#google_image_div > a#aw0 > img.img_ad`	tpc.googlesyndication.com/simgad/4539759241886776722	95.7 KiB	83.5 KiB
div.celtra-screen-holder > div#celtra-object-422 > div#celtra-object-1724 > div `div.celtra-screen-holder > div#celtra-object-422 > div#celtra-object-1724 > div`	/api/blobs/a22c8a185f234a25dc801baed7f988ac3db87e6debb5fe...	117.2 KiB	45.5 KiB
body.jar > div#google_image_div > a#aw0 > img.img_ad `body.jar > div#google_image_div > a#aw0 > img.img_ad`	tpc.googlesyndication.com/simgad/17200712027215199302	22.2 KiB	19.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

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.0 s

URL	Time Spent
charlotteobserver.com/	1.0 s
www.charlotteobserver.com/	0.0 ms

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: 380 ms 41.6 KiB

URL	Transfer Size	Est Savings
/wps/build/webpack/css/mi-styles.c759c39774ad6d697a46.css	44.1 KiB	41.6 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: 150 ms 1.1 MiB

URL	Transfer Size	Est Savings
/pagead/managed/js/gpt/m202604210101/pubads_impl.js?cb=31...	187.5 KiB	96.8 KiB
/p/324082750/player.js?cid=1ffe5d7e-eb53-11e9-b4d2-069484...	138.6 KiB	94.8 KiB
www.googletagmanager.com/gtag/js?id=AW-11133638285	140.4 KiB	83.1 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	169.7 KiB	74.5 KiB
cdn.confiant-integrations.net/gptprebidnative/202604221919/wrap.js	139.9 KiB	73.5 KiB
www.googletagmanager.com/gtag/js?id=G-EDBMXX4HYF&cx=c&gtm=4e64k0	163.8 KiB	66.2 KiB
www.googletagmanager.com/gtag/js?id=UA-48278383-1	124.8 KiB	62.7 KiB
www.charlotteobserver.com/zloysinb-o/engagement.prod1776882958719.js	64.9 KiB	61.2 KiB
www.googletagmanager.com/gtag/js?id=AW-848620132	144.4 KiB	60.7 KiB
micro.rubiconproject.com/prebid/dynamic/21666.js	166.6 KiB	56.6 KiB
www.charlotteobserver.com/zloysinb-o/dahdeyah.prod1776882958719.js	48.9 KiB	48.6 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	66.4 KiB	46.6 KiB
/wps/build/webpack/videoLoader.bundle-eb4e8a1ef2763bfaff1...	56.3 KiB	44.7 KiB
www.charlotteobserver.com/zloysinb-o/escenic.prod1776882958719.js	77.4 KiB	42.9 KiB
c.amazon-adsystem.com/aax2/apstag.js	90.4 KiB	37.6 KiB
www.charlotteobserver.com/zloysinb-o/hanealneh.prod1776882958719.js	54.9 KiB	35.8 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	73.1 KiB	31.7 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	73.1 KiB	31.5 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	73.1 KiB	31.0 KiB
sdk.mrf.io/statics/47bd3e88b6bda15c34ce.js	23.9 KiB	22.2 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=5315	59.8 KiB	21.9 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
Unattributable	2.4 s	937 ms	0.0 ms
cmp.osano.com/16A0CuTCdGtXx3A1C/ec63760f-40b0-4c2c-b76a-e71dda7f148e/osano.js	2.3 s	2.0 s	46 ms
www.charlotteobserver.com/	1.8 s	409 ms	8.3 ms
/pagead/managed/js/gpt/m202604210101/pubads_impl.js?cb=31...	1.5 s	1.4 s	50 ms
01.cdn.mediatradecraft.com/charlotteobserver/main/main.js?template=homepage	1.4 s	1.3 s	22 ms
cdn.confiant-integrations.net/gptprebidnative/202604221919/wrap.js	979 ms	718 ms	177 ms
/pagead/managed/js/activeview/current/ufs_web_display.js	652 ms	384 ms	18 ms
www.charlotteobserver.com/zloysinb-o/charlotteobservercore.js	446 ms	408 ms	8.7 ms
micro.rubiconproject.com/prebid/dynamic/21666.js	428 ms	346 ms	42 ms
sdk.mrf.io/statics/marfeel-sdk.js?id=5315	372 ms	355 ms	1.0 ms
cdn.amplitude.com/engagement-browser/prod/split/index.js	341 ms	319 ms	0.5 ms
/ads/8bfe4705/web.js?&accountId=590e1384&clickUrl=https%3...	316 ms	210 ms	90 ms
www.charlotteobserver.com/zloysinb-o/hanealneh.prod1776882958719.js	295 ms	260 ms	19 ms
www.charlotteobserver.com/akam/13/6017e660	233 ms	186 ms	6.4 ms
www.googletagmanager.com/gtag/js?id=AW-848620132	232 ms	196 ms	35 ms
www.charlotteobserver.com/zloysinb-o/quarantine.prod1776882958719.js	214 ms	200 ms	4.9 ms
c.amazon-adsystem.com/aax2/apstag.js	207 ms	174 ms	27 ms
www.googletagmanager.com/gtag/js?id=G-EDBMXX4HYF&cx=c&gtm=4e64k0	196 ms	147 ms	48 ms
www.charlotteobserver.com/zloysinb-o/escenic.prod1776882958719.js	174 ms	143 ms	27 ms
/p/324082750/player.js?cid=1ffe5d7e-eb53-11e9-b4d2-069484...	166 ms	109 ms	56 ms
www.googletagmanager.com/gtag/js?id=UA-48278383-1	163 ms	126 ms	35 ms
www.googletagmanager.com/gtag/js?id=AW-11133638285	157 ms	106 ms	50 ms
d-code.liadm.com/did-008d.min.js	155 ms	128 ms	17 ms
b-code.liadm.com/a-01du	132 ms	102 ms	15 ms
js.matheranalytics.com/s/ma12095/74930331/all/ml.js?cb=1714	110 ms	98 ms	9.6 ms
www.charlotteobserver.com/zloysinb-o/domkut.prod1776882958719.js	103 ms	91 ms	1.1 ms
www.charlotteobserver.com/zloysinb-o/zones.prod1776882958719.js	100 ms	89 ms	3.0 ms
cdn.taboola.com/libtrc/unip/1563813/tfa.js	98 ms	79 ms	7.0 ms
libraryfacts.com/build/pcppurm/l393_t.v2.js	86 ms	66 ms	12 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	83 ms	71 ms	11 ms
/wps/build/webpack/videoLoader.bundle-eb4e8a1ef2763bfaff1...	73 ms	48 ms	24 ms
www.charlotteobserver.com/zloysinb-o/netdale.prod1776882958719.js	70 ms	64 ms	4.9 ms
cmp.osano.com/16A0CuTCdGtXx3A1C/ec63760f-40b0-4c2c-b76a-e71dda7f148e/osano-ui.js	65 ms	36 ms	16 ms
secure.quantserve.com/quant.js	53 ms	42 ms	9.5 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	12.0 s
Other	2.5 s
Script Parsing & Compilation	1.1 s
Style & Layout	646 ms
Garbage Collection	376 ms
Rendering	181 ms
Parse HTML & CSS	159 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 the main frame.	Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
The page has an unload handler in a sub frame.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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
/pagead/managed/js/gpt/m202604210101/pubads_impl.js?cb=31...	187.6 KiB
/engagement-browser/prod/split/075f435c31b52ace48d7d8152b...	170.2 KiB
micro.rubiconproject.com/prebid/dynamic/21666.js	166.8 KiB
www.googletagmanager.com/gtag/js?id=G-EDBMXX4HYF&cx=c&gtm=4e64k0	163.9 KiB
/public/latest-news/nkbc1d/picture315496377/alternates/LA...	157.8 KiB
www.googletagmanager.com/gtag/js?id=AW-848620132	144.5 KiB
/public/latest-news/l994ar/picture315486350/alternates/LA...	144.1 KiB
www.googletagmanager.com/gtag/js?id=AW-11133638285	140.7 KiB
cdn.confiant-integrations.net/gptprebidnative/202604221919/wrap.js	140.3 KiB
/p/324082750/player.js?cid=1ffe5d7e-eb53-11e9-b4d2-069484...	139.2 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.

	URL
body.wps-body-main > footer.footer > div.item > img.footer-logo `body.wps-body-main > footer.footer > div.item > img.footer-logo`	www.charlotteobserver.com/wps/source/images/mcm-logo.png

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 CSS

●Minify JavaScript

●User Timing marks and measures 233 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 4 animated elements found

●Network Requests

●Network Round Trip Times 110 ms

●Server Backend Latencies 470 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 240 ms

●Avoid large layout shifts 4 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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home Customer Service Stay Connected Read today's Edition Top Workplaces Charlo… `div.newMastheadContainer > header#mastheadVueContainer > div.paper > nav#main-nav`
Reality Check `div.paper > nav#main-nav > a.row > div#menu-20`
Charlotte Five `div.paper > nav#main-nav > a.row > div#menu-21`
Rock Hill Herald `div.paper > nav#main-nav > a.row > div#menu-22`
Detour Travel `div.paper > nav#main-nav > a.row > div#menu-23`
Charlotte’s Best `div.paper > nav#main-nav > a.row > div#menu-24`

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
div.flag > div.flag-row > div.flag-menu > button#menu-toggle `div.flag > div.flag-row > div.flag-menu > button#menu-toggle`

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.wps-body-main > footer.footer > div.item > img.footer-logo `body.wps-body-main > footer.footer > div.item > img.footer-logo`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#google_ads_iframe_/7675/CLT.site_charlotteobserver/_HomePage/web-top-banner_0__container__ > div.celtra-ad-inline-host > div.notranslate > iframe `div#google_ads_iframe_/7675/CLT.site_charlotteobserver/_HomePage/web-top-banner_0__container__ > div.celtra-ad-inline-host > div.notranslate > iframe`

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.

○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]`s are contained by their required parent element

●`[role]` values are valid

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

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

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

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

●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

●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

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

●All heading elements contain content.

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

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

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

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
Topics	micro.rubiconproject.com/prebid/dynamic/21666.js line 25, col 84959
Unload event listeners are deprecated and will be removed.	cmp.osano.com/16A0CuTCdGtXx3A1C/ec63760f-40b0-4c2c-b76a-e71dda7f148e/osano.js
AttributionReporting	cdn.taboola.com/libtrc/unip/1563813/tfa.js line 2, col 82365

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
/profiles?device_id=0524c656-4f23-45e7-b007-749f04a4e740&...	`Failed to load resource: the server responded with a status of 404 ()`
api.rlcdn.com/api/identity/envelope?pid=1405	`Failed to load resource: the server responded with a status of 451 ()`

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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.wps-body-main > footer.footer > div.item > img.footer-logo `body.wps-body-main > footer.footer > div.item > img.footer-logo`

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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`