Tools & Wizards About Us
autodesk360.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

autodesk360.com

Autodesk Fusion Team | Autodesk Fusion | Autodesk

Page Load Speed

2.8 sec in total

First Response

11 ms

Resources Loaded

1 sec

Page Rendered

1.7 sec

autodesk360.com screenshot

About Website

Click here to check amazing Autodesk 360 content for United States. Otherwise, check out these important facts you probably never knew about autodesk360.com

Start collaborating now with Autodesk Fusion Team Participant. Work smarter and simplify collaboration when working with your internal and external teams.

Visit autodesk360.com

Key Findings

We analyzed Autodesk360.com page load time and found that the first response time was 11 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

autodesk360.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value5,530 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value38.3 s

0/100

10%

Network Requests Diagram

autodesk360.com

11 ms

team-participant

192 ms

dhig-global.css

39 ms

main.js

83 ms

main.js

98 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Autodesk360.com, 37% (22 requests) were made to Swc.autodesk.com and 29% (17 requests) were made to Static-dc.autodesk.net. The less responsive or slowest element that took the longest time to load (580 ms) relates to the external source Damassets.autodesk.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (56%)

Content Size

1.9 MB

After Optimization

840.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Autodesk360.com main page is 1.9 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. CSS take 958.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 236.3 kB

  • Original 276.2 kB
  • After minification 257.4 kB
  • After compression 39.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 236.3 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 2.8 kB

  • Original 204.6 kB
  • After minification 201.8 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Autodesk 360 images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.2 kB

  • Original 487.5 kB
  • After minification 487.5 kB
  • After compression 485.4 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-88%

Potential reduce by 845.4 kB

  • Original 958.7 kB
  • After minification 951.5 kB
  • After compression 113.3 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Autodesk360.com needs all CSS files to be minified and compressed as it can save up to 845.4 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (75%)

Requests Now

51

After Optimization

13

  • Images
  • JavaScript
  • CSS

The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Autodesk 360. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

autodesk360.com

autodesk360.com

11 ms

team-participant

team-participant

192 ms

dhig-global.css

dhig-global.css

39 ms

main.js

main.js

83 ms

main.js

main.js

98 ms

utag.sync.js

utag.sync.js

64 ms

clientlib-dhig.min.css

clientlib-dhig.min.css

63 ms

clientlib.min.css

clientlib.min.css

82 ms

clientlib.min.css

clientlib.min.css

90 ms

clientlib.min.css

clientlib.min.css

91 ms

clientlib.min.css

clientlib.min.css

90 ms

clientlib.min.css

clientlib.min.css

91 ms

clientlib.min.css

clientlib.min.css

105 ms

clientlib.min.css

clientlib.min.css

94 ms

clientlib.min.css

clientlib.min.css

136 ms

clientlib.min.css

clientlib.min.css

94 ms

clientlib.min.css

clientlib.min.css

93 ms

clientlib.min.css

clientlib.min.css

94 ms

clientlib.min.css

clientlib.min.css

95 ms

clientlib.min.css

clientlib.min.css

100 ms

clientlib.min.css

clientlib.min.css

96 ms

app.css

app.css

157 ms

flyout.css

flyout.css

85 ms

app.js

app.js

101 ms

app.css

app.css

118 ms

clientlib-dhig.min.js

clientlib-dhig.min.js

105 ms

clientlib-loader.min.js

clientlib-loader.min.js

98 ms

app.js

app.js

142 ms

app.js

app.js

97 ms

app.js

app.js

97 ms

app.js

app.js

198 ms

utag.js

utag.js

78 ms

iconography-cart-light.svg

iconography-cart-light.svg

82 ms

device-desktop.svg

device-desktop.svg

4 ms

products-and-services.svg

products-and-services.svg

6 ms

online-viewers.svg

online-viewers.svg

4 ms

caret-right.svg

caret-right.svg

6 ms

caret-down.svg

caret-down.svg

8 ms

facebook-circle.svg

facebook-circle.svg

7 ms

instagram-circle.svg

instagram-circle.svg

9 ms

twitter-circle.svg

twitter-circle.svg

11 ms

linkedin-circle.svg

linkedin-circle.svg

12 ms

youtube.svg

youtube.svg

12 ms

architecture-engineering-construction-collection-uhblack-banner-lockup-364x40.png

architecture-engineering-construction-collection-uhblack-banner-lockup-364x40.png

77 ms

product-design-manufacturing-collection-uhblack-banner-lockup-364x40.png

product-design-manufacturing-collection-uhblack-banner-lockup-364x40.png

76 ms

media-entertainment-collection-uhblack-banner-lockup-364x40.png

media-entertainment-collection-uhblack-banner-lockup-364x40.png

77 ms

fusion-lockup-610x66.png

fusion-lockup-610x66.png

76 ms

collaboration-video-thumb-370x218.jpg

collaboration-video-thumb-370x218.jpg

440 ms

user-management-video-thumb-370x218.jpg

user-management-video-thumb-370x218.jpg

165 ms

global-share-video-thumb-370x218.jpg

global-share-video-thumb-370x218.jpg

228 ms

commenting-and-redlining-video-thumb-370x218.jpg

commenting-and-redlining-video-thumb-370x218.jpg

279 ms

unlimited-access-video-thumb-370x218.jpg

unlimited-access-video-thumb-370x218.jpg

77 ms

public-private-design-sharing-video-thumb-370x218.jpg

public-private-design-sharing-video-thumb-370x218.jpg

340 ms

team-participant-video-thumb-370x218.jpg

team-participant-video-thumb-370x218.jpg

220 ms

collaborator-banner-1500x892.jpg

collaborator-banner-1500x892.jpg

580 ms

Artifakt%20Element%20Bold.woff

Artifakt%20Element%20Bold.woff

18 ms

Artifakt%20Element%20Semi%20Bold.woff

Artifakt%20Element%20Semi%20Bold.woff

7 ms

Artifakt%20Element%20Regular.woff

Artifakt%20Element%20Regular.woff

7 ms

Artifakt%20Legend%20Extra%20Bold.woff

Artifakt%20Legend%20Extra%20Bold.woff

3 ms

Accessibility Review

autodesk360.com accessibility score

67

Accessibility Issues

ARIA

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

[aria-*] attributes do not have valid values

Names and labels

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.

Impact

Issue

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best Practices

autodesk360.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

autodesk360.com SEO score

78

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Autodesk360.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Autodesk360.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

autodesk360.com

Open Graph data is detected on the main page of Autodesk 360. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: