25.8 sec in total
780 ms
24.3 sec
699 ms
Visit xcar.cn now to see the best up-to-date Xcar content and also check out these interesting facts you probably never knew about xcar.cn
爱卡汽车网为您提供最新汽车报价、汽车图片、车型资料、汽车论坛、汽车资讯信息,XCAR-爱卡汽车网是中国领先的汽车主题社区,其中包括85个主流品牌车型俱乐部,国内32个省市和地区分会,36个特色讨论区。
Visit xcar.cnWe analyzed Xcar.cn page load time and found that the first response time was 780 ms and then it took 25 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number 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.
xcar.cn performance score
name
value
score
weighting
Value12.5 s
0/100
10%
Value18.6 s
0/100
25%
Value12.9 s
2/100
10%
Value1,370 ms
16/100
30%
Value0.075
95/100
15%
Value21.9 s
1/100
10%
780 ms
719 ms
1718 ms
400 ms
402 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Xcar.cn, 33% (43 requests) were made to Img1.xcarimg.com and 13% (17 requests) were made to Xcar.com.cn. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Dx0.xcar.com.cn.
Page size can be reduced by 28.0 MB (89%)
31.5 MB
3.5 MB
In fact, the total size of Xcar.cn main page is 31.5 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. 80% 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. Images take 28.3 MB which makes up the majority of the site volume.
Potential reduce by 2.8 MB
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 2.8 MB or 95% of the original size.
Potential reduce by 25.1 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. Obviously, Xcar needs image optimization as it can save up to 25.1 MB or 89% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 50.7 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 50.7 kB or 26% of the original size.
Potential reduce by 1.9 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. Xcar.cn needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 27% of the original size.
Number of requests can be reduced by 31 (26%)
119
88
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xcar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
xcar.cn
780 ms
www.xcar.com.cn
719 ms
www.xcar.com.cn
1718 ms
sprite2x.css
400 ms
jquery-1.8.3.min.js
402 ms
load.min.js
1070 ms
template-web.js
332 ms
zhuge-pc.js
332 ms
main-template.full.js
333 ms
adpc
8737 ms
public_func.js
1208 ms
xlogin_box_utf.js
118 ms
2.3.js
321 ms
msg.js
320 ms
header2019.js
119 ms
clearCookie.js
321 ms
delayLoading.min.js
120 ms
commonCode.js
119 ms
adpc
4318 ms
main.js
118 ms
adpc
3351 ms
adpc
4724 ms
adpc
6136 ms
adpc
4712 ms
adpc
6568 ms
adpc
18107 ms
adpc
6981 ms
adpc
20452 ms
adpc
7384 ms
adpc
19062 ms
hm.js
1164 ms
analytics.php
852 ms
zhuge.js
211 ms
s16431_420.jpg
519 ms
8h7DVkhHgr8119.jpg
489 ms
534f8431462d11bcd9196916bf5c6c31.png
575 ms
proposal.jpg
615 ms
bl341_160s.png-80x60.jpg
514 ms
s16463_420.jpg
530 ms
bl370_160s.png-80x60.jpg
514 ms
s16592_420.jpg
531 ms
bl517_160s.png-80x60.jpg
518 ms
s16390_420.jpg
542 ms
bl25_160s.png-80x60.jpg
529 ms
s15829_420.jpg
547 ms
bl88_160s.png-80x60.jpg
533 ms
s16319_420.jpg
558 ms
bl63_160s.png-80x60.jpg
544 ms
s16286_420.jpg
561 ms
s15909_420.jpg
552 ms
s15999_420.jpg
558 ms
s16557_420.jpg
560 ms
s16135_420.jpg
561 ms
s16472_420.jpg
568 ms
s16359_420.jpg
573 ms
s15589_420.jpg
573 ms
s16355_420.jpg
575 ms
s16405_420.jpg
576 ms
s15363_420.jpg
590 ms
s16131_420.jpg
584 ms
s16324_420.jpg
603 ms
s16259_120.jpg
589 ms
s16622_120.jpg
589 ms
s16623_120.jpg
590 ms
s16618_120.jpg
598 ms
s16485_120.jpg
603 ms
s15945_120.jpg
604 ms
20231208113323392653266871952.jpg
605 ms
report.jpg
639 ms
app.jpg
621 ms
457569f0a77c57f56dbc337a1ead2f68.png
572 ms
sprite2x.5bc1e68349017.png
25 ms
web.gif
672 ms
web.gif
812 ms
web.gif
812 ms
web.gif
503 ms
web.gif
524 ms
hm.gif
299 ms
index_logo2x.png
57 ms
login.css
9 ms
md5.js
9 ms
jquery.xdomainrequest.min.js
25 ms
new_login_2019.php
275 ms
ip2getcity.php
950 ms
iwt-min.js
35 ms
push.js
901 ms
583 ms
739 ms
756 ms
791 ms
search_exec.r.js
33 ms
808 ms
analytics_foot.php
212 ms
a.gif
975 ms
1.9-nol.js
6 ms
search_tpl_c1.r.js
221 ms
search.r.js
15 ms
search_emptyfns.r.js
2 ms
979 ms
461 ms
427 ms
435 ms
536 ms
718 ms
693 ms
710 ms
749 ms
s14384_200.jpg
17 ms
s15432_200.jpg
16 ms
s14581_200.jpg
17 ms
s15760_200.jpg
17 ms
s13460_200.jpg
16 ms
s15363_200.jpg
18 ms
s15280_200.jpg
31 ms
s15957_200.jpg
31 ms
s15507_200.jpg
31 ms
s15527_200.jpg
32 ms
8ebe7e6e9ee14e5467243a8303783e6e.jpg
17 ms
strategy_20240507134805377506706896655.jpg
492 ms
10f73f7d1a04e2788f2e01d423e5429c.jpg
400 ms
556024483649c427436d2a1c675e90dd.jpg
511 ms
f2dbb8340591229c8cd86ab53bc25943.jpg
391 ms
d356dd9469a3f1bc82dc43fb12d426ac.jpg
497 ms
1ff106ebbc9d53536fd2dca8c40bc73e.jpg
388 ms
b5325c49840a0f06415328bd8734aad4.jpg
420 ms
strategy_20240424200649771928025538969.jpg
520 ms
1bd30c53161c4e0b6cf902e5c8866c0a.jpg
533 ms
ad1fc7051bf34ea92085b642f223d81d.jpg
547 ms
6edf8b2e2f244a8d42e11ec2111d801b.jpg
530 ms
94b0902a62ade12191a75606f04c57a0.jpg
595 ms
xcar.cn accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
xcar.cn best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
xcar.cn SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xcar.cn 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 Xcar.cn 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.
xcar.cn
Open Graph description is not detected on the main page of Xcar. 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: