Tools & Wizards About Us
tamarokuto.or.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tamarokuto.or.jp

多摩六都科学館―プラネタリウムと観察・実験・工作でDo！サイエンス （東京都西東京市）

Page Load Speed

11.6 sec in total

First Response

1.1 sec

Resources Loaded

10.3 sec

Page Rendered

196 ms

tamarokuto.or.jp screenshot

About Website

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

多摩六都科学館は、世界一に認定されたプラネタリウムと、観察・実験・工作が楽しめる体験型ミュージアムです。 東京都西東京市にあり、小平市、東村山市、清瀬市、東久留米市、西東京市の５市で運営しています。

Visit tamarokuto.or.jp

Key Findings

We analyzed Tamarokuto.or.jp page load time and found that the first response time was 1.1 sec and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

tamarokuto.or.jp performance score

0

Network Requests Diagram

www.tamarokuto.or.jp

1145 ms

jquery-1.6.2.min.js

1282 ms

tabs.js

321 ms

basic.js

640 ms

rollover.js

336 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 97% of them (94 requests) were addressed to the original Tamarokuto.or.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Tamarokuto.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 321.6 kB (26%)

Content Size

1.2 MB

After Optimization

917.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 24.5 kB

  • Original 31.5 kB
  • After minification 26.1 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 5.4 kB, which is 17% 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 24.5 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 35.8 kB

  • Original 855.6 kB
  • After minification 819.8 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. Tamarokuto images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 156.8 kB

  • Original 228.8 kB
  • After minification 195.8 kB
  • After compression 72.0 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 156.8 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 104.5 kB

  • Original 122.9 kB
  • After minification 93.5 kB
  • After compression 18.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. Tamarokuto.or.jp needs all CSS files to be minified and compressed as it can save up to 104.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (31%)

Requests Now

96

After Optimization

66

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.tamarokuto.or.jp

www.tamarokuto.or.jp

1145 ms

jquery-1.6.2.min.js

jquery-1.6.2.min.js

1282 ms

tabs.js

tabs.js

321 ms

basic.js

basic.js

640 ms

rollover.js

rollover.js

336 ms

jquery.easing.1.3.min.js

jquery.easing.1.3.min.js

671 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

641 ms

jquery.carouFredSel-6.2.1.js

jquery.carouFredSel-6.2.1.js

1494 ms

jquery.sliderkit.1.9.2.pack.js

jquery.sliderkit.1.9.2.pack.js

1025 ms

sliderkit-core.css

sliderkit-core.css

962 ms

sliderkit-demos.css

sliderkit-demos.css

1723 ms

rokuto.css

rokuto.css

1011 ms

tabs.css

tabs.css

1302 ms

floormap_b1_1.gif

floormap_b1_1.gif

763 ms

floormap_b1_2.gif

floormap_b1_2.gif

881 ms

floormap_b1_3.gif

floormap_b1_3.gif

951 ms

floormap_b1_4.gif

floormap_b1_4.gif

960 ms

floormap_b1_5.gif

floormap_b1_5.gif

1301 ms

floormap_b1_6.gif

floormap_b1_6.gif

1390 ms

reset.css

reset.css

993 ms

default.css

default.css

1543 ms

cafe.css

cafe.css

1195 ms

shop.css

shop.css

1184 ms

access.css

access.css

1450 ms

guide.css

guide.css

1708 ms

group.css

group.css

1519 ms

enkaku.css

enkaku.css

1538 ms

droppy.css

droppy.css

1582 ms

event.css

event.css

1945 ms

event_ctg.css

event_ctg.css

2045 ms

qanda.css

qanda.css

1860 ms

news.css

news.css

1866 ms

floorguide.css

floorguide.css

2224 ms

planetarium.css

planetarium.css

2037 ms

ts.css

ts.css

2201 ms

ftr.css

ftr.css

2210 ms

add-css.css

add-css.css

2281 ms

hdr_bg.gif

hdr_bg.gif

327 ms

hdr_logo.png

hdr_logo.png

666 ms

hdr_btn_mail.gif

hdr_btn_mail.gif

352 ms

hdr_btn_tw.gif

hdr_btn_tw.gif

352 ms

hdr_btn_fb.gif

hdr_btn_fb.gif

352 ms

navi_inf_off.jpg

navi_inf_off.jpg

529 ms

navi_cal_off.jpg

navi_cal_off.jpg

828 ms

navi_pla_off.jpg

navi_pla_off.jpg

828 ms

navi_gui_off.jpg

navi_gui_off.jpg

850 ms

navi_acs_off.jpg

navi_acs_off.jpg

865 ms

navi_blg_off.jpg

navi_blg_off.jpg

1071 ms

bg.gif

bg.gif

981 ms

main_img_bg.gif

main_img_bg.gif

1180 ms

main_img01.jpg

main_img01.jpg

2947 ms

main_img02.jpg

main_img02.jpg

2834 ms

main_img03.jpg

main_img03.jpg

2830 ms

slide_tab_bg.gif

slide_tab_bg.gif

1331 ms

tab_show_off.gif

tab_show_off.gif

1574 ms

tab_program.gif

tab_program.gif

1659 ms

s_20160131072204.jpg

s_20160131072204.jpg

1826 ms

s_20160120100543.jpg

s_20160120100543.jpg

2277 ms

s_20160120120240.jpg

s_20160120120240.jpg

2225 ms

s_20160305120521.jpg

s_20160305120521.jpg

2562 ms

s_20160202104456.jpg

s_20160202104456.jpg

2925 ms

s_20160131055554.jpg

s_20160131055554.jpg

2758 ms

s_20160301124614.jpg

s_20160301124614.jpg

3296 ms

arrows-h-btn.png

arrows-h-btn.png

3079 ms

info_back.gif

info_back.gif

3304 ms

bdr.gif

bdr.gif

3183 ms

tab08.png

tab08.png

3279 ms

tab02.png

tab02.png

3297 ms

tab04.png

tab04.png

3442 ms

tab03.png

tab03.png

3520 ms

tab05.png

tab05.png

3613 ms

tab01.png

tab01.png

3616 ms

widgets.js

widgets.js

137 ms

tab07.png

tab07.png

3599 ms

ga.js

ga.js

14 ms

__utm.gif

__utm.gif

12 ms

bot_list.gif

bot_list.gif

3338 ms

stit_report.gif

stit_report.gif

3434 ms

stit_dot.gif

stit_dot.gif

3511 ms

icon_news.gif

icon_news.gif

3606 ms

spacer.gif

spacer.gif

3442 ms

top.gif

top.gif

3327 ms

pegaroku_twt.png

pegaroku_twt.png

3507 ms

bot_shop01_off.png

bot_shop01_off.png

3529 ms

bot_shop02_off.png

bot_shop02_off.png

3345 ms

btn_dl_off.png

btn_dl_off.png

3587 ms

20160303013236.gif

20160303013236.gif

3322 ms

38.gif

38.gif

3397 ms

20160127034623.jpg

20160127034623.jpg

3540 ms

copyright.png

copyright.png

3324 ms

side_o.png

side_o.png

3088 ms

side_p.png

side_p.png

3030 ms

ftr_home.png

ftr_home.png

2944 ms

ftr_arr.png

ftr_arr.png

2592 ms

tab08_o.png

tab08_o.png

2695 ms

icon_lec.gif

icon_lec.gif

2417 ms

main_slide_bt.png

main_slide_bt.png

178 ms

SEO Factors

tamarokuto.or.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 Tamarokuto.or.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 Tamarokuto.or.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

tamarokuto.or.jp

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