5.3 sec in total
826 ms
3.6 sec
790 ms
Click here to check amazing Music Bells content for Japan. Otherwise, check out these important facts you probably never knew about music-bells.com
演奏会、コンクールの曲探しに役立つ様々な楽器編成の楽譜を豊富に取り揃えています。すべて当出版社オリジナルの楽譜ですので、是非チェックしてみてください!
Visit music-bells.comWe analyzed Music-bells.com page load time and found that the first response time was 826 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
music-bells.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value4.6 s
35/100
25%
Value5.5 s
55/100
10%
Value230 ms
86/100
30%
Value0.043
99/100
15%
Value5.7 s
68/100
10%
826 ms
329 ms
734 ms
34 ms
10 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 6% of them (6 requests) were addressed to the original Music-bells.com, 44% (43 requests) were made to Img09.shop-pro.jp and 15% (15 requests) were made to Img.shop-pro.jp. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Img09.shop-pro.jp.
Page size can be reduced by 211.3 kB (44%)
481.2 kB
269.9 kB
In fact, the total size of Music-bells.com main page is 481.2 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 261.1 kB which makes up the majority of the site volume.
Potential reduce by 37.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 37.8 kB or 76% of the original size.
Potential reduce by 4.6 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. Music Bells images are well optimized though.
Potential reduce by 133.4 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 133.4 kB or 51% of the original size.
Potential reduce by 35.6 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. Music-bells.com needs all CSS files to be minified and compressed as it can save up to 35.6 kB or 80% of the original size.
Number of requests can be reduced by 37 (39%)
95
58
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Music Bells. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
music-bells.com
826 ms
cross-border-cart.css
329 ms
index.css
734 ms
jquery.min.js
34 ms
show_ads.js
10 ms
cart.js
309 ms
product_stock.js
351 ms
li.php
482 ms
li.php
649 ms
menu_1_bg.jpg
270 ms
icons1.gif
374 ms
embed
104 ms
ja_follow_me-a.png
197 ms
icons29.gif
355 ms
side_cat_bg.jpg
305 ms
side_cat_title_bg.jpg
240 ms
side_cat_bottom_bg.jpg
241 ms
sp.gif
655 ms
side_bottom_bg.gif
295 ms
rss.gif
651 ms
atom.gif
650 ms
info_bg.jpg
271 ms
info_top_bg.gif
298 ms
info_text_bottom_bg.gif
394 ms
info_bottom_bg.gif
394 ms
main_title_bg.jpg
324 ms
side_cart.jpg
353 ms
4.gif
208 ms
PA01039691.gif
77 ms
PaymentBannerMusicBells.gif
633 ms
en_flag26.png
325 ms
sidemenu_group.gif
232 ms
sidemenu_genre.gif
633 ms
bnr_200_40.gif
287 ms
bnr_88_31.gif
408 ms
carslogo01.jpg
439 ms
13772539_th.png
606 ms
14979086_th.png
811 ms
14979140_th.png
706 ms
15951806_th.png
709 ms
17082493_th.png
803 ms
17532952_th.png
1013 ms
17534205_th.png
980 ms
17723489_th.png
917 ms
17831705_th.png
957 ms
18126499_th.png
1045 ms
18803985_th.png
1120 ms
22759508_th.png
1173 ms
24245734_th.png
1210 ms
25141661_th.png
1443 ms
36787263_th.png
1502 ms
37167279_th.png
1284 ms
41206013_th.png
1441 ms
66637505_th.png
1427 ms
66736706_th.png
1437 ms
67308404_th.png
1545 ms
83260543_th.png
1724 ms
catchcopy002.gif
1706 ms
catchcopy001.gif
1768 ms
feature001.gif
1758 ms
feature002.gif
1855 ms
feature003.gif
1832 ms
zrt_lookup.html
38 ms
show_ads_impl.js
46 ms
feature004.gif
1900 ms
feature005.gif
1914 ms
embed
227 ms
ads
349 ms
footer_bg.jpg
217 ms
osd.js
33 ms
feature006.gif
1915 ms
feature007.gif
1861 ms
feature008.gif
1819 ms
f7e12ba16863d79ebc50b5ad512d0dd5embedcompiled_fastui.css
13 ms
f7e12ba16863d79ebc50b5ad512d0dd5embedcompiled__en.js
51 ms
client.js
85 ms
publish_now002.gif
1838 ms
cb=gapi.loaded_0
36 ms
facebookpage_musicbells.jpg
1771 ms
postmessageRelay
46 ms
m_js_controller.js
22 ms
abg.js
40 ms
api.js
106 ms
core:rpc:shindig.random:shindig.sha1.js
130 ms
2536007149-postmessagerelay.js
122 ms
favicon
189 ms
googlelogo_color_112x36dp.png
155 ms
nessie_icon_tiamat_white.png
53 ms
s
65 ms
x_button_blue2.png
41 ms
logo-plus.png
63 ms
proxy.html
109 ms
googlelogo_color_46x16dp.png
32 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
5 ms
cb=gapi.loaded_0
12 ms
events
25 ms
events
156 ms
music-bells.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
music-bells.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
music-bells.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
Tap targets are not sized appropriately
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Music-bells.com 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 Music-bells.com main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
music-bells.com
Open Graph data is detected on the main page of Music Bells. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: