21.3 sec in total
2.1 sec
19 sec
162 ms
Welcome to 39soso.com homepage info - get ready to check 39 Soso best content right away, or after learning these important things about 39soso.com
Visit 39soso.comWe analyzed 39soso.com page load time and found that the first response time was 2.1 sec and then it took 19.2 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.
39soso.com performance score
2114 ms
875 ms
1543 ms
887 ms
723 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 38% of them (39 requests) were addressed to the original 39soso.com, 34% (35 requests) were made to Api.map.baidu.com and 7% (7 requests) were made to Map.baidu.com. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source Online0.map.bdimg.com.
Page size can be reduced by 272.4 kB (29%)
925.3 kB
652.9 kB
In fact, the total size of 39soso.com main page is 925.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. 35% of websites need less resources to load. Images take 652.1 kB which makes up the majority of the site volume.
Potential reduce by 8.4 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 8.4 kB or 69% of the original size.
Potential reduce by 79.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, 39 Soso needs image optimization as it can save up to 79.7 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 157.6 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 157.6 kB or 70% of the original size.
Potential reduce by 26.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. 39soso.com needs all CSS files to be minified and compressed as it can save up to 26.7 kB or 72% of the original size.
Number of requests can be reduced by 51 (50%)
102
51
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 39 Soso. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
39soso.com
2114 ms
style.css
875 ms
jquery.min.js
1543 ms
comm.js
887 ms
lang.js
723 ms
script.js
499 ms
comm.css
260 ms
focus.css
292 ms
diy.css
277 ms
tab.css
300 ms
logo.jpg
505 ms
ewm.jpg
799 ms
function.js
442 ms
dialog.js
215 ms
PIE.js
243 ms
popup.js
235 ms
finish.html
2777 ms
default.css
212 ms
top_lm_bg.jpg
258 ms
top_qq.jpg
303 ms
top_weib.jpg
241 ms
top_you.jpg
302 ms
dropmenu.css
250 ms
01.jpg
554 ms
qw.png
419 ms
fg_dh.png
326 ms
xw_1.png
265 ms
article_arrow.gif
341 ms
xw_2.png
324 ms
sy_tz_1.jpg
555 ms
sy_tz_2.jpg
643 ms
sy_tz_3.jpg
570 ms
ab_t.jpg
1037 ms
yw_t.png
669 ms
call_t.png
771 ms
zp_t.png
781 ms
db_qq.jpg
791 ms
db_wb.jpg
874 ms
db_yx.jpg
903 ms
gotop.png
1091 ms
tangram.js
1956 ms
api
983 ms
make.js
984 ms
scriptURL.js
1012 ms
mapCard.js
1143 ms
public.css
1347 ms
finish.css
1473 ms
preLoad.js
1469 ms
getscript
3783 ms
bmap.css
585 ms
bigMapIcon.jpg
503 ms
transparent.gif
2329 ms
2925 ms
5183 ms
3490 ms
4094 ms
2981 ms
headerTitle.jpg
530 ms
bigMap.jpg
529 ms
placeIcon.png
531 ms
button.png
489 ms
blank.gif
491 ms
openhand.cur
973 ms
3603 ms
h.js
1470 ms
getmodules
1489 ms
blank.gif
969 ms
confilter
849 ms
confilter
960 ms
confilter
1565 ms
confilter
2404 ms
confilter
1324 ms
geocoder
502 ms
confilter
1251 ms
hm.gif
1229 ms
2608 ms
1359 ms
mapctrls2d0.png
553 ms
copyright_logo.png
551 ms
mapctrls1d3.gif
549 ms
889 ms
1805 ms
5018 ms
2281 ms
1668 ms
2158 ms
1451 ms
getmodules
985 ms
transparent.gif
496 ms
911 ms
1743 ms
845 ms
2567 ms
3433 ms
1944 ms
api.map.baidu.com
528 ms
getmodules
2697 ms
location.gif
536 ms
marker_red_sprite.png
535 ms
api.map.baidu.com
489 ms
api.map.baidu.com
517 ms
api.map.baidu.com
560 ms
api.map.baidu.com
510 ms
api.map.baidu.com
529 ms
39soso.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 39soso.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 39soso.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.
39soso.com
Open Graph description is not detected on the main page of 39 Soso. 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: