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.

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.000633] map[node:map[boundingRect:map[bottom:184 height:34 left:532 right:818 top:150 width:286] lhId:page-2-DIV nodeLabel:The Next Evolution of Your Profile path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,2,MAIN,0,SECTION,0,DIV,0,DIV selector:main > section.hero-section > div.hero-content > div.hero-badge snippet:<div class="hero-badge"> type:node] score:0.000574] map[node:map[boundingRect:map[bottom:184 height:34 left:532 right:818 top:150 width:286] lhId:page-2-DIV nodeLabel:The Next Evolution of Your Profile path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,2,MAIN,0,SECTION,0,DIV,0,DIV selector:main > section.hero-section > div.hero-content > div.hero-badge snippet:<div class="hero-badge"> type:node] score:5.9e-05 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1411 height:553 left:227 right:1123 top:858 width:896] lhId:page-0-IMG nodeLabel:AI Twin Example - Virtual Brad chatbot interface path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,2,MAIN,0,SECTION,0,DIV,5,DIV,0,DIV,1,IMG selector:div.hero-content > div.hero-image-container > div.browser-window > img.hero-image snippet:<img src="https://about.me/s3/h/z/brad2.eb6fda1e.jpg" alt="AI Twin Example - Virtual Brad chatbot interface" class="hero-image"> type:node]]] type:subitems]]]

items: [map[node:map[type:text value:Total] score:0.144555] map[node:map[boundingRect:map[bottom:512 height:496 left:16 right:416 top:16 width:400] lhId:page-1-WEBCHAT-BOX nodeLabel:Chat with Ami, the About Me Virtual Twin guide We respond immediately Ami: Hi, … path:1,HTML,1,BODY,0,WEBCHAT-ROOT,0,DIV,0,WEBCHAT-BOX selector:body > webchat-root#webchat-root > div.chat-box-container-full > webchat-box.chat-box snippet:<webchat-box _ngcontent-ng-c3579468556="" _nghost-ng-c895854865="" role="dialog" aria-labelledby="webchat-title" tabindex="-1" class="chat-box chat-box--right chat-box--not-embedded full-view" style="position: relative; --primary-color: #010101; --text-color: white;" aria-modal="true"> type:node] score:0.078104] map[node:map[boundingRect:map[bottom:512 height:496 left:16 right:416 top:16 width:400] lhId:page-1-WEBCHAT-BOX nodeLabel:Chat with Ami, the About Me Virtual Twin guide We respond immediately Ami: Hi, … path:1,HTML,1,BODY,0,WEBCHAT-ROOT,0,DIV,0,WEBCHAT-BOX selector:body > webchat-root#webchat-root > div.chat-box-container-full > webchat-box.chat-box snippet:<webchat-box _ngcontent-ng-c3579468556="" _nghost-ng-c895854865="" role="dialog" aria-labelledby="webchat-title" tabindex="-1" class="chat-box chat-box--right chat-box--not-embedded full-view" style="position: relative; --primary-color: #010101; --text-color: white;" aria-modal="true"> type:node] score:0.043288] map[node:map[boundingRect:map[bottom:940 height:600 left:918 right:1350 top:340 width:432] lhId:page-3-IFRAME nodeLabel:body > iframe#webchat-floating-iframe-0935a23f-1ecd-11ef-887e-6655165221ea path:1,HTML,1,BODY,5,IFRAME selector:body > iframe#webchat-floating-iframe-0935a23f-1ecd-11ef-887e-6655165221ea snippet:<iframe id="webchat-floating-iframe-0935a23f-1ecd-11ef-887e-6655165221ea" data-widget-id="0935a23f-1ecd-11ef-887e-6655165221ea" allowtransparency="true" srcdoc="<!doctype html><html><head><meta charset="utf-8"/><meta name="viewport" co…" style="position: fixed; bottom: 0px; right: 0px; z-index: 2147483639;"> type:node] score:0.023163]]

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
about.me/s3/h/fonts/ca0cad13/aboutme-glyphs.woff2	40 ms
about.me/s3/h/fonts/f86d67b9/proxima_nova_bold-punc.woff2	40 ms
about.me/s3/h/fonts/da65b0a1/proxima_nova_reg-punc.woff2	40 ms
about.me/s3/h/fonts/0029417e/proximanova-light-webfont.woff2	40 ms
about.me/s3/h/fonts/83259c64/proximanova-regular-webfont.woff2	35 ms
about.me/s3/h/fonts/655552e3/proximanova-bold-webfont.woff2	30 ms
about.me/s3/h/fonts/e05ad036/proxima_nova_reg-latin-a.woff2	25 ms
about.me/s3/h/fonts/d961aea1/proxima_nova_bold-latin-a.woff2	20 ms
/af/bcdde2/00000000000000003b9af1d8/27/l?primer=7cdcb44be...	5.0 ms

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
AI Twin Example - Virtual Brad chatbot interface `div.hero-content > div.hero-image-container > div.browser-window > img.hero-image`	about.me/s3/h/z/brad2.eb6fda1e.jpg	372.9 KiB	313.8 KiB
div.chat-box-header > div.chat-box-avatar > glxy-avatar.glxy-avatar > div.avatar-wrapper `div.chat-box-header > div.chat-box-avatar > glxy-avatar.glxy-avatar > div.avatar-wrapper`	/grBnTepO8FUXYK6NMDccuESRBPLcmKulv0Xa_ZU1VCBZ49yjRWQNE50D...	151.2 KiB	125.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

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
use.typekit.net/geu7rrs.css	929 B	202 ms
/p.css?s=1&k=geu7rrs&ht=tk&f=32862.32864.32869&a=41&app=t...	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-cgi/image/q=85,dpr=2,f=auto,fit=contain,w=1200,h=177...	14400.0 s	231.0 KiB
/grBnTepO8FUXYK6NMDccuESRBPLcmKulv0Xa_ZU1VCBZ49yjRWQNE50D...	86400.0 s	151.6 KiB
/cdn-cgi/image/q=85,dpr=2,f=auto,fit=cover,w=620,h=413.33...	14400.0 s	49.0 KiB
dna8twue3dlxq.cloudfront.net/js/profitwell.js	14400.0 s	9.7 KiB
/cdn-cgi/image/q=85,dpr=2,f=auto,fit=cover,w=120,h=120,gr...	14400.0 s	6.7 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
connect.facebook.net/en_US/all.js?_=1776799402564	1200.0 s	1.8 KiB
/track?category=abtest&name=20230206_less_branding&auth=4...	0.0 ms	441 B
/track?category=metrics_signup&name=homepage%3Avisit&auth...	0.0 ms	58 B
/p.css?s=1&k=geu7rrs&ht=tk&f=32862.32864.32869&a=41&app=t...	604800.0 s	172 B

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

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
Chat with Ami, the About Me Virtual Twin guide We respond immediately Ami: Hi, … `body > webchat-root#webchat-root > div.chat-box-container-full > webchat-box.chat-box`	0.078
Chat with Ami, the About Me Virtual Twin guide We respond immediately Ami: Hi, … `body > webchat-root#webchat-root > div.chat-box-container-full > webchat-box.chat-box`	0.043
body > iframe#webchat-floating-iframe-0935a23f-1ecd-11ef-887e-6655165221ea `body > iframe#webchat-floating-iframe-0935a23f-1ecd-11ef-887e-6655165221ea`	0.023
The Next Evolution of Your Profile `main > section.hero-section > div.hero-content > div.hero-badge`	0.001
The Next Evolution of Your Profile `main > section.hero-section > div.hero-content > div.hero-badge`	0.000

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.

Estimated savings: 110 ms 763.8 KiB

URL	Transfer Size	Est Savings
cdn.apigateway.co/webchat-client.9223372035079267717.prod/chunk-PL5FAMYB.js	350.1 KiB	253.2 KiB
about.me/s3/h/7f668360.bundle.js	287.6 KiB	155.9 KiB
cdn.apigateway.co/webchat-client.9223372035079267717.prod/chunk-VJ22TLJQ.js	150.6 KiB	84.7 KiB
accounts.google.com/gsi/client?_=1776799402565	95.6 KiB	74.9 KiB
www.googletagmanager.com/gtag/js?id=G-LE3EMX7RDC	157.7 KiB	61.3 KiB
connect.facebook.net/en_US/all.js?hash=9c14cb89f82536b5d0b8ca26bf5baed9	82.4 KiB	53.4 KiB
cdn.apigateway.co/webchat-client.9223372035079267717.prod/chunk-4OIETVVK.js	45.8 KiB	36.3 KiB
cdn.apigateway.co/webchat-client.9223372035079267717.prod/chunk-FHEY42TO.js	25.0 KiB	22.7 KiB
cdn.apigateway.co/webchat-client.9223372035079267717.prod/chunk-SL74ZQ2Q.js	67.3 KiB	21.5 KiB

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 69.9 KiB

URL	Transfer Size	Est Savings
undefined?6177-0	37.6 KiB	30.8 KiB
undefined?24772-0	30.4 KiB	21.8 KiB
undefined?83347-0	13.6 KiB	10.9 KiB
undefined?76452-0	5.3 KiB	3.5 KiB
undefined?32778-0	3.4 KiB	2.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 96.1 KiB

URL	Transfer Size	Est Savings
undefined?6177-0	37.6 KiB	36.9 KiB
undefined?24772-0	30.4 KiB	28.3 KiB
.glyph-addon:before{content:"\e855"} …	26.7 KiB	19.8 KiB
undefined?83347-0	13.6 KiB	11.0 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
about.me/s3/h/z/brad2.eb6fda1e.jpg	373.7 KiB
cdn.apigateway.co/webchat-client.9223372035079267717.prod/chunk-PL5FAMYB.js	350.1 KiB
about.me/s3/h/7f668360.bundle.js	288.1 KiB
/cdn-cgi/image/q=85,dpr=2,f=auto,fit=contain,w=1200,h=177...	231.0 KiB
www.googletagmanager.com/gtag/js?id=G-LE3EMX7RDC	158.0 KiB
/grBnTepO8FUXYK6NMDccuESRBPLcmKulv0Xa_ZU1VCBZ49yjRWQNE50D...	151.6 KiB
cdn.apigateway.co/webchat-client.9223372035079267717.prod/chunk-VJ22TLJQ.js	150.6 KiB
about.me/s3/h/c68ce64e.bundle.js	133.7 KiB
about.me/s3/h/5d35ea1d.bundle.js	97.5 KiB
accounts.google.com/gsi/client?_=1776799402565	96.4 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
AI Twin Example - Virtual Brad chatbot interface `div.hero-content > div.hero-image-container > div.browser-window > img.hero-image`	about.me/s3/h/z/brad2.eb6fda1e.jpg

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

●Max Potential First Input Delay 110 ms

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●User Timing marks and measures 45 user timings

●JavaScript execution time 0.8 s

●Minimizes main-thread work 1.4 s

●Avoid long main-thread tasks 4 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 300 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 200 ms

○INP breakdown

○LCP request discovery

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

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
about.me/bfeld `div.browser-window > div.browser-header > div.browser-url-bar > span.browser-url`
Visit my website `div.body-content > section.spotlight > a.button > span.text`
EDUCATION `section.meta > ul.meta-sections > li.meta-section > div.meta-header`
© 2026 about.me™ `div.structure > section.bottom-row > p > span.copyright`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mini-profile-frame > div.mini-profile > div.profile > iframe `div.mini-profile-frame > div.mini-profile > div.profile > iframe`
div.mini-profile-frame > div.mini-profile > div.profile > iframe `div.mini-profile-frame > div.mini-profile > div.profile > iframe`
div.mini-profile-frame > div.mini-profile > div.profile > iframe `div.mini-profile-frame > div.mini-profile > div.profile > iframe`
div.mini-profile-frame > div.mini-profile > div.profile > iframe `div.mini-profile-frame > div.mini-profile > div.profile > iframe`

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.

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
Don't just show who you are. `section.feature-cards-section > div.feature-cards-grid > div.feature-card > h3`
Create your page once `div.features-steps > div.features-step > 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>`

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

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

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

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

○Form elements have associated labels

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

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