139.2 sec in total
1 sec
137.8 sec
450 ms
Click here to check amazing Ttll content for China. Otherwise, check out these important facts you probably never knew about ttll.cc
Visit ttll.ccWe analyzed Ttll.cc page load time and found that the first response time was 1 sec and then it took 138.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. Unfortunately, there were 77 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
ttll.cc performance score
1003 ms
1915 ms
36 ms
47 ms
32 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 22% of them (35 requests) were addressed to the original Ttll.cc, 58% (93 requests) were made to Imge.ttll.cc and 4% (6 requests) were made to Cpro.baidustatic.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Imge.ttll.cc.
Page size can be reduced by 371.4 kB (45%)
828.4 kB
457.0 kB
In fact, the total size of Ttll.cc main page is 828.4 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. 30% of websites need less resources to load. Images take 354.8 kB which makes up the majority of the site volume.
Potential reduce by 62.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. 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 62.7 kB or 77% of the original size.
Potential reduce by 47.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. Obviously, Ttll needs image optimization as it can save up to 47.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 203.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 203.2 kB or 63% of the original size.
Potential reduce by 58.0 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. Ttll.cc needs all CSS files to be minified and compressed as it can save up to 58.0 kB or 81% of the original size.
Number of requests can be reduced by 31 (40%)
77
46
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ttll. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.
ttll.cc
1003 ms
www.ttll.cc
1915 ms
style.css
36 ms
jquery.min.js
47 ms
remeng.js
32 ms
666ddcc.js
34 ms
PPXXC.js
33 ms
er_17866_7084.js
5090 ms
bg.png
57 ms
top.png
52 ms
logo.png
57 ms
bglist.png
83 ms
sjtg.jpg
53 ms
max_history.js
17 ms
sydb.js
18 ms
201632123301326899.jpg
16126 ms
s55656c.js
16 ms
20163282201977682.jpg
20339 ms
97259.jpg
6059 ms
20164120493240348.jpg
15750 ms
95210.jpg
4930 ms
99859.jpg
15805 ms
99409.jpg
12255 ms
98381.jpg
7443 ms
20164810243942086.jpg
20338 ms
98247.jpg
20338 ms
20162251164671582.jpg
18025 ms
20162251130355889.jpg
20339 ms
95854.jpg
20341 ms
201632320574766815.jpg
20342 ms
20164119592144671.jpg
20342 ms
98867.jpg
20343 ms
100017.jpg
20343 ms
98577.jpg
20344 ms
98482.jpg
20345 ms
98968.jpg
20345 ms
99361.jpg
20345 ms
98355.jpg
20345 ms
93651.jpg
20346 ms
94913.jpg
20347 ms
98772.jpg
20347 ms
96695.jpg
20348 ms
99786.jpg
20348 ms
97625.jpg
20349 ms
97818.jpg
20349 ms
100019.jpg
20349 ms
98519.jpg
20350 ms
99905.jpg
20350 ms
20163156184781636.jpg
20351 ms
20163917133050298.jpg
20350 ms
99805.jpg
20351 ms
98334.png
20351 ms
201311711183581012.png
8 ms
stat.php
2001 ms
new_js.js
4 ms
scroll.js
5 ms
tab_index.js
7 ms
tqq.js
6 ms
returntop.js
7 ms
rich03.js
1262 ms
navbg.png
17 ms
navli.png
9 ms
navicon01.png
11 ms
hidden_b.png
10 ms
mark.png
9 ms
c.js
983 ms
2016490494872947.jpg
20407 ms
scmm
739 ms
scmm
920 ms
num.png
19 ms
more.png
55 ms
ehd.png
56 ms
squre.png
55 ms
hm.js
2440 ms
stat.htm
161 ms
core.php
764 ms
20164817383155300.jpg
20279 ms
scmm
469 ms
arror_left.png
25 ms
cookie.php
1150 ms
cookie.php
1123 ms
arror_right.png
11 ms
menusort.png
9 ms
scmm
1298 ms
adx.php
1334 ms
tanx_ui.js
1228 ms
dot.gif
95 ms
close.gif
168 ms
20164815544670509.jpg
19894 ms
reduce_bd-logo1_oper.png
501 ms
adx.php
1071 ms
u=3203638994,3630319575&fm=76
1050 ms
u=3684748332,3347696426&fm=76
2126 ms
y.gif
1131 ms
hm.gif
303 ms
t.gif
19936 ms
e.gif
425 ms
closefeedback.min.js
578 ms
reduce_promotion_oper.png
494 ms
bd_logo.png
497 ms
bg_rb.png
504 ms
20164815501979791.jpg
19952 ms
20164815461343557.jpg
19588 ms
100684.jpg
19531 ms
20164810341246610.jpg
16687 ms
2016461113147625.jpg
20310 ms
20164718282715943.jpg
19999 ms
20163313414434530.jpg
19998 ms
98892.jpg
19997 ms
99275.jpg
19997 ms
99035.jpg
19997 ms
99947.jpg
19996 ms
201622011315720388.jpg
19996 ms
99748.jpg
19995 ms
20162202248452897.jpg
19994 ms
55451.jpg
19994 ms
99823.jpg
19993 ms
20163161430690279.jpg
19994 ms
99353.jpg
19993 ms
2016490394020595.jpg
19992 ms
2016490581296981.jpg
19992 ms
2016490473097703.jpg
19992 ms
99828.jpg
19991 ms
99745.jpg
19989 ms
99912.jpg
19990 ms
20164123103441941.jpg
19989 ms
2016412385049351.jpg
19989 ms
90718.jpg
19989 ms
90727.jpg
19988 ms
90849.jpg
19988 ms
90706.jpg
19988 ms
90720.jpg
19988 ms
20163282201977682.jpg
20082 ms
20164810243942086.jpg
20082 ms
98247.jpg
20000 ms
20162251130355889.jpg
20000 ms
95854.jpg
19999 ms
201632320574766815.jpg
20127 ms
20164119592144671.jpg
19527 ms
20163282201977682.jpg
20081 ms
20164810243942086.jpg
20082 ms
98247.jpg
20082 ms
20162251130355889.jpg
18882 ms
95854.jpg
13917 ms
201632320574766815.jpg
20083 ms
20164119592144671.jpg
20083 ms
20163282201977682.jpg
20111 ms
20164810243942086.jpg
20111 ms
98247.jpg
15274 ms
201632320574766815.jpg
20058 ms
20164119592144671.jpg
20058 ms
20163282201977682.jpg
17979 ms
20164810243942086.jpg
18408 ms
201632320574766815.jpg
19098 ms
20164119592144671.jpg
18268 ms
o.htm
8496 ms
hm.gif
1674 ms
ac.js
497 ms
wh.js
750 ms
ttll.cc SEO score
ZH
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ttll.cc 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 Ttll.cc main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
ttll.cc
Open Graph description is not detected on the main page of Ttll. 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: