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.

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
northe.runasp.net/icons/icon-512.png	300.0 s	11.7 KiB

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:59.054 source:map[column:19726 line:4 type:source-location url:https://northe.runasp.net/chunk-5CLS555X.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:31.524 source:map[column:425 line:0 type:source-location url:https://northe.runasp.net/chunk-WQFSAHGL.js urlProvider:network]] map[reflowTime:58.603 source:map[column:22837 line:0 type:source-location url:https://northe.runasp.net/main-6YIQ5DE6.js urlProvider:network]] map[reflowTime:0.451 source:map[column:51944 line:0 type:source-location url:https://northe.runasp.net/main-6YIQ5DE6.js urlProvider:network]] map[reflowTime:1.593 source:map[type:text value:[unattributed]]]]

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
Crew Neck Tee - White `article.group > a.block > div.relative > img.object-cover`	/photo-1521572163474-6864f9cf17ab?w=1920&q=80&auto=format...	59.3 KiB	57.3 KiB
Shirts `div.grid > app-category-slideshow-card > a.group > img.object-cover`	/photo-1602810319428-019690571b5b?w=384&q=80&auto=format&...	26.9 KiB	18.9 KiB
body > div#northe-boot-splash > img.northe-splash__icon `body > div#northe-boot-splash > img.northe-splash__icon`	northe.runasp.net/icons/icon-512.png	11.6 KiB	10.7 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:568.224 label:Time to first byte subpart:timeToFirstByte] map[duration:1504.677 label:Resource load delay subpart:resourceLoadDelay] map[duration:139.044 label:Resource load duration subpart:resourceLoadDuration] map[duration:607.925 label:Element render delay subpart:elementRenderDelay]]

lhId: page-3-IMG

nodeLabel: Modern menswear

path: 1,HTML,1,BODY,1,APP-ROOT,1,APP-MAIN-LAYOUT,1,MAIN,1,APP-HOME,0,APP-HERO,0,SECTION,0,DIV,0,IMG

selector: app-hero > section.relative > div.relative > img.object-cover

snippet: <img _ngcontent-ng-c3776823550="" ngsrc="https://images.unsplash.com/photo-1516257984-b1b4d707412e" alt="Modern menswear" fill="" priority="" sizes="100vw" class="object-cover object-center" loading="eager" fetchpriority="high" decoding="sync" ng-img="true" src="https://images.unsplash.com/photo-1516257984-b1b4d707412e?w=1920&q=80&auto…" srcset="https://images.unsplash.com/photo-1516257984-b1b4d707412e?w=640&q=80&auto=…" style="position: absolute; width: 100%; height: 100%; inset: 0px;">

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: Modern menswear

path: 1,HTML,1,BODY,1,APP-ROOT,1,APP-MAIN-LAYOUT,1,MAIN,1,APP-HOME,0,APP-HERO,0,SECTION,0,DIV,0,IMG

selector: app-hero > section.relative > div.relative > img.object-cover

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

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

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

Diagnostics

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: 200 ms 32.8 KiB

URL	Transfer Size	Est Savings
northe.runasp.net/chunk-5CLS555X.js	98.0 KiB	32.8 KiB

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

URL	Transfer Size	Est Savings
northe.runasp.net/styles-TQQNEC7B.css	19.7 KiB	13.0 KiB

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

●Time to Interactive 2.1 s

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Max Potential First Input Delay 70 ms

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 8 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 1.4 s

●Avoid long main-thread tasks 5 long tasks found

●Avoid non-composited animations 9 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 20 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 170 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

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
CASH ON DELIVERY `div.usp-track > a.usp-item > span.min-w-0 > span.usp-label`
Pay at your door `div.usp-track > a.usp-item > span.min-w-0 > span.block`
NEWSLETTER `div.py-14 > div.grid > div.lg:col-span-7 > p.text-eyebrow`
easypaisa `div.order-1 > ul.flex > li.pay-badge > span.pay-mark`

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NEED HELP? `app-root > app-main-layout > app-whatsapp-float > a.fixed`

○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

●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

●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

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

●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

○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

○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

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

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

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