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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	35 ms

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.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
www.virustotal.com/gui/static/qrcode.min.js	60.0 s	7.6 KiB
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB

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

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.

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: 892 ms

URL	Time Spent
virustotal.com/	892 ms
www.virustotal.com/gui/	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

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: 1.9 s 574.4 KiB

URL	Transfer Size	Est Savings
www.virustotal.com/gui/main.5f73bda39cfd0d4f4f27.js	602.3 KiB	215.8 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.6 KiB	177.2 KiB
www.googletagmanager.com/gtag/js?id=G-BLNDV9X2JR&cx=c&gtm=4e64h1	162.5 KiB	65.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-KFBGZNL	130.0 KiB	58.6 KiB
www.gstatic.com/dialogflow-console/fast/df-messenger/prod/v1/df-messenger.js	127.7 KiB	57.1 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
www.virustotal.com/gui/main.5f73bda39cfd0d4f4f27.js	1.5 s	1.1 s	221 ms
www.virustotal.com/gui/	814 ms	8.7 ms	3.1 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	784 ms	652 ms	87 ms
www.virustotal.com/gui/65783.2b004f046085d43ad1ef.js	608 ms	572 ms	4.4 ms
Unattributable	339 ms	49 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-BLNDV9X2JR&cx=c&gtm=4e64h1	241 ms	194 ms	45 ms
www.googletagmanager.com/gtm.js?id=GTM-KFBGZNL	222 ms	171 ms	42 ms
www.virustotal.com/gui/60748.5e0487ca603debd09abb.js	164 ms	129 ms	1.6 ms
www.gstatic.com/dialogflow-console/fast/df-messenger/prod/v1/df-messenger.js	76 ms	33 ms	39 ms
www.google-analytics.com/analytics.js	66 ms	47 ms	4.3 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.1 s
Other	716 ms
Script Parsing & Compilation	479 ms
Style & Layout	407 ms
Rendering	83 ms
Garbage Collection	79 ms
Parse HTML & CSS	65 ms

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: 0.0 ms 17.9 KiB

URL	Transfer Size	Est Savings
@charset "UTF-8"; /! Bootstrap v5.3.8 (https://getbootstrap.com/) * Copyright 2011-2025 The B…	88.0 KiB	10.3 KiB
:root, [data-bs-theme="light"] { --bs-blue: #0b4dda; --bs-indigo: #6610f2; --bs-purple: #6f42c1; --…	80.0 KiB	7.7 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: 0.0 ms 159.6 KiB

URL	Transfer Size	Est Savings
@charset "UTF-8"; /! Bootstrap v5.3.8 (https://getbootstrap.com/) * Copyright 2011-2025 The B…	88.0 KiB	81.2 KiB
:root, [data-bs-theme="light"] { --bs-blue: #0b4dda; --bs-indigo: #6610f2; --bs-purple: #6f42c1; --…	80.0 KiB	78.3 KiB

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify JavaScript

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

●User Timing marks and measures 10 user timings

●Avoid long main-thread tasks 13 long tasks found

●Avoid non-composited animations 1 animated element found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 140 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP request discovery

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
FILE URL SEARCH `div > div.omnibar > div.tabs-wrapper > ul.nav`

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

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.input-placeholder-wrapper > input#placeholderInput `div.input-placeholder-wrapper > input#placeholderInput`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wrapper > a.logo `div.wrapper > a.logo`
div.tabs-wrapper > ul.nav > li.nav-item > a.hstack `div.tabs-wrapper > ul.nav > li.nav-item > a.hstack`

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.

Contrast

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
Terms of Service `div.wrapper > div.sub > a#terms-of-service-file-link`
Privacy Notice `div.wrapper > div.sub > a#privacy-policy-file-link`
Learn more. `div.wrapper > div.sub > a#learn-more-file-link`
Check our API `div > div.tip > span.ms-1 > a#check-your-api-api-link`
API key `div > div.tip > span.ms-1 > a#api-key-api-link`

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FILE `div.omnibar > div.tabs-wrapper > ul.nav > li.nav-item`
URL `div.omnibar > div.tabs-wrapper > ul.nav > li.nav-item`
SEARCH `div.omnibar > div.tabs-wrapper > ul.nav > li.nav-item`
div.omnibar > div.tabs-wrapper > ul.nav > li.nav-item `div.omnibar > div.tabs-wrapper > ul.nav > li.nav-item`

These are opportunities to improve the experience of reading tabular or list data using 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.

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

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

●No element has a `[tabindex]` value greater than 0

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

○Heading elements appear in a sequentially-descending order

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

○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

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
www.virustotal.com/ui/me?relationships=active_group%2Cparent_group	`Failed to load resource: the server responded with a status of 401 ()`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Map URL
www.virustotal.com/gui/main.5f73bda39cfd0d4f4f27.js	www.virustotal.com/gui/main.5f73bda39cfd0d4f4f27.js.map
www.virustotal.com/gui/vt-ui-sw-installer.d948df1515ba212dffab.js	www.virustotal.com/gui/vt-ui-sw-installer.d948df1515ba212dffab.js.map
www.virustotal.com/gui/vt-ui-shell-extra-deps.ef2bcb9c198a7615c8ce.js	www.virustotal.com/gui/vt-ui-shell-extra-deps.ef2bcb9c198a7615c8ce.js.map
www.virustotal.com/gui/stackdriver-errors.da3ed71ed492c5a534a4.js	www.virustotal.com/gui/stackdriver-errors.da3ed71ed492c5a534a4.js.map
www.virustotal.com/gui/65783.2b004f046085d43ad1ef.js	www.virustotal.com/gui/65783.2b004f046085d43ad1ef.js.map
www.virustotal.com/gui/60748.5e0487ca603debd09abb.js	www.virustotal.com/gui/60748.5e0487ca603debd09abb.js.map
www.virustotal.com/gui/41628.ba45edaaddc125ece303.js	www.virustotal.com/gui/41628.ba45edaaddc125ece303.js.map
www.virustotal.com/gui/1532.2eb92de2970ebf5bc772.js	www.virustotal.com/gui/1532.2eb92de2970ebf5bc772.js.map
www.virustotal.com/gui/14700.c867d7dbdf47215b5a89.js	www.virustotal.com/gui/14700.c867d7dbdf47215b5a89.js.map

●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

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

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`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`