Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

alsoj.net

アルソ出版 -ONLINE- 楽器と自分のつくる音と、その物語。:管楽器レッスン専門雑誌と楽譜:フルート│サックス│クラリネット│オカリナ

Page Load Speed

17.8 sec in total

First Response

553 ms

Resources Loaded

13.9 sec

Page Rendered

3.3 sec

alsoj.net screenshot

About Website

Welcome to alsoj.net homepage info - get ready to check Alsoj best content for Japan right away, or after learning these important things about alsoj.net

アルソ出版はザ・フルート│THE FLUTE,ザ・サックス│THE SAX,ザ・クラリネット│THE CLARINET,Ocarinaの楽器レッスン情報誌、フルート・クラリネット・サックス・オカリナの楽譜を出版しています。

Visit alsoj.net

Key Findings

We analyzed Alsoj.net page load time and found that the first response time was 553 ms and then it took 17.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

alsoj.net performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value30.4 s

0/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.817

4/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

Network Requests Diagram

alsoj.net

553 ms

alsoj.net

703 ms

index.html

176 ms

index.html

1504 ms

user.css

846 ms

Our browser made a total of 322 requests to load all elements on the main page. We found that 94% of them (302 requests) were addressed to the original Alsoj.net, 2% (7 requests) were made to Use.fontawesome.com and 1% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Alsoj.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 767.1 kB (2%)

Content Size

32.8 MB

After Optimization

32.0 MB

In fact, the total size of Alsoj.net main page is 32.8 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 31.6 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 182.1 kB

  • Original 209.7 kB
  • After minification 178.8 kB
  • After compression 27.6 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 30.9 kB, which is 15% 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 182.1 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 107.7 kB

  • Original 31.6 MB
  • After minification 31.5 MB

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. Alsoj images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 374.8 kB

  • Original 771.0 kB
  • After minification 761.7 kB
  • After compression 396.2 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 374.8 kB or 49% of the original size.

CSS Optimization

-59%

Potential reduce by 102.5 kB

  • Original 173.2 kB
  • After minification 142.8 kB
  • After compression 70.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. Alsoj.net needs all CSS files to be minified and compressed as it can save up to 102.5 kB or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (14%)

Requests Now

314

After Optimization

270

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

Accessibility Review

alsoj.net accessibility score

54

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-hidden="true"] elements contain focusable descendents

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Image elements do not have [alt] attributes

High

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

High

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

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

alsoj.net best practices score

75

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

alsoj.net SEO score

76

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alsoj.net 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 Alsoj.net 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 Alsoj. 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: