Report Summary

  • 0

    Performance

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

nio.com

NIO - Home

Page Load Speed

5.6 sec in total

First Response

293 ms

Resources Loaded

4.2 sec

Page Rendered

1.1 sec

About Website

Click here to check amazing NIO content for China. Otherwise, check out these important facts you probably never knew about nio.com

NIO is much more than a car company. NIO designs and develops smart, high-performance, electric vehicles with an aim to be the first “User Enterprise” in the world.

Visit nio.com

Key Findings

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

Performance Metrics

nio.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value42.8 s

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value320 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.5 s

58/100

10%

Network Requests Diagram

nio.com

293 ms

www.nio.com

360 ms

62b4ca00ee754db9.css

440 ms

a73850a796d3c9da.css

317 ms

6b6c729aaef9cd80.css

338 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that all of those requests were addressed to Nio.com and no external sources were called. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Nio.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 166.0 kB (2%)

Content Size

8.9 MB

After Optimization

8.7 MB

In fact, the total size of Nio.com main page is 8.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. 65% of websites need less resources to load. Images take 8.0 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 118.9 kB

  • Original 136.7 kB
  • After minification 136.3 kB
  • After compression 17.8 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 118.9 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 46.6 kB

  • Original 8.0 MB
  • After minification 7.9 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. NIO images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 374 B

  • Original 676.7 kB
  • After minification 676.7 kB
  • After compression 676.3 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

-0%

Potential reduce by 122 B

  • Original 77.8 kB
  • After minification 77.8 kB
  • After compression 77.7 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. Nio.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (42%)

Requests Now

97

After Optimization

56

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

Accessibility Review

nio.com accessibility score

83

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-hidden="true"] elements contain focusable descendents

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

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

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

nio.com best practices score

75

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

SEO Factors

nio.com SEO score

90

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

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

Open Graph description is not detected on the main page of NIO. 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: