Skip to content
Audit Complete

Results for https://tinkercad.com

Visit site
Spain Spain · Madrid Completed: Apr 22, 2026 23:03 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

Score: 75 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Mostly accessible, but some users still face barriers.

Solid SEO basics — a few optimizations could boost rankings.

Solid infrastructure — fast server responses across the board.

Strong compliance posture across regulations.

Rich content metadata — your pages look great everywhere.

Reasonable footprint with room for optimization.

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.

How the composite score is calculated

How you compare

Amazon ELB · 172 peers
You 75
·
Avg 70
At average
0 50 100
Better than 86% of Amazon ELB sites See full Amazon ELB benchmark →
Amazon Route 53 · 975 peers
You 75
·
Avg 72
At average
0 50 100
Better than 77% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

1 image-only link(s) without alt text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
5

82 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Ftinkercad.com)](https://beavercheck.com/results/8ca755ab-d698-4cb6-b4a9-ea533adb2255)
<a href="https://beavercheck.com/results/8ca755ab-d698-4cb6-b4a9-ea533adb2255"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ftinkercad.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Ftinkercad.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 8.7s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
1 accessibility issue excludes users who rely on assistive technology.
Your LCP is 8.7s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

2 critical 6 warning

8 barrier(s) likely increasing bounce by ~30%.

Speed (2)

Page takes 8.7s to load

+12% bounce

Users abandon at ~3s — you're 6.2s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

High main-thread blocking time

+2% bounce

Page is non-interactive for 262ms after first paint

Fix: Defer third-party scripts and split large bundles

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

Severe layout shift during page load

+6% bounce

Users mis-click when content jumps — converting intent into frustration

Fix: Reserve space for images, ads, and embeds with explicit width/height

Content (2)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$500 investment → $6,521/month returns + USD 150,000 risk avoided

Payback period: < 1 month First-year ROI: +15550%

Investment

$500

5h · 5 findings

Monthly returns

$6,521 /mo

~$78,250 / year

  • Conversions recovered $6,520
  • Bandwidth savings $0.39

Regulatory risk avoided

USD 150,000

if kept compliant

  • ADA Title III USD 150,000

Payback period

0 12mo 24mo

$150 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$500

5.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$12,500 / month at risk

~$150,005 / year if left unfixed

Compliance Risk

$150,000

ADA Title III
  • Skip navigation link is missing (WCAG 2.4.1)
    ADA Title III: USD 25,000 – USD 150,000
  • Heading level skipped: H2 → H4 (missing H3)
    ADA Title III: USD 25,000 – USD 150,000
  • 1 image-only link(s) without alt text
    ADA Title III: USD 25,000 – USD 150,000

Bandwidth Waste

$0.39 /mo

4878.0 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~488 KB per page load
    Saves $0.39/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 4 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

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

Core Web Vitals

Key metrics that affect user experience.

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

4.25 s

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

8.66 s

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

262 ms

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

1.709

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

5.02 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.29 s

Detailed Report

Audit breakdown by category with detailed findings.

33

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:1.708805] map[node:map[boundingRect:map[bottom:7239 height:1708 left:0 right:412 top:5531 width:412] lhId:page-10-FOOTER nodeLabel:Tomorrow’s innovators are made today At Autodesk, we empower innovators everyw… path:1,HTML,1,BODY,0,DIV,0,DIV,5,APP,4,TK-FOOTER,0,FOOTER selector:div > app > tk-footer.ng-star-inserted > footer#footer snippet:<footer _ngcontent-ng-c1571661075="" id="footer" class="tk-footer ng-star-inserted"> type:node] score:1] map[node:map[boundingRect:map[bottom:6813 height:892 left:0 right:412 top:5921 width:412] lhId:page-1-DIV nodeLabel:Tinkercad is a free web app for 3D design, electronics, and coding. We’re the i… path:1,HTML,1,BODY,0,DIV,0,DIV,5,APP,4,TK-FOOTER,0,FOOTER,2,DIV selector:app > tk-footer.ng-star-inserted > footer#footer > div.tk-footer-content snippet:<div _ngcontent-ng-c1571661075="" class="tk-footer-content"> type:node] score:0.707052] map[node:map[boundingRect:map[bottom:6350 height:52 left:24 right:192 top:6298 width:168] lhId:page-6-IMG nodeLabel:div.tk-footer-content-right > tk-chrome-link > a > img path:1,HTML,1,BODY,0,DIV,0,DIV,5,APP,4,TK-FOOTER,0,FOOTER,2,DIV,4,DIV,2,TK-CHROME-LINK,0,A,0,IMG selector:div.tk-footer-content-right > tk-chrome-link > a > img snippet:<img _ngcontent-ng-c646579678="" alt="" src="https://static.tinkercad.com/nav/store/en.svg"> type:node] score:0.001753]]

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.

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-DIV
nodeLabel: Tomorrow’s innovators are made today At Autodesk, we empower innovators everyw…
path: 1,HTML,1,BODY,0,DIV,0,DIV,5,APP,4,TK-FOOTER,0,FOOTER,0,DIV
selector: app > tk-footer.ng-star-inserted > footer#footer > div.tk-footer-innovators
snippet: <div _ngcontent-ng-c1571661075="" class="tk-footer-innovators ng-star-inserted" style="background-image: url(&quot;https://static.tinkercad.com/nav/banner_innovators.…&quot;);">

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

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.

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.

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: 1.0 s
URLTime Spent
tinkercad.com/1.0 s
www.tinkercad.com/0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Tomorrow’s innovators are made today At Autodesk, we empower innovators everyw… div > app > tk-footer.ng-star-inserted > footer#footer
1.000
Tinkercad is a free web app for 3D design, electronics, and coding. We’re the i… app > tk-footer.ng-star-inserted > footer#footer > div.tk-footer-content
0.707
div.tk-footer-content-right > tk-chrome-link > a > img div.tk-footer-content-right > tk-chrome-link > a > img
0.002

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 170 ms 18.5 KiB
URLTransfer SizeEst Savings
www.tinkercad.com/bootstrap.min.css18.7 KiB18.5 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 1.5 s 278.0 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable

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
Autodesk Tinkercad tk-header-logo.ng-star-inserted > div.tk-header-logo > a#header-logo > img.tk-header-logo-text-svg
static.tinkercad.com/images/tinkercad-lockup-white.svg
div.tk-footer-content-right > tk-chrome-link > a > img div.tk-footer-content-right > tk-chrome-link > a > img
static.tinkercad.com/nav/store/en.svg

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

Optimize DOM size
Forced reflow
Improve image delivery
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 1,588 KiB
User Timing marks and measures 40 user timings
JavaScript execution time 1.0 s
Minimizes main-thread work 1.9 s
Avoid long main-thread tasks 7 long tasks found
Avoid non-composited animations 1 animated element found
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 490 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 150 ms
INP breakdown
92

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.

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
Free for everyone div.home > div.home-bullets > div.home-bullets-item > h3
Start designing in 3D div.home-products > div.home-products-item > div.home-products-item-text > h4

These are opportunities to improve keyboard navigation in your application.

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
footer#footer > div.footer-kidsafe > div#ksp-seals > a

Screen readers cannot translate non-text content. Adding alternate text to `<object>` elements helps screen readers convey meaning to users. Learn more about alt text for `object` elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer-kidsafe > div#ksp-seals > a > object div.footer-kidsafe > div#ksp-seals > a > object
div.footer-kidsafe > div#ksp-seals > a > object div.footer-kidsafe > div#ksp-seals > a > object

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
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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.
Select elements have associated label elements.
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
`<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.
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
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
`[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
Buttons have an accessible name
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">`
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
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.
96

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: the server responded with a status of 401 ()
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
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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Proceed anyway div.modal-content > div.modal-body > div.compatibility-actions > a.button-lg
Back to website div.modal-content > div.modal-body > div.compatibility-actions > a.button-lg
tk-home.ng-star-inserted > div.home > div.home-hero > a.home-hero-play tk-home.ng-star-inserted > div.home > div.home-hero > a.home-hero-play
tk-marketing-video > div.video-section-video > span > a.video-section-play tk-marketing-video > div.video-section-video > span > a.video-section-play
tk-marketing-video > div.video-section-video > span > a.video-section-play tk-marketing-video > div.video-section-video > span > a.video-section-play
tk-marketing-video > div.video-section-video > span > a.video-section-play tk-marketing-video > div.video-section-video > span > a.video-section-play

To appear in search results, crawlers need access to your app.

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

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

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

1.35 s

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

2.57 s

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

0 ms

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

0.265

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

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

2.58 s

Detailed Report

Audit breakdown by category with detailed findings.

67

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.264904] map[node:map[boundingRect:map[bottom:5355 height:884 left:0 right:1350 top:4471 width:1350] lhId:page-4-FOOTER nodeLabel:Tomorrow’s innovators are made today At Autodesk, we empower innovators everyw… path:1,HTML,1,BODY,0,DIV,0,DIV,5,APP,4,TK-FOOTER,0,FOOTER selector:div > app > tk-footer.ng-star-inserted > footer#footer snippet:<footer _ngcontent-ng-c1571661075="" id="footer" class="tk-footer ng-star-inserted"> type:node] score:0.257447] map[node:map[boundingRect:map[bottom:5093 height:355 left:75 right:1275 top:4738 width:1200] lhId:page-1-DIV nodeLabel:Tinkercad is a free web app for 3D design, electronics, and coding. We’re the i… path:1,HTML,1,BODY,0,DIV,0,DIV,5,APP,4,TK-FOOTER,0,FOOTER,2,DIV selector:app > tk-footer.ng-star-inserted > footer#footer > div.tk-footer-content snippet:<div _ngcontent-ng-c1571661075="" class="tk-footer-content"> type:node] score:0.007336] map[node:map[boundingRect:map[bottom:4557 height:38 left:370 right:980 top:4519 width:611] lhId:page-3-H2 nodeLabel:Tomorrow’s innovators are made today path:1,HTML,1,BODY,0,DIV,0,DIV,5,APP,4,TK-FOOTER,0,FOOTER,0,DIV,0,DIV,0,H2 selector:footer#footer > div.tk-footer-innovators > div.tk-footer-innovators-content > h2 snippet:<h2 _ngcontent-ng-c1571661075=""> type:node] score:0.000121 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://www.tinkercad.com/assets_fe_2200edbba71b52816a12975ae2f05b1895859de5/js/tinkercad-frontend/browser/media/ArtifaktLegendExtraBold.woff2]]] type:subitems]]]

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:34.548 source:map[type:text value:[unattributed]]]]

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-VIDEO
nodeLabel: Creating 3D designs of a racecar, plane, and LED light.
path: 1,HTML,1,BODY,0,DIV,0,DIV,5,APP,3,DIV,0,DIV,0,MAIN,1,TK-HOME,0,DIV,0,DIV,0,VIDEO
selector: tk-home.ng-star-inserted > div.home > div.home-hero > video
snippet: <video _ngcontent-ng-c2163060188="" playsinline="" poster="https://static.tinkercad.com/marketing/home/hero-home-poster-airplane_w180…" aria-label="Creating 3D designs of a racecar, plane, and LED light.">

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

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.

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
Common Core Logo div.home-column > div.home-standards-text > div.home-standards-icons > img
static.tinkercad.com/marketing/home/common-core_w450.png35.0 KiB34.0 KiB
NGSS Logo div.home-column > div.home-standards-text > div.home-standards-icons > img
static.tinkercad.com/marketing/home/ngss_w450.png32.8 KiB32.0 KiB
Creating 3D designs of a racecar, plane, and LED light. tk-home.ng-star-inserted > div.home > div.home-hero > video
static.tinkercad.com/marketing/home/hero-home-poster-airplane_w1800.jpg56.8 KiB21.0 KiB
A young girl using a laptop in a classroom. div.home-standards > div.home-column > div.home-standards-image > img
static.tinkercad.com/marketing/home/educational-standards_w600.jpg30.8 KiB12.8 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: 487 ms
URLTime Spent
tinkercad.com/487 ms
www.tinkercad.com/0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Tomorrow’s innovators are made today At Autodesk, we empower innovators everyw… div > app > tk-footer.ng-star-inserted > footer#footer
0.257
Tinkercad is a free web app for 3D design, electronics, and coding. We’re the i… app > tk-footer.ng-star-inserted > footer#footer > div.tk-footer-content
0.007
Tomorrow’s innovators are made today footer#footer > div.tk-footer-innovators > div.tk-footer-innovators-content > h2
0.000

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 170 ms 276.8 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable

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 18.5 KiB
URLTransfer SizeEst Savings
www.tinkercad.com/bootstrap.min.css18.7 KiB18.5 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
Autodesk Tinkercad tk-header-logo.ng-star-inserted > div.tk-header-logo > a#header-logo > img.tk-header-logo-text-svg
static.tinkercad.com/images/tinkercad-lockup-white.svg
div.tk-footer-content-right > tk-chrome-link > a > img div.tk-footer-content-right > tk-chrome-link > a > img
static.tinkercad.com/nav/store/en.svg

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

Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 50 ms
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 1,536 KiB
User Timing marks and measures 40 user timings
JavaScript execution time 0.2 s
Minimizes main-thread work 0.5 s
Avoid non-composited animations 1 animated element found
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 260 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 20 ms
INP breakdown
Avoid long main-thread tasks
92

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.

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
Free for everyone div.home > div.home-bullets > div.home-bullets-item > h3
Start designing in 3D div.home-products > div.home-products-item > div.home-products-item-text > h4

These are opportunities to improve keyboard navigation in your application.

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
footer#footer > div.footer-kidsafe > div#ksp-seals > a

Screen readers cannot translate non-text content. Adding alternate text to `<object>` elements helps screen readers convey meaning to users. Learn more about alt text for `object` elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer-kidsafe > div#ksp-seals > a > object div.footer-kidsafe > div#ksp-seals > a > object
div.footer-kidsafe > div#ksp-seals > a > object div.footer-kidsafe > div#ksp-seals > a > object

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
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
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.
Select elements have associated label elements.
`button`, `link`, and `menuitem` elements have accessible names
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
`<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.
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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
Buttons have an accessible name
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">`
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
Image elements do not have `[alt]` attributes that are redundant text.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: the server responded with a status of 401 ()
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
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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Proceed anyway div.modal-content > div.modal-body > div.compatibility-actions > a.button-lg
Back to website div.modal-content > div.modal-body > div.compatibility-actions > a.button-lg
tk-home.ng-star-inserted > div.home > div.home-hero > a.home-hero-play tk-home.ng-star-inserted > div.home > div.home-hero > a.home-hero-play
tk-marketing-video > div.video-section-video > span > a.video-section-play tk-marketing-video > div.video-section-video > span > a.video-section-play
tk-marketing-video > div.video-section-video > span > a.video-section-play tk-marketing-video > div.video-section-video > span > a.video-section-play
tk-marketing-video > div.video-section-video > span > a.video-section-play tk-marketing-video > div.video-section-video > span > a.video-section-play

To appear in search results, crawlers need access to your app.

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
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback