C — https://canva.com | BeaverCheck Audit

Site Health

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

Content-Security-Policy header is missing

Security › Security Headers

HSTS header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

1 image(s) missing alt attribute

Accessibility › Alt Text Quality

No H1 heading found

Accessibility › Heading Hierarchy

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fcanva.com)](https://beavercheck.com/results/212abc29-ef5c-4683-a272-e262197eef82)

HTML

<a href="https://beavercheck.com/results/212abc29-ef5c-4683-a272-e262197eef82"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fcanva.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fcanva.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

100

Accessibility

Best Practices

100

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.

3.37 s

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

3.80 s

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

1.55 s

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.

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

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

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:97.871 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

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

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
static.canva.com/web/f3cf4411110060c6.sentry_browser.js	38.3 KiB	150 ms
static.canva.com/web/22fdd39dabbac02e.strings.js	13.0 KiB
static.canva.com/web/9a407196cc2459d4.ltr.css	53.1 KiB	1.1 s
static.canva.com/web/7d238f3518d9fca3.en.js	1.1 KiB

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

Request	Cache TTL	Transfer Size
www.canva.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/625261456364/main.js?	14400.0 s	13.5 KiB
/de024e4a-5693-4372-a5c9-5857b329744d/floating-elements-v...	432000.0 s	23.1 KiB
/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c124171768917...	86400.0 s	6.9 KiB
/ef8d0b0b-20a1-4b4d-9c62-e2099cfd9e66/floating-elements-a...	432000.0 s	16.8 KiB
/4ef9c76c-921b-4188-bc98-28659758ecf8/floating-elements-b...	432000.0 s	11.4 KiB
/5647f184-5e44-42e4-84a4-0c45e945cf12/floating-elements-s...	432000.0 s	9.4 KiB
/ad62b206-41af-4529-9832-3b1137cd6990/floating-elements-s...	432000.0 s	5.9 KiB
/38c1cf77-57db-46b6-8d00-82a93ecf99ac/Download_on_the_App...	432000.0 s	4.6 KiB
/67d58c37-ef51-49d2-a73d-d9c16bbb2e9f/floating-elements-f...	432000.0 s	4.6 KiB
/6122da46-4357-4423-a18e-35bee4a9a33e/GetItOnGooglePlay_B...	432000.0 s	3.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
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/de024e4a-5693-4372-a5c9-5857b329744d/floating-elements-v...	21.8 KiB	5.1 KiB

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.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 815 ms

URL	Time Spent
canva.com/	815 ms
www.canva.com/	0.0 ms

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: 300 ms 43.2 KiB

URL	Transfer Size	Est Savings
static.canva.com/web/9a407196cc2459d4.ltr.css	52.2 KiB	43.2 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: 450 ms 245.8 KiB

URL	Transfer Size	Est Savings
static.canva.com/web/a6a5714cc6dea6f4.js	307.3 KiB	146.7 KiB
static.canva.com/web/243a21c2549ef88e.vendor.js	33.5 KiB	30.0 KiB
static.canva.com/web/ad1181f53942b02c.s4le6a.vendor.js	77.4 KiB	24.3 KiB
static.canva.com/web/a2ac72e9800c50ea.1ul071.vendor.js	39.9 KiB	22.5 KiB
static.canva.com/web/f3cf4411110060c6.sentry_browser.js	36.7 KiB	22.3 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
www.canva.com/	3.4 s	88 ms	44 ms
static.canva.com/web/a6a5714cc6dea6f4.js	2.6 s	2.3 s	187 ms
static.canva.com/web/ad1181f53942b02c.s4le6a.vendor.js	1.5 s	1.1 s	54 ms
static.canva.com/web/f3cf4411110060c6.sentry_browser.js	1.5 s	596 ms	26 ms
Unattributable	643 ms	23 ms	0.0 ms
www.canva.com/cdn-cgi/challenge-platform/scripts/jsd/main.js	556 ms	462 ms	5.0 ms
/chunk-batch/5b3d741bd5110ceb.js+9173ed5758dc2d0d.js+6c6f...	209 ms	170 ms	17 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	5.0 s
Other	2.7 s
Style & Layout	2.0 s
Script Parsing & Compilation	425 ms
Rendering	285 ms
Parse HTML & CSS	190 ms
Garbage Collection	128 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reason	Failure type
The page has an unload handler in the main frame.	Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

	URL
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/5647f184-5e44-42e4-84a4-0c45e945cf12/floating-elements-s...
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/de024e4a-5693-4372-a5c9-5857b329744d/floating-elements-v...
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/4ef9c76c-921b-4188-bc98-28659758ecf8/floating-elements-b...
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/ad62b206-41af-4529-9832-3b1137cd6990/floating-elements-s...
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/67d58c37-ef51-49d2-a73d-d9c16bbb2e9f/floating-elements-f...
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/ef8d0b0b-20a1-4b4d-9c62-e2099cfd9e66/floating-elements-a...
div.lJVQMg > div.eAUiHA > a.FSQmFA > img.TR_qYw `div.lJVQMg > div.eAUiHA > a.FSQmFA > img.TR_qYw`	/6122da46-4357-4423-a18e-35bee4a9a33e/GetItOnGooglePlay_B...
div.lJVQMg > div.eAUiHA > a.FSQmFA > img.TR_qYw `div.lJVQMg > div.eAUiHA > a.FSQmFA > img.TR_qYw`	/38c1cf77-57db-46b6-8d00-82a93ecf99ac/Download_on_the_App...

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

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,101 KiB

●Avoid long main-thread tasks 16 long tasks found

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 280 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 230 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

100

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.

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

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●Links have a discernible name

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

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

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	static.canva.com/web/f3cf4411110060c6.sentry_browser.js
SharedStorage	www.canva.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.canva.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.canva.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○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

Performance

100

Accessibility

Best Practices

100

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.

1.05 s

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

1.25 s

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

160 ms

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

0.002

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

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

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

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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:113.797 source:map[column:253828 line:2 type:source-location url:https://static.canva.com/web/ad1181f53942b02c.s4le6a.vendor.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:1.43 source:map[column:71 line:193 type:source-location url:https://static.canva.com/web/a6a5714cc6dea6f4.js urlProvider:network]] map[reflowTime:82.572 source:map[column:99 line:228 type:source-location url:https://static.canva.com/web/a6a5714cc6dea6f4.js urlProvider:network]] map[reflowTime:1.01 source:map[column:453 line:719 type:source-location url:https://static.canva.com/web/a6a5714cc6dea6f4.js urlProvider:network]] map[reflowTime:1.55 source:map[column:870 line:1038 type:source-location url:https://static.canva.com/web/a6a5714cc6dea6f4.js urlProvider:network]] map[reflowTime:1.708 source:map[type:text value:[unattributed]]] map[reflowTime:4.475 source:map[column:9114 line:0 type:source-location url:https://www.canva.com/cdn-cgi/challenge-platform/scripts/jsd/main.js urlProvider:network]] map[reflowTime:80.834 source:map[column:273 line:63 type:source-location url:https://static.canva.com/web/a6a5714cc6dea6f4.js urlProvider:network]] map[reflowTime:27.094 source:map[column:103605 line:1 type:source-location url:https://static.canva.com/web/a2ac72e9800c50ea.1ul071.vendor.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.

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.

URL	Transfer Size	Duration
static.canva.com/web/f3cf4411110060c6.sentry_browser.js	37.6 KiB
static.canva.com/web/9a407196cc2459d4.ltr.css	53.1 KiB	311 ms
static.canva.com/web/22fdd39dabbac02e.strings.js	13.0 KiB
static.canva.com/web/7d238f3518d9fca3.en.js	1.8 KiB

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

Request	Cache TTL	Transfer Size
www.canva.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/625261456364/main.js?	14400.0 s	12.1 KiB
/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c124171768917...	86400.0 s	6.9 KiB
/ef8d0b0b-20a1-4b4d-9c62-e2099cfd9e66/floating-elements-a...	432000.0 s	17.0 KiB
/ae5e1c8b-d4fd-436a-bfb2-fb9ae9c36475/floating-elements-v...	432000.0 s	15.7 KiB
/850101cb-0970-40ab-8179-128095512a54/floating-elements-b...	432000.0 s	11.0 KiB
/4684b1c9-92b5-4fb2-943a-1fab339f5d57/floating-elements-c...	432000.0 s	9.4 KiB
/90620cc0-c92f-4a5b-8c9b-c65743f9997a/floating-elements-c...	432000.0 s	9.3 KiB
/7365175c-ed25-4ee1-b1ae-29c87c2f3538/floating-elements-s...	432000.0 s	9.2 KiB
/3a6ec7cd-37c4-4270-b65d-42595f6b0f4b/floating-elements-s...	432000.0 s	6.3 KiB
/8b8264be-2599-450a-a114-2a6e670f3529/floating-elements-c...	432000.0 s	5.1 KiB
/67d58c37-ef51-49d2-a73d-d9c16bbb2e9f/floating-elements-f...	432000.0 s	4.7 KiB
/38c1cf77-57db-46b6-8d00-82a93ecf99ac/Download_on_the_App...	432000.0 s	4.3 KiB
/6122da46-4357-4423-a18e-35bee4a9a33e/GetItOnGooglePlay_B...	432000.0 s	3.8 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
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/ef8d0b0b-20a1-4b4d-9c62-e2099cfd9e66/floating-elements-a...	15.8 KiB	13.0 KiB
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/ae5e1c8b-d4fd-436a-bfb2-fb9ae9c36475/floating-elements-v...	14.4 KiB	11.8 KiB
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/850101cb-0970-40ab-8179-128095512a54/floating-elements-b...	10.5 KiB	8.6 KiB
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/4684b1c9-92b5-4fb2-943a-1fab339f5d57/floating-elements-c...	8.9 KiB	7.3 KiB
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/90620cc0-c92f-4a5b-8c9b-c65743f9997a/floating-elements-c...	8.5 KiB	7.0 KiB
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/7365175c-ed25-4ee1-b1ae-29c87c2f3538/floating-elements-s...	8.3 KiB	6.8 KiB
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/3a6ec7cd-37c4-4270-b65d-42595f6b0f4b/floating-elements-s...	5.0 KiB	4.1 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 264 ms

URL	Time Spent
canva.com/	264 ms
www.canva.com/	0.0 ms

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: 30 ms 41.6 KiB

URL	Transfer Size	Est Savings
static.canva.com/web/9a407196cc2459d4.ltr.css	52.2 KiB	41.6 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: 30 ms 355.4 KiB

URL	Transfer Size	Est Savings
static.canva.com/web/a6a5714cc6dea6f4.js	306.9 KiB	146.7 KiB
accounts.google.com/gsi/client	92.7 KiB	69.9 KiB
/chunk-batch/5b3d741bd5110ceb.js+9173ed5758dc2d0d.js+6c6f...	88.5 KiB	39.0 KiB
static.canva.com/web/243a21c2549ef88e.vendor.js	33.5 KiB	30.1 KiB
static.canva.com/web/ad1181f53942b02c.s4le6a.vendor.js	77.4 KiB	24.6 KiB
static.canva.com/web/a2ac72e9800c50ea.1ul071.vendor.js	39.9 KiB	23.1 KiB
static.canva.com/web/f3cf4411110060c6.sentry_browser.js	36.7 KiB	22.0 KiB

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	1.3 s
Style & Layout	805 ms
Other	704 ms
Script Parsing & Compilation	116 ms
Rendering	56 ms
Parse HTML & CSS	38 ms
Garbage Collection	29 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reason	Failure type
The page has an unload handler in the main frame.	Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

	URL
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/67d58c37-ef51-49d2-a73d-d9c16bbb2e9f/floating-elements-f...
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/ef8d0b0b-20a1-4b4d-9c62-e2099cfd9e66/floating-elements-a...
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/7365175c-ed25-4ee1-b1ae-29c87c2f3538/floating-elements-s...
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/ae5e1c8b-d4fd-436a-bfb2-fb9ae9c36475/floating-elements-v...
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/90620cc0-c92f-4a5b-8c9b-c65743f9997a/floating-elements-c...
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/3a6ec7cd-37c4-4270-b65d-42595f6b0f4b/floating-elements-s...
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/4684b1c9-92b5-4fb2-943a-1fab339f5d57/floating-elements-c...
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/850101cb-0970-40ab-8179-128095512a54/floating-elements-b...
div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA `div.gVI_3Q > div.DUDBPQ > div.qyOqcQ > img.p0KmZA`	/8b8264be-2599-450a-a114-2a6e670f3529/floating-elements-c...

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

●Time to Interactive 1.9 s

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,300 KiB

●JavaScript execution time 1.2 s

●Avoid long main-thread tasks 4 long tasks found

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 110 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 160 ms

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

100

Accessibility

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

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

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

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

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	static.canva.com/web/f3cf4411110060c6.sentry_browser.js
SharedStorage	www.canva.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.canva.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.canva.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

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
www.canva.com/	`Not signed in with the identity provider.`

●Uses HTTPS

●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

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

SEO

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

Results for https://canva.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

General

SEO

Keyboard Shortcuts