8.9 sec in total
1.6 sec
6.7 sec
667 ms
Visit otonami.com now to see the best up-to-date Otonami content for Japan and also check out these interesting facts you probably never knew about otonami.com
音が生まれる。波にのって人に伝わる。つながる。そして人は音楽を奏でる。音楽を愛する全ての人達へ。
Visit otonami.comWe analyzed Otonami.com page load time and found that the first response time was 1.6 sec and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
otonami.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value7.2 s
5/100
25%
Value10.1 s
9/100
10%
Value40 ms
100/100
30%
Value0.311
38/100
15%
Value7.8 s
44/100
10%
1563 ms
662 ms
511 ms
1156 ms
726 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that all of those requests were addressed to Otonami.com and no external sources were called. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Otonami.com.
Page size can be reduced by 342.4 kB (15%)
2.4 MB
2.0 MB
In fact, the total size of Otonami.com main page is 2.4 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 2.1 MB which makes up the majority of the site volume.
Potential reduce by 54.1 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 19.0 kB, which is 31% 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 54.1 kB or 87% of the original size.
Potential reduce by 153.9 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. Otonami images are well optimized though.
Potential reduce by 112.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 112.9 kB or 70% of the original size.
Potential reduce by 21.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. Otonami.com needs all CSS files to be minified and compressed as it can save up to 21.5 kB or 82% of the original size.
Number of requests can be reduced by 6 (11%)
55
49
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otonami. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
otonami.com
1563 ms
style.css
662 ms
jquery.bxslider.css
511 ms
jquery-1.11.3.min.js
1156 ms
jquery.bxslider.min.js
726 ms
footerFixed.js
377 ms
modal-multi.js
516 ms
script.js
565 ms
wp-emoji-release.min.js
341 ms
wp-embed.min.js
171 ms
bg-top.jpg
512 ms
logo-otonami.png
492 ms
nav-yotsuya.png
489 ms
nav-confort.png
487 ms
nav-switch.png
484 ms
gnav-top.png
485 ms
gnav-news.png
489 ms
gnav-interview.png
491 ms
gnav-pickup.png
492 ms
btn-nav-open.png
500 ms
sp-sub-01.png
660 ms
sp-sub-02.png
510 ms
sp-sub-03.png
725 ms
sp-sub-07.png
563 ms
sp-sub-04.png
661 ms
sp-sub-05.png
678 ms
sp-sub-06.png
680 ms
d23e34f6bf83206af4440babb1091eda.jpg
2062 ms
c2eb0de07149b5e04a6ee6395c397265.jpg
1483 ms
31bdbd5fc4b204d8cfc103578ff7243c.jpg
1851 ms
37b12aec621f7640c39cd6a2069a92e2.jpg
1526 ms
ttl-news.png
850 ms
85e54954fe20bc7f883cd831205f6e7d-2-e1456983917847.jpeg
1446 ms
9bacec2db615eebd07a53cac496c00a8.png
3101 ms
zenya.jpg
2210 ms
btn-more.png
1648 ms
ttl-pickup.png
1695 ms
0307e.jpg
1814 ms
ico-switch.png
1865 ms
modal-close.png
1978 ms
btn-tweet.png
2015 ms
btn-share.png
2035 ms
0315t.jpg
2472 ms
ico-yotsuya.png
2179 ms
0312c.jpg
2543 ms
ico-comfort.png
1769 ms
0313c.jpg
1867 ms
0320t.jpg
1912 ms
0324e.jpg
1954 ms
0325t.jpg
2398 ms
0325c.jpg
3763 ms
0326c.jpg
2512 ms
0327t-day.jpg
2317 ms
0327tnight.jpg
2563 ms
0327c.jpg
2639 ms
0327e.jpg
2543 ms
bx_loader.gif
3955 ms
controls.png
3485 ms
otonami.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
otonami.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
otonami.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otonami.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Otonami.com 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.
otonami.com
Open Graph description is not detected on the main page of Otonami. 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: