Lighthouse Mobile
· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.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.
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
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.
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.
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.
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.
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
Performance issues directly impact user engagement and conversion rates.
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.
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
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Houston received the lowest 'eco score' that measures sustainability of the hos… a > div.rel > picture > img.x100 | /statics/assetsab/9659/abimage/8d94caef-8f30-4614-a55d-b8... | 18.0 KiB | 17.0 KiB |
One Japanese Astros fan hopes a dose of superstition can cure the club's injury… a > div.rel > picture > img.x100 | s.hdnux.com/photos/01/66/02/23/30942443/3/ratio1x1_480.webp | 43.8 KiB | 6.3 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.
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| chron.com/ | 1.1 s |
| www.chron.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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| www.chron.com/ | 1.5 s |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.chron.com/_next/static/css/068ea46319039004.css | 23.7 KiB | 21.2 KiB |
| 22.1 KiB | 18.8 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.
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.
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 28.6 s |
| Other | 3.2 s |
| Script Parsing & Compilation | 1.4 s |
| Garbage Collection | 637 ms |
| Style & Layout | 606 ms |
| Parse HTML & CSS | 423 ms |
| Rendering | 243 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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| u566.chron.com/plugin/library/c639374ef06961b30d02cf0d29623622 | 203.5 KiB | 46.0 KiB |
| u566.chron.com/plugin/plugin/db46d7aeff1612c61d56388bc25f43ed | 88.0 KiB | 20.3 KiB |
| launchpad.privacymanager.io/latest/launchpad.bundle.js | 40.2 KiB | 12.7 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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
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.
Performance issues directly impact user engagement and conversion rates.
General
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | www.chron.com/ line 6, col 8711 |
| SharedStorage | u566.chron.com/script.js line 821, col 205 |
| AttributionReporting | connect.facebook.net/en_US/fbevents.js line 279, col 769 |
| Topics |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
www.chron.com/ line 6, col 8711 | [GPT] Exception in googletag.cmd function: TypeError: e.permutive.ready is not a function.
https://goo.gle/gpt-message#30 |
www.chron.com/ line 6, col 8711 | %c PerimeterXLoadError color: #f54f4f; font-weight:bold; [object Object] |
Access to fetch at 'https://fid.agkn.com/f?apiKey=2831332485' from origin 'https://www.chron.com' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. | |
Access to XMLHttpRequest at 'https://0272ac85-5199-4024-a555-397c3d825d95.prmutv.co/v2.0/pxid?k=' from origin 'https://www.chron.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. | |
Access to XMLHttpRequest at 'https://api.permutive.com/standard-audiences/v1/affinity?url=https%3A%2F%2Fwww.chron.com&k=' from origin 'https://www.chron.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. | |
Access to XMLHttpRequest at 'https://api.permutive.com/v2.0/geoip?include=geo&include=isp&include=ip_hash&k=' from origin 'https://www.chron.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. | |
Access to XMLHttpRequest at 'https://api.permutive.com/v2.0/internal/metrics?k=' from origin 'https://www.chron.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. | |
Access to XMLHttpRequest at 'https://api.permutive.com/v2.0/tpd/usage?k=' from origin 'https://www.chron.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. | |
Access to XMLHttpRequest at 'https://api.permutive.com/v2.0/watson?k=' from origin 'https://www.chron.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. | |
Access to XMLHttpRequest at 'https://ib.adnxs.com/getuidj?gdpr=1&gdpr_consent=' from origin 'https://www.chron.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. | |
www.chron.com/ line 6, col 8711 | Error fetching TransUnionID: TypeError: Failed to fetch
at e.<computed> (https://www.chron.com/:7:46307)
at loadInitialize (https://www.chron.com/_next/static/chunks/pages/_app-d6aa58070bba276d.js:1:158248)
at https://www.chron.com/_next/static/chunks/pages/_app-d6aa58070bba276d.js:1:89097
at Array.map (<anonymous>)
at https://www.chron.com/_next/static/chunks/pages/_app-d6aa58070bba276d.js:1:89051
at https://www.chron.com/_next/static/chunks/pages/_app-d6aa58070bba276d.js:1:89184
at oP (https://www.chron.com/_next/static/chunks/framework-f80cd7bf984bdace.js:1:81836)
at o6 (https://www.chron.com/_next/static/chunks/framework-f80cd7bf984bdace.js:1:97214)
at o4 (https://www.chron.com/_next/static/chunks/framework-f80cd7bf984bdace.js:1:97098)
at o6 (https://www.chron.com/_next/static/chunks/framework-f80cd7bf984bdace.js:1:98309) |
www.chron.com/ line 6, col 8711 | Exception in queued GPT command TypeError: e.permutive.ready is not a function
at m (https://0272ac85-5199-4024-a555-397c3d825d95.edge.permutive.app/6af07a2d-d0d3-4dfd-961a-bab066126220-web.js:1:162520)
at https://0272ac85-5199-4024-a555-397c3d825d95.edge.permutive.app/6af07a2d-d0d3-4dfd-961a-bab066126220-web.js:1:162368
at Yv.push (https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604160201/pubads_impl.js?cb=31097945:19:443590)
at Wv.push (https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604160201/pubads_impl.js?cb=31097945:19:96787)
at Module.p (https://0272ac85-5199-4024-a555-397c3d825d95.edge.permutive.app/6af07a2d-d0d3-4dfd-961a-bab066126220-web.js:1:162358)
at https://0272ac85-5199-4024-a555-397c3d825d95.edge.permutive.app/6af07a2d-d0d3-4dfd-961a-bab066126220-web.js:1:150898
at async Promise.all (index 0) |
www.chron.com/ line 6, col 8711 | Failed to initialize Ketch: TypeError: window.permutive.consent is not a function
at https://cdn.ketchjs.com/ketchtag/stable/v2.12/ketch-sdk.js:2:1360067
at https://cdn.ketchjs.com/ketchtag/stable/v2.12/ketch-sdk.js:2:1360225
at s.trigger (https://cdn.ketchjs.com/ketchtag/stable/v2.12/ketch-sdk.js:2:1324493)
at s.addListener (https://cdn.ketchjs.com/ketchtag/stable/v2.12/ketch-sdk.js:2:1323993)
at s.on (https://cdn.ketchjs.com/ketchtag/stable/v2.12/ketch-sdk.js:2:1324031)
at C.on (https://cdn.ketchjs.com/ketchtag/stable/v2.12/ketch-sdk.js:2:1451157)
at https://cdn.ketchjs.com/ketchtag/stable/v2.12/ketch-sdk.js:2:1359649
at Generator.next (<anonymous>)
at s (https://cdn.ketchjs.com/ketchtag/stable/v2.12/ketch-sdk.js:2:1560886) |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_NAME_NOT_RESOLVED | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 451 () | |
Uncaught (in promise) TypeError: r.addon is not a function | |
Uncaught (in promise) TypeError: t.wnd.permutive.ready is not a function | |
cdn.ketchjs.com/ketchtag/stable/v2.12/ketch-sdk.js line 1, col 1360066 | Uncaught (in promise) TypeError: window.permutive.consent is not a function |
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
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| www.chron.com/best/about | Learn More |
Format your HTML in a way that enables crawlers to better understand your app’s content.