Skip to content
Audit Complete

Results for https://www.figma.com

Visit site
Brazil Brazil · Sao Paulo Completed: Apr 4, 2026 17:25 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C76

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

1

'unsafe-eval' found in script source

Security › Content Security Policy
2

'unsafe-inline' found in script source

Security › Content Security Policy
3

Page weighs 21.3 MB (6.2 MB transferred)

Performance › Page Weight Budget
4

2 link(s) with no accessible text

Accessibility › Link & Button Quality
5

9 image-only link(s) without alt text

Accessibility › Link & Button Quality
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.figma.com)](https://beavercheck.com/results/d4731502-5cbc-42ff-8b5a-536718afb3e9)
<a href="https://beavercheck.com/results/d4731502-5cbc-42ff-8b5a-536718afb3e9"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.figma.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.figma.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

34
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
94
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.92 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

16.52 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

3.36 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.081

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

8.90 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

16.91 s

Detailed Report

Audit breakdown by category with detailed findings.

34

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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.

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:48.179 source:map[column:97922 line:1 type:source-location url:https://www.figma.com/_netlify/_next/static/chunks/3914-2bab184028cadf54.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:10.599 source:map[column:34581 line:0 type:source-location url:https://www.figma.com/_netlify/_next/static/chunks/4529-4e6ca69dcb6eff9e.js urlProvider:network]] map[reflowTime:11.444 source:map[column:55748 line:0 type:source-location url:https://www.figma.com/_netlify/_next/static/chunks/4529-4e6ca69dcb6eff9e.js urlProvider:network]] map[reflowTime:11.235 source:map[column:34027 line:0 type:source-location url:https://www.figma.com/_netlify/_next/static/chunks/4529-4e6ca69dcb6eff9e.js urlProvider:network]] map[reflowTime:10.003 source:map[column:968185 line:0 type:source-location url:https://www.figma.com/_netlify/_next/static/chunks/8992-43f84a35aafd5858.js urlProvider:network]] map[reflowTime:3.125 source:map[column:980031 line:0 type:source-location url:https://www.figma.com/_netlify/_next/static/chunks/8992-43f84a35aafd5858.js urlProvider:network]] map[reflowTime:1.773 source:map[column:37188 line:0 type:source-location url:https://www.figma.com/_netlify/_next/static/chunks/6716-9f1340a0be6a105c.js urlProvider:network]] map[reflowTime:18.377 source:map[type:text value:[unattributed]]]]

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.

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

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
Multiple assets surrounding button to "Export assets" div.fig-92lpi3 > section.fig-gcn2ga > div.fig-z0kf9t > img.fig-vgi589
/images/599r6htc/regionalized/d2d61daa22d944ec3cd62677c2a...100.5 KiB91.2 KiB
A UI design interface showing card components for a travel app. The left side d… div.fig-92lpi3 > section.fig-gcn2ga > div.fig-z0kf9t > img.fig-vgi589
/images/599r6htc/regionalized/2f1c0ba703010a1b4126b14a9b0...32.5 KiB29.5 KiB
Screenshot of a design-to-code interface showing completed API calls on the lef… div.fig-gvtxu4 > div#drawer-content-_R_6daj9bsnpgqaivb_ > div.fig-1o2fbcf > img.fig-j94shh
/images/599r6htc/regionalized/24e122cd8a5089bd145f3fd46a3...21.8 KiB14.7 KiB

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.

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

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

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.

TTI

Diagnostics

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

CategoryTime Spent
Script Evaluation6.2 s
Other2.9 s
Style & Layout922 ms
Rendering713 ms
Script Parsing & Compilation701 ms
Parse HTML & CSS366 ms
Garbage Collection167 ms

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.

Estimated savings: 0.0 ms 19.1 KiB
URLTransfer SizeEst Savings
html{line-height:1.15;-webkit-text-size-adjust:100%;} …28.5 KiB19.1 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
Font display
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 1 user timing
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 2 animated elements found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 190 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 70 ms
Avoid large layout shifts 15 layout shifts found
INP breakdown
LCP request discovery
94

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Failing Elements
Make my cursor reveal an image div.fig-cf28vb > div.fig-1dfrfw8 > div.fig-1j1iokz > div.fig-1cbvupn
Make an infinite canvas gallery div.fig-cf28vb > div.fig-1dfrfw8 > div.fig-1j1iokz > div.fig-1cbvupn
Make this design move with a parallax effect div.fig-cf28vb > div.fig-1dfrfw8 > div.fig-1j1iokz > div.fig-1cbvupn
Make these photos rotate in 3D div.fig-cf28vb > div.fig-1dfrfw8 > div.fig-1j1iokz > div.fig-1cbvupn
Make my site squish when scrolled div.fig-cf28vb > div.fig-1dfrfw8 > div.fig-1j1iokz > div.fig-1cbvupn
Make a clock with a shader background div.fig-cf28vb > div.fig-1dfrfw8 > div.fig-1j1iokz > div.fig-1cbvupn
Make text move on a path div.fig-cf28vb > div.fig-1dfrfw8 > div.fig-1j1iokz > div.fig-1cbvupn

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
Masaya Takizawa ul.fig-ge4hzg > li > article > a.fig-9ka48u
Raul Marin Calleja ul.fig-ge4hzg > li > article > a.fig-9ka48u
Seungmee Lee ul.fig-ge4hzg > li > article > a.fig-9ka48u
Ayaneshu Bhardwaj ul.fig-ge4hzg > li > article > a.fig-9ka48u
Gui Seiz ul.fig-ge4hzg > li > article > a.fig-9ka48u
Benjamin Leonard ul.fig-ge4hzg > li > article > a.fig-9ka48u
Nayli C. Naza ul.fig-ge4hzg > li > article > a.fig-9ka48u
Holly Li ul.fig-ge4hzg > li > article > a.fig-9ka48u

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.

Failing Elements
English div.fig-19c8ja > div.fig-17o2drt > div.fig-79elbk > button.fig-xhgx56
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
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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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 attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<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
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements 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
`<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
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.
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.
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.
96

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
Screenshot of a web design interface showing a museum website with artwork disp… div.fig-92lpi3 > section.fig-gcn2ga > div.fig-1qkml7u > img.fig-vekl8e
364 x 205 (1.78)20 x 11 (1.82)
Interface for a "Quantum Portal Dimensional Transport System" showing current l… div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
364 x 205 (1.78)20 x 11 (1.82)
Website homepage for Bubbles Design System showing dark teal interface with nav… div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
364 x 205 (1.78)20 x 11 (1.82)
Digital graffiti application interface showing a black spray-painted signature … div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
364 x 205 (1.78)20 x 11 (1.82)
pixel interface with a colorpicker and a pixelated flower shape div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
364 x 205 (1.78)20 x 11 (1.82)
four overlapping images of a person next to a car, a motorcycle, a person weari… div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
364 x 205 (1.78)20 x 11 (1.82)
a pattern generator with sliders and toggles to adjust the preview of the patte… div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
364 x 205 (1.78)20 x 11 (1.82)
a basket catching flowers at the bottom with time and score div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
364 x 205 (1.78)20 x 11 (1.82)
Screenshot of Earworm Studio drum machine interface with dark theme. Shows inst… div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
364 x 205 (1.78)20 x 11 (1.82)

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

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
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
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

66
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
94
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

846 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.89 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

294 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.188

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.09 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

3.43 s

Detailed Report

Audit breakdown by category with detailed findings.

66

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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.

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.018184] map[node:map[boundingRect:map[bottom:880 height:128 left:0 right:1350 top:752 width:1350] lhId:page-1-SECTION nodeLabel:Logo marquee path:1,HTML,1,BODY,1,DIV,4,MAIN,1,SECTION selector:body > div#app > main#main > section.fig-1db00we snippet:<section class="fig-1db00we"> type:node] score:0.018184]]
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.18830699999999997] map[node:map[boundingRect:map[bottom:607 height:486 left:-56 right:1406 top:121 width:1463] lhId:page-5-DIV nodeLabel:Make my cursor reveal an image Make my cursor reveal an image​ Get started SLID… path:1,HTML,1,BODY,1,DIV,4,MAIN,0,SECTION,1,DIV,0,DIV selector:main#main > section.fig-dvbxa9 > div#_R_2gpbsnpgqaivb_ > div.fig-cf28vb snippet:<div class="fig-cf28vb"> type:node] score:0.17234] map[node:map[boundingRect:map[bottom:498 height:194 left:396 right:954 top:304 width:559] lhId:page-6-DIV nodeLabel:div.fig-cf28vb > div.fig-bpnbm5 > div.fig-17xhnpg > div.fig-1na308s path:1,HTML,1,BODY,1,DIV,4,MAIN,0,SECTION,1,DIV,0,DIV,1,DIV,0,DIV,0,DIV selector:div.fig-cf28vb > div.fig-bpnbm5 > div.fig-17xhnpg > div.fig-1na308s snippet:<div class="fig-1na308s"> type:node] score:0.012073 subItems:map[items:[map[cause:Unsized image element]] type:subitems]] map[node:map[boundingRect:map[bottom:0 height:0 left:0 right:0 top:0 width:0] lhId:page-8-SPAN nodeLabel:​ path: selector:span.fig-bytzjo snippet:<span aria-hidden="true" class="fig-bytzjo"> type:node] score:0.000298] map[node:map[boundingRect:map[bottom:0 height:0 left:0 right:0 top:0 width:0] lhId:page-8-SPAN nodeLabel:​ path: selector:span.fig-bytzjo snippet:<span aria-hidden="true" class="fig-bytzjo"> type:node] score:0.000282] map[node:map[boundingRect:map[bottom:0 height:0 left:0 right:0 top:0 width:0] lhId:page-8-SPAN nodeLabel:​ path: selector:span.fig-bytzjo snippet:<span aria-hidden="true" class="fig-bytzjo"> type:node] score:0.000279]]

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.

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:39.017 source:map[column:97922 line:1 type:source-location url:https://www.figma.com/_netlify/_next/static/chunks/3914-2bab184028cadf54.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:119.573 source:map[type:text value:[unattributed]]] map[reflowTime:11.386 source:map[column:34617 line:0 type:source-location url:https://www.figma.com/_netlify/_next/static/chunks/4529-4e6ca69dcb6eff9e.js urlProvider:network]] map[reflowTime:12.875 source:map[column:34027 line:0 type:source-location url:https://www.figma.com/_netlify/_next/static/chunks/4529-4e6ca69dcb6eff9e.js urlProvider:network]] map[reflowTime:9.057 source:map[column:968185 line:0 type:source-location url:https://www.figma.com/_netlify/_next/static/chunks/8992-43f84a35aafd5858.js urlProvider:network]] map[reflowTime:3.621 source:map[column:980031 line:0 type:source-location url:https://www.figma.com/_netlify/_next/static/chunks/8992-43f84a35aafd5858.js urlProvider:network]] map[reflowTime:2.078 source:map[column:37188 line:0 type:source-location url:https://www.figma.com/_netlify/_next/static/chunks/6716-9f1340a0be6a105c.js urlProvider:network]] map[reflowTime:0.774 source:map[column:27282 line:0 type:source-location url:https://www.figma.com/_netlify/_next/static/chunks/6716-9f1340a0be6a105c.js urlProvider:network]] map[reflowTime:0.842 source:map[column:72352 line:0 type:source-location url:https://www.figma.com/_netlify/_next/static/chunks/4867-f406a2b91c16aafd.js urlProvider:network]]]

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.

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.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
Screenshot of a web design interface showing a museum website with artwork disp… div.fig-92lpi3 > section.fig-gcn2ga > div.fig-1qkml7u > img.fig-vekl8e
/images/599r6htc/regionalized/278b3fae156f139de38afab1b01...100.6 KiB89.2 KiB
Multiple assets surrounding button to "Export assets" div.fig-92lpi3 > section.fig-gcn2ga > div.fig-z0kf9t > img.fig-vgi589
/images/599r6htc/regionalized/d2d61daa22d944ec3cd62677c2a...105.0 KiB81.9 KiB
Screenshot of a design-to-code interface showing completed API calls on the lef… div.fig-gvtxu4 > div#drawer-content-_R_6daj9bsnpgqaivb_ > div.fig-1o2fbcf > img.fig-j94shh
/images/599r6htc/regionalized/24e122cd8a5089bd145f3fd46a3...58.2 KiB43.9 KiB
A UI design interface showing card components for a travel app. The left side d… div.fig-92lpi3 > section.fig-gcn2ga > div.fig-z0kf9t > img.fig-vgi589
/images/599r6htc/regionalized/2f1c0ba703010a1b4126b14a9b0...34.7 KiB27.0 KiB

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

ElementLayout shift score
Make my cursor reveal an image Make my cursor reveal an image​ Get started SLID… main#main > section.fig-dvbxa9 > div#_R_2gpbsnpgqaivb_ > div.fig-cf28vb
0.172
Logo marquee body > div#app > main#main > section.fig-1db00we
0.018
div.fig-cf28vb > div.fig-bpnbm5 > div.fig-17xhnpg > div.fig-1na308s div.fig-cf28vb > div.fig-bpnbm5 > div.fig-17xhnpg > div.fig-1na308s
0.012
span.fig-bytzjo
0.000
span.fig-bytzjo
0.000
span.fig-bytzjo
0.000
span.fig-bytzjo
0.000
span.fig-bytzjo
0.000
span.fig-bytzjo
0.000
span.fig-bytzjo
0.000
span.fig-bytzjo
0.000
span.fig-bytzjo
0.000
span.fig-bytzjo
0.000
span.fig-bytzjo
0.000
span.fig-bytzjo
0.000

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

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.

TTI

Diagnostics

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

URLTotal CPU TimeScript EvaluationScript Parse
www.figma.com/_netlify/_next/static/chunks/3914-2bab184028cadf54.js1.5 s1.3 s14 ms
www.figma.com/832 ms19 ms69 ms
Unattributable291 ms5.9 ms0.0 ms
www.figma.com/_netlify/_next/static/chunks/8992-43f84a35aafd5858.js267 ms215 ms45 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

CategoryTime Spent
Script Evaluation1.6 s
Other733 ms
Style & Layout307 ms
Script Parsing & Compilation175 ms
Rendering137 ms
Parse HTML & CSS72 ms
Garbage Collection58 ms

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.

Estimated savings: 0.0 ms 16.6 KiB
URLTransfer SizeEst Savings
html{line-height:1.15;-webkit-text-size-adjust:100%;} …28.5 KiB16.6 KiB

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

Document request latency
Optimize DOM size
Font display
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 1 user timing
Avoid long main-thread tasks 6 long tasks found
Avoid non-composited animations 2 animated elements found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 180 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 70 ms
INP breakdown
LCP request discovery
94

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Failing Elements
Make my cursor reveal an image div.fig-cf28vb > div.fig-1dfrfw8 > div.fig-1j1iokz > div.fig-1cbvupn
Make an infinite canvas gallery div.fig-cf28vb > div.fig-1dfrfw8 > div.fig-1j1iokz > div.fig-1cbvupn
Make this design move with a parallax effect div.fig-cf28vb > div.fig-1dfrfw8 > div.fig-1j1iokz > div.fig-1cbvupn
Make these photos rotate in 3D div.fig-cf28vb > div.fig-1dfrfw8 > div.fig-1j1iokz > div.fig-1cbvupn
Make my site squish when scrolled div.fig-cf28vb > div.fig-1dfrfw8 > div.fig-1j1iokz > div.fig-1cbvupn
Make a clock with a shader background div.fig-cf28vb > div.fig-1dfrfw8 > div.fig-1j1iokz > div.fig-1cbvupn
Make text move on a path div.fig-cf28vb > div.fig-1dfrfw8 > div.fig-1j1iokz > div.fig-1cbvupn

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
Masaya Takizawa ul.fig-ge4hzg > li > article > a.fig-9ka48u
Raul Marin Calleja ul.fig-ge4hzg > li > article > a.fig-9ka48u
Seungmee Lee ul.fig-ge4hzg > li > article > a.fig-9ka48u
Ayaneshu Bhardwaj ul.fig-ge4hzg > li > article > a.fig-9ka48u
Gui Seiz ul.fig-ge4hzg > li > article > a.fig-9ka48u
Benjamin Leonard ul.fig-ge4hzg > li > article > a.fig-9ka48u
Nayli C. Naza ul.fig-ge4hzg > li > article > a.fig-9ka48u
Holly Li ul.fig-ge4hzg > li > article > a.fig-9ka48u

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.

Failing Elements
English div.fig-19c8ja > div.fig-17o2drt > div.fig-79elbk > button.fig-xhgx56
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
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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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 attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<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
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements 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
`<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
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.
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.
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.
96

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
Interface for a "Quantum Portal Dimensional Transport System" showing current l… div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
291 x 164 (1.77)20 x 11 (1.82)
Website homepage for Bubbles Design System showing dark teal interface with nav… div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
291 x 164 (1.77)20 x 11 (1.82)
Digital graffiti application interface showing a black spray-painted signature … div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
291 x 164 (1.77)20 x 11 (1.82)
pixel interface with a colorpicker and a pixelated flower shape div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
291 x 164 (1.77)20 x 11 (1.82)
four overlapping images of a person next to a car, a motorcycle, a person weari… div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
291 x 164 (1.77)20 x 11 (1.82)
a pattern generator with sliders and toggles to adjust the preview of the patte… div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
291 x 164 (1.77)20 x 11 (1.82)
a basket catching flowers at the bottom with time and score div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
291 x 164 (1.77)20 x 11 (1.82)
Screenshot of Earworm Studio drum machine interface with dark theme. Shows inst… div > a.fig-1bxo6l4 > div.fig-1d9le9m > img.fig-1syutp1
291 x 164 (1.77)20 x 11 (1.82)

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

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
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
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback