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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
/wp-content/themes/a16z/assets/compiled/vite/assets/vite-...	180 ms

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

nodeLabel: div.wr25-w1 > main.wr25-main > div.before:bg-fade-black > video#home-video

path: 1,HTML,1,BODY,1,DIV,0,DIV,3,MAIN,0,DIV,0,VIDEO

selector: div.wr25-w1 > main.wr25-main > div.before:bg-fade-black > video#home-video

snippet: <video id="home-video" autoplay="" muted="" loop="" playsinline="" preload="auto" poster="https://a16z.com/wp-content/themes/a16z/assets/images/wr25/bg-homepage.jpg" aria-hidden="true">

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
a16z.com/wp-content/themes/a16z/assets/compiled/vite/css/vite-core-css.css	69.7 KiB	124 ms
/wp-content/plugins/a16z-better-click-to-tweet/assets/css...	626 B
use.typekit.net/fut6uin.css	934 B	204 ms
/p.css?s=1&k=fut6uin&ht=tk&f=28977.28982.28991&a=6043753&...	172 B	201 ms

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
cdn.jsdelivr.net/npm/algoliasearch@4/dist/algoliasearch-lite.umd.js	604800.0 s	5.4 KiB
/p.css?s=1&k=fut6uin&ht=tk&f=28977.28982.28991&a=6043753&...	604800.0 s	172 B
d1lamhf6l6yk6d.cloudfront.net/uploads/2026/03/fundraise-landscape.webm	0.0 ms	0 B

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
div.wr25-w1 > main.wr25-main > div.before:bg-fade-black > video#home-video `div.wr25-w1 > main.wr25-main > div.before:bg-fade-black > video#home-video`	a16z.com/wp-content/themes/a16z/assets/images/wr25/bg-homepage.jpg	117.2 KiB	5.1 KiB

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

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: 80 ms 67.6 KiB

URL	Transfer Size	Est Savings
a16z.com/wp-content/themes/a16z/assets/compiled/vite/css/vite-core-css.css	69.6 KiB	67.6 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
d1lamhf6l6yk6d.cloudfront.net/uploads/2026/03/fundraise-landscape.webm	6.9 MiB
a16z.com/wp-content/themes/a16z/assets/images/wr25/bg-homepage.jpg	117.3 KiB
a16z.com/wp-content/themes/a16z/assets/compiled/vite/css/vite-core-css.css	69.7 KiB
/wp-content/themes/a16z/assets/compiled/vite/assets/vite-...	40.1 KiB
/wp-content/themes/a16z/assets/compiled/vite/assets/vite-...	39.1 KiB
a16z.com/wp-content/themes/a16z/assets/compiled/vite/js/vite-homepage.js	27.7 KiB
a16z.com/wp-content/themes/a16z/assets/compiled/vite/js/vite-index.js	26.4 KiB
a16z.com/wp-content/themes/a16z/assets/compiled/vite/js/vite-core.js	25.3 KiB
a16z.com/	20.0 KiB
/wp-content/themes/a16z/assets/compiled/vite/assets/vite-...	17.7 KiB

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

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.0 s

●Max Potential First Input Delay 30 ms

●Minify CSS

●Minify JavaScript

●Reduce unused JavaScript

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.9 s

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 0 ms

●Server Backend Latencies 120 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 140 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

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.

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
div#wr25-header > div.wr25-header-navbar > div.wr25-header-navbar--inner > button#header-menu-button `div#wr25-header > div.wr25-header-navbar > div.wr25-header-navbar--inner > button#header-menu-button`
div#wr25-header > div.wr25-header-navbar > div.wr25-header-navbar--inner > button#header-search-button `div#wr25-header > div.wr25-header-navbar > div.wr25-header-navbar--inner > button#header-search-button`
main.wr25-main > div.min-h-[100vh] > div.w-full > button#home-icon-sound `main.wr25-main > div.min-h-[100vh] > div.w-full > button#home-icon-sound`

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
div.wr25-header-navbar > div.wr25-header-navbar--inner > div.wr25-logo > a.logo `div.wr25-header-navbar > div.wr25-header-navbar--inner > div.wr25-logo > a.logo`
div.flex > ul.flex > li > a.icon-twitter `div.flex > ul.flex > li > a.icon-twitter`
div.flex > ul.flex > li > a.icon-linkedin `div.flex > ul.flex > li > a.icon-linkedin`
div.flex > ul.flex > li > a.icon-facebook-a `div.flex > ul.flex > li > a.icon-facebook-a`
div.flex > ul.flex > li > a.icon-instagram `div.flex > ul.flex > li > a.icon-instagram`
div.flex > ul.flex > li > a.icon-youtube-alt `div.flex > ul.flex > li > a.icon-youtube-alt`
div.flex > ul.flex > li > a.icon-substack `div.flex > ul.flex > li > a.icon-substack`

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.

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.

○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

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○Heading elements appear in a sequentially-descending order

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

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

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

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

●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

○Use a strong HSTS policy

○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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid

○Image elements have `[alt]` attributes