C — https://store.figma.com | BeaverCheck Audit

Site Health

Score: 75 / 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)

Cookie '_shopify_s' is missing the Secure flag

Security › Cookie Security

Cookie '_shopify_y' is missing the Secure flag

Security › Cookie Security

Cookie 'cart_currency' is missing the Secure flag

Security › Cookie Security

Cookie 'localization' is missing the Secure flag

Security › Cookie Security

2 image(s) missing alt attribute

Accessibility › Alt Text Quality

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fstore.figma.com)](https://beavercheck.com/results/4af92524-b235-4b48-bd82-6d0ecbaa5347)

HTML

<a href="https://beavercheck.com/results/4af92524-b235-4b48-bd82-6d0ecbaa5347"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fstore.figma.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fstore.figma.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

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.

10.83 s

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

19.32 s

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

544 ms

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

0.000

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

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

19.48 s

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.

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 long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
cdn.feedbucket.app/assets/feedbucket.js	0.0 ms	148.3 KiB
media.9gtb.com/script.js?rev=9b8201f	86400.0 s	60.5 KiB
/cdn/shopifycloud/portable-wallets/latest/accelerated-che...	300.0 s	2.4 KiB
/loader.js?g_cvt_id=454bf216-f0ac-4c2c-9139-82617cb3a1d2&...	86400.0 s	1.9 KiB
shop.app/checkouts/internal/preloads.js?locale=en-US&shop_id=57683640503	60.0 s	553 B

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:7.386 source:map[column:53 line:4297 type:source-location url:https://store.figma.com/ 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:58.749 source:map[type:text value:[unattributed]]] map[reflowTime:32.604 source:map[column:15 line:9122 type:source-location url:https://store.figma.com/ urlProvider:network]] map[reflowTime:25.314 source:map[column:35004 line:0 type:source-location url:https://store.figma.com/cdn/shopifycloud/perf-kit/shopify-perf-kit-3.3.1.min.js urlProvider:network]] map[reflowTime:7.386 source:map[column:31 line:4225 type:source-location url:https://store.figma.com/ 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

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.

URL	Transfer Size	Duration
/cdn/shop/t/70/compiled_assets/styles.css?v=9928481419522...	36.6 KiB	754 ms
/cdn/shopifycloud/portable-wallets/latest/accelerated-che...	2.4 KiB
store.figma.com/cdn/shop/t/70/assets/custom.css?v=29212849477045231151770140281	2.5 KiB

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

	URL	Resource Size	Est Savings
Culture fit tee in violet `div.cc-card-wrapper > a.cc-card > div.cc-card-image-wrapper > img.cc-card-image`	/cdn/shop/files/FigmaStore_ProductImages_StoryStudioTshir...	46.4 KiB	20.2 KiB
Culture fit tee in yellow `div.cc-card-wrapper > a.cc-card > div.cc-card-image-wrapper > img.cc-card-image`	/cdn/shop/files/FigmaStore_ProductImages_StoryStudioTshir...	46.2 KiB	20.1 KiB
Culture fit tee in blue `div.cc-card-wrapper > a.cc-card > div.cc-card-image-wrapper > img.cc-card-image`	/cdn/shop/files/FigmaStore_ProductImages_StoryStudioTshir...	44.4 KiB	19.3 KiB

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

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

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.

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.

Estimated savings: 300 ms 47.0 KiB

URL	Transfer Size	Est Savings
/cdn/shop/t/70/compiled_assets/styles.css?v=9928481419522...	35.7 KiB	35.1 KiB
store.figma.com/cdn/shop/t/70/assets/base.css?v=96368032574344298451770140284	13.4 KiB	11.9 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 1.7 s 265.0 KiB

URL	Transfer Size	Est Savings
cdn.feedbucket.app/assets/feedbucket.js	147.9 KiB	105.2 KiB
www.googletagmanager.com/gtag/js?id=GT-MBH3SZ62	135.3 KiB	61.7 KiB
assets.gorgias.chat/build/static/js/279.58c6a32e6ae4fc54.js	92.3 KiB	41.3 KiB
media.9gtb.com/script.js?rev=9b8201f	59.7 KiB	32.0 KiB
store.figma.com/cdn/wpm/bcfa8229ew36b6053dp1e134caame9d83f21m.js	56.8 KiB	24.8 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
store.figma.com/	1.1 s	159 ms	45 ms
Unattributable	1.1 s	163 ms	0.0 ms
assets.gorgias.chat/build/static/js/279.58c6a32e6ae4fc54.js	675 ms	611 ms	34 ms
store.figma.com/cdn/wpm/bcfa8229ew36b6053dp1e134caame9d83f21m.js	288 ms	205 ms	22 ms
assets.gorgias.chat/build/static/js/557.f9e30f4c6d8d87de.js	263 ms	187 ms	14 ms
store.figma.com/cdn/shopifycloud/perf-kit/shopify-perf-kit-3.3.1.min.js	236 ms	101 ms	31 ms
store.figma.com/cdn/shopifycloud/importmap-polyfill/es-modules-shim.2.4.0.js	233 ms	186 ms	23 ms
www.googletagmanager.com/gtag/js?id=GT-MBH3SZ62	216 ms	163 ms	52 ms
/cdn/s/trekkie.storefront.793024e5c781b83428b9784ec5054da...	118 ms	96 ms	14 ms
media.9gtb.com/script.js?rev=9b8201f	98 ms	73 ms	25 ms
cdn.feedbucket.app/assets/feedbucket.js	97 ms	36 ms	60 ms
assets.gorgias.chat/build/static/js/vendor-react-core.820de3d88eb95c8f.js	89 ms	15 ms	17 ms
assets.gorgias.chat/build/static/js/199.d56484bedf68e703.js	86 ms	1.0 ms	11 ms
/cdn/shopifycloud/storefront/assets/shop_events_listener-...	76 ms	59 ms	1.8 ms
/cdn/shopifycloud/shop-js/modules/v2/chunk.index_4uAqGWkW...	70 ms	65 ms	0.7 ms
/cdn/shopifycloud/storefront/assets/shopify_pay/storefron...	63 ms	52 ms	10 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

Category	Time Spent
Script Evaluation	2.5 s
Other	1.3 s
Style & Layout	981 ms
Script Parsing & Compilation	418 ms
Parse HTML & CSS	127 ms
Rendering	44 ms
Garbage Collection	19 ms

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

URL	Transfer Size
/cdn/shopifycloud/checkout-web/assets/c1/hooks-useHasOrde...	344.6 KiB
cdn.shopify.com/s/files/1/0576/8364/0503/files/Figma-Sans-VF.woff2?v=1757390135	195.5 KiB
store.figma.com/cdn/shop/files/Figma-Sans-VF.woff2?v=1757390135	195.3 KiB
assets.gorgias.chat/build/static/js/471.998b51c0138186f0.js	159.0 KiB
cdn.feedbucket.app/assets/feedbucket.js	148.3 KiB
www.googletagmanager.com/gtag/js?id=GT-MBH3SZ62	135.7 KiB
/cdn/shopifycloud/checkout-web/assets/c1/approval-scopes-...	108.0 KiB
/cdn/shop/files/a9b6c5d2bd5de0a07c73b7d03e4b04818a7a2cf0....	95.5 KiB
assets.gorgias.chat/build/static/js/279.58c6a32e6ae4fc54.js	92.8 KiB
/cdn/shop/files/3x4_1x_SoftwareIsCultureSwag_MaxGuther_Cl...	82.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

●Font display

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 19 user timings

●Avoid long main-thread tasks 20 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 330 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 10 ms

○INP breakdown

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

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
©2025 Figma `footer.ftr-footer-wrapper > div.ftr-menu-box > div.ftr-bottom-section > div.ftr-copyright`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.sc-category-card > a.sc-category-link > div.sc-image-container > img `div.sc-category-card > a.sc-category-link > div.sc-image-container > img`
div.sc-category-card > a.sc-category-link > div.sc-image-container > img `div.sc-category-card > a.sc-category-link > div.sc-image-container > img`

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.

Failing Elements
div.max-w-screen-2xl > div.sc-cards-wrapper > div.sc-category-card > a.sc-category-link `div.max-w-screen-2xl > div.sc-cards-wrapper > div.sc-category-card > a.sc-category-link`
div.max-w-screen-2xl > div.sc-cards-wrapper > div.sc-category-card > a.sc-category-link `div.max-w-screen-2xl > div.sc-cards-wrapper > div.sc-category-card > a.sc-category-link`

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.

○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

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

●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

●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 are distinguishable without relying on color.

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●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

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

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

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

Best Practices

General

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

Source	Description
fonts.cdnfonts.com/css/figma-sans	`Failed to load resource: the server responded with a status of 500 ()`
store.figma.com/ line 1538, col 39	`MinMaxify is deactivated for this website. Please don't forget to remove minmaxify-head.liquid still being referenced by theme.liquid`

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

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.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.sc-category-card > a.sc-category-link > div.sc-image-container > img `div.sc-category-card > a.sc-category-link > div.sc-image-container > img`
div.sc-category-card > a.sc-category-link > div.sc-image-container > img `div.sc-category-card > a.sc-category-link > div.sc-image-container > img`

Format your HTML in a way that enables crawlers to better understand your app’s content.

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

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.

449 ms

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

1.32 s

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

3 ms

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

0.010

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

1.24 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.70 s

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.

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

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:8.4 source:map[column:53 line:4297 type:source-location url:https://store.figma.com/ 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:99.207 source:map[type:text value:[unattributed]]] map[reflowTime:55.073 source:map[column:29 line:9134 type:source-location url:https://store.figma.com/ urlProvider:network]] map[reflowTime:0.491 source:map[column:119902 line:0 type:source-location url:https://store.figma.com/cdn/wpm/bcfa8229ew36b6053dp1e134caame9d83f21m.js urlProvider:network]] map[reflowTime:8.4 source:map[column:31 line:4225 type:source-location url:https://store.figma.com/ 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.

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.

URL	Transfer Size	Duration
store.figma.com/cdn/shop/t/70/assets/custom.css?v=29212849477045231151770140281	2.2 KiB
/cdn/shop/t/70/compiled_assets/styles.css?v=9928481419522...	36.5 KiB	84 ms
/cdn/shopifycloud/portable-wallets/latest/accelerated-che...	2.1 KiB

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

Request	Cache TTL	Transfer Size
cdn.feedbucket.app/assets/feedbucket.js	0.0 ms	148.3 KiB
media.9gtb.com/script.js?rev=9b8201f	86400.0 s	60.5 KiB
/cdn/shopifycloud/portable-wallets/latest/accelerated-che...	300.0 s	2.1 KiB
/loader.js?g_cvt_id=454bf216-f0ac-4c2c-9139-82617cb3a1d2&...	86400.0 s	1.9 KiB
shop.app/checkouts/internal/preloads.js?locale=en-US&shop_id=57683640503	60.0 s	556 B

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

	URL	Resource Size	Est Savings
section#shopify-section-template--27031286317427__figma_hero_section_Rp7ggC > section.fhs-hero > div.fhs-photo-wrapper > img.fhs-hero-image `section#shopify-section-template--27031286317427__figma_hero_section_Rp7ggC > section.fhs-hero > div.fhs-photo-wrapper > img.fhs-hero-image`	/cdn/shop/files/16x9_1x_SoftwareIsCultureSwag_MaxGuther_C...	111.9 KiB	21.3 KiB
div.sc-category-card > a.sc-category-link > div.sc-image-container > img `div.sc-category-card > a.sc-category-link > div.sc-image-container > img`	/cdn/shop/files/a9b6c5d2bd5de0a07c73b7d03e4b04818a7a2cf0....	94.7 KiB	12.8 KiB

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

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

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 47.4 KiB

URL	Transfer Size	Est Savings
/cdn/shop/t/70/compiled_assets/styles.css?v=9928481419522...	35.7 KiB	35.3 KiB
store.figma.com/cdn/shop/t/70/assets/base.css?v=96368032574344298451770140284	13.4 KiB	12.1 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 0.0 ms 264.6 KiB

URL	Transfer Size	Est Savings
cdn.feedbucket.app/assets/feedbucket.js	147.9 KiB	105.2 KiB
www.googletagmanager.com/gtag/js?id=GT-MBH3SZ62	134.9 KiB	61.3 KiB
assets.gorgias.chat/build/static/js/279.58c6a32e6ae4fc54.js	92.3 KiB	41.3 KiB
media.9gtb.com/script.js?rev=9b8201f	59.7 KiB	32.0 KiB
store.figma.com/cdn/wpm/bcfa8229ew36b6053dp1e134caame9d83f21m.js	56.8 KiB	24.8 KiB

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

URL	Transfer Size
/cdn/shopifycloud/checkout-web/assets/c1/hooks-useHasOrde...	344.7 KiB
/cdn/shop/files/3x4_1x_SoftwareIsCultureSwag_MaxGuther_Cl...	206.7 KiB
cdn.shopify.com/s/files/1/0576/8364/0503/files/Figma-Sans-VF.woff2?v=1757390135	195.5 KiB
store.figma.com/cdn/shop/files/Figma-Sans-VF.woff2?v=1757390135	195.3 KiB
assets.gorgias.chat/build/static/js/471.998b51c0138186f0.js	159.0 KiB
cdn.feedbucket.app/assets/feedbucket.js	148.3 KiB
www.googletagmanager.com/gtag/js?id=GT-MBH3SZ62	135.3 KiB
/cdn/shop/files/16x9_1x_SoftwareIsCultureSwag_MaxGuther_C...	112.5 KiB
/cdn/shopifycloud/checkout-web/assets/c1/approval-scopes-...	108.0 KiB
/cdn/shop/files/a9b6c5d2bd5de0a07c73b7d03e4b04818a7a2cf0....	95.5 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

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 19 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 1.4 s

●Avoid long main-thread tasks 1 long task found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 210 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 10 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

Accessibility

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.sc-category-card > a.sc-category-link > div.sc-image-container > img `div.sc-category-card > a.sc-category-link > div.sc-image-container > img`
div.sc-category-card > a.sc-category-link > div.sc-image-container > img `div.sc-category-card > a.sc-category-link > div.sc-image-container > img`

Failing Elements
div.max-w-screen-2xl > div.sc-cards-wrapper > div.sc-category-card > a.sc-category-link `div.max-w-screen-2xl > div.sc-cards-wrapper > div.sc-category-card > a.sc-category-link`
div.max-w-screen-2xl > div.sc-cards-wrapper > div.sc-category-card > a.sc-category-link `div.max-w-screen-2xl > div.sc-cards-wrapper > div.sc-category-card > a.sc-category-link`

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.

○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

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

●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

●`<frame>` or `<iframe>` elements have a title

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

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

●Links are distinguishable without relying on color.

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●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

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

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

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

Best Practices

General

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

Source	Description
fonts.cdnfonts.com/css/figma-sans	`Failed to load resource: the server responded with a status of 500 ()`
store.figma.com/ line 1538, col 39	`MinMaxify is deactivated for this website. Please don't forget to remove minmaxify-head.liquid still being referenced by theme.liquid`

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

SEO

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.sc-category-card > a.sc-category-link > div.sc-image-container > img `div.sc-category-card > a.sc-category-link > div.sc-image-container > img`
div.sc-category-card > a.sc-category-link > div.sc-image-container > img `div.sc-category-card > a.sc-category-link > div.sc-image-container > img`

Format your HTML in a way that enables crawlers to better understand your app’s content.

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

Results for https://store.figma.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts