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.

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

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
cdn.tailwindcss.com/3.4.17	123.9 KiB	791 ms
www.vcsift.com/wp-content/themes/vcsift/assets/css/main.css?ver=1.0.0	4.5 KiB	251 ms
www.vcsift.com/wp-content/themes/vcsift/assets/js/main.js?ver=1.0.0	1.8 KiB
fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&display=swap	1.2 KiB	817 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
www.vcsift.com/wp-content/themes/vcsift/assets/css/main.css?ver=1.0.0	0.0 ms	4.5 KiB
www.vcsift.com/wp-content/themes/vcsift/assets/js/main.js?ver=1.0.0	0.0 ms	1.8 KiB

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: 0.0 ms 39.7 KiB

URL	Transfer Size	Est Savings
cdn.tailwindcss.com/	123.6 KiB	39.7 KiB

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

●Time to Interactive 3.2 s

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 194 KiB

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.1 s

●Avoid long main-thread tasks 4 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 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 110 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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.max-w-6xl > div.relative > div.flex > button.md:hidden `div.max-w-6xl > div.relative > div.flex > button.md:hidden`

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.

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
3-day free trial · No credit card required `section > div.max-w-5xl > div > p`
Investors `div.max-w-5xl > div > div > div`
Email addresses `div.max-w-5xl > div > div > div`
Countries `div.max-w-5xl > div > div > div`
Data updates `div.max-w-5xl > div > div > div`
LIVE PREVIEW `section > div.max-w-5xl > div > p`
vcsift.com/search `div.max-w-5xl > div > div > div`
Search by name, firm, location… `div > div > div > span`
+ Filter `div > div > div > div`
2,841 investors `div > div > div > span`
SC `div > div.investor-card > div.flex > div.investor-avatar`
SaaS `div.flex > div.flex-1 > div.flex > span.tag-badge`
VC Firm `div.flex > div.flex-1 > div.flex > span.tag-badge`
PK `div > div.investor-card > div.flex > div.investor-avatar`
Seed `div.flex > div.flex-1 > div.flex > span.tag-badge`
Fintech `div.flex > div.flex-1 > div.flex > span.tag-badge`
VC Firm `div.flex > div.flex-1 > div.flex > span.tag-badge`
Unlock Email `div.flex > div.flex-1 > div.mt-3 > a`
Unlock LinkedIn `div.flex > div.flex-1 > div.mt-3 > a`
STEP 02 `div > div > div > span`
STEP 03 `div > div > div > span`
31k+ `div.max-w-5xl > div > a > span`
28k+ `div.max-w-5xl > div > a > span`
22k+ `div.max-w-5xl > div > a > span`
18k+ `div.max-w-5xl > div > a > span`
15k+ `div.max-w-5xl > div > a > span`
12k+ `div.max-w-5xl > div > a > span`
9k+ `div.max-w-5xl > div > a > span`
8k+ `div.max-w-5xl > div > a > span`
SC `div > div > div > div`
CEO, Series A SaaS `div > div > div > div`
MR `div > div > div > div`
COO, B2B Startup `div > div > div > div`
JP `div > div > div > div`
Head of Fundraising `div > div > div > div`
/ year `div > div > div > span`
3-day free trial `div.max-w-5xl > div > div > div`
/ year `div > div > div > span`
3-day free trial `div.max-w-5xl > div > div > div`
Find & contact 250,000+ VC investors worldwide. `div.max-w-6xl > div.grid > div.col-span-2 > p`
DIRECTORY `div.max-w-6xl > div.grid > div > h4`
PRODUCT `div.max-w-6xl > div.grid > div > h4`
RESOURCES `div.max-w-6xl > div.grid > div > h4`
INVESTMENT STAGE `div > div.grid > div > h4`
TOP SECTORS `div > div.grid > div > h4`
TOP COUNTRIES `div > div.grid > div > h4`
INVESTOR TYPES `div > div.grid > div > h4`
© 2026 VC Sift. All rights reserved. `footer > div.max-w-6xl > div > div`
Privacy `div.max-w-6xl > div > div > a`
Terms `div.max-w-6xl > div > div > a`
Data Removal `div.max-w-6xl > div > div > a`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
DIRECTORY `div.max-w-6xl > div.grid > div > h4`

These are opportunities to improve keyboard navigation in your application.

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

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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Identical links have the same purpose.

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

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

○Image elements have `[alt]` attributes

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

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

○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

●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

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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○Image elements have `[alt]` attributes