5.1 sec in total
1 sec
3.8 sec
228 ms
Visit naxos.jp now to see the best up-to-date NAXOS content for Japan and also check out these interesting facts you probably never knew about naxos.jp
NAXOS JAPAN 世界最大のレパートリーを誇るクラシック音楽レーベル - ナクソス・ジャパン
Visit naxos.jpWe analyzed Naxos.jp page load time and found that the first response time was 1 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
naxos.jp performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value15.2 s
0/100
25%
Value12.0 s
4/100
10%
Value1,740 ms
10/100
30%
Value0.055
98/100
15%
Value22.0 s
1/100
10%
1018 ms
332 ms
692 ms
348 ms
344 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 67% of them (76 requests) were addressed to the original Naxos.jp, 9% (10 requests) were made to Image.rakuten.co.jp and 5% (6 requests) were made to Ml.naxos.jp. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Naxos.jp.
Page size can be reduced by 106.8 kB (10%)
1.1 MB
998.1 kB
In fact, the total size of Naxos.jp main page is 1.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 764.6 kB which makes up the majority of the site volume.
Potential reduce by 38.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 8.2 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 38.1 kB or 79% of the original size.
Potential reduce by 23.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. NAXOS images are well optimized though.
Potential reduce by 5.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. This website has mostly compressed JavaScripts.
Potential reduce by 39.3 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. Naxos.jp needs all CSS files to be minified and compressed as it can save up to 39.3 kB or 37% of the original size.
Number of requests can be reduced by 42 (38%)
111
69
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NAXOS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
naxos.jp
1018 ms
import.css
332 ms
jquery.js
692 ms
common.js
348 ms
index-behavior.js
344 ms
widgets.js
51 ms
js
72 ms
reset.css
169 ms
structure.css
169 ms
header.css
178 ms
footer.css
188 ms
navigation.css
335 ms
textdecorations.css
336 ms
others.css
337 ms
others.css
344 ms
home.css
362 ms
modify.css
504 ms
bruckner2024_banner.jpg
872 ms
8.574308.gif
1109 ms
artwork-440x440.jpg
131 ms
900217.gif
1280 ms
8.559916.gif
1295 ms
C8091.gif
1303 ms
body_bg_01.gif
230 ms
sitetitle_logo_01.gif
231 ms
globalnavi_btn_01.gif
230 ms
globalnavi_btn_02.gif
230 ms
globalnavi_btn_03.gif
230 ms
globalnavi_btn_04.gif
229 ms
globalnavi_btn_05.gif
596 ms
globalnavi_btn_06.gif
597 ms
globalnavi_btn_07.gif
597 ms
home_tit_02.gif
596 ms
detaillink_btn_01.gif
596 ms
detaillink_btn_03.gif
596 ms
home_tit_03.gif
837 ms
home_tit_04.gif
837 ms
SNRT2001.jpg
1290 ms
home_tit_05.gif
835 ms
ce_App_Pass.jpg
835 ms
full_icon-01.jpg
837 ms
sm_full_icon_74.jpg
936 ms
full_qr.gif
937 ms
value_qr.gif
937 ms
call_qr.gif
945 ms
YT-Channel_banner.png
939 ms
note_banner.png
1102 ms
sensyu_banner_top.jpg
1105 ms
navigation_tit_01.gif
1105 ms
navigation_tit_02.gif
1107 ms
navigation_tit_04.gif
1117 ms
bnr_nml_01.jpg
1270 ms
bnr_digital_distribute_01.jpg
1273 ms
bnr_naxos_licencing_01.jpg
1272 ms
bnr_physical_products_01.jpg
1274 ms
pagetop_btn_01.gif
1290 ms
brso75-banner2.jpg
1044 ms
banner_s100467.jpg
1031 ms
mehta-bb.jpg
1055 ms
nxcx-10403_banner.jpg
1243 ms
nycc27314-banner.jpg
1068 ms
brazil-00.jpg
1035 ms
banner-elisabeth.jpg
1219 ms
2110770.jpg
1219 ms
2110740.jpg
1258 ms
headwrap_bg_01.gif
1434 ms
header_bg_02.gif
1437 ms
OKIZXAeHkTM
236 ms
all.js
72 ms
header_bg_01.jpg
1423 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
195 ms
all.js
72 ms
globalnavi_bg_03.gif
1216 ms
globalnavi_bg_02.gif
1236 ms
globalnavi_bg_01.gif
1242 ms
wrapper_bg_01.gif
1378 ms
toprelease_bg_01.gif
1381 ms
toprelease_bg_01_btm.gif
1378 ms
www-player.css
8 ms
www-embed-player.js
35 ms
base.js
61 ms
settings
341 ms
ad_status.js
178 ms
vTEfc-jlr9e_tfMt-BR8Zcc1_6XGLRk25TFtjqWuknE.js
126 ms
embed.js
49 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
54 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
54 ms
title01_bg_01.gif
1017 ms
title01_bg_03.gif
1043 ms
title01_bg_04.gif
1044 ms
detaillink_btn_01_o.gif
1180 ms
line_dotted01_gray01.gif
1182 ms
detaillink_btn_03_o.gif
1184 ms
button.856debeac157d9669cf51e73a08fbc93.js
108 ms
Create
107 ms
id
87 ms
embeds
88 ms
follow_button.2f70fb173b9000da126c79afe2098f02.ja.html
99 ms
GP926.gif
520 ms
8.573391.gif
767 ms
line_dotted02_gray01.jpg
945 ms
line_dotted03_gray01.gif
976 ms
title01_bg_02.gif
975 ms
navigation_bg_01.gif
1105 ms
ico_circle01_green01.gif
1107 ms
GenerateIT
15 ms
navibox_bg_01.gif
1011 ms
navibox_bg_top_01.gif
1011 ms
navibox_bg_btm_01.gif
1047 ms
footer_bg_01.gif
1045 ms
pagetop_btn_01_o.gif
1164 ms
bg_dotted01_gray01.gif
1009 ms
ico_circle01_gray01.gif
1010 ms
ico_circle01_blue01.gif
1009 ms
naxos.jp accessibility score
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
naxos.jp 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
Page has valid source maps
naxos.jp SEO score
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Naxos.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 Naxos.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.
naxos.jp
Open Graph description is not detected on the main page of NAXOS. 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: