Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

naxos.jp

NAXOS JAPAN

Page Load Speed

5.1 sec in total

First Response

1 sec

Resources Loaded

3.8 sec

Page Rendered

228 ms

naxos.jp screenshot

About Website

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.jp

Key Findings

We 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.

Performance Metrics

naxos.jp performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value1,740 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.055

98/100

15%

TTI (Time to Interactive)

Value22.0 s

1/100

10%

Network Requests Diagram

naxos.jp

1018 ms

import.css

332 ms

jquery.js

692 ms

common.js

348 ms

index-behavior.js

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 Optimization Overview & Recommendations

Page size can be reduced by 106.8 kB (10%)

Content Size

1.1 MB

After Optimization

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.

HTML Optimization

-79%

Potential reduce by 38.1 kB

  • Original 48.5 kB
  • After minification 40.3 kB
  • After compression 10.4 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.

Image Optimization

-3%

Potential reduce by 23.8 kB

  • Original 764.6 kB
  • After minification 740.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.

JavaScript Optimization

-3%

Potential reduce by 5.6 kB

  • Original 186.0 kB
  • After minification 185.8 kB
  • After compression 180.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. This website has mostly compressed JavaScripts.

CSS Optimization

-37%

Potential reduce by 39.3 kB

  • Original 105.8 kB
  • After minification 87.0 kB
  • After compression 66.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. 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.

Requests Breakdown

Number of requests can be reduced by 42 (38%)

Requests Now

111

After Optimization

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.

Accessibility Review

naxos.jp accessibility score

64

Accessibility Issues

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

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

naxos.jp best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

naxos.jp SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 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.

Social Sharing Optimization

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: