90.6 sec in total
7.4 sec
80.8 sec
2.4 sec
Click here to check amazing Wedqingdao content. Otherwise, check out these important facts you probably never knew about wedqingdao.cn
wedqingdao.cn
Visit wedqingdao.cnWe analyzed Wedqingdao.cn page load time and found that the first response time was 7.4 sec and then it took 83.3 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 43 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
wedqingdao.cn performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value1.2 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
7363 ms
10475 ms
5498 ms
20233 ms
5526 ms
Our browser made a total of 170 requests to load all elements on the main page. We found that 66% of them (112 requests) were addressed to the original Wedqingdao.cn, 6% (10 requests) were made to Www1.53kf.com and 5% (8 requests) were made to Lxbjs.baidu.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Wedqingdao.cn.
Page size can be reduced by 321.1 kB (59%)
544.3 kB
223.2 kB
In fact, the total size of Wedqingdao.cn main page is 544.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 230.3 kB which makes up the majority of the site volume.
Potential reduce by 63.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 63.9 kB or 76% of the original size.
Potential reduce by 17.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. Obviously, Wedqingdao needs image optimization as it can save up to 17.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 160.2 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 160.2 kB or 70% of the original size.
Potential reduce by 79.6 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. Wedqingdao.cn needs all CSS files to be minified and compressed as it can save up to 79.6 kB or 84% of the original size.
Number of requests can be reduced by 19 (16%)
119
100
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wedqingdao. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
wedqingdao.cn
7363 ms
style.css
10475 ms
sexylightbox.css
5498 ms
jquery.tools.min.js
20233 ms
iaviva.js
5526 ms
tip.js
5523 ms
jquery.easing.1.3.js
6097 ms
sexylightbox.v2.3.jquery.js
20234 ms
tj.js
985 ms
kf.php
5671 ms
hm.js
791 ms
vg1.jpg
7802 ms
iaviva.gif
9674 ms
bg3.png
548 ms
bg15.gif
566 ms
bg74.gif
1107 ms
t0.gif
2461 ms
t4.gif
1125 ms
t00.gif
2144 ms
t09.gif
1627 ms
bg75.gif
3322 ms
t5.gif
4725 ms
t6.gif
5899 ms
t9.gif
2984 ms
t3.gif
4409 ms
t2.gif
5337 ms
bg76.gif
4937 ms
logo.png
9385 ms
Stars.gif
5434 ms
bg6.gif
7836 ms
20151112115444289.gif
19981 ms
20150625160416384.jpg
17388 ms
20160324104601956.jpg
19981 ms
20150625172131095.jpg
19102 ms
20150625102124497.jpg
19981 ms
20150722144036066.jpg
19982 ms
20150710154908415.jpg
19982 ms
20150722143530533.jpg
19986 ms
20150722144111101.jpg
19987 ms
20150722141235374.jpg
19989 ms
20150710155030608.jpg
19991 ms
20150710155127598.jpg
19991 ms
20150710155207382.jpg
19993 ms
20150710155244543.jpg
19995 ms
20150710155312783.jpg
19994 ms
20150710155531240.jpg
19996 ms
20150710155555745.jpg
19980 ms
ApiSus.asp
455 ms
sv.php
1457 ms
20150710155909290.jpg
20439 ms
20150710160231787.jpg
20423 ms
FangkeHa.php
1056 ms
hm.gif
790 ms
s.js
4283 ms
lxb.js
4449 ms
20150710161121719.jpg
19882 ms
20150422094509602.jpg
19864 ms
sendacc.jsp
3291 ms
kf_new.php
8535 ms
ApiSus.asp
503 ms
20150630153559759.jpg
20358 ms
FangkeGo.php
617 ms
FangkeHa.php
486 ms
20150630153950978.jpg
19843 ms
20150630154027885.jpg
19528 ms
FangkeGo.php
597 ms
20150630154624752.jpg
19998 ms
tjvip.asp
1483 ms
20150707154007850.jpg
19662 ms
20150707154043357.jpg
19576 ms
20150707154119008.jpg
20261 ms
20150707154140299.jpg
20049 ms
log.gif
351 ms
_l.js
753 ms
20150625105936913.jpg
19649 ms
20150626112323542.jpg
19552 ms
20160408100015768.gif
20083 ms
log.gif
3198 ms
10.css
3456 ms
p.php
1432 ms
p.php
1453 ms
p.php
1639 ms
p.php
1654 ms
20160408095633904.gif
20186 ms
20160408095048286.gif
20146 ms
s
6454 ms
s
8597 ms
tjvip.asp
1482 ms
s
1452 ms
s
1757 ms
20160406121011603.gif
19597 ms
20160406120509243.gif
20316 ms
w.gif
1220 ms
icon_mobile_min.png
1580 ms
0.gif
991 ms
kf_ivt_new.php
13650 ms
arrow_left.gif
822 ms
list_36.gif
929 ms
list_05.gif
932 ms
list_06.gif
4443 ms
timg
3470 ms
timg
3482 ms
timg
3426 ms
timg
3484 ms
timg
3514 ms
20160406120134446.gif
16552 ms
20151228141516895.jpg
19881 ms
20150711175101607.jpg
10355 ms
20150711175125450.jpg
11384 ms
20150711175150767.jpg
12711 ms
20150711175222353.jpg
12988 ms
20150711175248473.jpg
12356 ms
20150708095212472.jpg
15105 ms
20150711173423160.jpg
15111 ms
20150711173401865.jpg
13435 ms
20150711173327710.jpg
14405 ms
qq.gif
16129 ms
btm_01.gif
16675 ms
ValidateCode.aspx
19979 ms
bg96.gif
16954 ms
bg97.gif
15590 ms
nav_01.png
16115 ms
nav_02.png
15609 ms
nav_03.png
15526 ms
nav_04.png
15927 ms
nav_05.png
16337 ms
index.jpg
19998 ms
bg7.gif
15335 ms
bg1.png
19995 ms
bg8.gif
15120 ms
bg9.gif
17028 ms
closebtn_2.png
2249 ms
clickbtn_10.png
2429 ms
box_100732841431588469.jpg
11290 ms
bg10.gif
16099 ms
jquery-1.4.2.flp.js
2489 ms
loaderc.gif
15841 ms
bg12.gif
16906 ms
bg16.gif
16633 ms
bg10s.gif
19337 ms
bg10s1.gif
18560 ms
bg17.gif
18625 ms
bg2.png
18221 ms
y_1.png
18932 ms
bg19.gif
14959 ms
bg26.gif
18004 ms
bg27.gif
15632 ms
bg28.gif
14671 ms
bg29.gif
14908 ms
bg30.gif
14577 ms
bg20.gif
19551 ms
bg21.gif
14220 ms
bg22.gif
14232 ms
btm1_03.gif
14663 ms
btm_02.gif
13501 ms
bg2_01.jpg
20386 ms
bg49.gif
14274 ms
bg4.png
19854 ms
2.png
1048 ms
bpa.js
2923 ms
s
884 ms
s
2832 ms
www.baidu.com
892 ms
log.gif
690 ms
log.gif
1054 ms
hm.gif
903 ms
bd_logo1.png
618 ms
baidu_jgylogo3.gif
635 ms
w.gif
532 ms
resultLogo_u.png
504 ms
wedqingdao.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
wedqingdao.cn best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
wedqingdao.cn SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wedqingdao.cn can be misinterpreted by Google and other search engines. Our service has detected that English 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 Wedqingdao.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.
wedqingdao.cn
Open Graph description is not detected on the main page of Wedqingdao. 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: