31 sec in total
693 ms
30.2 sec
104 ms
Welcome to geely.com homepage info - get ready to check Geely best content for China right away, or after learning these important things about geely.com
浙江吉利控股集团始建于1986年,1997年进入汽车行业,多年来专注实业,专注技术创新和人才培养,取得了快速发展。现资产总值超过1000亿元,连续十年进入中国企业500强,连续八年进入中国汽车行业十强,是国家
Visit geely.comWe analyzed Geely.com page load time and found that the first response time was 693 ms and then it took 30.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.
geely.com performance score
693 ms
4782 ms
5258 ms
7985 ms
4625 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 54% of them (50 requests) were addressed to the original Geely.com, 35% (32 requests) were made to Admin.geely.com and 5% (5 requests) were made to V3.jiathis.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Admin.geely.com.
Page size can be reduced by 403.5 kB (20%)
2.0 MB
1.6 MB
In fact, the total size of Geely.com main page is 2.0 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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 55.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 23.8 kB, which is 36% 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 55.8 kB or 85% of the original size.
Potential reduce by 245.7 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, Geely needs image optimization as it can save up to 245.7 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 19.3 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 19.3 kB or 51% of the original size.
Potential reduce by 82.7 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. Geely.com needs all CSS files to be minified and compressed as it can save up to 82.7 kB or 84% of the original size.
Number of requests can be reduced by 26 (31%)
84
58
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geely. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
index.html
693 ms
base.css
4782 ms
style.css
5258 ms
global.css
7985 ms
page.css
4625 ms
jquery-1.9.1.min.js
7244 ms
index_top.js
6376 ms
scroll_index.js
5423 ms
jia.js
401 ms
index_bottom.js
6304 ms
stat.php
2066 ms
cdf2564cd171a873972f9b29311a3c9f.png
6477 ms
infinite_bottom.png
335 ms
logo_150x75.png
434 ms
pic_220x160.jpg
977 ms
jg.png
6147 ms
xm.png
3454 ms
gx2.png
5107 ms
pic02_220x160.jpg
3326 ms
qr-code_71x70.jpg
1294 ms
erweima_n.jpg
2254 ms
a0352ff37afcc09e721648471f15e2d4.png
5751 ms
feb1fe2daccdeb594b1a72e437151caa.jpg
5281 ms
faa71e245656b4173a9b4b92ca406856.jpg
5131 ms
c081391bb485dcd956a20ac42b270ffb.jpg
4379 ms
aefad79442b80bb423315587dc1d4884.png
7416 ms
26eb1de552f2c09c5c8c7a0174c82409.png
8163 ms
82e2b8ca85b95d39d93076d3671b480d.png
6036 ms
d3c73732f79344a0cc16f53ac42ca202.jpg
7027 ms
aeb6cb077fbc67a89c63d67f20bdb939.jpg
6199 ms
fe86489ccd5370677f47065d84ba8d75.jpg
7426 ms
2aee7af886be2a3323230703b94dc782.jpg
6698 ms
f47facf1ab84a70bef5ac13e99213127.png
6882 ms
3d527e282f6d97d8f16742b7844303f7.jpg
8940 ms
b3dfcda2571e0f29fac4c1bb32a8eee2.png
7283 ms
416feb08d6ea244bf5396e15c3f73857.jpg
7608 ms
429adb2686d2848c90aef74fe8d3f09b.jpg
7765 ms
7d5bcbd31ff1364cc2b86b7a896cda91.png
9969 ms
77415164827af40face60e7abfe4c7d7.png
11709 ms
433266adc3c686f9bb6315ac4dd2edb4_thumb.jpg
8478 ms
924869f41193e7426abca05cbbfb9339_thumb.jpg
9175 ms
c6e30b71eb3e3a072cd212effe0dac3f_thumb.jpg
10774 ms
cd7bc257215afc37a86d91fd588a8623_thumb.jpg
11422 ms
7e1e3cc452f99a278b65adfd09de3ece_thumb.JPG
10010 ms
5aa745b8d2f9ac6f17f9bb273eeeaf19_thumb.JPG
10986 ms
1f4475b04bc60b177e516af1cf4730c9_thumb.JPG
11812 ms
01d8030df2a7e7f161bfcbaaffd27787_thumb.jpg
10433 ms
headerLine_2x18.png
1721 ms
h-sNavGg-l_12x28.png
2153 ms
h-sNavGg-c_1x28.png
2586 ms
signPic.gif
2581 ms
h-sNavGg-r_12x28.png
2916 ms
searchBox_165x30s.png
3022 ms
searchSign_18x15.png
3248 ms
sign-04_14x14.png
4019 ms
indexBtn_76x25.png
3923 ms
button01.png
3626 ms
button02.png
3772 ms
index-moreDetailBg.jpg
5412 ms
button03.png
4128 ms
liBg01.png
5227 ms
button05.jpg
7787 ms
button04.png
5273 ms
indexFooter.jpg
5508 ms
indexLink.jpg
5557 ms
sign06.jpg
5622 ms
sign07.jpg
5737 ms
jiathis_utility.html
6 ms
jiathis_share.css
17 ms
plugin.client.js
5 ms
stat.htm
158 ms
core.php
780 ms
9.gif
1217 ms
jiathis_ico.png
61 ms
h-picBoxSign.gif
5005 ms
dialogbox_top.png
4960 ms
dialogbox_left.png
5412 ms
dialogbox_right.png
5141 ms
dialogbox_bottom.png
5299 ms
dialogbox_corner.png
6017 ms
h-subNavBg_919x107.jpg
5622 ms
input-07_116x36.jpg
5605 ms
footer-bg_79x9.gif
5987 ms
7006c1d18009e0a75d6ccbf044eab8c7.jpg
19877 ms
26d1735d7929ea929104c11242b855f8.jpg
11654 ms
b00c79f259c1e018b1bea36fb1c47822.jpg
19877 ms
adb5dbbf0ffda47e07d9487b99ac02ea.jpg
19877 ms
16ad00d27ce93116f3b40d86450ee8b8.jpg
19877 ms
footerBoxTl_1x30.gif
5759 ms
sign-05_14x14.png
7350 ms
br.png
5678 ms
app.gif
4537 ms
geely.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 Geely.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 Geely.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.
geely.com
Open Graph description is not detected on the main page of Geely. 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: