57.4 sec in total
7 sec
50 sec
380 ms
Welcome to xm.vanke.com homepage info - get ready to check Xm Vanke best content for China right away, or after learning these important things about xm.vanke.com
厦门市万科房地产有限公司在厦门已连续开发湖心岛,金域华府,金色悦城,水晶湖郡,金域蓝湾,恒邦C等多个项目。
Visit xm.vanke.comWe analyzed Xm.vanke.com page load time and found that the first response time was 7 sec and then it took 50.4 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 35 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
xm.vanke.com performance score
6959 ms
7737 ms
20367 ms
20367 ms
3865 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 68% of them (90 requests) were addressed to the original Xm.vanke.com, 8% (10 requests) were made to Img.t.sinajs.cn and 5% (7 requests) were made to Ww4.sinaimg.cn. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Xm.vanke.com.
Page size can be reduced by 341.7 kB (32%)
1.1 MB
718.4 kB
In fact, the total size of Xm.vanke.com main page is 1.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. 30% of websites need less resources to load. Images take 628.9 kB which makes up the majority of the site volume.
Potential reduce by 36.8 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 9.7 kB, which is 21% 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 36.8 kB or 80% of the original size.
Potential reduce by 30.1 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. Xm Vanke images are well optimized though.
Potential reduce by 177.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 177.2 kB or 67% of the original size.
Potential reduce by 97.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. Xm.vanke.com needs all CSS files to be minified and compressed as it can save up to 97.6 kB or 81% of the original size.
Number of requests can be reduced by 26 (40%)
65
39
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xm Vanke. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
xm.vanke.com
6959 ms
global.css
7737 ms
style.css
20367 ms
index.css
20367 ms
colorbox.css
3865 ms
fancybox.css
7363 ms
xiangmu.css
6545 ms
pic01.jpg
9567 ms
NavforeAPic02.jpg
19910 ms
NavforeAPic03.jpg
19910 ms
NavforeAPic04.jpg
11506 ms
NavforeAPic05.jpg
19911 ms
NavforeAPic07.jpg
11050 ms
pic08.jpg
11049 ms
NavLogo01.jpg
11049 ms
NavLogo02.jpg
11050 ms
NavLogo03.jpg
11050 ms
NavLogo04.jpg
11050 ms
NavLogo05.jpg
11051 ms
NavLogo06.jpg
11051 ms
NavLogo07.jpg
11052 ms
NavforeAPic09.jpg
11051 ms
NavLogo08.jpg
11051 ms
NavforeAPic10.jpg
11051 ms
350X246.jpg
11051 ms
246.jpg
11052 ms
yzydh.jpg
11052 ms
NavforeAPic12.jpg
11053 ms
vkjs11.jpg
11052 ms
pic05.jpg
11052 ms
pic06.jpg
11053 ms
1.jpg
11053 ms
980X355.jpg
11053 ms
1.20%E7%BD%91%E7%BB%9C%E9%80%9A%E6%A0%8F980X290px-01.jpg
11053 ms
2.jpg
11054 ms
2.jpg
11054 ms
index.php
1717 ms
jquery-1.8.2.js
9708 ms
weiboShow.css
466 ms
skin_default.css
463 ms
gaea_1_19.js
9 ms
show.js
9 ms
suda.js
9 ms
1
988 ms
smile.gif
341 ms
47233d0fjw1epu15nk438j20hs0dbgoc.jpg
292 ms
a716fd45jw1epxyyjewjgj20c80go0us.jpg
533 ms
9e5389bbjw1epo0xjblnzj20hs0aiwfk.jpg
721 ms
703a9882jw1epjjram7i0j20fj0a3gvw.jpg
279 ms
heart.gif
274 ms
ye_org.gif
273 ms
6c9f96b9gw1epk7owi6vhj20dw0drq5o.jpg
714 ms
a716fd45jw1epfjj20cdzj20c80c8gmy.jpg
697 ms
633d71c5jw1epav106lx2j20ef24un6d.jpg
711 ms
67be458fgw1eox2k76dcsj20c83zyh99.jpg
699 ms
67be458fgw1eptdvyc5tpj20c80853yu.jpg
505 ms
9e5389bbjw1epnz4m0n8jj20c80ilgmm.jpg
533 ms
9be419dbjw1epk8l73tmoj20iy0hswft.jpg
511 ms
6332ae54jw1epezxg1727j20dw099q4l.jpg
512 ms
9e5389bbjw1ep0pscskdcj20c8g707wi.jpg
514 ms
703a9882jw1eowj0239uej20hs18f79o.jpg
592 ms
icon_user.png
89 ms
btns_bg.png
89 ms
icon_follow.png
89 ms
yw_org.gif
91 ms
m_org.gif
90 ms
kl_org.gif
89 ms
703a9882jw1ep6wq7ukd6j20hs11qzmm.jpg
264 ms
a716fd45jw1ep3xgckutmj20c80c8q45.jpg
282 ms
703a9882jw1epdxo5m60fj209g07nq30.jpg
247 ms
a5da769egw1ep5c5rnjtlj20c80c80u3.jpg
261 ms
bg_trans.png
7 ms
icon_tips.png
2 ms
tmp.gif
1171 ms
jquery.colorbox.js
8123 ms
minmax.js
5445 ms
InNav.js
4628 ms
InFocus.js
4255 ms
fancybox.js
1952 ms
waypoints.js
1406 ms
autoWidth.js
1819 ms
easing.js
2257 ms
jscript_jquery.faded.js
4316 ms
jquery.HooRay.js
5907 ms
style.js
10001 ms
FormCheck_Jquery.js
10064 ms
template.min.js
10046 ms
template-extensions.min.js
11146 ms
User.js
13431 ms
InRoll.js
20380 ms
InSlide.js
10623 ms
Weather.js
11188 ms
cloudy.png
13075 ms
wankehui.jpg
13683 ms
weixin.jpg
20383 ms
weixinbig.jpg
16838 ms
9.png
20383 ms
9.webp.jpg
15380 ms
0.jpg
20383 ms
%E5%9B%BE%E7%89%875.png
20383 ms
%E5%9B%BE%E7%89%871.png
20383 ms
3.jpg
20382 ms
derydh.jpg
20382 ms
ProjectLogo01.jpg
20382 ms
XMmap.jpg
20382 ms
XmSl02.jpg
20382 ms
XMpic01.jpg
20381 ms
ProjectLogo02.jpg
20382 ms
HCmap.jpg
20382 ms
HcSl07.jpg
20381 ms
HCpic01.jpg
19981 ms
ProjectLogo03.jpg
19567 ms
QZmap.jpg
20127 ms
QzYb01.jpg
20069 ms
QZpic01.jpg
20478 ms
ga.js
115 ms
ProjectLogo04.jpg
16770 ms
HXpic01.jpg
19983 ms
HXpic02.jpg
19982 ms
HXpic03.jpg
19982 ms
ProjectLogo05.jpg
17570 ms
h.js
514 ms
__utm.gif
16 ms
__utm.gif
10 ms
hm.gif
257 ms
HFpic01.jpg
20381 ms
HFpic03.jpg
20338 ms
HFpic05.jpg
20318 ms
colorbox_pic03.png
19759 ms
colorbox_pic01.png
20235 ms
colorbox_pic02.png
20192 ms
ShopCar.jpg
20303 ms
xm.vanke.com SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xm.vanke.com 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 Xm.vanke.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.
xm.vanke.com
Open Graph description is not detected on the main page of Xm Vanke. 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: