Report Summary

  • 24

    Performance

    Renders faster than
    44% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    34% of websites

  • 73

    SEO

    Google-friendlier than
    40% of websites

audio-heritage.jp

オーディオの足跡 オーディオ機器を何でも紹介

Page Load Speed

36.4 sec in total

First Response

4.2 sec

Resources Loaded

14.8 sec

Page Rendered

17.4 sec

audio-heritage.jp screenshot

About Website

Click here to check amazing Audio Heritage content for Japan. Otherwise, check out these important facts you probably never knew about audio-heritage.jp

Visit audio-heritage.jp

Key Findings

We analyzed Audio-heritage.jp page load time and found that the first response time was 4.2 sec and then it took 32.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

audio-heritage.jp performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value30,300 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value42.0 s

0/100

10%

Network Requests Diagram

audio-heritage.jp

4169 ms

adsbygoogle.js

83 ms

logo.jpg

3590 ms

a1.jpg

1866 ms

a4.jpg

2105 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 26% of them (11 requests) were addressed to the original Audio-heritage.jp, 33% (14 requests) were made to Tpc.googlesyndication.com and 14% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (7.3 sec) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 792.5 kB (56%)

Content Size

1.4 MB

After Optimization

613.6 kB

In fact, the total size of Audio-heritage.jp main page is 1.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. 50% of websites need less resources to load. Javascripts take 828.8 kB which makes up the majority of the site volume.

HTML Optimization

-97%

Potential reduce by 214.9 kB

  • Original 222.6 kB
  • After minification 53.1 kB
  • After compression 7.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 169.5 kB, which is 76% 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 214.9 kB or 97% of the original size.

Image Optimization

-11%

Potential reduce by 37.4 kB

  • Original 337.9 kB
  • After minification 300.5 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. Obviously, Audio Heritage needs image optimization as it can save up to 37.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 526.2 kB

  • Original 828.8 kB
  • After minification 820.7 kB
  • After compression 302.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 526.2 kB or 63% of the original size.

CSS Optimization

-83%

Potential reduce by 14.0 kB

  • Original 16.8 kB
  • After minification 12.8 kB
  • After compression 2.8 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. Audio-heritage.jp needs all CSS files to be minified and compressed as it can save up to 14.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (26%)

Requests Now

39

After Optimization

29

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

Accessibility Review

audio-heritage.jp accessibility score

66

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

audio-heritage.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

audio-heritage.jp SEO score

73

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

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

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Audio-heritage.jp 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 Audio-heritage.jp main page’s claimed encoding is shift_jis. 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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Audio Heritage. 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: