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.

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
lord.porn/templates/toplist/fonts/fontawesome/fontawesome-webfont.woff2?v=4.4.0	250 ms
/s/robotocondensed/v31/ieVl2ZhZI2eCN5jzbjEETS9weq8-19K7DQ...	60 ms
fonts.gstatic.com/s/roboto/v51/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	60 ms

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:23.466 source:map[column:30242 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:33.13 source:map[type:text value:[unattributed]]] map[reflowTime:21.191 source:map[column:31266 line:1 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js urlProvider:network]] map[reflowTime:0.338 source:map[column:31319 line:4 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js urlProvider:network]] map[reflowTime:1.937 source:map[column:29825 line:4 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js urlProvider:network]]]

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
Tube8 `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/70/icon.png?v=20260805c	10.0 KiB	9.9 KiB
ImLive `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/87/icon.png?v=20260805c	9.2 KiB	9.2 KiB
SpiceVids `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/78/icon.png?v=20260805c	9.2 KiB	9.1 KiB
Camera Prive `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/113/icon.png?v=20260805c	9.1 KiB	9.1 KiB
lord.porn `div.row > div.logo-col > a > img`	lord.porn/templates/toplist/images/logo.png?v=20260805newlogo	10.5 KiB	8.8 KiB
Reality Kings `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/74/icon.png?v=20260805c	8.7 KiB	8.6 KiB
LuckyCrush `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/90/icon.png?v=20260805c	7.2 KiB	7.1 KiB
Cam4 `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/112/icon.png?v=20260805c	7.2 KiB	7.1 KiB
Beeg `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/71/icon.png?v=20260805c	7.0 KiB	7.0 KiB
Naughty America `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/105/icon.png?v=20260805c	6.6 KiB	6.5 KiB
XNXX `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/65/icon.png?v=20260805c	6.5 KiB	6.4 KiB
Digital Playground `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/106/icon.png?v=20260805c	6.3 KiB	6.2 KiB
CamSoda `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/82/icon.png?v=20260805c	6.3 KiB	6.2 KiB
SpankBang `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/69/icon.png?v=20260805c	6.2 KiB	6.2 KiB
TeamSkeet `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/104/icon.png?v=20260805c	6.0 KiB	5.9 KiB
Brazzers `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/72/icon.png?v=20260805c	5.5 KiB	5.4 KiB
Chaturbate `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/79/icon.png?v=20260805c	5.5 KiB	5.4 KiB
BongaCams `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/83/icon.png?v=20260805c	5.3 KiB	5.3 KiB
Streamate `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/111/icon.png?v=20260805c	4.8 KiB	4.7 KiB
Flirt4Free `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/88/icon.png?v=20260805c	4.7 KiB	4.6 KiB
SkyPrivate `ul > li.site-row > a > img.site-thumb`	lord.porn/media/thumbs/0/89/icon.png?v=20260805c	4.5 KiB	4.4 KiB

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.

URL	Transfer Size	Duration
ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js	33.3 KiB	429 ms
lord.porn/includes/rating/js/jRating.jquery.js	2.7 KiB	153 ms
lord.porn/templates/toplist/js/extra/jquery.mCustomScrollbar.js	21.3 KiB	258 ms
lord.porn/templates/toplist/js/bootstrap/bootstrap.min.js	9.9 KiB	206 ms
fonts.googleapis.com/css?family=Roboto:700,300\|Roboto+Condensed:300,400,500,700	2.3 KiB	234 ms
lord.porn/templates/toplist/js/extra/mb.semiWaterfall.js	1.9 KiB	153 ms
lord.porn/templates/toplist/js/extra/layzr.min.js	1.4 KiB	153 ms
lord.porn/templates/toplist/js/extra/jquery.scrollTo.min.js	1.8 KiB	153 ms
lord.porn/templates/toplist/js/extra/bootstrap-select.js	10.4 KiB	206 ms
lord.porn/templates/toplist/js/extra/jquery.nhancedBootstrapCollapse.js	2.6 KiB	153 ms
lord.porn/templates/toplist/js/extra/easing.js	2.5 KiB	153 ms
lord.porn/templates/toplist/js/extra/jquery.scrollUp.min.js	1.4 KiB	153 ms
lord.porn/templates/toplist/js/extra/jquery.mousewheel.js	3.1 KiB	153 ms
lord.porn/templates/toplist/css/page.css	5.7 KiB	153 ms
lord.porn/templates/toplist/css/overwrite.css?v=20260805agegate1	2.0 KiB	258 ms
lord.porn/templates/toplist/css/overwrite.css	2.0 KiB	153 ms
lord.porn/templates/toplist/css/rwd.css	530 B	258 ms
lord.porn/templates/toplist/css/style.css	586 B	258 ms
lord.porn/templates/toplist/css/jquery.mCustomScrollbar.css	6.0 KiB	258 ms
lord.porn/templates/toplist/css/bootstrap.css	12.4 KiB	311 ms
lord.porn/includes/rating/js/jRating.jquery.css	1002 B	153 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
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
www.statcounter.com/counter/counter.js	43200.0 s	17.5 KiB

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 657 ms

URL	Time Spent
lord.porn/	757 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.

Estimated savings: 0.0 ms 11.3 KiB

URL	Transfer Size	Est Savings
lord.porn/templates/toplist/css/bootstrap.css	11.8 KiB	11.3 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 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 11.3 KiB

URL	Transfer Size	Est Savings
lord.porn/templates/toplist/js/extra/jquery.mCustomScrollbar.js	20.7 KiB	8.1 KiB
lord.porn/templates/toplist/js/extra/bootstrap-select.js	9.9 KiB	3.3 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 69.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-9CYY34S519&cx=c&_slc=1	154.4 KiB	69.3 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
Lord.porn `div#age-gate-overlay > div.age-gate-card > div.age-gate-logo > img`	lord.porn/templates/toplist/images/logo.png?v=20260805newlogo
lord.porn `div.row > div.logo-col > a > img`	lord.porn/templates/toplist/images/logo.png?v=20260805newlogo

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

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify CSS

●Avoids enormous network payloads Total size was 854 KiB

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.6 s

●Avoid long main-thread tasks 1 long task found

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 230 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○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
This site uses cookies to remember your confirmation. `body.page-home > div#age-gate-overlay > div.age-gate-card > p.age-gate-footnote`

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.no-js `html.no-js`

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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-hidden="true"]` is not present on the document `<body>`

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●Document has a `<title>` element

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

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

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○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

○`[role]` values are valid

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

100

Best Practices

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

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`