66.9 sec in total
2.1 sec
63.9 sec
894 ms
Visit find800.cn now to see the best up-to-date Find 800 content for China and also check out these interesting facts you probably never knew about find800.cn
方得网是商用车行业的权威媒体,架设起企业和市场的桥梁,是行业沟通交流的平台
Visit find800.cnWe analyzed Find800.cn page load time and found that the first response time was 2.1 sec and then it took 64.8 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.
find800.cn performance score
name
value
score
weighting
Value20.2 s
0/100
10%
Value39.0 s
0/100
25%
Value40.0 s
0/100
10%
Value120 ms
97/100
30%
Value0
100/100
15%
Value38.6 s
0/100
10%
2108 ms
4815 ms
633 ms
7 ms
9 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 83% of them (122 requests) were addressed to the original Find800.cn, 6% (9 requests) were made to Bdimg.share.baidu.com and 3% (5 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Find800.cn.
Page size can be reduced by 383.7 kB (14%)
2.7 MB
2.3 MB
In fact, the total size of Find800.cn main page is 2.7 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. 60% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 94.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 16.3 kB, which is 14% 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 94.3 kB or 80% of the original size.
Potential reduce by 176.8 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. Find 800 images are well optimized though.
Potential reduce by 78.5 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 78.5 kB or 49% of the original size.
Potential reduce by 34.1 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. Find800.cn needs all CSS files to be minified and compressed as it can save up to 34.1 kB or 78% of the original size.
Number of requests can be reduced by 50 (34%)
145
95
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Find 800. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and as a result speed up the page load time.
find800.cn
2108 ms
www.find800.cn
4815 ms
uaredirect.js
633 ms
public.css
7 ms
index.css
9 ms
jquery-1.3.1.js
13 ms
main01.js
9 ms
search.js
6 ms
jquery.cxslide.min.js
9 ms
sousuo.js
9 ms
config.js
3 ms
common.js
6 ms
login.js
4 ms
changmember.php
710 ms
hm.js
1459 ms
logo.gif
1148 ms
33.js
5 ms
27.js
7 ms
28.js
9 ms
js.php
1956 ms
094702tubkvfzz4enyyrun.jpg
5230 ms
20160316091054324.jpg
1878 ms
20160315054828979.jpg
990 ms
20160314094757568.jpg
935 ms
20160314090537452.jpg
5566 ms
20160309022141698.jpg
1803 ms
094039bxk1km4ss8imkc28.jpg
3667 ms
pay_icon01.png
4891 ms
is.png
2825 ms
header_content01.png
2532 ms
search_icon01.gif
2547 ms
20150911115009812.gif
3350 ms
20150907105149137.jpg
5728 ms
20160111054120916.gif
3655 ms
20140527095523926.gif
5573 ms
29.js
6956 ms
31.js
5573 ms
32.js
5240 ms
38.js
5995 ms
39.js
7211 ms
48.js
10174 ms
49.js
6475 ms
20151231031423971.jpg
7250 ms
20160203114140379.jpg
7869 ms
20160129090148156.jpg
7473 ms
20150807095155398.jpg
7681 ms
20160128091534293.png
9867 ms
20150807094407695.jpg
8171 ms
20140716031658523.jpg
9536 ms
20140716032014516.jpg
9432 ms
20140301013722196.jpg
9655 ms
20140301024147618.jpg
10077 ms
20140301030413427.jpg
10479 ms
20140301031657659.jpg
10468 ms
20140702030811493.jpg
10258 ms
20140714033754769.jpg
10245 ms
hm.gif
1269 ms
34.js
9271 ms
35.js
9201 ms
36.js
9109 ms
37.js
8487 ms
46.js
8481 ms
x.gif
3784 ms
17712149.js
887 ms
47.js
8213 ms
20140530115345232.jpg
8391 ms
20140714032435146.jpg
8420 ms
20140702042111410.jpg
7969 ms
20140714032629882.jpg
6997 ms
20160112021556182.png
7862 ms
20160214111750790.jpg
19514 ms
20151216031113459.jpg
14110 ms
20151209043656112.jpg
11621 ms
20151209043512134.jpg
18292 ms
20150930032206203.jpg
12056 ms
20150819123847568.jpg
16109 ms
20150802080845647.jpg
13491 ms
20160121112211722.png
15930 ms
20151113083915436.png
19885 ms
20160307044924987.jpg
17031 ms
column_icon01.png
15892 ms
column_icon02.png
19089 ms
column_icon03.png
17008 ms
list_icon02.png
17392 ms
index_icon02.png
18066 ms
20140310030840114.jpg
19241 ms
20160107103713475.gif
19209 ms
20160302035647427.gif
15436 ms
20150813025808668.gif
16829 ms
20160224113927271.gif
19640 ms
icon_0.gif
927 ms
share.js
2027 ms
h.js
1543 ms
20160127044145712.gif
16280 ms
t.js
1363 ms
hm.gif
452 ms
share_api.js
293 ms
share_view.js
581 ms
tangram.js
3890 ms
api_base.js
465 ms
view_base.js
358 ms
20150923125444292.gif
11141 ms
tj.gif
1913 ms
hm.gif
450 ms
t-slide-arrows.svg
1278 ms
u=149753914,881423514&fm=72
2574 ms
t-list-styles.svg
1373 ms
20160105101439676.gif
10883 ms
20151012042720597.gif
11300 ms
20160126113430835.gif
13760 ms
logger.js
393 ms
20160126113603396.gif
19058 ms
20151103044153218.gif
10802 ms
partners.js
293 ms
share_style1_24.css
293 ms
20151103044259793.gif
11181 ms
20151105011825467.gif
11453 ms
20151112033749372.gif
12163 ms
20151126054930463.gif
15334 ms
20151201110410298.png
11893 ms
20151202042014950.gif
15353 ms
20151210023526365.gif
13281 ms
20151218111010598.gif
13461 ms
au_icon01.png
13017 ms
au_icon02.png
16217 ms
au_icon03.png
13393 ms
au_icon04.png
13620 ms
20140307113746404.gif
17575 ms
20140308040937911.gif
19993 ms
20160126031403277.gif
17354 ms
20160301123520389.gif
19990 ms
20150906021928781.jpg
19989 ms
20150326103918532.gif
19986 ms
20150306020407330.gif
20000 ms
20151209033207388.png
20070 ms
20151208042758956.png
20035 ms
column_icon05.png
17780 ms
20140314104741500.gif
19687 ms
20150828053422645.jpg
18869 ms
20140916053959634.gif
19588 ms
20151228045900433.gif
17663 ms
20140821093730674.gif
19817 ms
20151125044354814.gif
19544 ms
20151123025055341.gif
20387 ms
list_icon01.png
16021 ms
foot_float_bg.png
16483 ms
search01.gif
17034 ms
find800.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.
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
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.
find800.cn 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
Page has valid source maps
find800.cn SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Find800.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 Find800.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.
find800.cn
Open Graph description is not detected on the main page of Find 800. 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: