66.6 sec in total
3 sec
61 sec
2.7 sec
Welcome to 315che.com homepage info - get ready to check 315 Che best content for China right away, or after learning these important things about 315che.com
汽车消费网
Visit 315che.comWe analyzed 315che.com page load time and found that the first response time was 3 sec and then it took 63.6 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 were 81 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
315che.com performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value12.9 s
0/100
25%
Value11.9 s
4/100
10%
Value760 ms
38/100
30%
Value0.131
81/100
15%
Value11.1 s
20/100
10%
2994 ms
19661 ms
12268 ms
5343 ms
19660 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 23% of them (24 requests) were addressed to the original 315che.com, 65% (69 requests) were made to Img.315che.com and 2% (2 requests) were made to W.cnzz.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain 315che.com.
Page size can be reduced by 1.8 MB (20%)
8.9 MB
7.1 MB
In fact, the total size of 315che.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. 20% of websites need less resources to load. Images take 7.3 MB which makes up the majority of the site volume.
Potential reduce by 144.1 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 144.1 kB or 80% of the original size.
Potential reduce by 472.4 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. 315 Che images are well optimized though.
Potential reduce by 806.4 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 806.4 kB or 78% of the original size.
Potential reduce by 389.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. 315che.com needs all CSS files to be minified and compressed as it can save up to 389.4 kB or 84% of the original size.
Number of requests can be reduced by 6 (27%)
22
16
The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 315 Che. 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.
315che.com
2994 ms
styles.css
19661 ms
cars-more-one.css
12268 ms
jcalendar.css
5343 ms
photos-depot.css
19660 ms
jquery-1.11.2.min.js
19661 ms
jquery-cookie.js
2991 ms
stat.js
19722 ms
jquery.bxslider.min.js
7486 ms
global.js
20356 ms
jcalendar.min.js
20355 ms
jquery.lazyload.min.js
20356 ms
base64.js
20356 ms
ad.js
20356 ms
dateformat.js
20356 ms
common.js
20356 ms
addFav.js
20356 ms
activity_chezhan.js
1186 ms
c.php
1195 ms
f303f1f9-9d65-40a5-971b-be7fb51b3bb0.png
19978 ms
cert.png
10548 ms
0396e093-b731-4929-8593-25c6c3c4d1e9.png
19952 ms
ee16d189-9687-46de-9729-dd3f78bae342.png
19952 ms
5fd79ceb-ece0-4840-8359-683bff55cd48.png
19952 ms
9531dbdd-2a8c-4741-a0af-88e1c7e21b3c.png
19953 ms
99c17f43-5492-4697-bdd3-75942ef212ac.png
19953 ms
1831fd14-9ed8-4a2c-be60-7973ece43d2e.png
19954 ms
4ac6b20e-9172-474a-857c-6d438077e004.jpg
19954 ms
08219d55-a77d-4260-bb4c-ed89591f5563.jpg
19954 ms
5a5e64f0-2903-4dcd-9970-9d8e9a4089a2.jpg
19955 ms
6f500058-35a8-4d7b-b320-1cbaee330a2f.jpg
19956 ms
599d250b-bcfe-4033-b403-7865812be5b3.jpg
19956 ms
e7375522-f758-489a-9cb5-eae8a64004f8.jpg
19957 ms
2eda1ab1-a857-4b10-84de-5bf909f1de08.jpg
19958 ms
25441710-ec59-4702-9b7f-21dd6963c62b.jpg
19958 ms
6721bf6b-6213-4504-8c7f-084cda4f38bf.jpg
19958 ms
3ee0fa89-88fb-4017-af3d-2be74487da4a.jpg
19959 ms
b9239f43-35da-4b69-974e-a6c7b8f2e8a0.jpg
19958 ms
2c8144eb-8d48-4f24-8346-e7ed739f70bc.jpg
19959 ms
5a173d51-3d5c-4804-9e21-470eb9a4c0bd.jpg
19959 ms
b2df3717-f669-4486-a811-7a15422f220f.jpg
19959 ms
cf2ca747-203c-4bcc-a83d-fe5cd3a0ea7a.jpg
19959 ms
61d916ad-c7d1-4b72-866b-ccbdc6d11fd7.jpg
19959 ms
U0.jpg
19960 ms
U0.jpg
19961 ms
U0.jpg
19961 ms
453d905c-1579-48fc-9db0-f36b62cc37ce.jpg
19961 ms
U0.jpg
19961 ms
U0.jpg
19962 ms
U0.jpg
19961 ms
U0.jpg
19962 ms
U0.jpg
19961 ms
U0.jpg
19962 ms
U0.jpg
19961 ms
U0.jpg
19962 ms
U0.jpg
19962 ms
logo.png
3829 ms
icons.png
7156 ms
sh_gongshang.jpg
8580 ms
zx110.jpg
5633 ms
sh_110.jpg
6405 ms
itrust_315che.jpg
7683 ms
wx_qrcode.jpg
7699 ms
hm.js
19993 ms
stat.htm
261 ms
core.php
562 ms
c.php
1448 ms
9.gif
830 ms
app.gif
981 ms
stat.htm
177 ms
core.php
290 ms
9.gif
429 ms
app.gif
715 ms
U0.jpg
19999 ms
U0.jpg
19999 ms
U0.jpg
19999 ms
90bfc866-9c60-4b44-9311-73fb16d00b72.jpg
19999 ms
218d7901-1a10-4d34-b3cb-53d720f4ed05.jpg
13227 ms
cc18196f-4930-4f2c-ab0e-272c62f15860.jpg
19998 ms
U0.jpg
19997 ms
c510fd4f-f75d-4206-9c90-483c6ac14c86.jpg
19996 ms
U0.jpg
19996 ms
U0.jpg
19996 ms
1464ba2a-7c0d-4b84-b877-bcbc91869883.jpg
19996 ms
566170fa-f650-4735-bcd4-f97da3d81720.jpg
19994 ms
U0.jpg
19993 ms
U0.jpg
20020 ms
U0.jpg
20021 ms
U0.jpg
20020 ms
U0.jpg
20020 ms
54144196-9fcd-45a7-9013-c0335e9bc621.jpg
20020 ms
922fb436-ab9b-4019-992d-ee6a536dff56.jpg
20020 ms
20766f1d-dec8-48b1-9905-53b76b8fc209.jpg
20019 ms
93420d54-241d-4bbb-9948-edfc87a807b1.jpg
20019 ms
27ab8f7f-dfc1-4d25-87fe-0a7ef89706d7.jpg
20019 ms
ecb2bb3a-990a-47c0-82ec-0fae4fb62ff8.jpg
20019 ms
623831ee-cf9a-40d2-bfac-65d6d5a5d32c.jpg
20018 ms
2c1a6e29-5cd7-4b40-aafc-92ec00413067.jpg
20018 ms
7e519151-04ce-4b9a-9083-5e6b16edcdd0.jpg
20018 ms
30068b99-45d8-4d6f-b4aa-ea571b0ff738.jpg
20018 ms
0f31200d-8d29-4c7c-9dda-dea0bdd70c55.jpg
20017 ms
85dc2e8b-c27e-4ecb-848b-6173cee58aaf.jpg
20018 ms
04d6a4b1-24ab-400b-8692-8e383860dfd7.jpg
20017 ms
10ebc9b0-070e-4ba0-b1c5-a1cfe7fc2623.jpg
20017 ms
c236034b-192b-4d3b-9610-7555ad58efe1.jpg
20017 ms
365af09d-d847-4d47-9f41-c1459da1c716.jpg
20017 ms
315che.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Form elements do not have associated labels
Links do not have a discernible name
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.
315che.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
315che.com SEO score
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
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 315che.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that 315che.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.
315che.com
Open Graph description is not detected on the main page of 315 Che. 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: