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
connect.facebook.net/en_US/fbevents.js	1200.0 s	105.0 KiB
lfx-segment.platform.linuxfoundation.org/latest/lfx-segment-analytics.min.js	0.0 ms	83.6 KiB
/signals/config/232741255631043?v=2.9.380&r=stable&domain...	1200.0 s	66.7 KiB
js.hs-analytics.net/analytics/1787255700000/8112310.js	300.0 s	45.0 KiB
js.usemessages.com/conversations-embed.js	600.0 s	28.3 KiB
js.hubspot.com/web-interactives-embed.js	600.0 s	28.2 KiB
js.hs-banner.com/v2/8112310/banner.js	300.0 s	25.9 KiB
/pagead/managed/js/adsense/m202608180101/show_ads_impl_fy...	1209600.0 s	162.0 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	20.6 KiB
snap.licdn.com/li.lms-analytics/insight.old.min.js	86400.0 s	18.5 KiB
js.hsadspixel.net/pixels.js	600.0 s	5.3 KiB
js.hs-scripts.com/8112310.js	90.0 s	1.4 KiB
/collect?v=2&fmt=js&pid=1241050&time=1787255936390&url=ht...	0.0 ms	913 B
/tr/?id=232741255631043&ev=PageView&dl=https%3A%2F%2Fwww....	0.0 ms	19 B

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

nodeLabel: div.td-module-container > div.td-module-thumb > a.td-image-wrap > span.entry-thumb

path: 4,HTML,2,BODY,6,DIV,1,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,DIV,1,DIV,1,DIV,4,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,A,0,SPAN

selector: div.td-module-container > div.td-module-thumb > a.td-image-wrap > span.entry-thumb

snippet: <span class="entry-thumb td-thumb-css " style="background-image: url("https://www.linux.com/wp-content/uploads/2024/09/Op…");">

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.

URL	Transfer Size	Duration
/wp-content/plugins/profile-builder/assets/css/style-fron...	8.9 KiB
www.linux.com/wp-content/themes/Newspaper-child/style.css?ver=12.7.7c	554 B
/css?family=Open+Sans:400,600,700\|Roboto:400,600,700&disp...	2.6 KiB	854 ms
lfx-segment.platform.linuxfoundation.org/latest/lfx-segment-analytics.min.js	83.6 KiB	2.3 s
/wp-content/plugins/td-standard-pack/Newspaper/assets/css...	92.5 KiB	1.4 s
www.linux.com/wp-content/themes/Newspaper/style.css?ver=12.7.7	33.7 KiB	602 ms
www.linux.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	35.0 KiB	151 ms
/wp-content/plugins/td-composer/td-multi-purpose/style.cs...	6.7 KiB
/wp-content/plugins/td-cloud-library/assets/css/tdb_main....	9.6 KiB
www.linux.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.5 KiB
/wp-content/plugins/td-composer/legacy/Newspaper/assets/c...	34.1 KiB	753 ms
/wp-content/plugins/profile-builder/add-ons-free/user-pro...	4.3 KiB	151 ms

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.

	URL	Resource Size	Est Savings
spot_img `div.td_block_wrap > div > a.td_spot_img_all > img`	www.linux.com/wp-content/uploads/2025/12/kceu_ad.jpg	11.4 KiB	8.7 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: 761 ms

URL	Time Spent
linux.com/	761 ms
www.linux.com/	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

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: 300 ms 38.5 KiB

URL	Transfer Size	Est Savings
/wp-content/plugins/td-standard-pack/Newspaper/assets/css...	92.5 KiB	20.1 KiB
www.linux.com/wp-content/themes/Newspaper/style.css?ver=12.7.7	33.7 KiB	9.1 KiB
/wp-content/plugins/td-composer/legacy/Newspaper/assets/c...	34.1 KiB	6.4 KiB
/wp-content/plugins/profile-builder/assets/css/style-fron...	8.9 KiB	2.8 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: 930 ms 153.6 KiB

URL	Transfer Size	Est Savings
/wp-content/plugins/td-standard-pack/Newspaper/assets/css...	92.3 KiB	91.6 KiB
/wp-content/plugins/td-composer/legacy/Newspaper/assets/c...	33.8 KiB	32.7 KiB
www.linux.com/wp-content/themes/Newspaper/style.css?ver=12.7.7	33.4 KiB	29.2 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: 4.1 s 609.5 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/adsense/m202608180101/show_ads_impl_fy...	162.0 KiB	120.2 KiB
www.googletagmanager.com/gtag/js?id=AW-1032976986&cx=c&gtm=4e68j0h1	160.2 KiB	110.7 KiB
www.googletagmanager.com/gtag/js?id=G-RJHFVBNKK7&cx=c&gtm=4e68j0h1	169.6 KiB	70.4 KiB
www.googletagmanager.com/gtag/js?id=AW-1032976986	160.2 KiB	62.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-NXGNZW	137.4 KiB	61.8 KiB
/wp-content/plugins/td-composer/legacy/Newspaper/js/tagdi...	46.8 KiB	36.2 KiB
js.driftt.com/include/1787256000000/zxhkzyedc2xb.js	62.5 KiB	34.6 KiB
connect.facebook.net/en_US/fbevents.js	104.9 KiB	34.4 KiB
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js	55.8 KiB	30.7 KiB
lfx-segment.platform.linuxfoundation.org/latest/lfx-segment-analytics.min.js	82.7 KiB	27.3 KiB
/signals/config/232741255631043?v=2.9.380&r=stable&domain...	66.6 KiB	20.8 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	675 ms	160 ms	0.0 ms
js.hs-analytics.net/analytics/1787255700000/8112310.js	600 ms	489 ms	10 ms
js.driftt.com/include/1787256000000/zxhkzyedc2xb.js	593 ms	563 ms	27 ms
www.linux.com/	419 ms	37 ms	18 ms
/signals/config/232741255631043?v=2.9.380&r=stable&domain...	288 ms	242 ms	44 ms
www.googletagmanager.com/gtag/js?id=AW-1032976986	273 ms	240 ms	32 ms
/pagead/managed/js/adsense/m202608180101/show_ads_impl_fy...	253 ms	181 ms	48 ms
connect.facebook.net/en_US/fbevents.js	252 ms	220 ms	32 ms
www.googletagmanager.com/gtag/js?id=G-RJHFVBNKK7&cx=c&gtm=4e68j0h1	249 ms	207 ms	39 ms
www.googletagmanager.com/gtm.js?id=GTM-NXGNZW	209 ms	175 ms	31 ms
www.linux.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	138 ms	103 ms	5.8 ms
js-agent.newrelic.com/nr-rum-1.320.1.min.js	134 ms	114 ms	5.9 ms
lfx-segment.platform.linuxfoundation.org/latest/lfx-segment-analytics.min.js	100 ms	81 ms	19 ms
/wp-content/plugins/td-composer/legacy/Newspaper/js/tagdi...	94 ms	42 ms	14 ms
snap.licdn.com/li.lms-analytics/insight.old.min.js	80 ms	60 ms	14 ms
js.hsadspixel.net/pixels.js	79 ms	24 ms	1.6 ms
js.usemessages.com/conversations-embed.js	68 ms	56 ms	6.1 ms
www.googletagmanager.com/gtag/js?id=AW-1032976986&cx=c&gtm=4e68j0h1	65 ms	23 ms	41 ms
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js	56 ms	45 ms	11 ms
js.hubspot.com/web-interactives-embed.js	54 ms	44 ms	6.7 ms
www.google-analytics.com/analytics.js	51 ms	42 ms	5.1 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	3.3 s
Other	585 ms
Script Parsing & Compilation	456 ms
Style & Layout	426 ms
Garbage Collection	125 ms
Parse HTML & CSS	121 ms
Rendering	30 ms

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
spot_img `div.td_block_wrap > div > a.td_spot_img_all > img`	www.linux.com/wp-content/uploads/2025/12/kceu_ad.jpg

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

●Avoids enormous network payloads Total size was 2,391 KiB

●User Timing marks and measures 4 user timings

●Avoid long main-thread tasks 20 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 210 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

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
Featured News `div.td_block_wrap > div.td-block-title-wrap > h4.td-block-title > span.td-pulldown-size`
Linux Foundation `div.td_block_wrap > div.td-block-title-wrap > h4.td-block-title > span.td-pulldown-size`
System Administration + Linux Kernel `div.td_block_wrap > div.td-block-title-wrap > h4.td-block-title > span.td-pulldown-size`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Trademark Usage `div.td-pb-row > div.td-pb-span10 > aside.footer-text-wrap > a`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Linux Foundation Announces OpenSearch Software Foundation to Foster Open Collab… `div.td_module_flex_2 > div.td-module-container > div.td-module-meta-info > h3.entry-title`

These are opportunities to improve keyboard navigation in your application.

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

○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

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

○The document does not use `<meta http-equiv="refresh">`

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

○Identical links have the same purpose.

○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
AttributionReporting	snap.licdn.com/li.lms-analytics/insight.old.min.js

●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 browser errors logged to the console

●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

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`