13 sec in total
2.8 sec
9.6 sec
541 ms
Visit media.1111.com.tw now to see the best up-to-date Media 1111 content for Taiwan and also check out these interesting facts you probably never knew about media.1111.com.tw
提供各大知名傳播媒體最新工作職缺、產業新聞與媒體人故事,包含記者、主播、資深媒體人的工作經驗與故事分享,還有新聞傳播媒體人職場上應該注意的事在1111媒體人專區通通找得到!
Visit media.1111.com.twWe analyzed Media.1111.com.tw page load time and found that the first response time was 2.8 sec and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
media.1111.com.tw performance score
2825 ms
424 ms
424 ms
869 ms
439 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 30% of them (38 requests) were addressed to the original Media.1111.com.tw, 19% (24 requests) were made to Static.xx.fbcdn.net and 12% (15 requests) were made to Images.1111.com.tw. The less responsive or slowest element that took the longest time to load (4.8 sec) relates to the external source Images.1111.com.tw.
Page size can be reduced by 157.0 kB (49%)
318.0 kB
161.0 kB
In fact, the total size of Media.1111.com.tw main page is 318.0 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. 60% of websites need less resources to load. Javascripts take 140.9 kB which makes up the majority of the site volume.
Potential reduce by 86.2 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 86.2 kB or 78% of the original size.
Potential reduce by 7.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. Obviously, Media 1111 needs image optimization as it can save up to 7.0 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 43.1 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 43.1 kB or 31% of the original size.
Potential reduce by 20.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. Media.1111.com.tw needs all CSS files to be minified and compressed as it can save up to 20.7 kB or 83% of the original size.
Number of requests can be reduced by 63 (53%)
120
57
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Media 1111. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
media.1111.com.tw
2825 ms
reset.css
424 ms
jquery.bxslider.css
424 ms
zone.css
869 ms
style.css
439 ms
jquery-1.7.min.js
1190 ms
jquery.bxslider.min.js
882 ms
script.js
685 ms
smart-app-banner.css
688 ms
smart-app-banner.js
863 ms
marquee_discusszone.js
707 ms
jquery.fancybox.css
720 ms
discuss.css
902 ms
jquery.fancybox.pack.js
897 ms
jquery.mousewheel-3.0.6.pack.js
895 ms
jquery.lazyload.js
936 ms
discuss.js
1163 ms
topLinkNew.js
659 ms
topLink.css
884 ms
jsapi
20 ms
conversion.js
19 ms
adImpression_jquery.js
890 ms
adImpression.js
892 ms
adkeyword.js
901 ms
discuss_zoneset.css
944 ms
sdk.js
280 ms
logo_l.png
706 ms
icon_line.png
302 ms
fontawesome-webfont.woff
799 ms
51001452_17521793.5727437.png
3446 ms
discusszone_media_banner_6.gif
533 ms
discusszone_media_banner_7.gif
834 ms
discusszone_media_banner_4.png
1269 ms
discusszone_media_banner_5.png
1343 ms
discusszone_media_banner_1.JPG
833 ms
logo_s.jpg
937 ms
discusszone_media_watterbanner_0.png
958 ms
icon_hover.png
223 ms
51001452_17609816.884797.png
3205 ms
51001452_17501996.9295778.png
4099 ms
51001452_17178881.0584109.png
3543 ms
icon_search.png
1031 ms
icon_search.png
1036 ms
u.php
135 ms
clickCount.js
225 ms
topLinkArray.js
275 ms
topLinkArrayAD.js
421 ms
41 ms
80 ms
xd_arbiter.php
214 ms
xd_arbiter.php
491 ms
search_box_icon.png
237 ms
customer.png
237 ms
test_headerbar.png
228 ms
13 ms
default+en.css
5 ms
default.css
17 ms
default+en.I.js
13 ms
default.css
28 ms
atrk.js
137 ms
152 ms
analytics.js
92 ms
readTopicList.asp
627 ms
memberCenter.png
418 ms
bx_loader.gif
474 ms
controls.png
472 ms
collect
22 ms
atrk.gif
40 ms
collect
57 ms
44 ms
test.png
166 ms
page.php
236 ms
BE45KdLvtnt.css
308 ms
IkDOfJS_DMJ.css
379 ms
pepHF3XKFXU.css
446 ms
u-VzxJsCQIC.css
579 ms
3xHhS1aNtZL.css
592 ms
6bIl72b-rkY.js
645 ms
E0rdciiEihq.js
644 ms
mn6tHWuLI-Y.js
512 ms
x8BMxYCqTb9.js
515 ms
QKy94bWvcbp.js
598 ms
5paioeCYCa7.js
597 ms
wRXOQ26LQ1k.js
712 ms
UMeIUxuSxxa.js
849 ms
50Trs1RKgUY.js
680 ms
bookli-p1.jpg
61 ms
User_51001452.png
437 ms
51001452_17742428.0715668.jpg
1080 ms
51110044_14489187.4696118.png
2985 ms
51001452_17693213.4871388.png
3032 ms
51001452_17656151.7085675.jpg
2062 ms
51001452_17569600.264834.jpg
2288 ms
51001452_17520197.0073397.png
3027 ms
default.png
2391 ms
51001452_17483550.9974985.jpg
2512 ms
51001452_17176414.9495055.png
3940 ms
51001452_17509873.255253.png
4794 ms
statscontainer_orange.gif
214 ms
statscontainer.gif
222 ms
11084274_860437277328787_5352676526191024995_n.jpg
293 ms
safe_image.php
292 ms
safe_image.php
422 ms
safe_image.php
555 ms
safe_image.php
491 ms
safe_image.php
532 ms
11080983_860436980662150_4555731422971960785_n.jpg
346 ms
10153654_1707919406158490_2196157916489241257_n.jpg
490 ms
11230728_10207369709616991_3556136673976963300_n.jpg
672 ms
10354686_10150004552801856_220367501106153455_n.jpg
487 ms
10428599_904124409598967_1253625654702888668_n.jpg
483 ms
12227624_954932011246754_7053332951841125652_n.jpg
599 ms
183149_4630568931674_1914376135_n.jpg
485 ms
12800168_1163268930349838_3217069848555523846_n.jpg
553 ms
wL6VQj7Ab77.png
76 ms
s7jcwEQH7Sx.png
78 ms
mbF8ssTVP_5.png
77 ms
Fe6g47SXw-8.png
76 ms
L5AOQ9vzKfo.png
77 ms
oULnqcel5Nm.png
77 ms
q2ibvFgTxmh.png
148 ms
A2JLtDOGyCJ.png
148 ms
Fy3hs8lKW0M.png
148 ms
VXcANLwwL5J.js
70 ms
async-ads.js
33 ms
media.1111.com.tw SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Media.1111.com.tw 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 Media.1111.com.tw 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.
media.1111.com.tw
Open Graph data is detected on the main page of Media 1111. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: