72.9 sec in total
7.2 sec
65 sec
588 ms
Visit 1666.com now to see the best up-to-date 1666 content for China and also check out these interesting facts you probably never knew about 1666.com
1666游戏网为大家带来了时下最新最热门的手机游戏及软件,这里能够看到各种类型的手机app,本站持续为用户提供绿色、安全、优质的手机游戏及软件,赶快来下载吧。
Visit 1666.comWe analyzed 1666.com page load time and found that the first response time was 7.2 sec and then it took 65.6 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. Unfortunately, there were 22 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
1666.com performance score
7221 ms
3160 ms
6856 ms
3101 ms
780 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 8% of them (5 requests) were addressed to the original 1666.com, 85% (55 requests) were made to Static.1666.com and 2% (1 request) were made to S20.cnzz.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Static.1666.com.
Page size can be reduced by 680.4 kB (46%)
1.5 MB
790.1 kB
In fact, the total size of 1666.com main page is 1.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. 25% of websites need less resources to load. Images take 909.7 kB which makes up the majority of the site volume.
Potential reduce by 57.7 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 33.8 kB, which is 53% 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 57.7 kB or 90% of the original size.
Potential reduce by 201.5 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, 1666 needs image optimization as it can save up to 201.5 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 360.8 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 360.8 kB or 85% of the original size.
Potential reduce by 60.3 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. 1666.com needs all CSS files to be minified and compressed as it can save up to 60.3 kB or 83% of the original size.
Number of requests can be reduced by 9 (23%)
40
31
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1666. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
1666.com
7221 ms
www.1666.com
3160 ms
common.css
6856 ms
platform.css
3101 ms
stat.php
780 ms
jquery.js
3705 ms
jquery.placeholder.js
1033 ms
1666.js
3711 ms
home.js
1240 ms
home.js
1500 ms
formValidator-4.1.3.js
2381 ms
formValidatorRegex.js
1851 ms
theme.js
1955 ms
201603116394190118.jpg
11462 ms
201505148269738601.jpg
3878 ms
201603113261261506.jpg
2937 ms
201511178952306339.jpg
4028 ms
201409091794692250.jpg
5454 ms
201510306734582412.jpg
5553 ms
201509172164113333.jpg
5818 ms
201507083899336600.jpg
6762 ms
201310152754925550.png
5564 ms
201412121948247949.jpg
7523 ms
201505147982649717.jpg
10916 ms
201309014470947800.png
6141 ms
anti-addiction.jpg
9477 ms
201508076820357976.jpg
19660 ms
201603111973974587.jpg
19660 ms
201505184374465259.jpg
15362 ms
201310159075259852.png
13052 ms
201309017169584235.png
19659 ms
201603111092462408.jpg
19660 ms
201511172589658555.jpg
19660 ms
201510307775218296.jpg
18240 ms
201509177405344653.jpg
19659 ms
201507086117751623.jpg
19659 ms
201412121190342396.jpg
19659 ms
201409095453314341.jpg
19659 ms
201503181085279603.jpg
19659 ms
201405042618284389.jpg
19634 ms
201403195805675616.jpg
20427 ms
201402192087740160.png
20408 ms
201401147243564278.png
20167 ms
201311196308568805.jpg
19816 ms
201310153328753336.png
19713 ms
201309016509450745.png
20284 ms
normalize.css
19659 ms
stat.htm
291 ms
core.php
1112 ms
bg_2.png
564 ms
icons.png
909 ms
logo.png
1100 ms
140117.png
1668 ms
bg_text.jpg
1205 ms
sign-jifen.png
1670 ms
platform.png
1799 ms
9.gif
961 ms
left.jpg
19760 ms
right.jpg
19756 ms
weixin.gif
10924 ms
201508076820357976.jpg
17980 ms
app.gif
906 ms
201506231704445145.jpg
13179 ms
201505294720362100.jpg
19765 ms
201505186611119300.jpg
19761 ms
1666.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 1666.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 1666.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.
1666.com
Open Graph description is not detected on the main page of 1666. 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: