Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

apollo.auto

智能驾驶系统-百度智能驾驶解决方案及汽车智能化产品-百度Apollo|Baidu阿波罗

Page Load Speed

30.8 sec in total

First Response

745 ms

Resources Loaded

29.4 sec

Page Rendered

595 ms

apollo.auto screenshot

About Website

Welcome to apollo.auto homepage info - get ready to check Apollo best content for China right away, or after learning these important things about apollo.auto

百度Apollo智能驾驶系统助力车企打造面向未来的智能网联汽车,提供智驾/智舱/智图的全栈式智能驾驶解决方案,百度Apollo已与蔚来,领克,理想,凯达拉克,长城哈弗,吉利等70+车企合作,800+合作车型,1800万车主享受服务.想了解更多百度汽车智能化,AVP,ANP,百度地图汽车版,小度助手等智能辅助驾驶,智能驾驶汽车解决方案关注百度Apollo官网.

Visit apollo.auto

Key Findings

We analyzed Apollo.auto page load time and found that the first response time was 745 ms and then it took 30 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

apollo.auto performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value39.3 s

0/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value25.3 s

0/100

10%

Network Requests Diagram

apollo.auto

745 ms

apollo.auto

1019 ms

apollo-self-driving

3420 ms

layui.css

261 ms

extend.css

522 ms

Our browser made a total of 138 requests to load all elements on the main page. We found that 65% of them (90 requests) were addressed to the original Apollo.auto, 34% (47 requests) were made to Apollo-new.cdn.bcebos.com and 1% (1 request) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Hm.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (36%)

Content Size

3.8 MB

After Optimization

2.4 MB

In fact, the total size of Apollo.auto main page is 3.8 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. 50% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 339.0 kB

  • Original 368.4 kB
  • After minification 206.1 kB
  • After compression 29.3 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. This page needs HTML code to be minified as it can gain 162.3 kB, which is 44% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 339.0 kB or 92% of the original size.

Image Optimization

-9%

Potential reduce by 216.9 kB

  • Original 2.5 MB
  • After minification 2.3 MB

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. Apollo images are well optimized though.

CSS Optimization

-89%

Potential reduce by 812.0 kB

  • Original 910.4 kB
  • After minification 776.5 kB
  • After compression 98.4 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. Apollo.auto needs all CSS files to be minified and compressed as it can save up to 812.0 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (18%)

Requests Now

97

After Optimization

80

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

Accessibility Review

apollo.auto accessibility score

79

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

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

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

apollo.auto best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

apollo.auto SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Apollo.auto can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Apollo.auto 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 description is not detected on the main page of Apollo. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: