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.

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
www.nirsoft.net/	http/1.1
www.nirsoft.net/main.css	http/1.1
www.nirsoft.net/nirsoft2.gif	http/1.1
www.nirsoft.net/banners/empty729x90.gif	http/1.1
www.nirsoft.net/feed.png	http/1.1
www.nirsoft.net/menubg.png	http/1.1
www.nirsoft.net/menutomain.gif	http/1.1
www.nirsoft.net/toptomain.gif	http/1.1
www.nirsoft.net/whatnewbg.gif	http/1.1
www.nirsoft.net/favicon.ico	http/1.1

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
www.nirsoft.net/main.css	1.8 KiB	218 ms

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
/pagead/managed/js/activeview/current/ufs_web_display.js	3600.0 s	73.1 KiB
/pagead/managed/js/adsense/m202604170101/show_ads_impl_fy...	1209600.0 s	177.5 KiB
www.nirsoft.net/nirsoft2.gif	0.0 ms	3.8 KiB
cse.google.com/cse.js?cx=partner-pub-5286073190998405:5399172980	0.0 ms	3.0 KiB
www.nirsoft.net/main.css	0.0 ms	1.8 KiB
www.nirsoft.net/feed.png	0.0 ms	1.6 KiB
/pagead/js/r20260422/r20110914/client/one_click_handler_o...	1209600.0 s	15.6 KiB
www.nirsoft.net/banners/empty729x90.gif	0.0 ms	1.4 KiB
www.nirsoft.net/whatnewbg.gif	0.0 ms	1.3 KiB
www.nirsoft.net/toptomain.gif	0.0 ms	1.0 KiB
www.nirsoft.net/menutomain.gif	0.0 ms	1.0 KiB
www.google.com/cse/static/style/look/v6/default.css	3000.0 s	1.2 KiB
/pagead/js/r20260422/r20110914/client/qs_click_protection...	1209600.0 s	8.9 KiB
tpc.googlesyndication.com/pagead/js/r20260422/r20110914/abg_lite_fy2021.js	1209600.0 s	8.4 KiB
www.nirsoft.net/menubg.png	0.0 ms	689 B
/pagead/js/r20260422/r20110914/client/window_focus_fy2021.js	1209600.0 s	1.3 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
FAQ `table > tbody > tr.menub1 > td`	tpc.googlesyndication.com/simgad/8476523500059891530	139.3 KiB	68.3 KiB

Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

URL	Time Spent
nirsoft.net/	951 ms
www.nirsoft.net/	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 303.5 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/adsense/m202604170101/show_ads_impl_fy...	177.5 KiB	131.8 KiB
www.googletagmanager.com/gtag/js?id=G-P2Q08WF7BK	145.7 KiB	60.8 KiB
/cse/static/element/dc329f57de078f5d/cse_element__en.js?u...	102.7 KiB	53.0 KiB
cse.google.com/adsense/search/async-ads.js	43.3 KiB	33.4 KiB
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js	54.2 KiB	24.4 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
/pagead/managed/js/adsense/m202604170101/show_ads_impl_fy...	558 ms	458 ms	55 ms
www.nirsoft.net/	481 ms	161 ms	3.4 ms
Unattributable	317 ms	16 ms	0.0 ms
cse.google.com/cse.js?cx=partner-pub-5286073190998405:5399172980	192 ms	128 ms	0.9 ms
www.googletagmanager.com/gtag/js?id=G-P2Q08WF7BK	152 ms	99 ms	41 ms
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js	144 ms	123 ms	17 ms
ep2.adtrafficquality.google/sodar/sodar2.js	111 ms	102 ms	4.6 ms
/cse/static/element/dc329f57de078f5d/cse_element__en.js?u...	83 ms	40 ms	39 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	1.2 s
Other	448 ms
Style & Layout	185 ms
Script Parsing & Compilation	177 ms
Rendering	130 ms
Parse HTML & CSS	35 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 3.3 KiB

URL	Transfer Size	Est Savings
www.google.com/cse/static/element/dc329f57de078f5d/default_v6+en.css	12.0 KiB	3.3 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 11.5 KiB

URL	Transfer Size	Est Savings
www.google.com/cse/static/element/dc329f57de078f5d/default_v6+en.css	11.9 KiB	11.5 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
tbody > tr > td > img `tbody > tr > td > img`	www.nirsoft.net/banners/empty729x90.gif
tr > td > a > img `tr > td > a > img`	www.nirsoft.net/nirsoft2.gif

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

●Minify JavaScript

●Avoids enormous network payloads Total size was 967 KiB

●User Timing marks and measures 7 user timings

●Avoid long main-thread tasks 9 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 70 ms

●Server Backend Latencies 30 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP request discovery

○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
Password Recovery Utilities `ul > li > span.aboutexamples > a`
Network Monitoring Tools `ul > li > span.aboutexamples > a`
Internet Related Utilities `ul > li > span.aboutexamples > a`
MS-Outlook Tools `ul > li > span.aboutexamples > a`
Command-Line Utilities `ul > li > span.aboutexamples > a`
Desktop Utilities `ul > li > span.aboutexamples > a`
Freeware System Tools `ul > li > span.aboutexamples > a`

These are opportunities to improve the legibility of your content.

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.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
tr > td > a > img `tr > td > a > img`
tbody > tr > td > img `tbody > tr > td > img`
tr > td > a > img `tr > td > a > img`

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
tbody > tr > td > a `tbody > tr > td > a`
tbody > tr > td > a `tbody > tr > td > a`

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
TOP 10 `tbody > tr.menub1 > td > a`
Pad Files `tbody > tr.menub1 > td > a`
Contact `tbody > tr.menub1 > td > a`
About... `tbody > tr.menub1 > td > a`
Donate `tbody > tr.menub1 > td > a`
System Tools `tbody > tr.menub2 > td > a`
Browser Tools `tbody > tr.menub2 > td > a`
Network Tools `tbody > tr.menub2 > td > a`
Outlook/Office `tbody > tr.menub2 > td > a`
64-bit Download `tbody > tr.menub2 > td > a`
Password Recovery Utilities `ul > li > span.aboutexamples > a`
Network Monitoring Tools `ul > li > span.aboutexamples > a`
Internet Related Utilities `ul > li > span.aboutexamples > a`
MS-Outlook Tools `ul > li > span.aboutexamples > a`
Command-Line Utilities `ul > li > span.aboutexamples > a`
Desktop Utilities `ul > li > span.aboutexamples > a`
Freeware System Tools `ul > li > span.aboutexamples > a`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○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

●Form elements have associated labels

●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

●Document has a `<title>` element

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

●Links are distinguishable without relying on color.

●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

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Deprecated ARIA roles were not used

●The page contains a heading, skip link, or landmark region

●Identical links have the same purpose.

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

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

○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

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

○Heading elements appear in a sequentially-descending order

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

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

○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
tbody > tr > td > img `tbody > tr > td > img`	www.nirsoft.net/banners/empty729x90.gif	728 x 90	728 x 90	1092 x 135
tr > td > a > img `tr > td > a > img`	www.nirsoft.net/nirsoft2.gif	176 x 44	176 x 44	264 x 66
tr > td > a > img `tr > td > a > img`	www.nirsoft.net/feed.png	32 x 32	32 x 32	48 x 48

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
s7.addthis.com/js/250/addthis_widget.js#pubid=nirsofer	`Failed to load resource: net::ERR_NAME_NOT_RESOLVED`

●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

●Properly defines charset

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

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.nirsoft.net/password_recovery_tools.html	click here
www.nirsoft.net/network_tools.html	click here
www.nirsoft.net/show_my_ip_address.php	click here
www.nirsoft.net/countryip	click here
blog.nirsoft.net/	click here

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
tr > td > a > img `tr > td > a > img`
tbody > tr > td > img `tbody > tr > td > img`
tr > td > a > img `tr > td > a > img`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○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 are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`