Report Summary

  • 37

    Performance

    Renders faster than
    58% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

autoware.org

The Autoware Foundation - Open Source for Autonomous Driving

Page Load Speed

6.6 sec in total

First Response

2.3 sec

Resources Loaded

4.1 sec

Page Rendered

110 ms

autoware.org screenshot

About Website

Visit autoware.org now to see the best up-to-date Autoware content and also check out these interesting facts you probably never knew about autoware.org

The Autoware Foundation is a non-profit organization supporting open-source projects enabling self-driving mobility. The Autoware Foundation creates synergies between corporate development and academi...

Visit autoware.org

Key Findings

We analyzed Autoware.org page load time and found that the first response time was 2.3 sec and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

autoware.org performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value1,940 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

www.autoware.org

2302 ms

bt

50 ms

minified.js

49 ms

fetch.umd.js

171 ms

bolt-custom-elements.min.js

189 ms

Our browser made a total of 159 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Autoware.org, 84% (134 requests) were made to Static.wixstatic.com and 11% (17 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Autoware.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 997.2 kB (79%)

Content Size

1.3 MB

After Optimization

272.6 kB

In fact, the total size of Autoware.org main page is 1.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 964.4 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 137.4 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 964.4 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 78.6 kB
  • After minification 78.6 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. Autoware images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 32.8 kB

  • Original 89.4 kB
  • After minification 63.8 kB
  • After compression 56.6 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 32.8 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (6%)

Requests Now

142

After Optimization

134

The browser has sent 142 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Autoware. 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 as a result speed up the page load time.

Accessibility Review

autoware.org accessibility score

83

Accessibility Issues

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

Image elements do not have [alt] attributes

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

autoware.org best practices score

92

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

Page has valid source maps

SEO Factors

autoware.org SEO score

91

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

Image elements do not have [alt] attributes

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 Autoware.org 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 Autoware.org 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

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