42.3 sec in total
204 ms
41.3 sec
825 ms
Click here to check amazing 236 Zz content for China. Otherwise, check out these important facts you probably never knew about 236zz.com
236宅宅网提供第一手电影电视剧网络免费在线观看、迅雷下载,以及各大视频网站会员视频在本站都可以免费无广告高清观看,努力做有回头客的优质在线电影网站!
Visit 236zz.comWe analyzed 236zz.com page load time and found that the first response time was 204 ms and then it took 42.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.
236zz.com performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value11.5 s
0/100
25%
Value11.5 s
5/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value6.0 s
64/100
10%
204 ms
4537 ms
779 ms
3659 ms
1372 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 56% of them (76 requests) were addressed to the original 236zz.com, 6% (8 requests) were made to 77kp.com and 4% (5 requests) were made to Mu1.sinaimg.cn. The less responsive or slowest element that took the longest time to load (12.7 sec) relates to the external source Mu1.sinaimg.cn.
Page size can be reduced by 774.2 kB (21%)
3.7 MB
2.9 MB
In fact, the total size of 236zz.com main page is 3.7 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. 50% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 77.3 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 77.3 kB or 78% of the original size.
Potential reduce by 204.0 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. 236 Zz images are well optimized though.
Potential reduce by 336.2 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 336.2 kB or 64% of the original size.
Potential reduce by 156.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. 236zz.com needs all CSS files to be minified and compressed as it can save up to 156.7 kB or 84% of the original size.
Number of requests can be reduced by 35 (26%)
134
99
The browser has sent 134 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 236 Zz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
236zz.com
204 ms
www.236zz.com
4537 ms
home.css
779 ms
jquery.js
3659 ms
jquery.lazyload.js
1372 ms
jquery.autocomplete.js
1388 ms
home.js
2341 ms
tpl.js
437 ms
header.css
960 ms
index.css
999 ms
jquery-1.7.1.min.js
1448 ms
playclass.js
1182 ms
playlist.js
1425 ms
jquery-lazyload.js
1630 ms
jquery.autocomplete.js
1629 ms
js.js
1655 ms
jquery.cookie.js
1633 ms
Topnav.js
2081 ms
Topfenxiang.js
1779 ms
tj.js
1646 ms
jquery.colorbox.js
1837 ms
jquery.vod.js
1801 ms
index_top.js
1801 ms
fmt.js
1976 ms
vod_index.css
269 ms
61e7f4aajw1f1i7w5gxqcj208y0ciq4d.jpg
584 ms
176971_vertical.jpg
4389 ms
201512171450367551.jpg
1108 ms
91e87880gw1ewuvdd1fqyj20iu0qntc3.jpg
1123 ms
ad740181f01634fbfed74c05cecd3936
2735 ms
006iGN3Hgw1f284pp5vx9j30bh0gomz2.jpg
285 ms
006iGN3Hgw1f27nz04x43j306e08yaaz.jpg
512 ms
144997231411.jpg
2124 ms
1448444408771.jpg
1352 ms
2015121215173431704.jpg
7933 ms
e7b1b0ae78fa2705bb0456708b5e1804
3891 ms
2015121123421139940.jpg
7928 ms
2015121213335111776.jpg
7923 ms
2015121014405284418.jpg
7922 ms
144946102710.jpg
2116 ms
14492830830.jpg
2116 ms
14499837870.jpg
2118 ms
14500635310.jpg
2119 ms
14497150106.jpg
2118 ms
14497303116.jpg
2323 ms
14497303114.jpg
2324 ms
006iGN3Hgw1f28468unb8j307g0adaab.jpg
1027 ms
006iGN3Hgw1ezy14ar907j304w06lq3h.jpg
1096 ms
177162_vertical.jpg
7612 ms
99946_vertical.jpg
8521 ms
177438_vertical.jpg
12660 ms
178846_vertical.jpg
7498 ms
ce0967daf39b214e3260b96df13acb26
4539 ms
bg.jpg
507 ms
toplogo.png
236 ms
ad1000.jpg
493 ms
144657774511.jpg
234 ms
144657706311.jpg
337 ms
14465826250.jpg
278 ms
14465853766.jpg
508 ms
14465776427.jpg
453 ms
www.236zz.com
620 ms
144656715611.jpg
628 ms
14465668454.jpg
930 ms
144656700616.jpg
779 ms
14465790447.jpg
1063 ms
144657778716.jpg
1372 ms
14465742537.jpg
928 ms
14466131504.jpg
1016 ms
14466131453.jpg
2441 ms
14466131392.jpg
1544 ms
14466131331.jpg
1769 ms
144661311819.jpg
1471 ms
144656661518.jpg
1396 ms
14466174400.jpg
2049 ms
14466158890.jpg
1508 ms
footlogo.png
1700 ms
1448444321910.jpg
1327 ms
1440476251574.jpg
1386 ms
006iGN3Hgw1f27nryd70pj304w06l3yz.jpg
481 ms
a16a0103gw1f1rol0dienj20ci0g5q4f.jpg
568 ms
006iGN3Hgw1f290tip164j306e08zjs7.jpg
523 ms
006gIazRjw1ez7o0b084hj30iu0qvwix.jpg
615 ms
006iGN3Hgw1eyvnlgeogpj30c80hswg4.jpg
586 ms
navtitle_black1.png
1577 ms
jia.js
647 ms
jiathis_utility.html
64 ms
jiathis_share.css
119 ms
plugin.client.js
102 ms
jiathis_ico_32x32.png
271 ms
topico.png
907 ms
ui-icon.gif
1091 ms
index.php
1068 ms
logo.png
289 ms
headerpage.png
315 ms
top_ico.png
266 ms
top_ico2.png
268 ms
navbg.gif
294 ms
nav_l.png
754 ms
nav_r.png
521 ms
www.236zz.com
549 ms
index_tit_bg2.gif
444 ms
title2bg.png
451 ms
picdownbg.png
528 ms
index_tit_bg1.gif
650 ms
title1bg.png
655 ms
index_tit_bg4.gif
684 ms
title4bg.png
741 ms
index_tit_bg3.gif
567 ms
title3bg.png
797 ms
index_tit_ph.gif
659 ms
tit_ph_rbg.gif
742 ms
tit17.gif
829 ms
footerbg.jpg
867 ms
stat.php
1294 ms
stat.htm
239 ms
core.php
858 ms
rightmenumapbg.png
223 ms
o.js
5109 ms
ucnm
996 ms
fm_b.js
2439 ms
ir.ashx
4719 ms
rv1.ashx
2132 ms
vip.jisucn.com
3805 ms
timming.php
132 ms
z_stat.php
2225 ms
close.png
1070 ms
v2.ashx
9383 ms
logo.png
2127 ms
stat.htm
253 ms
core.php
308 ms
o.htm
1068 ms
wh.js
1366 ms
ac.js
605 ms
fp.htm
834 ms
fp.htm
320 ms
236zz.com 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
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
236zz.com 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
236zz.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 236zz.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that 236zz.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.
236zz.com
Open Graph description is not detected on the main page of 236 Zz. 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: