Tools & Wizards About Us
buzzmac.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

buzzmac.jp

Mac App Storeのアプリ検索・ランキング BuzzMac!

Page Load Speed

7.1 sec in total

First Response

836 ms

Resources Loaded

6.1 sec

Page Rendered

190 ms

buzzmac.jp screenshot

About Website

Visit buzzmac.jp now to see the best up-to-date Buzz Mac content for Japan and also check out these interesting facts you probably never knew about buzzmac.jp

Mac App StoreのMacアプリを紹介。人気のMacアプリランキングも。

Visit buzzmac.jp

Key Findings

We analyzed Buzzmac.jp page load time and found that the first response time was 836 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

buzzmac.jp performance score

0

Network Requests Diagram

buzzmac.jp

836 ms

gsearch.css

17 ms

main.css

326 ms

jsapi

30 ms

jquery-1.4.2.min.js

484 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 65% of them (71 requests) were addressed to the original Buzzmac.jp, 6% (6 requests) were made to Pagead2.googlesyndication.com and 5% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Buzzmac.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 386.9 kB (57%)

Content Size

678.4 kB

After Optimization

291.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Buzzmac.jp main page is 678.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. 60% of websites need less resources to load. Javascripts take 318.1 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 64.0 kB

  • Original 73.7 kB
  • After minification 69.5 kB
  • After compression 9.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 64.0 kB or 87% of the original size.

Image Optimization

-19%

Potential reduce by 35.9 kB

  • Original 190.3 kB
  • After minification 154.4 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, Buzz Mac needs image optimization as it can save up to 35.9 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 205.1 kB

  • Original 318.1 kB
  • After minification 306.0 kB
  • After compression 112.9 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 205.1 kB or 64% of the original size.

CSS Optimization

-85%

Potential reduce by 81.9 kB

  • Original 96.5 kB
  • After minification 70.8 kB
  • After compression 14.5 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. Buzzmac.jp needs all CSS files to be minified and compressed as it can save up to 81.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (36%)

Requests Now

106

After Optimization

68

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Buzz Mac. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

buzzmac.jp

buzzmac.jp

836 ms

gsearch.css

gsearch.css

17 ms

main.css

main.css

326 ms

jsapi

jsapi

30 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

484 ms

jquery.scrollTo.js

jquery.scrollTo.js

333 ms

reflection.js

reflection.js

334 ms

corner.js

corner.js

333 ms

ddsmoothmenu-1.4.js

ddsmoothmenu-1.4.js

360 ms

pc.js.ycomp.js

pc.js.ycomp.js

938 ms

widgets.js

widgets.js

87 ms

google_service.js

google_service.js

21 ms

show_ads.js

show_ads.js

29 ms

google_ads.js

google_ads.js

18 ms

ga.js

ga.js

31 ms

header_bg2.png

header_bg2.png

320 ms

120_60_03.gif

120_60_03.gif

403 ms

show

show

24 ms

logo.png

logo.png

321 ms

verButtonImage.png

verButtonImage.png

354 ms

icon_28x28.png

icon_28x28.png

355 ms

preview1_thumb.png

preview1_thumb.png

355 ms

download_button_s.gif

download_button_s.gif

360 ms

icon_28x28.png

icon_28x28.png

675 ms

preview1_thumb.png

preview1_thumb.png

838 ms

icon_28x28.png

icon_28x28.png

691 ms

preview1_thumb.png

preview1_thumb.png

692 ms

icon_28x28.png

icon_28x28.png

723 ms

preview1_thumb.png

preview1_thumb.png

838 ms

icon_28x28.png

icon_28x28.png

944 ms

preview1_thumb.png

preview1_thumb.png

1160 ms

icon_28x28.png

icon_28x28.png

1001 ms

preview1_thumb.png

preview1_thumb.png

1002 ms

icon_28x28.png

icon_28x28.png

1151 ms

preview1_thumb.png

preview1_thumb.png

1320 ms

icon_28x28.png

icon_28x28.png

1248 ms

preview1_thumb.png

preview1_thumb.png

1306 ms

icon_28x28.png

icon_28x28.png

1360 ms

preview1_thumb.png

preview1_thumb.png

1479 ms

icon_28x28.png

icon_28x28.png

1478 ms

preview1_thumb.png

preview1_thumb.png

1780 ms

icon_28x28.png

icon_28x28.png

1629 ms

preview1_thumb.png

preview1_thumb.png

1852 ms

icon_28x28.png

icon_28x28.png

1663 ms

preview1_thumb.png

preview1_thumb.png

1795 ms

icon_28x28.png

icon_28x28.png

1836 ms

new007_02.gif

new007_02.gif

1946 ms

preview1_thumb.png

preview1_thumb.png

1982 ms

icon_28x28.png

icon_28x28.png

2102 ms

preview1_thumb.png

preview1_thumb.png

2255 ms

icon_28x28.png

icon_28x28.png

2173 ms

preview1_thumb.png

preview1_thumb.png

2374 ms

icon_28x28.png

icon_28x28.png

2272 ms

show

show

15 ms

ads

ads

77 ms

39157_417.jpg

39157_417.jpg

233 ms

__utm.gif

__utm.gif

18 ms

zrt_lookup.html

zrt_lookup.html

102 ms

show_ads_impl.js

show_ads_impl.js

54 ms

timeline.1b43d11859b7663a2225b885f87704a5.js

timeline.1b43d11859b7663a2225b885f87704a5.js

131 ms

ads

ads

271 ms

osd.js

osd.js

17 ms

ads

ads

222 ms

preview1_thumb.png

preview1_thumb.png

2211 ms

icon_28x28.png

icon_28x28.png

2110 ms

syndication

syndication

93 ms

572313210426884096

572313210426884096

147 ms

preview1_thumb.png

preview1_thumb.png

2132 ms

icon_28x28.png

icon_28x28.png

2211 ms

preview1_thumb.png

preview1_thumb.png

2406 ms

preview1_thumb_i.png

preview1_thumb_i.png

2338 ms

1394256549187024080

1394256549187024080

35 ms

abg.js

abg.js

36 ms

m_js_controller.js

m_js_controller.js

47 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

46 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

61 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

113 ms

css

css

126 ms

s

s

34 ms

x_button_blue2.png

x_button_blue2.png

34 ms

logo_twitter_normal.png

logo_twitter_normal.png

320 ms

favicon

favicon

85 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

51 ms

preview1_thumb_i.png

preview1_thumb_i.png

2070 ms

preview1_thumb_i.png

preview1_thumb_i.png

2382 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

70 ms

preview1_thumb_i.png

preview1_thumb_i.png

2473 ms

preview1_thumb_i.png

preview1_thumb_i.png

2529 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

65 ms

preview1_thumb_i.png

preview1_thumb_i.png

2417 ms

preview1_thumb_i.png

preview1_thumb_i.png

2475 ms

preview1_thumb_i.png

preview1_thumb_i.png

2292 ms

jot

jot

27 ms

preview1_thumb_i.png

preview1_thumb_i.png

2417 ms

AppDamBanner255.png

AppDamBanner255.png

2546 ms

icon_28x28.png

icon_28x28.png

2416 ms

icon_28x28.png

icon_28x28.png

2412 ms

icon_28x28.png

icon_28x28.png

2400 ms

icon_28x28.png

icon_28x28.png

2557 ms

icon_28x28.png

icon_28x28.png

2546 ms

icon_28x28.png

icon_28x28.png

2511 ms

icon_28x28.png

icon_28x28.png

2464 ms

icon_28x28.png

icon_28x28.png

2504 ms

icon_28x28.png

icon_28x28.png

2379 ms

list_bg.png

list_bg.png

2520 ms

activeview

activeview

14 ms

activeview

activeview

27 ms

down.gif

down.gif

2444 ms

right.gif

right.gif

2434 ms

SEO Factors

buzzmac.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buzzmac.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Buzzmac.jp 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.

Social Sharing Optimization

buzzmac.jp

Open Graph description is not detected on the main page of Buzz Mac. 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: