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.

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
Girls' Solution to the Heatwave! `div.card-scene > div.card-scene__view > a > img`	/5XjWoY5Ce5ncI6YTi5SpTg==,1989961200/8ebf458f8301c26935ee...	58.8 KiB	42.7 KiB
div.modal-content > div.row > div.col-sm-auto > img `div.modal-content > div.row > div.col-sm-auto > img`	pissvids.com/assets/img/agree18/pissvids.jpg	44.4 KiB	39.3 KiB
div.container-fluid > div.header__row > a.header__logo > img `div.container-fluid > div.header__row > a.header__logo > img`	pissvids.com/assets/img/logo/pissvids.png	22.6 KiB	18.8 KiB
is Unbreakable #2 Wet, Vittoria Divine, 8on1, ATM, Balls Deep, DAP, Extreme Dee… `div.card-scene > div.card-scene__view > a > img`	/CxHbcT-zMtZe80ujet9P_A==,1989961200/617d1085f9635391d6ee...	34.1 KiB	17.9 KiB
The beautiful MADYLU JONES loves to have two cocks in her ass all the time, DAP… `div.card-scene > div.card-scene__view > a > img`	/a6KbkqkecHz8JJDf4xyANA==,1989961200/39ecef84be4d3dc7530f...	27.0 KiB	10.9 KiB

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:625.7209990234375 label:Time to first byte subpart:timeToFirstByte] map[duration:1179.1280009765626 label:Resource load delay subpart:resourceLoadDelay] map[duration:1016.809 label:Resource load duration subpart:resourceLoadDuration] map[duration:25.44 label:Element render delay subpart:elementRenderDelay]]

lhId: page-3-IMG

nodeLabel: is Unbreakable #2 Wet, Vittoria Divine, 8on1, ATM, Balls Deep, DAP, Extreme Dee…

path: 1,HTML,1,BODY,1,MAIN,0,SECTION,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,2,A,0,IMG

selector: div.card-scene > div.card-scene__view > a > img

snippet: <img src="/casting/4960485/1083135549" class="" alt="is Unbreakable #2 Wet, Vittoria Divine, 8on1, ATM, Balls Deep, DAP, Extrem…">

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

nodeLabel: is Unbreakable #2 Wet, Vittoria Divine, 8on1, ATM, Balls Deep, DAP, Extreme Dee…

path: 1,HTML,1,BODY,1,MAIN,0,SECTION,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,2,A,0,IMG

selector: div.card-scene > div.card-scene__view > a > img

snippet: <img src="/casting/4960485/1083135549" class="" alt="is Unbreakable #2 Wet, Vittoria Divine, 8on1, ATM, Balls Deep, DAP, Extrem…">

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
pissvids.com/assets/css/pissvids.css?rev=815	43.9 KiB	699 ms
pissvids.com/assets/css/fonts.css?rev=815	490 B

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
tracking.sexcash.com/tracking-script.js	0.0 ms	1.1 KiB
/collect/v.gif?cd=0&a=577004&d=pissvids.com&u=D17B0149E1D...	43200.0 s	160 B

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.

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: 160 ms 41.8 KiB

URL	Transfer Size	Est Savings
pissvids.com/assets/css/pissvids.css?rev=815	43.6 KiB	41.8 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: 1.7 s 456.7 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/rL1ELiQAg1kPezz6_H9hTZ_i/recaptcha__en.js	374.0 KiB	247.8 KiB
pissvids.com/assets/js/app.js?rev=815	106.8 KiB	74.8 KiB
www.googletagmanager.com/gtag/js?id=G-QMXK2HPN3M&cx=c&gtm=4e6781	154.6 KiB	69.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-TLR8T2C	119.2 KiB	64.3 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
pissvids.com/assets/js/app.js?rev=815	804 ms	399 ms	58 ms
pissvids.com/	756 ms	28 ms	3.8 ms
Unattributable	441 ms	94 ms	0.0 ms
www.gstatic.com/recaptcha/releases/rL1ELiQAg1kPezz6_H9hTZ_i/recaptcha__en.js	350 ms	198 ms	151 ms
www.googletagmanager.com/gtag/js?id=G-QMXK2HPN3M&cx=c&gtm=4e6781	331 ms	231 ms	74 ms
www.googletagmanager.com/gtm.js?id=GTM-TLR8T2C	223 ms	164 ms	57 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.1 s
Other	661 ms
Style & Layout	499 ms
Script Parsing & Compilation	348 ms
Rendering	208 ms
Parse HTML & CSS	66 ms
Garbage Collection	57 ms

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
div.container-fluid > div.header__row > a.header__logo > img `div.container-fluid > div.header__row > a.header__logo > img`	pissvids.com/assets/img/logo/pissvids.png
footer.footer > div.container-fluid > a.footer__logo > img `footer.footer > div.container-fluid > a.footer__logo > img`	pissvids.com/assets/img/logo/pissvids.png
div.modal-content > div.row > div.col-sm-auto > img `div.modal-content > div.row > div.col-sm-auto > img`	pissvids.com/assets/img/agree18/pissvids.jpg
div.container-fluid > div.banner > a > img.d-lg-none `div.container-fluid > div.banner > a > img.d-lg-none`

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●Avoid long main-thread tasks 11 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 200 ms

●Server Backend Latencies 240 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 200 ms

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
PissVids.com, All The Piss You Need! This website contains age-restricted mater… `body.__blur-thumbnails > div#agree18`

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

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
header#header > div.container-fluid > div.header__row > button#menu-btn `header#header > div.container-fluid > div.header__row > button#menu-btn`
div.header__row > div.header__search > div.input-group > button.btn `div.header__row > div.header__search > div.input-group > button.btn`
div.header__row > div.header__search > div.input-group > button.btn `div.header__row > div.header__search > div.input-group > button.btn`

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
div.container-fluid > div.banner > a > img.d-lg-none `div.container-fluid > div.banner > a > img.d-lg-none`

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
header#header > div.container-fluid > div.header__row > a.header__logo `header#header > div.container-fluid > div.header__row > a.header__logo`
body.__blur-thumbnails > footer.footer > div.container-fluid > a.footer__logo `body.__blur-thumbnails > footer.footer > div.container-fluid > a.footer__logo`

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
ACCESS NOW `div.container-fluid > div.header__row > div.join-now > a.js-show-guest`
I agree, ENTER PissVids `div.row > div.col-sm > div.text-center > a.btn`

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
here `footer.footer > div.container-fluid > p.mb-10 > a`

These are opportunities to improve the legibility of your content.

○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

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

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

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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 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 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.

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

○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

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
div.modal-content > div.row > div.col-sm-auto > img `div.modal-content > div.row > div.col-sm-auto > img`	pissvids.com/assets/img/agree18/pissvids.jpg	150 x 210	150 x 210	225 x 315

●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

●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

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

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

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
div.container-fluid > div.banner > a > img.d-lg-none `div.container-fluid > div.banner > a > img.d-lg-none`

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 have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`