Skip to content
https://sitevalue.org

Lighthouse Desktop

· 0 checks — Desktop 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.

76

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.

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.

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:196.681001953125 label:Time to first byte subpart:timeToFirstByte] map[duration:2216.911998046875 label:Resource load delay subpart:resourceLoadDelay] map[duration:77.904 label:Resource load duration subpart:resourceLoadDuration] map[duration:35.918 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: themanifest.com
path: 1,HTML,1,BODY,1,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,4,DIV,0,DIV,0,DIV,1,A,0,IMG
selector: div.col > div.card > a > img#thumb_89750
snippet: <img class="card-img-top" id="thumb_89750" src="https://api.pagepeeker.com/v2/thumbs.php?size=l&amp;url=themanifest.com" alt="themanifest.com">

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-IMG
nodeLabel: themanifest.com
path: 1,HTML,1,BODY,1,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,4,DIV,0,DIV,0,DIV,1,A,0,IMG
selector: div.col > div.card > a > img#thumb_89750
snippet: <img class="card-img-top" id="thumb_89750" src="https://api.pagepeeker.com/v2/thumbs.php?size=l&amp;url=themanifest.com" alt="themanifest.com">

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.

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.

URLResource SizeEst Savings
animesuge.ing div.col > div.card > a > img#thumb_89746
api.pagepeeker.com/v2/thumbs.php?size=l&url=animesuge.ing33.7 KiB19.0 KiB
syrusindustry.com div.col > div.card > a > img#thumb_89749
api.pagepeeker.com/v2/thumbs.php?size=l&url=syrusindustry.com22.5 KiB7.7 KiB
cichlidwarehouse.co.za div.col > div.card > a > img#thumb_89745
api.pagepeeker.com/v2/thumbs.php?size=l&url=cichlidwarehouse.co.za18.8 KiB4.6 KiB
themanifest.com div.col > div.card > a > img#thumb_89750
api.pagepeeker.com/v2/thumbs.php?size=l&url=themanifest.com17.9 KiB4.4 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: 234 ms
URLTime Spent
sitevalue.org/234 ms
sitevalue.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

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.

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.

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

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
themanifest.com div.col > div.card > a > img#thumb_89750
api.pagepeeker.com/v2/thumbs.php?size=l&url=themanifest.com
syrusindustry.com div.col > div.card > a > img#thumb_89749
api.pagepeeker.com/v2/thumbs.php?size=l&url=syrusindustry.com
codearena.space div.col > div.card > a > img#thumb_89748
api.pagepeeker.com/v2/thumbs.php?size=l&url=codearena.space
beavercheck.com div.col > div.card > a > img#thumb_89747
api.pagepeeker.com/v2/thumbs.php?size=l&url=beavercheck.com
animesuge.ing div.col > div.card > a > img#thumb_89746
api.pagepeeker.com/v2/thumbs.php?size=l&url=animesuge.ing
cichlidwarehouse.co.za div.col > div.card > a > img#thumb_89745
api.pagepeeker.com/v2/thumbs.php?size=l&url=cichlidwarehouse.co.za

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

●Max Potential First Input Delay 80 ms
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 936 KiB
●JavaScript execution time 0.3 s
●Minimizes main-thread work 0.8 s
●Avoid long main-thread tasks 2 long tasks found
●Network Requests
●Network Round Trip Times 230 ms
●Server Backend Latencies 130 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 4 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
92

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
Learn more div.cc_banner-wrapper > div.cc_banner > p.cc_message > a.cc_more_info
SiteValue div.d-flex > nav.navbar > div.container > a.navbar-brand
Home div#navbarPrimary > ul.navbar-nav > li.nav-item > a.nav-link
Top div#navbarPrimary > ul.navbar-nav > li.nav-item > a.nav-link
Upcoming div#navbarPrimary > ul.navbar-nav > li.nav-item > a.nav-link
Sell Websites div#navbarPrimary > ul.navbar-nav > li.nav-item > a.nav-link
Buy Websites div#navbarPrimary > ul.navbar-nav > li.nav-item > a.nav-link
Contact us div#navbarPrimary > ul.navbar-nav > li.nav-item > a.nav-link
Language   div#navbarPrimary > ul.navbar-nav > li.nav-item > a#navbarDropdownMenuLink
Sign in div#navbarPrimary > ul.navbar-nav > li.nav-item > a.nav-link
div.form-group > div.input-group > span.input-group-append > input#submit div.form-group > div.input-group > span.input-group-append > input#submit
89,609 div.row > div.col-md-6 > p > span.badge
Explore more div.col > div.card > div.card-body > a.btn
Explore more div.col > div.card > div.card-body > a.btn
Explore more div.col > div.card > div.card-body > a.btn
Explore more div.col > div.card > div.card-body > a.btn
Explore more div.col > div.card > div.card-body > a.btn
Explore more div.col > div.card > div.card-body > a.btn
Website Worth Calculator div.col-md-8 > p.text-muted > strong > a
Privacy Policy div.col-md-4 > ul > li > a
Terms and Conditions div.col-md-4 > ul > li > a
Learn more div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label
List of partners. div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog

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
themanifest.com div.row > div.col > div.card > h3.card-header

These are opportunities to improve keyboard navigation in your application.

Names and labels

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#navbarPrimary > ul.navbar-nav > li.nav-item > a.nav-link

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.

○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
●Input buttons have discernible text.
●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.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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.
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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 an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<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>`.
○All heading elements contain content.
○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.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
●Uses HTTPS
●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
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
92

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 destinationLink Text
sitevalue.net/en/privacy-policyLearn more

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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback