Skip to content
https://manuelferrara.com

Lighthouse Mobile

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

72

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.

RequestCache TTLTransfer Size
www.manuelferrara.com/trial_pg/pg_mf_header.jpg0.0 ms2.0 MiB

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.

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
Header body > img.header
www.manuelferrara.com/trial_pg/pg_mf_header.jpg2.0 MiB2.0 MiB

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: Header
path: 1,HTML,1,BODY,0,IMG
selector: body > img.header
snippet: <img src="pg_mf_header.jpg" alt="Header" class="header">

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.

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

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.

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
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
Reduce unused JavaScript
Avoids enormous network payloads Total size was 2,064 KiB
JavaScript execution time 0.0 s
Minimizes main-thread work 0.3 s
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 140 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 140 ms
INP breakdown
User Timing marks and measures
Avoid long main-thread tasks
Avoid non-composited animations
Avoid large layout shifts
90

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
Verify Age body > div.container > div.button-group > a.cta-button
Current Members body > div.container > div.button-group > a.cta-button

These are opportunities to improve the legibility of your content.

Best practices

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-hidden="true"]` is not present on the document `<body>`
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
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.
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
`[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
Buttons have an accessible name
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
Form elements have associated labels
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.
96

Best Practices

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.

SourceDescription
Failed to load resource: the server responded with a status of 404 ()
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 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
83

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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
1<!DOCTYPE html>Syntax not understood
2<html lang="en">Syntax not understood
3<head>Syntax not understood
4 <meta charset="UTF-8">Syntax not understood
5 <meta name="viewport" content="width=device-width, initial-scale=1.0">Syntax not understood
6 <title>ManuelFerrara.com - Age Verification</title>Syntax not understood
7 <link rel="stylesheet" href="styles.css">Syntax not understood
8 <style>Syntax not understood
9 body {Syntax not understood
10 margin: 0;Unknown directive
11 font-family: Arial, sans-serif;Unknown directive
12 background-color: #f4f4f4;Unknown directive
13 color: #333;Unknown directive
14 min-height: 100vh;Unknown directive
15 display: flex;Unknown directive
16 flex-direction: column;Unknown directive
17 justify-content: space-between;Unknown directive
18 align-items: center;Unknown directive
19 padding: 0;Unknown directive
20 box-sizing: border-box;Unknown directive
21 }Syntax not understood
22 .header {Syntax not understood
23 width: 100%;Unknown directive
24 max-width: 100%;Unknown directive
25 height: auto;Unknown directive
26 }Syntax not understood
27 .container {Syntax not understood
28 background-color: rgba(255, 255, 255, 0.9);Unknown directive
29 padding: 20px;Unknown directive
30 border-radius: 8px;Unknown directive
31 box-shadow: 0 4px 8px rgba(0, 0, 0, 0.2);Unknown directive
32 width: 75%;Unknown directive
33 max-width: 1200px;Unknown directive
34 text-align: left;Unknown directive
35 position: absolute;Unknown directive
36 bottom: 25%;Unknown directive
37 left: 50%;Unknown directive
38 transform: translateX(-50%);Unknown directive
39 }Syntax not understood
40 .footer-container {Syntax not understood
41 background-color: rgba(255, 255, 255, 0.9);Unknown directive
42 padding: 15px;Unknown directive
43 border-radius: 8px;Unknown directive
44 box-shadow: 0 4px 8px rgba(0, 0, 0, 0.2);Unknown directive
45 width: 75%;Unknown directive
46 max-width: 1200px;Unknown directive
47 text-align: center;Unknown directive
48 margin-bottom: 5px;Unknown directive
49 }Syntax not understood
50 .footer-container a {Syntax not understood
51 color: #000;Unknown directive
52 text-decoration: underline;Unknown directive
53 margin: 0 5px;Unknown directive
54 }Syntax not understood
55 .footer-container a:hover {Unknown directive
56 text-decoration: underline;Unknown directive
57 }Syntax not understood
58 h1 {Syntax not understood
59 font-size: 24px;Unknown directive
60 color: #000;Unknown directive
61 text-align: center;Unknown directive
62 }Syntax not understood
63 p {Syntax not understood
64 font-size: 16px;Unknown directive
65 margin: 10px 0;Unknown directive
66 }Syntax not understood
67 .cta-button {Syntax not understood
68 display: inline-block;Unknown directive
69 margin-top: 20px;Unknown directive
70 padding: 10px 20px;Unknown directive
71 font-size: 16px;Unknown directive
72 color: #fff;Unknown directive
73 border: none;Unknown directive
74 border-radius: 5px;Unknown directive
75 text-decoration: none;Unknown directive
76 cursor: pointer;Unknown directive
77 transition: background-color 0.3s;Unknown directive
78 }Syntax not understood
79 .cta-button:hover {Unknown directive
80 opacity: 0.9;Unknown directive
81 }Syntax not understood
82 .cta-button.verify-age {Syntax not understood
83 background-color: #28a745;Unknown directive
84 }Syntax not understood
85 .cta-button.current-members {Syntax not understood
86 background-color: #fd7e14;Unknown directive
87 }Syntax not understood
88 .button-group {Syntax not understood
89 display: flex;Unknown directive
90 justify-content: center;Unknown directive
91 gap: 10px;Unknown directive
92 margin-top: 20px;Unknown directive
93 }Syntax not understood
94 @media (max-width: 768px) {Unknown directive
95 .container {Syntax not understood
96 position: relative;Unknown directive
97 margin-top: 10px;Unknown directive
98 width: 95%;Unknown directive
99 }Syntax not understood
100 body {Syntax not understood
101 overflow-x: hidden;Unknown directive
102 }Syntax not understood
103 }Syntax not understood
104 @media (min-width: 769px) {Unknown directive
105 .container {Syntax not understood
106 position: absolute;Unknown directive
107 bottom: 25%;Unknown directive
108 left: 50%;Unknown directive
109 transform: translateX(-50%);Unknown directive
110 }Syntax not understood
111 }Syntax not understood
112 </style>Syntax not understood
114 <script>Syntax not understood
115 document.addEventListener("DOMContentLoaded", function () {Syntax not understood
116 const yearSpan = document.getElementById("current-year");Syntax not understood
117 yearSpan.textContent = new Date().getFullYear();Syntax not understood
118 });Syntax not understood
119 </script>Syntax not understood
121</head>Syntax not understood
122<body>Syntax not understood
123 <img src="pg_mf_header.jpg" alt="Header" class="header">Syntax not understood
124 <div class="container">Syntax not understood
125 <h1>Age Verification Required</h1>Syntax not understood
126 <p>Welcome to <strong>ManuelFerrara.com</strong>!</p>Syntax not understood
127 <p>You’ve been redirected here because your location requires age verification to access adult content on our site.</p>Syntax not understood
128 <p>To comply with local regulations and ensure a safe browsing experience, we must confirm that you are at least 18 years old (or the age of majority in your jurisdiction).</p>Syntax not understood
129 <p><strong>What Happens Next?</strong></p>Syntax not understood
130 <ul>Syntax not understood
131 <li>You will be prompted to complete a quick and secure age verification process.</li>Syntax not understood
132 <li>Once verified, you’ll have unrestricted access to all content on <strong>ManuelFerrara.com</strong>.</li>Syntax not understood
133 </ul>Syntax not understood
134 <p>We appreciate your understanding and cooperation in helping us comply with local laws.</p>Syntax not understood
135 <div class="button-group">Syntax not understood
136 <a href="https://enter.manuelferrara.com/signup/signup.php?nats=MC4wLjcuMTYuMC4wLjAuMC4w&step=2" class="cta-button verify-age">Verify Age</a>Unknown directive
137 <a href="https://www.manuelferrara.com/verifymyage/" class="cta-button current-members">Current Members</a>Unknown directive
138 </div>Syntax not understood
139 </div>Syntax not understood
140 <div class="footer-container">Syntax not understood
141 For billing inquiries, customer support or to cancel your membership, please visit: Unknown directive
142 <a href="#">Support</a> | <a href="#">Contact Us</a> | <a href="#">Terms</a> | <a href="#">Privacy Policy</a> | <a href="#">Report Content</a> | <a href="#">Webmasters</a>Syntax not understood
143 <br>Syntax not understood
144 <a href="https://www.manuelferrara.com/2257.html">18 U.S.C. 2257 Record-Keeping Requirements Compliance Statement</a>Unknown directive
145 <br>Syntax not understood
146 Copyright © 2006 - <span id="current-year">2025</span> ManuelFerrara.com, All Rights ReservedSyntax not understood
147 </div>Syntax not understood
148</body>Syntax not understood
149</html>Syntax not understood

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback