Tools & Wizards About Us
f01.ototoy.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

f01.ototoy.jp

OTOTOY - Hi-res music store, reviews and interviews

Page Load Speed

12.9 sec in total

First Response

576 ms

Resources Loaded

11.3 sec

Page Rendered

1 sec

f01.ototoy.jp screenshot

About Website

Welcome to f01.ototoy.jp homepage info - get ready to check F 01 OTOTOY best content for Japan right away, or after learning these important things about f01.ototoy.jp

Hi-res music store, reviews and interviews

Visit f01.ototoy.jp

Key Findings

We analyzed F01.ototoy.jp page load time and found that the first response time was 576 ms and then it took 12.3 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

f01.ototoy.jp performance score

0

Network Requests Diagram

f01.ototoy.jp

576 ms

4056 ms

jquery.min.js

37 ms

jquery-ui.min.js

68 ms

jquery.balloon.min.js

512 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 35% of them (28 requests) were addressed to the original F01.ototoy.jp, 43% (34 requests) were made to Imgs.ototoy.jp and 5% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain F01.ototoy.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 373.1 kB (46%)

Content Size

802.6 kB

After Optimization

429.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 101.8 kB

  • Original 122.6 kB
  • After minification 109.1 kB
  • After compression 20.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. This page needs HTML code to be minified as it can gain 13.5 kB, which is 11% 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 101.8 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 11.1 kB

  • Original 311.8 kB
  • After minification 300.7 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. F 01 OTOTOY images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 148.1 kB

  • Original 235.6 kB
  • After minification 199.1 kB
  • After compression 87.6 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 148.1 kB or 63% of the original size.

CSS Optimization

-85%

Potential reduce by 112.2 kB

  • Original 132.6 kB
  • After minification 108.3 kB
  • After compression 20.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. F01.ototoy.jp needs all CSS files to be minified and compressed as it can save up to 112.2 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

74

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

f01.ototoy.jp

f01.ototoy.jp

576 ms

4056 ms

jquery.min.js

jquery.min.js

37 ms

jquery-ui.min.js

jquery-ui.min.js

68 ms

jquery.balloon.min.js

jquery.balloon.min.js

512 ms

audio.min.js

audio.min.js

779 ms

freetile.min.js

freetile.min.js

554 ms

jquery.mmenu.min.all.js

jquery.mmenu.min.all.js

802 ms

jquery.hoverIntent.min.js

jquery.hoverIntent.min.js

375 ms

jquery.mb.flipText.js

jquery.mb.flipText.js

906 ms

mbExtruder.js

mbExtruder.js

1217 ms

mbExtruder.build.ototoy.js

mbExtruder.build.ototoy.js

901 ms

mbExtruder.css

mbExtruder.css

1170 ms

mbExtruder.ototoy.css

mbExtruder.ototoy.css

1126 ms

ototoy.util.js

ototoy.util.js

1356 ms

jquery.mmenu.all.css

jquery.mmenu.all.css

1788 ms

font-awesome.css

font-awesome.css

6 ms

columns.css

columns.css

1624 ms

ototoy.css

ototoy.css

1872 ms

jquery.bxslider.css

jquery.bxslider.css

1576 ms

jquery.bxslider.js

jquery.bxslider.js

2153 ms

jquery.newsticker.js

jquery.newsticker.js

1720 ms

css

css

24 ms

UW1.jpg

UW1.jpg

2355 ms

ototoy_logo.png

ototoy_logo.png

508 ms

google_play_newsstand_s.png

google_play_newsstand_s.png

358 ms

noimage.png

noimage.png

527 ms

App_Store_Badge_US-UK_135x40.svg

App_Store_Badge_US-UK_135x40.svg

579 ms

Get_it_on_Google_play.svg

Get_it_on_Google_play.svg

583 ms

org1.jpg

org1.jpg

2291 ms

_8109343_.jpg

_8109343_.jpg

2136 ms

top.jpg

top.jpg

2638 ms

IMG_02.jpg

IMG_02.jpg

2622 ms

korg1.jpg

korg1.jpg

2665 ms

main01.jpg

main01.jpg

3071 ms

0

0

2677 ms

0

0

2680 ms

all.js

all.js

93 ms

analytics.js

analytics.js

93 ms

wish.php

wish.php

395 ms

get_login.php

get_login.php

712 ms

extruder_blank.png

extruder_blank.png

453 ms

bx_loader.gif

bx_loader.gif

803 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

52 ms

7xkFOeTxxO1GMC1suOUYWVRF2Zew_pgh0xNsNWxurqo.ttf

7xkFOeTxxO1GMC1suOUYWVRF2Zew_pgh0xNsNWxurqo.ttf

53 ms

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

53 ms

linkid.js

linkid.js

38 ms

ec.js

ec.js

39 ms

222 ms

xd_arbiter.php

xd_arbiter.php

121 ms

xd_arbiter.php

xd_arbiter.php

152 ms

collect

collect

13 ms

collect

collect

94 ms

P5.jpg

P5.jpg

611 ms

_8101008.jpg

_8101008.jpg

587 ms

top2.jpg

top2.jpg

649 ms

_DSC0058.jpg

_DSC0058.jpg

497 ms

top1.jpg

top1.jpg

504 ms

02.jpg

02.jpg

1032 ms

top.jpg

top.jpg

1074 ms

web-0034.jpg

web-0034.jpg

1161 ms

top.jpg

top.jpg

1185 ms

list.jpg

list.jpg

1798 ms

00106888.1454996039.676_180.jpg

00106888.1454996039.676_180.jpg

1036 ms

00106888.1429178689.5093_180.jpg

00106888.1429178689.5093_180.jpg

1371 ms

00013828.1393313212.8447_180.jpg

00013828.1393313212.8447_180.jpg

1408 ms

00098141.1457941225.6994_180.jpg

00098141.1457941225.6994_180.jpg

1590 ms

00013828.1445304149.1383_180.jpg

00013828.1445304149.1383_180.jpg

1656 ms

0000012226.1300881652_180.jpg

0000012226.1300881652_180.jpg

1546 ms

top2.jpg

top2.jpg

1776 ms

korg1.jpg

korg1.jpg

1816 ms

top.jpg

top.jpg

1937 ms

P5.jpg

P5.jpg

2003 ms

_8101008.jpg

_8101008.jpg

2091 ms

main01.jpg

main01.jpg

2252 ms

hatakeyama_01.jpg

hatakeyama_01.jpg

2241 ms

sasakura_03.jpg

sasakura_03.jpg

2248 ms

02.jpg

02.jpg

2372 ms

xd_arbiter.php

xd_arbiter.php

9 ms

SEO Factors

f01.ototoy.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 F01.ototoy.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 F01.ototoy.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

f01.ototoy.jp

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