Skip to content
https://designrush.com

Lighthouse Desktop

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

93

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.

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
Looking to Hire an Agency? - How It Works div.inner > div.video-box > figure.js-show-video-box > img
www.designrush.com/topbest/images/webp/homepage/about-video-placeholder.webp89.2 KiB62.2 KiB
The Conversation Keeper, pictured alongside a jar of Prego sauce, pasta noodles… aside.d-flex > a.item > div.item-img > img
/articles/1022808/conversions/prego-storycorps-conversati...67.1 KiB55.5 KiB
The new American Dew section.d-flex > a.item > div.item-img > img
/articles/1023073/conversions/Mountain-Dew-TGS48-details_...32.4 KiB27.2 KiB
Two women in a yellow car section.d-flex > a.item > div.item-img > img
/articles/1024058/conversions/banana-boat-details_mobile-...21.6 KiB16.4 KiB
Allbirds Drops Sustainability and Sneakers to Become NewBird AI section.d-flex > a.item > div.item-img > img
/articles/1024277/conversions/allbirds-wool-runner-detail...18.8 KiB13.6 KiB
Infographic showing digital video ad growth: $72B spend by 2025, 60% of TV/vide… section.d-flex > a.item > div.item-img > img
/articles/1024127/conversions/The-Power-of-Video-in-Produ...15.0 KiB9.8 KiB
Huckberry's Behind the Brand Exclusive Look Inside Nike ACG section.d-flex > a.item > div.item-img > img
/articles/1024130/conversions/nike-ldv-sneaker-huckberry-...14.9 KiB9.7 KiB
Lounge Lizard div.item > div.item-logo > a.gtm-logo > img
/agencies/993021/conversions/Lounge-Lizard-logo-profile-w...7.7 KiB6.5 KiB
A screenshot from Nissan's "Happy Chaos" ad showing a father buckling his cryin… section.d-flex > a.item > div.item-img > img
/articles/1024266/conversions/2026-nissan-rogue-happy-cha...9.9 KiB6.1 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.

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: 369 ms
URLTime Spent
designrush.com/369 ms
www.designrush.com/0.0 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 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.

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

●Max Potential First Input Delay 70 ms
●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 1,589 KiB
●User Timing marks and measures 5 user timings
●JavaScript execution time 0.3 s
●Minimizes main-thread work 1.6 s
●Avoid long main-thread tasks 1 long task found
●Avoid non-composited animations 82 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 170 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 450 ms
●Avoid large layout shifts 3 layout shifts found
○INP breakdown
78

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
LATEST AI CREATIVE MARKETING ECOMMERCE TECHNOLOGY section.hp--trending > div.site-width-grid > nav.d-flex > ul.d-flex
Featured Services Branding & Creative Website & Interface Marketing Software & … aside.fl-grow > nav.d-flex > div.types > ul.d-flex

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
LATEST ul.d-flex > li > h3 > button#trending-tab-latest
AI ul.d-flex > li > h3 > button#trending-tab-artificial-intelligence
CREATIVE ul.d-flex > li > h3 > button#trending-tab-creative
MARKETING ul.d-flex > li > h3 > button#trending-tab-marketing
ECOMMERCE ul.d-flex > li > h3 > button#trending-tab-ecommerce
TECHNOLOGY ul.d-flex > li > h3 > button#trending-tab-tech
Featured Services div.types > ul.d-flex > li > button#agency-tab-featured
Branding & Creative div.types > ul.d-flex > li > button#agency-tab-category-branding-creative
Website & Interface div.types > ul.d-flex > li > button#agency-tab-dashboard-design
Marketing div.types > ul.d-flex > li > button#agency-tab-category-marketing
Software & App div.types > ul.d-flex > li > button#agency-tab-digital-design-agencies
IT Services div.types > ul.d-flex > li > button#agency-tab-category-technology
Business Services div.types > ul.d-flex > li > button#agency-tab-business-services

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.

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
ID div.d-flex > div.info > dl.id > dt
15036 div.info > dl.id > dd > strong
ID div.d-flex > div.info > dl.id > dt
37018 div.info > dl.id > dd > strong
ID div.d-flex > div.info > dl.id > dt
37017 div.info > dl.id > dd > strong
ID div.d-flex > div.info > dl.id > dt
15035 div.info > dl.id > dd > strong
APR 2026 div.item > div.item-inner > div.item-ribbon > time.d-i-flex
GOLD WINNER div.item > div.item-inner > div.item-ribbon > mark.d-i-flex
APR 2026 div.item > div.item-inner > div.item-ribbon > time.d-i-flex
BRONZE WINNER div.item > div.item-inner > div.item-ribbon > mark.d-i-flex

These are opportunities to improve the legibility of your content.

Names and labels

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
section.section > div.list > div.item > a section.section > div.list > div.item > a
section.section > div.list > div.item > a section.section > div.list > div.item > a
section.section > div.list > div.item > a section.section > div.list > div.item > a
section.section > div.list > div.item > a section.section > div.list > div.item > a
section.section > div.list > div.item > a section.section > div.list > div.item > a
section.section > div.list > div.item > a section.section > div.list > div.item > a
section.section > div.list > div.item > a section.section > div.list > div.item > a
section.section > div.list > div.item > a section.section > div.list > div.item > a
section.section > div.list > div.item > a section.section > div.list > div.item > a
section.section > div.list > div.item > a section.section > div.list > div.item > a
section.section > div.list > div.item > a section.section > div.list > div.item > a
section.section > div.list > div.item > a section.section > div.list > div.item > a
section.section > div.list > div.item > a section.section > div.list > div.item > a

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
LATEST div.site-width-grid > nav.d-flex > ul.d-flex > li
AI div.site-width-grid > nav.d-flex > ul.d-flex > li
CREATIVE div.site-width-grid > nav.d-flex > ul.d-flex > li
MARKETING div.site-width-grid > nav.d-flex > ul.d-flex > li
ECOMMERCE div.site-width-grid > nav.d-flex > ul.d-flex > li
TECHNOLOGY div.site-width-grid > nav.d-flex > ul.d-flex > li
Featured Services nav.d-flex > div.types > ul.d-flex > li
Branding & Creative nav.d-flex > div.types > ul.d-flex > li
Website & Interface nav.d-flex > div.types > ul.d-flex > li
Marketing nav.d-flex > div.types > ul.d-flex > li
Software & App nav.d-flex > div.types > ul.d-flex > li
IT Services nav.d-flex > div.types > ul.d-flex > li
Business Services nav.d-flex > div.types > ul.d-flex > li

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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.

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
LOG IN div#headerMenu > div.inner > div.user > a.user-login
Prego, StoryCorps Invite Families to Record Dinner Conversations div.holder > div#trending-panel-latest > aside.d-flex > a.item
Allbirds Sells Its Footwear Brand, Pivots to NewBird AI div.holder > div#trending-panel-latest > section.d-flex > a.item
Nissan Turns Family Chaos Into Sound-Led Story for Rogue div.holder > div#trending-panel-latest > section.d-flex > a.item
Banana Boat Invites Americans to Head Outdoors in Summer Campaign div.holder > div#trending-panel-latest > section.d-flex > a.item
Nike Brings Back LDV Sneaker With Huckberry Documentary div.holder > div#trending-panel-latest > section.d-flex > a.item
Amazon Fire TV Targets $72B Market With AY OK, Colormatics Campaign div.holder > div#trending-panel-latest > section.d-flex > a.item
Mountain Dew Revisits Roots in ‘An American Original’ Campaign div.holder > div#trending-panel-latest > section.d-flex > a.item
○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
●`button`, `link`, and `menuitem` elements have accessible names
●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
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●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>`).
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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
○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
○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.
77

Best Practices

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 / WarningSource
AttributionReporting

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: net::ERR_NAME_NOT_RESOLVED
●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
●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 DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○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`

Send Feedback