Tools & Wizards About Us
tokyorakuichirakuza.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tokyorakuichirakuza.jp

東京楽市楽座・アキバ系クラウドファンディング

Page Load Speed

4.2 sec in total

First Response

586 ms

Resources Loaded

3.2 sec

Page Rendered

351 ms

tokyorakuichirakuza.jp screenshot

About Website

Welcome to tokyorakuichirakuza.jp homepage info - get ready to check Tokyorakuichirakuza best content for Japan right away, or after learning these important things about tokyorakuichirakuza.jp

「実現したい！」を支援する応援サイト

Visit tokyorakuichirakuza.jp

Key Findings

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

Performance Metrics

tokyorakuichirakuza.jp performance score

0

Network Requests Diagram

tokyorakuichirakuza.jp

586 ms

prepare.css

346 ms

clearfix.css

372 ms

layout.css

382 ms

contents.css

572 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 44% of them (20 requests) were addressed to the original Tokyorakuichirakuza.jp, 22% (10 requests) were made to Static.xx.fbcdn.net and 18% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Tokyorakuichirakuza.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 148.3 kB (41%)

Content Size

361.6 kB

After Optimization

213.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-72%

Potential reduce by 12.6 kB

  • Original 17.4 kB
  • After minification 16.1 kB
  • After compression 4.8 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 12.6 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 1.8 kB

  • Original 148.4 kB
  • After minification 146.5 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. Tokyorakuichirakuza images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 102.2 kB

  • Original 159.1 kB
  • After minification 154.6 kB
  • After compression 56.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 102.2 kB or 64% of the original size.

CSS Optimization

-86%

Potential reduce by 31.6 kB

  • Original 36.8 kB
  • After minification 26.0 kB
  • After compression 5.1 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. Tokyorakuichirakuza.jp needs all CSS files to be minified and compressed as it can save up to 31.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (55%)

Requests Now

44

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tokyorakuichirakuza.jp

tokyorakuichirakuza.jp

586 ms

prepare.css

prepare.css

346 ms

clearfix.css

clearfix.css

372 ms

layout.css

layout.css

382 ms

contents.css

contents.css

572 ms

jquery.js

jquery.js

1004 ms

yuga.js

yuga.js

426 ms

jquery.adjust_height.js

jquery.adjust_height.js

714 ms

analytics.js

analytics.js

29 ms

all.js

all.js

32 ms

bg_header.jpg

bg_header.jpg

193 ms

591 ms

logo.jpg

logo.jpg

554 ms

bg_header_btn.png

bg_header_btn.png

381 ms

ornament_btn.png

ornament_btn.png

387 ms

main_image.jpg

main_image.jpg

1564 ms

title_683.png

title_683.png

553 ms

title_260.png

title_260.png

749 ms

title_side_260.png

title_side_260.png

800 ms

bg_footer.jpg

bg_footer.jpg

911 ms

icon_twitter.png

icon_twitter.png

922 ms

icon_facebook.png

icon_facebook.png

956 ms

likebox.php

likebox.php

435 ms

collect

collect

38 ms

28 ms

xd_arbiter.php

xd_arbiter.php

27 ms

xd_arbiter.php

xd_arbiter.php

32 ms

ebiMDO3r-8l.css

ebiMDO3r-8l.css

25 ms

jGc-59L_9lo.css

jGc-59L_9lo.css

32 ms

TKuNj0xVh4A.js

TKuNj0xVh4A.js

43 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

62 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

41 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

42 ms

10481451_1434463320159702_4562859198980843200_n.png

10481451_1434463320159702_4562859198980843200_n.png

93 ms

10487295_1434463413493026_4563004045828042948_n.png

10487295_1434463413493026_4563004045828042948_n.png

17 ms

10464006_1469839706587717_2180979914654023487_n.jpg

10464006_1469839706587717_2180979914654023487_n.jpg

16 ms

534594_126907437463084_199517850_n.jpg

534594_126907437463084_199517850_n.jpg

17 ms

12316172_925958360822735_1795039725941820856_n.jpg

12316172_925958360822735_1795039725941820856_n.jpg

123 ms

10565237_784546428276706_3583837031387057039_n.jpg

10565237_784546428276706_3583837031387057039_n.jpg

87 ms

551802_313612338713027_246585790_n.jpg

551802_313612338713027_246585790_n.jpg

42 ms

10277302_1374783449475887_7456872649130295168_n.jpg

10277302_1374783449475887_7456872649130295168_n.jpg

17 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

8 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

8 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

4 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

9 ms

SEO Factors

tokyorakuichirakuza.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

tokyorakuichirakuza.jp

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