Skip to content
https://diagrams.net

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

98

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
www.drawio.com/assets/webfonts/fa-solid-900.woff285 ms
fonts.gstatic.com/s/poppins/v24/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff240 ms
fonts.gstatic.com/s/poppins/v24/pxiByp8kv8JHgFVrLGT9Z1xlFd2JQEk.woff235 ms
fonts.gstatic.com/s/poppins/v24/pxiByp8kv8JHgFVrLCz7Z1xlFd2JQEk.woff230 ms

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: Example diagram
path: 1,HTML,1,BODY,7,MAIN,1,DIV,0,DIV,1,DIV,0,IMG
selector: div.container > div.row > div.col-lg-6 > img.img-fluid
snippet: <img class="img-fluid" src="assets/svg/home-dia1.svg" style="padding-bottom: 100px;" alt="Example diagram">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
fonts.googleapis.com/css?family=Poppins:300,400,500,600,700667 B287 ms
fonts.googleapis.com/css?family=Lato&display=swap853 B69 ms
www.drawio.com/assets/css/theme.css62.4 KiB112 ms
www.drawio.com/assets/css/fontawesome-all.min.css12.2 KiB56 ms
www.drawio.com/assets/css/animate.min.css4.7 KiB
www.drawio.com/assets/css/hs.megamenu.css1.1 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
static.cloudflareinsights.com/beacon.min.js86400.0 s10.7 KiB

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

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 13.1 KiB
URLTransfer SizeEst Savings
www.drawio.com/assets/css/theme.css62.4 KiB13.1 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 71.8 KiB
URLTransfer SizeEst Savings
www.drawio.com/assets/css/theme.css62.1 KiB60.0 KiB
www.drawio.com/assets/css/fontawesome-all.min.css12.0 KiB11.9 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Example diagram div.container > div.row > div.col-lg-6 > img.img-fluid
www.drawio.com/assets/svg/home-dia1.svg
Example diagram 2 div.col-lg-7 > div.tab-content > div#pills-one-code-features > img.img-fluid
www.drawio.com/assets/svg/home-dia2.svg

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 246 ms
URLTime Spent
diagrams.net/246 ms
www.drawio.com/0.0 ms
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Time to Interactive 1.0 s
●Max Potential First Input Delay 20 ms
●Minify JavaScript
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 731 KiB
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.2 s
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 50 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 60 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid non-composited animations
70

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Share with everyone Don't worry about licenses or platforms, it just works. P… div.container > div.row > div.col-lg-5 > ul.nav

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Share with everyone Don't worry about licenses or platforms, it just works. div.col-lg-5 > ul.nav > li.nav-item > a#pills-one-code-features-tab
Powerful features Collaborate with shared cursors in real-time. draw.io has ev… div.col-lg-5 > ul.nav > li.nav-item > a#pills-two-code-features-tab
Privacy first Store your data wherever you want to. We cannot access your data. div.col-lg-5 > ul.nav > li.nav-item > a#pills-three-code-features-tab

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.js-form-message > div.input-group > div.input-group-append > button.btn div.js-form-message > div.input-group > div.input-group-append > button.btn

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Blog div#navBar > ul.navbar-nav > li.nav-item > a#blogMegaMenu
Start Now div#navBar > ul.navbar-nav > li.nav-item > a.btn
Bring your storage to our online tool, or save locally with the desktop app. div.row > div.col-lg-5 > div.mb-5 > p
Describe your diagram: div.container > div.row > div.col-lg-5 > p.small
Start div.row > div.col-lg-5 > div.mb-3 > a#startButton
Download div.row > div.col-lg-5 > div.mb-3 > a.btn
No login or registration required. Diagram generation uses OpenAI. div.container > div.row > div.col-lg-5 > p.small
Share with everyone a#pills-one-code-features-tab > div.media > div.media-body > h3.h6
Don't worry about licenses or platforms, it just works. a#pills-one-code-features-tab > div.media > div.media-body > p.mb-0
Collaborate with shared cursors in real-time. draw.io has everything you expect… a#pills-two-code-features-tab > div.media > div.media-body > p.mb-0
Store your data wherever you want to. We cannot access your data. a#pills-three-code-features-tab > div.media > div.media-body > p.mb-0
Works with Google Drive and Google Workplace (G Suite). div.container > div.row > div.col-sm-6 > p
Google Drive div.row > div.col-sm-6 > p > a
Google Workplace div.row > div.col-sm-6 > p > a
Works with OneDrive and Sharepoint. Office 365 and Microsoft Teams apps provide… div.container > div.row > div.col-sm-6 > p
OneDrive and Sharepoint div.row > div.col-sm-6 > p > a
Office 365 div.row > div.col-sm-6 > p > a
Microsoft Teams div.row > div.col-sm-6 > p > a
Highest-rated Confluence app, delivered by us as draw.io. Also for Jira. div.container > div.row > div.col-sm-6 > p
Confluence app div.row > div.col-sm-6 > p > a
Jira div.row > div.col-sm-6 > p > a
Works with GitHub, GitLab and Dropbox for visual documentation in distributed t… div.container > div.row > div.col-sm-6 > p
GitHub div.row > div.col-sm-6 > p > a
GitLab div.row > div.col-sm-6 > p > a
Dropbox div.row > div.col-sm-6 > p > a
Download draw.io Desktop for offline use, or draw.io for VSCode.* div.container > div.row > div.col-sm-6 > p
draw.io Desktop div.row > div.col-sm-6 > p > a
draw.io for VSCode div.row > div.col-sm-6 > p > a
Embed and edit diagrams directly with the draw.io for Notion Chrome extension. div.container > div.row > div.col-sm-6 > p
draw.io for Notion Chrome extension div.row > div.col-sm-6 > p > a
See more div.container > div.text-center > div.mb-3 > a.btn
Start Now div.container > div.text-center > div.mb-3 > a.btn
* Third-party integration. main#content > div.container > div.text-center > p.small

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
OneDrive and Sharepoint div.row > div.col-sm-6 > p > a
Office 365 div.row > div.col-sm-6 > p > a
Microsoft Teams div.row > div.col-sm-6 > p > a
Confluence app div.row > div.col-sm-6 > p > a
Jira div.row > div.col-sm-6 > p > a
GitHub div.row > div.col-sm-6 > p > a
GitLab div.row > div.col-sm-6 > p > a
Dropbox div.row > div.col-sm-6 > p > a
draw.io for Notion Chrome extension div.row > div.col-sm-6 > p > a

These are opportunities to improve the legibility of your content.

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Google Workplace and Google Drive div.col-sm-6 > div.media > div.media-body > h4.h6

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Share with everyone Don't worry about licenses or platforms, it just works. div.row > div.col-lg-5 > ul.nav > li.nav-item
Powerful features Collaborate with shared cursors in real-time. draw.io has ev… div.row > div.col-lg-5 > ul.nav > li.nav-item
Privacy first Store your data wherever you want to. We cannot access your data. div.row > div.col-lg-5 > ul.nav > li.nav-item

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
draw.io div.u-header__section > div#logoAndNav > nav.js-mega-menu > a.navbar-brand
draw.io div.container > div.row > div.col-lg-4 > a.d-inline-flex
○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
●Image elements have `[alt]` attributes
●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
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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 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 a valid value for its `[lang]` attribute
○`<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.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
83

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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
app.diagrams.net/?src=aboutStart
www.drawio.com/integrations.htmlSee more

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
●Page has successful HTTP status code
●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