8 sec in total
1.3 sec
6.4 sec
306 ms
Click here to check amazing I Buzz content for Taiwan. Otherwise, check out these important facts you probably never knew about i-buzz.com.tw
我們堅信數據會說話,專注於網路口碑網羅與解讀,緊追重要產業趨勢及新聞時事議題。從數據找線索,讀懂網友的心,了解消費者真正在乎、想要什麼。
Visit i-buzz.com.twWe analyzed I-buzz.com.tw page load time and found that the first response time was 1.3 sec and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
i-buzz.com.tw performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value9.9 s
0/100
25%
Value33.8 s
0/100
10%
Value17,470 ms
0/100
30%
Value0.302
39/100
15%
Value51.1 s
0/100
10%
1314 ms
519 ms
529 ms
882 ms
754 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 45% of them (36 requests) were addressed to the original I-buzz.com.tw, 28% (22 requests) were made to Static.xx.fbcdn.net and 11% (9 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain I-buzz.com.tw.
Page size can be reduced by 589.5 kB (17%)
3.5 MB
2.9 MB
In fact, the total size of I-buzz.com.tw main page is 3.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. 55% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 23.0 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 23.0 kB or 74% of the original size.
Potential reduce by 224.7 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. I Buzz images are well optimized though.
Potential reduce by 279.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 279.4 kB or 64% of the original size.
Potential reduce by 62.4 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. I-buzz.com.tw needs all CSS files to be minified and compressed as it can save up to 62.4 kB or 82% of the original size.
Number of requests can be reduced by 29 (38%)
77
48
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I Buzz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
i-buzz.com.tw
1314 ms
jquery-ui.css
519 ms
style0305.css
529 ms
jquery-1.11.1.min.js
882 ms
jquery.cycle2.js
754 ms
jquery-ui.min.js
1311 ms
reset.css
363 ms
logo.jpg
348 ms
focus.png
349 ms
1427685559.png
905 ms
1427685548.png
886 ms
1427685539.png
958 ms
1427685519.png
1265 ms
icon_left_15x40.png
725 ms
icon_right_15x40.png
969 ms
1456199634.jpg
2345 ms
1456199736.jpg
1789 ms
1454955793.jpg
2245 ms
1455607103.jpg
1651 ms
1454737580.jpg
1825 ms
1427962348.png
1990 ms
1427962338.png
2613 ms
1427962325.png
2552 ms
1427962303.png
2489 ms
indextitle-1.jpg
2326 ms
btn-left.jpg
2619 ms
1442548120.jpg
3010 ms
iconview.jpg
2705 ms
1440564754.jpg
4246 ms
1443069198.JPG
3307 ms
1447130142.jpg
3342 ms
1445916391.png
3341 ms
btn-right.jpg
3035 ms
1427962409.png
3912 ms
1427962396.png
4138 ms
cse.js
31 ms
menu_bg.jpg
3635 ms
cse.js
185 ms
likebox.php
248 ms
jsapi
32 ms
default+zh_TW.css
7 ms
default+zh_TW.I.js
18 ms
default.css
35 ms
FbUd6dZS1Af.css
176 ms
dGJLq38YL-C.css
216 ms
jsSBgYmM8Bv.css
257 ms
_rx8naC75Dy.js
334 ms
x5F9OMjKyLw.js
362 ms
ICDbTSzjQEg.js
331 ms
TTCre3391I0.js
332 ms
C-h3nYPqETO.js
359 ms
rFmE1g6Dkoz.js
412 ms
7cm7D75Y0Sf.js
376 ms
oRoBXlHCpEy.js
360 ms
336JejShbZp.js
385 ms
sj-JwAJi4AH.js
409 ms
DKRU1bYTkTw.js
445 ms
ZNPAadQNc33.js
399 ms
W0OV23mIOyO.js
401 ms
36TdwhIHusi.js
452 ms
10247377_575134299260802_736752545872215634_n.jpg
212 ms
10250197_575164442591121_5859231987261291037_n.jpg
251 ms
12227712_10153926008358287_8455641504604337900_n.jpg
292 ms
12144806_10205273532741481_7161597516083997232_n.jpg
323 ms
1911636_807293029340889_5955493718347137239_n.jpg
450 ms
922973_135874240119398_5124922495951775333_n.jpg
364 ms
190689_100484176703696_4119266_n.jpg
331 ms
12036458_720074764791533_6835628264855630106_n.jpg
333 ms
10989121_10200275066435463_5622432036162434450_n.jpg
333 ms
wL6VQj7Ab77.png
72 ms
s7jcwEQH7Sx.png
71 ms
pUFVdPjIRct.png
41 ms
I6-MnjEovm5.js
41 ms
vlXaquuXMrr.js
74 ms
async-ads.js
53 ms
google_custom_search_watermark.gif
25 ms
small-logo.png
13 ms
search_box_icon.png
13 ms
clear.png
12 ms
google_custom_search_watermark.gif
16 ms
i-buzz.com.tw 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
i-buzz.com.tw 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
i-buzz.com.tw SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I-buzz.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 I-buzz.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.
i-buzz.com.tw
Open Graph description is not detected on the main page of I Buzz. 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: