Skip to content
https://arduino.cc

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.

69

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.

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
www.arduino.cc/_next/static/chunks/pages/_app-6c6282e55ed0056f.js0.0 ms57.8 KiB
www.arduino.cc/_next/static/css/90ba35feb71cde2a.css0.0 ms46.4 KiB
www.arduino.cc/_next/static/chunks/framework-f00fddb9800f9292.js0.0 ms45.0 KiB
www.arduino.cc/_next/static/chunks/main-695e353efc0a2998.js0.0 ms36.5 KiB
www.arduino.cc/_next/static/chunks/9575-5ded90c66ba306b0.js0.0 ms35.9 KiB
www.arduino.cc/_next/static/chunks/9104-95c6abddeae501c7.js0.0 ms35.8 KiB
www.arduino.cc/_next/static/chunks/5008.58b3314f8171a05c.js0.0 ms30.2 KiB
www.arduino.cc/_next/static/chunks/9742.cfecb3637b05db11.js0.0 ms28.2 KiB
evs.aayinltcs.arduino.cc/5yy37B6M2UBwaTzKNi37Ls/qUh2Pce5EsyeGTFGda1mDz.min.js10800.0 s30.2 KiB
www.arduino.cc/_next/static/chunks/5075.348ecaf5ec9672e5.js0.0 ms13.6 KiB
content.arduino.cc/fonts/Roboto-Mono-Bold-webfont.woff86400.0 s26.7 KiB
content.arduino.cc/fonts/Roboto-Mono-Regular-webfont.woff86400.0 s26.7 KiB
www.arduino.cc/_next/static/chunks/pages/%5B%5B...slug%5D%5D-97c74d60bdea974f.js0.0 ms10.6 KiB
embeds.iubenda.com/widgets/9a0b3c88-6db6-11ee-8bfc-5ad8d8c564c0.js60.0 s10.6 KiB
content.arduino.cc/fonts/OpenSans-Italic-webfont.woff86400.0 s21.8 KiB
content.arduino.cc/fonts/OpenSans-Semibold-webfont.woff86400.0 s20.8 KiB
content.arduino.cc/fonts/OpenSans-Regular-webfont.woff86400.0 s20.7 KiB
content.arduino.cc/fonts/OpenSans-Bold-webfont.woff86400.0 s20.7 KiB
www.arduino.cc/_next/static/chunks/9896.4c725aae1fd7c940.js0.0 ms8.2 KiB
public.profitwell.com/js/profitwell.js?auth=53f534183f43f5110cb688bef343b0bd14400.0 s9.7 KiB
www.arduino.cc/_next/static/chunks/2590.da601b28fbf7a379.js0.0 ms5.0 KiB
www.arduino.cc/_next/static/chunks/4010.7ce1954d61342ff7.js0.0 ms4.5 KiB
www.arduino.cc/_next/static/chunks/7840.fd9bc36549f85b9c.js0.0 ms4.4 KiB
www.arduino.cc/_next/static/chunks/3646.e442f3dbc624618f.js0.0 ms4.3 KiB
www.arduino.cc/_next/static/chunks/webpack-a5744e0d7ad55e7d.js0.0 ms4.3 KiB
www.arduino.cc/_next/static/chunks/3221.bec8ecc8d169e394.js0.0 ms3.4 KiB
www.arduino.cc/_next/static/chunks/reactPlayerFilePlayer.689258353e0f5071.js0.0 ms3.3 KiB
www.arduino.cc/_next/static/chunks/5364.ffbe220b2df40def.js0.0 ms2.8 KiB
www.arduino.cc/_next/static/chunks/6590.39c622cabf735c04.js0.0 ms2.6 KiB
www.arduino.cc/_next/static/chunks/1600.e80c31bb8c886e1d.js0.0 ms2.1 KiB
www.arduino.cc/_next/static/css/2f39f2f3537629df.css0.0 ms2.1 KiB
cdn.arduino.cc/header-footer/prod/cookieSolution.css86400.0 s5.1 KiB
www.arduino.cc/_next/static/css/90dfe282a754efa7.css0.0 ms2.0 KiB
www.arduino.cc/_next/static/chunks/1099.58bb53eced3b6d6e.js0.0 ms1.9 KiB
www.arduino.cc/_next/static/css/1877494b167afcc1.css0.0 ms1.8 KiB
cdn.arduino.cc/header-footer/prod/cookieSolution.js86400.0 s3.8 KiB
www.arduino.cc/_next/static/chunks/387.11de658b66f767eb.js0.0 ms1.3 KiB
www.arduino.cc/_next/static/css/9ecf58cd11b16fa7.css0.0 ms1.2 KiB
www.arduino.cc/_next/static/4qJ0ibVGo3Pi6iHxuXXag/_buildManifest.js0.0 ms967 B
www.arduino.cc/_next/static/css/c924c4baaad337e3.css0.0 ms685 B
www.arduino.cc/_next/static/css/4440a680f9832684.css0.0 ms667 B
www.arduino.cc/_next/static/4qJ0ibVGo3Pi6iHxuXXag/_ssgManifest.js0.0 ms614 B
www.arduino.cc/images/arrow.svg86400.0 s1.1 KiB
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s2.3 KiB
content.arduino.cc/assets/16-9.webm86400.0 s0 B

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
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff240 ms

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
cdn.arduino.cc/header-footer/prod/cookieSolution.css5.1 KiB237 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Arduino UNO Q div.product-list > div.product-list__item > div.product-list__image > img
/cdn-cgi/image/width=1080,quality=60,format=auto/https://...37.4 KiB32.2 KiB
Empowering anyone to innovate div#homepage-content > div.secondary-hero-banner__wrapper > div.secondary-hero-banner > img
/cdn-cgi/image/width=1920,quality=60,format=auto/https://...47.8 KiB29.1 KiB
Arduino R4 Starter Kit div.product-list > div.product-list__item > div.product-list__image > img
/cdn-cgi/image/width=1080,quality=60,format=auto/https://...22.8 KiB19.6 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 205 ms
URLTime Spent
arduino.cc/205 ms
www.arduino.cc/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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 41.0 KiB
URLTransfer SizeEst Savings
www.arduino.cc/_next/static/css/90ba35feb71cde2a.css45.9 KiB41.0 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 400 ms 445.1 KiB
URLTransfer SizeEst Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js361.8 KiB177.0 KiB
www.googletagmanager.com/gtag/js?id=G-NEXN8H46L5&cx=c&gtm=4e64k0h2174.0 KiB70.2 KiB
cdn.iubenda.com/cookie_solution/iubenda_cs/1.98.0/core-en.js110.2 KiB67.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-NK2TW8L199.0 KiB51.0 KiB
www.arduino.cc/_next/static/chunks/pages/_app-6c6282e55ed0056f.js57.3 KiB36.6 KiB
www.arduino.cc/_next/static/chunks/9104-95c6abddeae501c7.js35.3 KiB21.6 KiB
www.arduino.cc/_next/static/chunks/9575-5ded90c66ba306b0.js35.4 KiB20.8 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
content.arduino.cc/assets/16-9.webm5.3 MiB
/cdn-cgi/image/width=640,quality=60,format=auto/https://w...3.5 MiB
/cdn-cgi/image/width=640,quality=60,format=auto/https://w...1.5 MiB
/cdn-cgi/image/width=640,quality=60,format=auto/https://w...1.1 MiB
www.datocms-assets.com/150482/1742310237-brand-dark.jpg365.8 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js362.4 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js361.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-NK2TW8L199.4 KiB
www.googletagmanager.com/gtag/js?id=G-NEXN8H46L5&cx=c&gtm=4e64k0h2174.1 KiB
/cdn-cgi/image/width=1920,quality=60,format=auto/https://...137.3 KiB

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

●Max Potential First Input Delay 80 ms
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 9 user timings
●JavaScript execution time 0.6 s
●Minimizes main-thread work 1.4 s
●Avoid long main-thread tasks 3 long tasks found
●Avoid non-composited animations 4 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 50 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 30 ms
○INP breakdown
○LCP request discovery
○Avoid large layout shifts
90

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Bring your IoT projects to life quickly div#content-page-cRxHrrg9SD2c58bY5VmNug > div.product-list > div.product-list__item > div.product-list__description
DISCOVER CLOUD div.product-list__buttons > div.button-list > a.button-list__item > span
EDUCATION div.success-stories-card__text > div.success-stories-card__badge > div.tag-content > span
ABOUT ARDUINO div._Footer__row_1usg3_14 > div._Footer__column_1usg3_69 > div._Footer__column--link-list_1usg3_108 > a._Typography_6tld9_1
CAREERS div._Footer__row_1usg3_14 > div._Footer__column_1usg3_69 > div._Footer__column--link-list_1usg3_108 > a._Typography_6tld9_1

These are opportunities to improve the legibility of your content.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div._Header-content_93jou_79 > div._StandardHeader-content_1go1u_1 > div._StandardHeader-mobile-buttons_1go1u_9 > a._Typography_6tld9_1 div._Header-content_93jou_79 > div._StandardHeader-content_1go1u_1 > div._StandardHeader-mobile-buttons_1go1u_9 > a._Typography_6tld9_1

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
For Professionals For Education For Makers div._StandardHeader-content_1go1u_1 > div._MenuList-wrapper_q55wc_14 > div > ul._MenuList_q55wc_5

These are opportunities to improve the experience of reading tabular or list data using 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
●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
●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
●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.
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●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.
○`[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 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
○`<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
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○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
92

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

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
www.arduino.cc/qualcommLEARN MORE
www.arduino.cc/en/about#our-mission--visionLEARN 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
●Document has a meta description
●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