Tools & Wizards About Us
xmotors.ai screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 0

    Best Practices

  • 85

    SEO

    Google-friendlier than
    55% of websites

xmotors.ai

XPENG - Official Website | XPENG Motors – XPENG

Page Load Speed

7.4 sec in total

First Response

437 ms

Resources Loaded

6 sec

Page Rendered

966 ms

xmotors.ai screenshot

About Website

Visit xmotors.ai now to see the best up-to-date X Motors content for United States and also check out these interesting facts you probably never knew about xmotors.ai

Welcome to the official website of XPENG Motors. Discover our newest models, customize your smart e-vehicle and drive today the car of tomorrow.

Visit xmotors.ai

Key Findings

We analyzed Xmotors.ai page load time and found that the first response time was 437 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

xmotors.ai performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value65.9 s

0/100

25%

SI (Speed Index)

Value47.6 s

0/100

10%

TBT (Total Blocking Time)

Value1,800 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value90.1 s

0/100

10%

Network Requests Diagram

xmotors.ai

437 ms

2527 ms

www.heyxpeng.com

845 ms

www.xpeng.com

541 ms

gtm.js

60 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Xmotors.ai, 38% (12 requests) were made to A-cdn.xpeng.com and 28% (9 requests) were made to S-cdn.xpeng.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source En.xiaopeng.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 152.0 kB (1%)

Content Size

19.1 MB

After Optimization

19.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xmotors.ai main page is 19.1 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. 35% of websites need less resources to load. Images take 17.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 151.5 kB

  • Original 189.4 kB
  • After minification 189.4 kB
  • After compression 37.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 151.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 17.5 MB
  • After minification 17.5 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. X Motors images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 450 B

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 1.4 MB

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

  • Original 47.5 kB
  • After minification 47.5 kB
  • After compression 47.5 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. Xmotors.ai has all CSS files already compressed.

Requests Breakdown

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

Requests Now

26

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xmotors.ai

xmotors.ai

437 ms

2527 ms

www.heyxpeng.com

www.heyxpeng.com

845 ms

www.xpeng.com

www.xpeng.com

541 ms

gtm.js

gtm.js

60 ms

Page.068c988a.chunk.css

Page.068c988a.chunk.css

252 ms

index.a34b7e32.chunk.css

index.a34b7e32.chunk.css

262 ms

otSDKStub.js

otSDKStub.js

42 ms

runtime~Page.f62fd73f.js

runtime~Page.f62fd73f.js

235 ms

vendor.60dc94a0.chunk.js

vendor.60dc94a0.chunk.js

278 ms

Page.d95b639d.chunk.js

Page.d95b639d.chunk.js

253 ms

50ef7a2c-292e-43cb-b866-63105f6064b3.json

50ef7a2c-292e-43cb-b866-63105f6064b3.json

78 ms

c21c0defade64b0498ab159c2f4c9817.png

c21c0defade64b0498ab159c2f4c9817.png

258 ms

G92024-360.png

G92024-360.png

1368 ms

g6-sprite.png

g6-sprite.png

1428 ms

logo-white.e37e4b0b.svg

logo-white.e37e4b0b.svg

58 ms

g3i-sprite.a8c7d1ec.png

g3i-sprite.a8c7d1ec.png

152 ms

x9-sprite.91933574.png

x9-sprite.91933574.png

149 ms

p7i-sprite.6e2c553a.png

p7i-sprite.6e2c553a.png

147 ms

p5-sprite.b26a0bb2.png

p5-sprite.b26a0bb2.png

154 ms

79782f3a2b2d46ef8cadb415ff5f97a6.png

79782f3a2b2d46ef8cadb415ff5f97a6.png

257 ms

070103fd2b44492c84cd8fbd90ea8b5a.png

070103fd2b44492c84cd8fbd90ea8b5a.png

648 ms

693ae3eed1304c6db5548c5add83b72c.png

693ae3eed1304c6db5548c5add83b72c.png

260 ms

ee815d1570b549a7a3bbd5442b0e71dd.png

ee815d1570b549a7a3bbd5442b0e71dd.png

261 ms

0d416611716542a49ccccf56280a5b44.png

0d416611716542a49ccccf56280a5b44.png

262 ms

04eea4ec8a724ec389207517f949f19c.jpg

04eea4ec8a724ec389207517f949f19c.jpg

264 ms

428f21828558420a89a92b7f24bad05d.jpg

428f21828558420a89a92b7f24bad05d.jpg

265 ms

df9008393454443aaa9b985d15cb1dd8.jpg

df9008393454443aaa9b985d15cb1dd8.jpg

652 ms

basis_grotesque_regular.otf

basis_grotesque_regular.otf

416 ms

BasisGrotesque_Bold.otf

BasisGrotesque_Bold.otf

689 ms

location

location

98 ms

otBannerSdk.js

otBannerSdk.js

30 ms

Accessibility Review

xmotors.ai accessibility score

82

Accessibility Issues

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

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

Image elements do not have [alt] attributes

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.

SEO Factors

xmotors.ai SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

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 Xmotors.ai 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 Xmotors.ai 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

xmotors.ai

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