Lighthouse Desktop

· 0 checks — Desktop 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
siteworth.co/theme/default/fonts/fontawesome-webfont.woff?v=4.1.0	0.0 ms	81.9 KiB
siteworth.co/site_snapshot/facebook.com.jpg	0.0 ms	76.0 KiB
/theme/default/js/plugins/jvectormap/jquery-jvectormap-wo...	0.0 ms	54.2 KiB
siteworth.co/site_snapshot/google.com.jpg	0.0 ms	39.7 KiB
siteworth.co/theme/default/img/img-icons-background.jpg	0.0 ms	33.1 KiB
siteworth.co/site_snapshot/wikipedia.org.jpg	0.0 ms	32.7 KiB
siteworth.co/theme/default/css/theme.css	0.0 ms	31.2 KiB
siteworth.co/theme/default/css/AdminLTE.css	0.0 ms	18.4 KiB
/pagead/managed/js/adsense/m202605190101/show_ads_impl_fy...	1209600.0 s	172.8 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
siteworth.co/theme/default/js/AdminLTE/app.js	0.0 ms	15.2 KiB
siteworth.co/theme/default/js/plugins/morris/morris.min.js	0.0 ms	12.8 KiB
siteworth.co/theme/default/img/no-preview.png	0.0 ms	12.5 KiB
siteworth.co/theme/default/js/plugins/jvectormap/jquery-jvectormap-1.2.2.min.js	0.0 ms	10.6 KiB
siteworth.co/theme/default/js/bootstrap.min.js	0.0 ms	10.3 KiB
siteworth.co/theme/default/js/plugins/jqueryKnob/jquery.knob.js	0.0 ms	6.4 KiB
siteworth.co/theme/default/css/ionicons.min.css	0.0 ms	6.3 KiB
siteworth.co/core/img/32947_SiteWorth_logo5.png	0.0 ms	4.8 KiB
siteworth.co/theme/default/css/font-awesome.min.css	0.0 ms	4.7 KiB
siteworth.co/theme/default/css/reset.css	0.0 ms	2.9 KiB
siteworth.co/theme/default/img/gp.png	0.0 ms	468 B
siteworth.co/theme/default/img/twitter.png	0.0 ms	464 B
siteworth.co/theme/default/css/jvectormap/jquery-jvectormap-1.2.2.css	0.0 ms	340 B
siteworth.co/theme/default/img/facebook.png	0.0 ms	302 B
siteworth.co/theme/default/css/morris/morris.css	0.0 ms	281 B

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
siteworth.co/theme/default/fonts/fontawesome-webfont.woff?v=4.1.0	95 ms
/s/sourcesanspro/v23/6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdu...	25 ms
/s/sourcesanspro/v23/6xK1dSBYKcSV-LCoeQqfX1RYOo3qPZ7nsDJB...	20 ms
/s/sourcesanspro/v23/6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj...	10 ms
/s/googlesans/v69/4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iq...	5.0 ms
/s/googlesans/v69/4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iq...	5.0 ms

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
facebook.com `div.col-md-4 > div.thumbnail > a > img.image-overlay`	siteworth.co/site_snapshot/facebook.com.jpg	76.0 KiB	69.5 KiB
google.com `div.col-md-4 > div.thumbnail > a > img.image-overlay`	siteworth.co/site_snapshot/google.com.jpg	39.6 KiB	36.2 KiB
wikipedia.org `div.col-md-4 > div.thumbnail > a > img.image-overlay`	siteworth.co/site_snapshot/wikipedia.org.jpg	32.6 KiB	24.5 KiB
aiseomate.com `div.col-md-4 > div.thumbnail > a > img.image-overlay`	siteworth.co/theme/default/img/no-preview.png	12.4 KiB	11.3 KiB

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

nodeLabel: SITE WORTH CALCULATOR Quickly Calculate the Estimated Worth of Your Website for…

path: 1,HTML,1,BODY,3,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,CENTER,0,DIV

selector: div#newcontent > div.wrapper > center > div.home

snippet: <div class="home">

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
siteworth.co/theme/default/css/theme.css	31.2 KiB	208 ms
siteworth.co/theme/default/css/AdminLTE.css	18.4 KiB
siteworth.co/theme/default/css/ionicons.min.css	6.3 KiB
siteworth.co/theme/default/css/font-awesome.min.css	4.7 KiB
siteworth.co/theme/default/css/reset.css	2.9 KiB
siteworth.co/theme/default/css/morris/morris.css	281 B
siteworth.co/theme/default/css/jvectormap/jquery-jvectormap-1.2.2.css	340 B
/css?family=Source+Sans+Pro:300,400,600,300italic,400ital...	1.0 KiB	228 ms
fonts.googleapis.com/css?family=Kaushan+Script	865 B
ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js	32.8 KiB	245 ms

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

Diagnostics

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: 190 ms 47.2 KiB

URL	Transfer Size	Est Savings
siteworth.co/theme/default/css/theme.css	31.2 KiB	29.1 KiB
siteworth.co/theme/default/css/AdminLTE.css	18.4 KiB	18.1 KiB

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 reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
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

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.6 KiB

URL	Transfer Size	Est Savings
siteworth.co/theme/default/css/AdminLTE.css	18.4 KiB	3.6 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 10.4 KiB

URL	Transfer Size	Est Savings
siteworth.co/theme/default/js/AdminLTE/app.js	15.2 KiB	6.7 KiB
siteworth.co/theme/default/js/plugins/jqueryKnob/jquery.knob.js	6.4 KiB	3.7 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: 0.0 ms 236.4 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/adsense/m202605190101/show_ads_impl_fy...	172.8 KiB	122.1 KiB
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js	54.1 KiB	43.5 KiB
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js	54.1 KiB	25.2 KiB
cdnjs.cloudflare.com/ajax/libs/raphael/2.1.0/raphael-min.js	26.7 KiB	23.5 KiB
ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js	32.2 KiB	22.1 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
google.com `div.col-md-4 > div.thumbnail > a > img.image-overlay`	siteworth.co/site_snapshot/google.com.jpg
facebook.com `div.col-md-4 > div.thumbnail > a > img.image-overlay`	siteworth.co/site_snapshot/facebook.com.jpg
salutelazio.it `div.col-md-4 > div.thumbnail > a > img.image-overlay`	siteworth.co/theme/default/img/no-preview.png
viatieri.it `div.col-md-4 > div.thumbnail > a > img.image-overlay`	siteworth.co/theme/default/img/no-preview.png
tusciatimesold.it `div.col-md-4 > div.thumbnail > a > img.image-overlay`	siteworth.co/theme/default/img/no-preview.png
emiliosacco.it `div.col-md-4 > div.thumbnail > a > img.image-overlay`	siteworth.co/theme/default/img/no-preview.png
l3harris.com `div.col-md-4 > div.thumbnail > a > img.image-overlay`	siteworth.co/theme/default/img/no-preview.png
aiseomate.com `div.col-md-4 > div.thumbnail > a > img.image-overlay`	siteworth.co/theme/default/img/no-preview.png
wikipedia.org `div.col-md-4 > div.thumbnail > a > img.image-overlay`	siteworth.co/site_snapshot/wikipedia.org.jpg
worthmysite `div.container > div.navbar-header > a.navbar-brand > img.worth_my_site_logo`	siteworth.co/core/img/32947_SiteWorth_logo5.png

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

●Time to Interactive 1.4 s

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 40 ms

●Avoids enormous network payloads Total size was 1,002 KiB

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.8 s

●Avoid non-composited animations 1 animated element found

●Network Requests

●Network Round Trip Times 60 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 170 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.input-group > div.input-group-btn > button.btn `div.row > div.input-group > div.input-group-btn > button.btn`

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.container > div.row > div.none > a.ultm `div.container > div.row > div.none > a.ultm`
div.container > div.row > div.none > a.ultm `div.container > div.row > div.none > a.ultm`
div.container > div.row > div.none > a.ultm `div.container > div.row > div.none > a.ultm`

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. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Top Sites `div#collapse-menu > ul.nav > li > a`
Contact `div#collapse-menu > ul.nav > li > a`
About `div#collapse-menu > ul.nav > li > a`
Sign In `div#collapse-menu > ul.nav > li > a`
Sign Up `div#collapse-menu > ul.nav > li > a`
Visit `div.thumbnail > div.caption > p > a.btn`
Details `div.thumbnail > div.caption > p > a.btn`
Visit `div.thumbnail > div.caption > p > a.btn`
Details `div.thumbnail > div.caption > p > a.btn`
Visit `div.thumbnail > div.caption > p > a.btn`
Details `div.thumbnail > div.caption > p > a.btn`
Visit `div.thumbnail > div.caption > p > a.btn`
Details `div.thumbnail > div.caption > p > a.btn`
Visit `div.thumbnail > div.caption > p > a.btn`
Details `div.thumbnail > div.caption > p > a.btn`
Visit `div.thumbnail > div.caption > p > a.btn`
Details `div.thumbnail > div.caption > p > a.btn`
Visit `div.thumbnail > div.caption > p > a.btn`
Details `div.thumbnail > div.caption > p > a.btn`
Visit `div.thumbnail > div.caption > p > a.btn`
Details `div.thumbnail > div.caption > p > a.btn`
Visit `div.thumbnail > div.caption > p > a.btn`
Details `div.thumbnail > div.caption > p > a.btn`

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
Quickly Calculate the Estimated Worth of Your Website for Free. `div#myhome > div.container > div.row > h4`
SiteWorth.co is a free website worth calculator tool. It uses publicly availab… `div.more > div.container > div.contentx > h4`
Google.com `div.col-md-4 > div.thumbnail > div.caption > h4`
Salutelazio.it `div.col-md-4 > div.thumbnail > div.caption > h4`

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.

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
Get Paid to Post on Social Media `div.row > div#xxxd > i > a`
Get Paid to Test Apps `div.row > div#xxxd > i > a`
Get Paid to Take Pics `div.row > div#xxxd > i > 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

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●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

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

○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

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

○Uses ARIA roles only on compatible elements

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

○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

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URL	Request Resolution
/css?family=Source+Sans+Pro:200,300,400,600,200italic,300...	Blocked

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
siteworth.co/	`Mixed Content: The page at 'https://siteworth.co/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Source+Sans+Pro:200,300,400,600,200italic,300italic,400italic,600italic'. This request has been blocked; the content must be served over HTTPS.`

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Mixed content

●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

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