Tools & Wizards About Us
fannta.jugem.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fannta.jugem.jp

無果汁炭酸飲料

Page Load Speed

7.4 sec in total

First Response

1.3 sec

Resources Loaded

5.1 sec

Page Rendered

1 sec

fannta.jugem.jp screenshot

About Website

Click here to check amazing Fannta Jugem content for Japan. Otherwise, check out these important facts you probably never knew about fannta.jugem.jp

超暇人駄目星が書くきまぐれほぼ毎日日記。とか言ってたら、最近は６のつく日にしか更新しなくなってきた。…別に炭酸飲料はあんまり関係ないらしい。

Visit fannta.jugem.jp

Key Findings

We analyzed Fannta.jugem.jp page load time and found that the first response time was 1.3 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

fannta.jugem.jp performance score

0

Network Requests Diagram

fannta.jugem.jp

1274 ms

jm_style.css

1016 ms

style.css

6 ms

cookie.js

358 ms

script.js

5 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 11% of them (9 requests) were addressed to the original Fannta.jugem.jp, 24% (19 requests) were made to Imaging.jugem.jp and 13% (10 requests) were made to Plugins.mixi.jp. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Img-cdn.jg.jugem.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 194.1 kB (15%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fannta.jugem.jp main page is 1.3 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 78.5 kB

  • Original 99.8 kB
  • After minification 91.6 kB
  • After compression 21.4 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 78.5 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 36.9 kB

  • Original 1.1 MB
  • After minification 1.0 MB

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. Fannta Jugem images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 71.5 kB

  • Original 127.4 kB
  • After minification 121.7 kB
  • After compression 55.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 71.5 kB or 56% of the original size.

CSS Optimization

-80%

Potential reduce by 7.3 kB

  • Original 9.1 kB
  • After minification 8.3 kB
  • After compression 1.8 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. Fannta.jugem.jp needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (47%)

Requests Now

70

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fannta Jugem. 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 as a result speed up the page load time.

Network Requests Diagram

fannta.jugem.jp

fannta.jugem.jp

1274 ms

jm_style.css

jm_style.css

1016 ms

style.css

style.css

6 ms

cookie.js

cookie.js

358 ms

script.js

script.js

5 ms

AdLantisLoader.js

AdLantisLoader.js

475 ms

widget.js

widget.js

58 ms

widgets.js

widgets.js

5 ms

share.js

share.js

294 ms

cookie.js

cookie.js

3 ms

analytics.js

analytics.js

37 ms

61XF13WMY1L._SL160_.jpg

61XF13WMY1L._SL160_.jpg

34 ms

20100831_622382.jpg

20100831_622382.jpg

2522 ms

fannta.jugem.jp

fannta.jugem.jp

754 ms

powered_07b.gif

powered_07b.gif

186 ms

entrytop.gif

entrytop.gif

206 ms

20100820_619837.jpg

20100820_619837.jpg

445 ms

20100820_619834.jpg

20100820_619834.jpg

1518 ms

20100706_609433.jpg

20100706_609433.jpg

865 ms

20100625_606706.jpg

20100625_606706.jpg

3077 ms

bg_header.gif

bg_header.gif

7 ms

titlebg.jpg

titlebg.jpg

383 ms

linkbg.gif

linkbg.gif

382 ms

logo_jugem.gif

logo_jugem.gif

27 ms

bg_dot.gif

bg_dot.gif

27 ms

logo_pepabo.gif

logo_pepabo.gif

27 ms

collect

collect

29 ms

entrymiddle.gif

entrymiddle.gif

328 ms

jg_ads_init_inactive.js

jg_ads_init_inactive.js

3 ms

jg_ads_inactive.js

jg_ads_inactive.js

2 ms

show_ads.js

show_ads.js

5 ms

show_ads_impl.js

show_ads_impl.js

61 ms

jg_ads_init_display2.js

jg_ads_init_display2.js

4 ms

collect

collect

117 ms

jg_ads_display2.js

jg_ads_display2.js

5 ms

jg_ads_init_bottom_entry.js

jg_ads_init_bottom_entry.js

33 ms

jg_ads_bottom_entry2.js

jg_ads_bottom_entry2.js

33 ms

ads

ads

237 ms

osd.js

osd.js

70 ms

share_button.html

share_button.html

365 ms

share_button.html

share_button.html

366 ms

share_button.html

share_button.html

364 ms

share_button.html

share_button.html

365 ms

share_button.html

share_button.html

363 ms

share_button.html

share_button.html

361 ms

share_button.html

share_button.html

650 ms

share_button.html

share_button.html

656 ms

share_button.html

share_button.html

659 ms

share_button.html

share_button.html

655 ms

powered_07b.gif

powered_07b.gif

20 ms

ads

ads

198 ms

sdk.js

sdk.js

46 ms

adlantis.www.js

adlantis.www.js

189 ms

swfobject.js

swfobject.js

349 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

80 ms

entrytop.gif

entrytop.gif

18 ms

ads

ads

206 ms

174 ms

xd_arbiter.php

xd_arbiter.php

43 ms

xd_arbiter.php

xd_arbiter.php

113 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

61 ms

entrybottom.gif

entrybottom.gif

4 ms

titlebg.jpg

titlebg.jpg

125 ms

entrymiddle.gif

entrymiddle.gif

44 ms

linkbg.gif

linkbg.gif

11 ms

css

css

68 ms

m_js_controller.js

m_js_controller.js

31 ms

abg.js

abg.js

39 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

23 ms

s

s

14 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

53 ms

x_button_blue2.png

x_button_blue2.png

5 ms

bt_check_6.png

bt_check_6.png

9 ms

load_script

load_script

398 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

9 ms

PuwvqkdbcqU-fCZ9Ed-b7S3USBnSvpkopQaUR-2r7iU.ttf

PuwvqkdbcqU-fCZ9Ed-b7S3USBnSvpkopQaUR-2r7iU.ttf

34 ms

jot.html

jot.html

2 ms

a75869f2bec919121cee72bed286150c2eccce04.png

a75869f2bec919121cee72bed286150c2eccce04.png

601 ms

activeview

activeview

13 ms

SEO Factors

fannta.jugem.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fannta.jugem.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Fannta.jugem.jp main page’s claimed encoding is euc-jp. 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.

Social Sharing Optimization

fannta.jugem.jp

Open Graph data is detected on the main page of Fannta Jugem. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: