Skip to content
https://www.osintatlas.io

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.

82

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.25061957497508736] map[node:map[boundingRect:map[bottom:765 height:182 left:20 right:392 top:583 width:372] lhId:page-3-UL nodeLabel:All 7,700+ official portals: inmates, property, businesses, licenses and more U… path:1,HTML,1,BODY,0,DIV,1,MAIN,0,SECTION,1,DIV,4,UL selector:main#main > section.lp-hero > div.lp-hero-in > ul.lp-checks snippet:<ul class="lp-checks lp-unlock" style="max-width:560px;margin:14px auto 0;text-align:left"> type:node] score:0.1289136250500198] map[node:map[boundingRect:map[bottom:765 height:182 left:20 right:392 top:583 width:372] lhId:page-3-UL nodeLabel:All 7,700+ official portals: inmates, property, businesses, licenses and more U… path:1,HTML,1,BODY,0,DIV,1,MAIN,0,SECTION,1,DIV,4,UL selector:main#main > section.lp-hero > div.lp-hero-in > ul.lp-checks snippet:<ul class="lp-checks lp-unlock" style="max-width:560px;margin:14px auto 0;text-align:left"> type:node] score:0.1209626421741355] map[node:map[boundingRect:map[bottom:46 height:34 left:228 right:396 top:12 width:168] lhId:page-1-DIV nodeLabel:Guides Log in path:1,HTML,1,BODY,0,DIV,0,HEADER,1,DIV selector:body.auth-page > div.wrap > header.topbar > div.topbar-actions snippet:<div class="topbar-actions"> type:node] score:0.0004982202759104304 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/inter/v20/UcC73FwrK3iLTeHuS_nVMrMxCp50SjIa1ZL7W0Q5nw.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:302 height:32 left:254 right:257 top:270 width:3] lhId:page-2-SPAN nodeLabel:section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret path:1,HTML,1,BODY,0,DIV,1,MAIN,0,SECTION,1,DIV,1,H1,2,SPAN selector:section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret snippet:<span class="lp-caret" aria-hidden="true"> type:node] score:2.315634797774416e-05] map[node:map[boundingRect:map[bottom:302 height:32 left:254 right:257 top:270 width:3] lhId:page-2-SPAN nodeLabel:section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret path:1,HTML,1,BODY,0,DIV,1,MAIN,0,SECTION,1,DIV,1,H1,2,SPAN selector:section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret snippet:<span class="lp-caret" aria-hidden="true"> type:node] score:7.084509432373911e-06]]

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

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.

URLTransfer SizeDuration
www.osintatlas.io/styles.css13.5 KiB166 ms
www.osintatlas.io/landing/landing.css?v=covpop14.4 KiB
www.osintatlas.io/coverage/coverage-ux.css?v=cmp21.7 KiB
fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&display=swap1.2 KiB836 ms
www.osintatlas.io/auth/ui.css1.1 KiB166 ms
www.osintatlas.io/auth/auth.css1.2 KiB
www.osintatlas.io/theme-v2.css?v=abdd678e445.5 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

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

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 11.5 KiB
URLTransfer SizeEst Savings
www.osintatlas.io/styles.css13.2 KiB11.5 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.

CategoryTime Spent
Other1.0 s
Style & Layout696 ms
Rendering391 ms
Script Evaluation365 ms
Garbage Collection41 ms
Parse HTML & CSS38 ms
Script Parsing & Compilation16 ms

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
All 7,700+ official portals: inmates, property, businesses, licenses and more U… main#main > section.lp-hero > div.lp-hero-in > ul.lp-checks
0.129
All 7,700+ official portals: inmates, property, businesses, licenses and more U… main#main > section.lp-hero > div.lp-hero-in > ul.lp-checks
0.121
Guides Log in body.auth-page > div.wrap > header.topbar > div.topbar-actions
0.000
section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret
0.000
section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret
0.000
section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret
0.000
section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret
0.000
section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret
0.000
section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret
0.000
section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret
0.000
section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret
0.000
section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret
0.000
section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret
0.000
section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret
0.000
section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret section.lp-hero > div.lp-hero-in > h1.lp-type > span.lp-caret
0.000
●Time to Interactive 2.8 s
●Use efficient cache lifetimes
●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 106 KiB
●JavaScript execution time 0.3 s
●Avoid long main-thread tasks 5 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 80 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 60 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
91

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
Coverage map categories main#main > section.lp-section > div.lp-map > div.lp-cov-dots

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA U… div.lp-map > div.lp-cov-vp > div.lp-cov-track > div.lp-cov-slide
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA U… div.lp-map > div.lp-cov-vp > div.lp-cov-track > div.lp-cov-slide
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA U… div.lp-map > div.lp-cov-vp > div.lp-cov-track > div.lp-cov-slide
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA U… div.lp-map > div.lp-cov-vp > div.lp-cov-track > div.lp-cov-slide
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA U… div.lp-map > div.lp-cov-vp > div.lp-cov-track > div.lp-cov-slide

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.

○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
●`[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 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
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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.
○Image elements have `[alt]` attributes
○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.
○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.
○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.
96

Best Practices

General

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
www.osintatlas.io/api/auth/me
Failed to load resource: the server responded with a status of 401 ()
●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 issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Ensure proper origin isolation with COOP
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
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
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○Image elements have `[alt]` attributes

Send Feedback