42.7 sec in total
7.5 sec
34.8 sec
313 ms
Welcome to 158.net homepage info - get ready to check 158 best content right away, or after learning these important things about 158.net
Visit 158.netWe analyzed 158.net page load time and found that the first response time was 7.5 sec and then it took 35.1 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.
158.net performance score
7517 ms
2003 ms
11620 ms
5568 ms
871 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 87% of them (55 requests) were addressed to the original 158.net, 3% (2 requests) were made to Pat.zoosnet.net and 2% (1 request) were made to S13.cnzz.com. The less responsive or slowest element that took the longest time to load (18.7 sec) belongs to the original domain 158.net.
Page size can be reduced by 271.0 kB (48%)
569.9 kB
298.9 kB
In fact, the total size of 158.net main page is 569.9 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. 15% of websites need less resources to load. Images take 350.5 kB which makes up the majority of the site volume.
Potential reduce by 61.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. This page needs HTML code to be minified as it can gain 20.9 kB, which is 29% 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 61.4 kB or 85% of the original size.
Potential reduce by 110.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, 158 needs image optimization as it can save up to 110.7 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 81.7 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 81.7 kB or 65% of the original size.
Potential reduce by 17.2 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. 158.net needs all CSS files to be minified and compressed as it can save up to 17.2 kB or 79% of the original size.
Number of requests can be reduced by 20 (33%)
61
41
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 158. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
158.net
7517 ms
base.css
2003 ms
158sy.css
11620 ms
page.css
5568 ms
jzxx.css
871 ms
jquery.min.js
9594 ms
packUp.js
2423 ms
app.home.index.index.js
2384 ms
creatCon.js
2404 ms
focusblur.js
2734 ms
position.js
2763 ms
158sy.js
2831 ms
158sy1.js
12784 ms
changeNav.js
6598 ms
1
6236 ms
6
5533 ms
158swt.js
3629 ms
wx.js
5070 ms
stat.php
1482 ms
158sy_29.png
18704 ms
82%2077.jpg
8119 ms
158sy_37.png
4806 ms
158sy_38.png
10770 ms
158sy_39.png
398 ms
158sy_40.png
754 ms
158sy_41.png
7560 ms
158sy_42.png
3749 ms
158sy_43.png
1145 ms
158sy_blue01.jpg
4974 ms
158sy_blue02.jpg
5488 ms
158sy_blue03.jpg
7051 ms
158sy_blue04.jpg
5725 ms
158sy_04.png
5851 ms
543b95f24ba96.jpg
11755 ms
158sy_10.png
6217 ms
158sy_12.png
7319 ms
53fc37a4a2d83.jpg
11178 ms
158sy_16.png
7708 ms
158sy_18.png
13917 ms
158sy_19.png
8165 ms
158sy_20.png
8185 ms
158sy_21.png
8586 ms
158sy_25.png
13562 ms
158sy_28.png
10128 ms
158sy_31.png
10498 ms
158sy_32.png
10873 ms
158sy_33.png
13684 ms
158sy_34.png
11236 ms
158sy_35.png
11526 ms
158sy_36.png
12817 ms
swt.js
362 ms
swt2.js
2035 ms
LsJS.aspx
1984 ms
online_en3.gif
2466 ms
wx.jpg
8911 ms
stat.htm
285 ms
core.php
1204 ms
9.gif
1094 ms
pic.gif
832 ms
ajaxGetProvinces
6304 ms
AjaxBaiduData
7532 ms
jzaiz.jpg
10704 ms
app.gif
1103 ms
158.net SEO score
ZH
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 158.net can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that 158.net 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.
158.net
Open Graph description is not detected on the main page of 158. 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: