Analyze

dff.jp: sumabo クリックで救える命がある。 | dff.jp

dff.jpは、日本最大の「クリック募金」サイトです。募金ボタンをワンクリックするだけで無料で1円募金できる「クリック募金」にご協力ください。東日本大震災復興などを支援する「アンケート募金」も実施中です。

Page load speed analysis

  • 53/100

    Normal result
  • 6

    Successful tests
  • 2

    Failed tests
  • First response

    309 ms

  • Resources loaded

    3 sec

  • Page rendered

    193 ms

  • Total page load time

    3.5 sec

Click here to check amazing Dff content for Japan. Otherwise, check out these important facts you probably never knew about dff.jp

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

Page optimization

  • HTML 92.7 kB
    Images 566.6 kB
    Javascripts 301.7 kB
    CSS 39.0 kB

    In fact, the total size of Dff.jp main page is 999.9 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. 65% of websites need less resources to load. Images take 566.6 kB which makes up the majority of the site volume.

    • Original 92.7 kB
    • After minification 35.4 kB
    • After compression 9.7 kB

    HTML optimization

    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. This page needs HTML code to be minified as it can gain 57.3 kB, which is 62% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 82.9 kB or 90% of the original size.

    • Original 566.6 kB
    • After optimization 508.2 kB

    Image optimization

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

    • Original 301.7 kB
    • After minification 284.4 kB
    • After compression 101.8 kB

    JavaScript optimization

    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 200.0 kB or 66% of the original size.

    • Original 39.0 kB
    • After minification 28.5 kB
    • After compression 6.3 kB

    CSS optimization

    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. Dff.jp needs all CSS files to be minified and compressed as it can save up to 32.7 kB or 84% of the original size.

Network requests diagram

  • dff.jp
  • www.dff.jp
  • common_main.css
  • main.css
  • jquery_sidr.css
  • jquery-1.9.1.min.js
  • common.js
  • jquery.sidr.min.js
  • snscoop.js
  • sdk.js
  • jquery.cookie.js
  • jquery.layerBoard.js
  • top.js
  • swfobject.js
  • adsbygoogle.js
  • ga.js
  • logo_dff_b_151116.gif
  • logo_fb_b_r.gif
  • txt_sumabo_supporter_151116.gif
  • btn_menu_sp.gif
  • btn_fb_newregist_sp.gif
  • btn_newregist_sp.gif
  • btn_login_sumabo_sp.gif
  • btn_login_facebook_sp.gif
  • txt_share_milestone.gif
  • txt_lead.gif
  • btn_beginner_r.gif
  • txt_lead_sp.gif
  • btn_beginner_sp_r.gif
  • btn_close.gif
  • img_welcome.gif
  • h2_01.gif
  • h2_02.gif
  • bnr_torecruit_r.gif
  • btn_cosmo_r.jpg
  • btn_jx_2015_r.gif
  • btn_canon_2016_r.jpg
  • btn_takara_2016_02_r.gif
  • img_list_bg.gif
  • logo_fb_b_r.gif
  • logo_tw_b_r.gif
  • img_list_bg_02.gif
  • btn_fb_newregist_r.gif
  • btn_newregist_r.gif
  • btn_takasago_r.jpg
  • btn_jfe_r.jpg
  • btn_jx_r.jpg
  • btn_sbfoods_r.jpg
  • btn_csrengage_r.gif
  • txt_method_01.gif
  • btn_method_r.gif
  • txt_closed_01.gif
  • __utm.gif
  • ca-pub-2802189302858660.js
  • zrt_lookup.html
  • show_ads_impl.js
  • widgets.js
  • xd_arbiter.php
  • xd_arbiter.php
  • timeline.1b43d11859b7663a2225b885f87704a5.js
  • ads
  • expansion_embed.js
  • osd.js
  • syndication
  • 540746454969503744
  • 540746454969503744
  • click_counter.json
  • btn_closed_r.gif
  • btn_login_top_sumabo.gif
  • btn_login_top_fb.gif
  • btn_sponsor_r.gif
  • icn_blanklink_y.gif
  • xd_arbiter.php
  • icn_triangle_01.gif
  • 17482072598122414215
  • abg.js
  • m_js_controller.js
  • googlelogo_color_112x36dp.png
  • x_button_blue2.svg
  • s
  • MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
  • 2663.png
  • 2660.png
  • 2665.png
  • 1f496.png
  • 1f493.png
  • 2763.png
  • 1f495.png
  • 1f498.png
  • 260e.png
  • 1f344.png
  • 2764.png
  • 1f42f.png
  • 1f4a7.png
  • 1f375.png
  • 1f4a2.png
  • 1f4a5.png
  • 2620.png
  • 1f480.png
  • 1f436.png
  • 1f440.png
  • 1f47f.png
  • timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
  • timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
  • fad9a495cbdebe0c7efbd94a0ced78ca_normal.png
  • b8b52b6acfb8b7c7cc52a0ad6d14a8ac_normal.jpeg
  • x6obFkHI_normal.jpg
  • ikakowai2_normal.jpeg
  • 36e5gm1ndcnrhd2g35bx_normal.jpeg
  • LSphXuBv_normal.jpg
  • tokyobot1981_normal.jpg
  • soleil_normal.jpg
  • ______normal.jpg
  • Su4kdIA2_normal.jpeg
  • ILs6p5ve_normal.jpeg
  • Kn9T1a2W_normal.jpg
  • tokyoboy1981_normal.jpg
  • 820487bf36db099cafa9d9739be8fd42_normal.jpeg
  • 000061-600x401_normal.jpg
  • donate1209_normal.jpg
  • rokkakubashi01_normal.JPG
  • cocolog_oekaki_2011_07_14_23_12_normal.png
  • T3Q3Hth5_normal.png
  • 2388a9e10b35fb30259451e5435775a6_normal.png
  • timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
  • timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
  • jot.html

Our browser made a total of 128 requests to load all elements on the main page. We found that 44% of them (56 requests) were addressed to the original Dff.jp, 16% (21 requests) were made to Abs.twimg.com and 16% (20 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Dff.jp.

Additional info on dff.jp

Requests

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

22

Javascripts

89

Images

7

CSS

8

AJAX

126

All

Possible request optimization

1

Javascripts

70

Images

1

CSS

8

AJAX

46

Optimized

80

All

Normal result

Redirects

As for redirects, our browser was forwarded to http://www.dff.jp/ before it reached this domain.

IP address

This IP address is dedicated to Dff.jp. This is the best domain hosting practice .

Normal result

IP Trace

dff.jp

54.238.63.155

54.248.116.129

DNS records

Type Host Target/ip TTL Other
A

dff.jp

54.238.63.155 42
NS

dff.jp

ns-1910.awsdns-46.co.uk 86400
NS

dff.jp

ns-468.awsdns-58.com 86400
NS

dff.jp

ns-600.awsdns-11.net 86400
NS

dff.jp

ns-1229.awsdns-25.org 86400

Language and encoding

Good result

Language

JA ja language flag

Detected

JA ja language flag

Claimed

Encoding

UTF-8

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dff.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 Dff.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.

HTTPS certificate

SSL Certificate

Dff.jp has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Poor result

Visitor World Map

Country of origin for 99.9% of all visits is Japan. It’s good for Dff.jp that their server is also located in Japan, as that enables the majority of their visitors to benefit from a much faster page load time.

Good result

Normal result

Social Sharing Optimization

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

dff.jp

Share this report in social media

Analyze another website

Analyze