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.

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
nu11cyber.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/1eec422858ff/main.js?	14400.0 s	10.9 KiB
/beacon.min.js/v833ccba57c9e4d2798f2e76cebdd09a1177817227...	86400.0 s	11.4 KiB
beavercheck.com/badge?url=https%3A%2F%2Fnu11cyber.com	3600.0 s	1.3 KiB

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.14238399999999998] map[node:map[boundingRect:map[bottom:1202 height:111 left:0 right:412 top:1091 width:412] lhId:page-2-FOOTER nodeLabel:© 2026 Nu11Cyber. All rights reserved. 隐私政策 · 服务条款 · Cookie · 无障碍 · 联系… path:1,HTML,1,BODY,4,FOOTER selector:body > footer#static-footer snippet:<footer id="static-footer" class="static-footer"> type:node] score:0.134872] map[node:map[boundingRect:map[bottom:5 height:10 left:-15 right:-5 top:-5 width:10] lhId:page-3-::before nodeLabel:div#root > div.app-shell > div.waves > ::before path:1,HTML,1,BODY,1,DIV,0,DIV,0,DIV,0,::before selector:div#root > div.app-shell > div.waves > ::before snippet:<::before> type:node] score:0.007512]]

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.

	URL	Resource Size	Est Savings
Nu11Cyber logo `div.page-grid > section.ops-hero > div.hero-logo-panel > img`	nu11cyber.com/nu11-logo-transparent.png	48.5 KiB	10.4 KiB
DMCA.com Protection Status `footer#static-footer > div.static-footer-badges > a.dmca-badge > img`	/Badges/dmca_protected_8_120.png?ID=61bc9d91-68a2-4ea3-9c...	5.3 KiB	4.4 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:674.196 label:Time to first byte subpart:timeToFirstByte] map[duration:1460.766 label:Resource load delay subpart:resourceLoadDelay] map[duration:1021.523 label:Resource load duration subpart:resourceLoadDuration] map[duration:68.029 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: Nu11Cyber logo

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

selector: div.page-grid > section.ops-hero > div.hero-logo-panel > img

snippet: <img src="/nu11-logo-transparent.png" alt="Nu11Cyber logo" width="280" height="280">

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: Nu11Cyber logo

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

selector: div.page-grid > section.ops-hero > div.hero-logo-panel > img

snippet: <img src="/nu11-logo-transparent.png" alt="Nu11Cyber logo" width="280" height="280">

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
nu11cyber.com/assets/style-QBX_CkpW.css	13.9 KiB	320 ms
unpkg.com/react-dom@18.3.1/umd/react-dom.production.min.js	42.3 KiB	781 ms
unpkg.com/react@18.3.1/umd/react.production.min.js	4.6 KiB	777 ms

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: 528 ms

URL	Time Spent
nu11cyber.com/	628 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
© 2026 Nu11Cyber. All rights reserved. 隐私政策 · 服务条款 · Cookie · 无障碍 · 联系… `body > footer#static-footer`	0.135
div#root > div.app-shell > div.waves > ::before `div#root > div.app-shell > div.waves > ::before`	0.008

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.

Diagnostics

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
Other	3.0 s
Script Evaluation	879 ms
Style & Layout	387 ms
Rendering	127 ms
Garbage Collection	42 ms
Script Parsing & Compilation	24 ms
Parse HTML & CSS	15 ms

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

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

●Time to Interactive 3.6 s

●Optimize DOM size

●Font display

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 340 KiB

●JavaScript execution time 0.8 s

●Avoid long main-thread tasks 2 long tasks found

●Avoid non-composited animations 1 animated element found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 250 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

○INP breakdown

○User Timing marks and measures

100

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.

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

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

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

●Buttons have an accessible name

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

●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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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

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

○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

○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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
DMCA.com Protection Status `footer#static-footer > div.static-footer-badges > a.dmca-badge > img`	/Badges/dmca_protected_8_120.png?ID=61bc9d91-68a2-4ea3-9c...	120 x 30 (4.00)	120 x 46 (2.61)
BeaverCheck Score `footer#static-footer > div.static-footer-badges > a > img`	beavercheck.com/badge?url=https%3A%2F%2Fnu11cyber.com	88 x 31 (2.84)	125 x 20 (6.25)

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 / Warning	Source
SharedStorage	nu11cyber.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	nu11cyber.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	nu11cyber.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

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
nu11cyber.com/	`Access to script at 'https://images.dmca.com/Badges/DMCABadgeHelper.min.js' from origin 'https://nu11cyber.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
images.dmca.com/Badges/DMCABadgeHelper.min.js	`Failed to load resource: net::ERR_FAILED`
nu11cyber.com/n1Cy/v1/auth/refresh	`Failed to load resource: the server responded with a status of 401 ()`
nu11cyber.com/n1Cy/v1/bookmarks	`Failed to load resource: the server responded with a status of 401 ()`
nu11cyber.com/n1Cy/v1/auth/refresh	`Failed to load resource: the server responded with a status of 401 ()`
nu11cyber.com/ line 13, col 0	`The Content Security Policy directive 'frame-ancestors' is ignored when delivered via a <meta> element.`
nu11cyber.com/ line 93, col 602	`The Content Security Policy directive 'frame-ancestors' is ignored when delivered via a <meta> element.`
nu11cyber.com/ line 93, col 602	`The Content Security Policy directive 'frame-ancestors' is ignored when delivered via a <meta> element.`
nu11cyber.com/cdn-cgi/challenge-platform/scripts/jsd/main.js	`The Content Security Policy directive 'frame-ancestors' is ignored when delivered via a <meta> element.`
nu11cyber.com/cdn-cgi/challenge-platform/scripts/jsd/main.js	`The Content Security Policy directive 'frame-ancestors' is ignored when delivered via a <meta> element.`

●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

●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

●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

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`