17.4 sec in total
1.2 sec
15.9 sec
333 ms
Click here to check amazing 1616 content for China. Otherwise, check out these important facts you probably never knew about 1616.net
Visit 1616.netWe analyzed 1616.net page load time and found that the first response time was 1.2 sec and then it took 16.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
1616.net performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value3.0 s
77/100
25%
Value5.2 s
61/100
10%
Value1,150 ms
22/100
30%
Value0.011
100/100
15%
Value5.0 s
76/100
10%
1164 ms
387 ms
2456 ms
2769 ms
2230 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 30% of them (26 requests) were addressed to the original 1616.net, 23% (20 requests) were made to Pic2.kangjianw.com and 19% (17 requests) were made to R.61658.com. The less responsive or slowest element that took the longest time to load (7.6 sec) relates to the external source Pic2.kangjianw.com.
Page size can be reduced by 1.4 MB (39%)
3.5 MB
2.1 MB
In fact, the total size of 1616.net main page is 3.5 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 46.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. 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 46.8 kB or 72% of the original size.
Potential reduce by 113.6 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. 1616 images are well optimized though.
Potential reduce by 896.5 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 896.5 kB or 73% of the original size.
Potential reduce by 302.5 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. 1616.net needs all CSS files to be minified and compressed as it can save up to 302.5 kB or 84% of the original size.
Number of requests can be reduced by 5 (6%)
85
80
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1616. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
1616.net
1164 ms
www.1616.net
387 ms
www_1616_0927.css
2456 ms
jquery-1.7.1.min.js
2769 ms
common.js
2230 ms
jquery_1.4.2.js
5061 ms
www_1616_static_exp.js
3830 ms
checkLogin.php
1183 ms
st.php
1387 ms
stat.php
2026 ms
blank
32 ms
logo.png
903 ms
qipao.gif
386 ms
tianmao.jpg
795 ms
weather_bg.png
22 ms
1616zuoce.htm
27 ms
appbg.png
73 ms
lf_icon.png
80 ms
h_bg.png
712 ms
navbg_m.png
709 ms
stat.htm
564 ms
core.php
822 ms
jinglingcss.png
1117 ms
1616.neiye.htm
81 ms
i_lianglihui.htm
108 ms
i_mvllk.htm
185 ms
i_hlrs.html
190 ms
mv_bg.png
854 ms
150X120.gif
2053 ms
bg_1.png
958 ms
150X120.gif
2109 ms
150X120.gif
2121 ms
150X120.gif
2512 ms
150X120.gif
2119 ms
150X120.gif
3158 ms
akjunshi_data.json
657 ms
li_bg.png
903 ms
lianglihui_data.json
1496 ms
lianliankan_data.json
510 ms
iptolocal.php
1183 ms
clock.php
1334 ms
indexad.json
498 ms
1616left.txt
4488 ms
news_data.json
517 ms
stat.htm
187 ms
yiqifa_data_530.json
1466 ms
41.gif
1125 ms
45.gif
3269 ms
44.gif
1758 ms
43.gif
2239 ms
42.gif
3282 ms
46.gif
2277 ms
50.gif
3995 ms
47.gif
4389 ms
49.gif
4801 ms
48.gif
3074 ms
%25E5%258C%2597%25E4%25BA%25AC.htm
1000 ms
clockbg_a.png
455 ms
t1.jpg
1149 ms
t2.jpg
4567 ms
a1.jpg
2629 ms
a2.jpg
1328 ms
a3.jpg
1837 ms
a4.jpg
1985 ms
a5.jpg
2808 ms
a6.jpg
2839 ms
a7.jpg
4704 ms
b1.jpg
3984 ms
b2.jpg
4951 ms
b3.jpg
4208 ms
b4.jpg
4267 ms
b5.jpg
5150 ms
b6.jpg
7638 ms
b7.jpg
5778 ms
c3.jpg
7226 ms
c4.jpg
5971 ms
c5.jpg
7390 ms
c6.jpg
6874 ms
a.jpg
677 ms
b.jpg
2909 ms
c.jpg
1033 ms
d.jpg
1297 ms
e.jpg
690 ms
a0.png
460 ms
1.jpg
5 ms
2.jpg
6 ms
3.jpg
918 ms
tc.css
458 ms
1616.net 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.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
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
1616.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
1616.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1616.net 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 1616.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.
1616.net
Open Graph description is not detected on the main page of 1616. 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: