36.5 sec in total
1.7 sec
34.4 sec
382 ms
Welcome to 3lian.com homepage info - get ready to check 3 Lian best content for Taiwan right away, or after learning these important things about 3lian.com
Visit 3lian.comWe analyzed 3lian.com page load time and found that the first response time was 1.7 sec and then it took 34.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
3lian.com performance score
1682 ms
668 ms
768 ms
2789 ms
4459 ms
Our browser made a total of 146 requests to load all elements on the main page. We found that 29% of them (42 requests) were addressed to the original 3lian.com, 8% (11 requests) were made to Img16.3lian.com and 4% (6 requests) were made to Img11.3lian.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Img9.3lian.com.
Page size can be reduced by 939.5 kB (13%)
7.1 MB
6.2 MB
In fact, the total size of 3lian.com main page is 7.1 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. 40% of websites need less resources to load. Images take 6.5 MB which makes up the majority of the site volume.
Potential reduce by 57.1 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 57.1 kB or 76% of the original size.
Potential reduce by 535.1 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. 3 Lian images are well optimized though.
Potential reduce by 258.4 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 258.4 kB or 67% of the original size.
Potential reduce by 88.9 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. 3lian.com needs all CSS files to be minified and compressed as it can save up to 88.9 kB or 79% of the original size.
Number of requests can be reduced by 48 (37%)
130
82
The browser has sent 130 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 3 Lian. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
3lian.com
1682 ms
dh.js
668 ms
js.js
768 ms
topfoot1.css
2789 ms
topnav2013.css
4459 ms
newupdate.css
1979 ms
share3.js
1138 ms
qzopensl.js
140 ms
cvc.css
373 ms
followbutton.php
2121 ms
31.jpg
9569 ms
small99986e4f9b95b9f05f4a41f4df6dc8791460081345.png
4169 ms
small94ead8fdd33db0cf1209354a6c0afcfc1459155651.png
2992 ms
1.jpg
3413 ms
60s.jpg
5464 ms
90s.jpg
10762 ms
65s.jpg
2624 ms
topbg.jpg
373 ms
inavmenu.jpg
345 ms
logo.gif
879 ms
inav.gif
442 ms
inavbgx.jpg
374 ms
top-new-bg.png
1337 ms
dian.gif
1526 ms
index01.gif
1664 ms
hao123_88_31.gif
746 ms
p2plogoppcn.gif
878 ms
erw.png
1515 ms
smallfc965d55d0c6bf9f25ac6d9a8e2c85631459134409.png
9021 ms
small7b647c7569d92e4ac5ca7f7f66c1903f1458962577.jpg
3122 ms
small009265631b0a75d2bd84a22dd34831bf1459328338.jpg
4550 ms
small405d6a886dda5e7745248ce6042c31201458982438.png
10051 ms
small6a61fcdc1c0bd0bb654dfdcb18dc84231459216058.jpg
7071 ms
64s.jpg
14442 ms
63s.jpg
4376 ms
62s.jpg
5823 ms
61s.jpg
15078 ms
60s.jpg
10145 ms
59s.jpg
17066 ms
58s.jpg
20334 ms
57s.jpg
11919 ms
56s.jpg
12682 ms
55s.jpg
13172 ms
small0d383572b20f65f2b8fdecc28a2485ad1459846961.jpg
2248 ms
smalld6f75cafde05fbd8425967bac6c75b081460083316.jpg
20333 ms
small52df6647455b3a915d169c0d365bffb51460083189.jpg
2528 ms
small3ecb4fe2464051f1d58bb3095a03b1821460082973.jpg
2630 ms
smallb01e1023fb97f279cc95ccd81fd8a8b01460080750.jpg
4525 ms
small1cba7de8899e865465606417822efb741460080600.jpg
3028 ms
smalladc9177190217904cf09c92bc4f337a91460080443.jpg
3425 ms
smallc35128ece9c26d6696a37dfa51473e641460079910.jpg
3824 ms
small33c0dd109ad44b4ab4724452b578a3ad1460107133.jpg
4222 ms
small4a98eb2e9486f75c9f98e189d37724831460107383.jpg
5481 ms
small8d19e72df1f089b06bf349ef2d216f371459580278.jpg
4619 ms
89s.jpg
4145 ms
88s.jpg
5438 ms
87s.jpg
5529 ms
86s.jpg
20328 ms
85s.jpg
13457 ms
101.jpg
3991 ms
81.jpg
5825 ms
61.jpg
5974 ms
41.jpg
7043 ms
1.jpg
5306 ms
41.jpg
12953 ms
1.jpg
20326 ms
91.jpg
7153 ms
41.jpg
11568 ms
81.jpg
7853 ms
sprite_bg.png
2975 ms
sprite.png
3746 ms
shell_v2.js
778 ms
icon01.jpg
1152 ms
recommend-ico.jpg
1623 ms
tit.png
1831 ms
i2.gif
1818 ms
c.js
1039 ms
bds_s_v2.js
382 ms
mcem
2153 ms
dian.gif
903 ms
dott.jpg
896 ms
s009.js
1840 ms
bdsstyle.css
1925 ms
getnum
1314 ms
followButton.css
49 ms
sso.js
30 ms
followButton.js
26 ms
suda.js
28 ms
b.gif
1076 ms
bg_flbtn.png
3 ms
ex
1616 ms
is_32.png
2705 ms
sc.png
624 ms
mcem
1080 ms
adx.php
884 ms
reduce_bd-logo1_oper.png
494 ms
tanxssp.js
341 ms
closefeedback.min.js
540 ms
ex
1108 ms
reduce_promotion_oper.png
496 ms
bd_logo.png
498 ms
bg_rb.png
510 ms
acbeacon2.html
336 ms
TB1DmcoJXXXXXavXpXXXXXXXXXX-26-26.png
166 ms
mcem
494 ms
k_bg.jpg
386 ms
k2.gif
407 ms
TB1Lt7aJXXXXXcjXVXXXXXXXXXX-117-26.png
144 ms
TB1rRQpJXXXXXcvXXXXXXXXXXXX-40-26.png
147 ms
TB1upAiJXXXXXa5aXXXXXXXXXXX-116-30.png
144 ms
443 ms
TB1p.iLGFXXXXXJXVXXO04pFXXX.html
298 ms
t.gif
891 ms
h.js
1724 ms
t.gif
924 ms
bl
1954 ms
js
1574 ms
mcem
524 ms
m
4776 ms
adx.php
433 ms
app.gif
3860 ms
logger.js
414 ms
cgi_qzshare_likeurl
557 ms
T1VFpJFoFaXXbtNKPk-62-38.jpg
366 ms
T21iWuXexbXXXXXXXX_!!0-1-newland.gif
231 ms
tanxclick.js
33 ms
T2nb9NXjhXXXXXXXXX_!!0-1-newland.gif
375 ms
open_guanzhu_widget.css
70 ms
1.0.js
70 ms
cgi_qzsharegetlike
536 ms
like_bg_zan.png
139 ms
like_bg_guanzhu.png
137 ms
code.cgi
511 ms
um.js
321 ms
img
2767 ms
um.json
1424 ms
getDeviceInfo
907 ms
T2E9JOXoXdXXXXXXXX_!!0-0-newland.jpg
11 ms
T2gNOqXjtbXXXXXXXX_!!0-0-newland.jpg
20 ms
getDeviceInfo
1052 ms
T2iHkPXlxXXXXXXXXX_!!0-2-newland.png
50 ms
T2SL50XgRaXXXXXXXX_!!0-1-newland.gif
36 ms
T2N6HrXaBaXXXXXXXX_!!0-1-newland.gif
28 ms
T2YpcQXcFXXXXXXXXX_!!0-2-newland.png
999 ms
T20gCCXm4bXXXXXXXX_!!0-1-newland.gif
28 ms
T20bCNXnVXXXXXXXXX_!!0-1-newland.gif
13 ms
3lian.com SEO score
ZH
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 3lian.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 3lian.com 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.
3lian.com
Open Graph description is not detected on the main page of 3 Lian. 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: