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.

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

nodeLabel: Select, organize, share the best content Professionals Start your intelligence…

path: 2,HTML,1,BODY,1,DIV,1,MAIN,0,SECTION

selector: body.open_sans_af80e835-module__alJfWW__variable > div.flex > main.grow > section.text-white

snippet: <section class="text-white bg-center bg-no-repeat bg-fixed bg-cover text-center h-auto" style="background-image:url(/hp_assets/home/header.jpg)">

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

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
www.scoop.it/hp_assets/home/icon-highlight-scalable.svg	86400.0 s	7.3 KiB
www.scoop.it/hp_assets/home/icon-highlight-roi.svg	86400.0 s	4.4 KiB
www.scoop.it/hp_assets/home/icon-highlight-brain.svg	86400.0 s	3.2 KiB
www.scoop.it/hp_assets/logo-teal.svg	86400.0 s	2.9 KiB
www.scoop.it/hp_assets/home/icon-highlight-easy-to-use2.svg	86400.0 s	2.5 KiB
www.scoop.it/hp_assets/home/icon-for-public-sector-opt.svg	86400.0 s	2.1 KiB
www.scoop.it/hp_assets/home/icon-highlight-interact.svg	86400.0 s	2.0 KiB
www.scoop.it/hp_assets/home/icon-highlight-security.svg	86400.0 s	2.0 KiB
www.scoop.it/hp_assets/home/icon-highlight-governance.svg	86400.0 s	2.0 KiB
www.scoop.it/hp_assets/home/icon-for-education-opt.svg	86400.0 s	1.9 KiB
www.scoop.it/hp_assets/home/icon-for-individuals-opt.svg	86400.0 s	1.9 KiB
www.scoop.it/hp_assets/home/icon-highlight-integrated-content-solution2.svg	86400.0 s	1.8 KiB
www.scoop.it/hp_assets/home/icon-for-business-opt.svg	86400.0 s	1.5 KiB

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
hero.gifAlt `div.px-4 > div.mx-auto > div > img`	www.scoop.it/hp_assets/home/gif-homepage-en.gif	5.1 MiB	5.1 MiB

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
www.scoop.it/_next/static/chunks/2e7dcb3ec1660f87.css	4.1 KiB
www.scoop.it/_next/static/chunks/3aa9eb043859e10e.css	572 B
www.scoop.it/_next/static/chunks/2ee5ee9d38f85b43.css	8.0 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: 2.0 s

URL	Time Spent
scoop.it/	969 ms
www.scoop.it/	841 ms
www.scoop.it/en	150 ms
www.scoop.it/en/	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 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: 450 ms 124.0 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-C94KXM161H	156.9 KiB	65.2 KiB
www.scoop.it/_next/static/chunks/0c2796b626873136.js	51.1 KiB	30.8 KiB
www.scoop.it/_next/static/chunks/9f4008469d0c7cdf.js	69.3 KiB	27.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 minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Other	1.4 s
Script Evaluation	831 ms
Style & Layout	383 ms
Rendering	341 ms
Script Parsing & Compilation	162 ms
Parse HTML & CSS	29 ms

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
www.scoop.it/hp_assets/home/gif-homepage-en.gif	5.1 MiB
www.scoop.it/hp_assets/home/header.jpg	244.2 KiB
www.googletagmanager.com/gtag/js?id=G-C94KXM161H	157.2 KiB
www.scoop.it/_next/static/chunks/9f4008469d0c7cdf.js	69.3 KiB
www.scoop.it/_next/static/chunks/0c2796b626873136.js	51.2 KiB
www.scoop.it/_next/static/media/cf514f5d0007dafa.p.417aa1a2.woff2	42.0 KiB
www.scoop.it/_next/static/media/797e433ab948586e.p.dbea232f.woff2	30.6 KiB
www.scoop.it/_next/static/chunks/557be5c833d730fe.js	22.6 KiB
www.scoop.it/_next/static/chunks/4355222d68f1d053.js	17.8 KiB
www.scoop.it/_next/static/chunks/f04b1fa7deb178f1.js	17.6 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
hero.gifAlt `div.px-4 > div.mx-auto > div > img`	www.scoop.it/hp_assets/home/gif-homepage-en.gif
Scoop.it logo `div.mx-auto > div > a > img.h-auto`	www.scoop.it/hp_assets/logo-teal.svg

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

●Reduce unused CSS

●User Timing marks and measures 6 user timings

●JavaScript execution time 0.9 s

●Avoid long main-thread tasks 8 long tasks found

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 0 ms

●Server Backend Latencies 220 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift 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.

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
1. Select `div.mx-auto > div > div.flex > div`
2. Organize `div.mx-auto > div > div.flex > div`
3. Share `div.mx-auto > div > div.flex > div`
1. Select `section.mt-section-spacing > div.mx-auto > div.my-6 > div.ml-4`
3. Share `section > div.mx-auto > div.my-6 > div.ml-4`
© 2026 Scoop.it. All rights reserved. `div.flex > footer.sf-footer > div.sf-container > div.sf-bottom`

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
Scoop.it `div.sf-container > div.sf-grid > div > h4.sf-heading`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

○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 use only permitted ARIA attributes

●Document has a `<title>` element

●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

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

○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 a valid value for its `[lang]` attribute

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

○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

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

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

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

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.

Line #	Content	Error
32	`Host-load: 5`	`Unknown directive`

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

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`