Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

amatsuki.jp

天月 Official Web Site

Page Load Speed

50.1 sec in total

First Response

2.1 sec

Resources Loaded

42 sec

Page Rendered

6 sec

amatsuki.jp screenshot

About Website

Welcome to amatsuki.jp homepage info - get ready to check Amatsuki best content for Japan right away, or after learning these important things about amatsuki.jp

天月 -あまつき-のオフィシャルウェブサイト。ライブやイベント・メディア出演などの最新情報をいち早くお届けします!!

Visit amatsuki.jp

Key Findings

We analyzed Amatsuki.jp page load time and found that the first response time was 2.1 sec and then it took 48 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. Unfortunately, there were 48 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

amatsuki.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value14.8 s

1/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.21

59/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

amatsuki.jp

2132 ms

common.css

850 ms

top.css

668 ms

gurchin.js

420 ms

moonphace.js

1573 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that 62% of them (81 requests) were addressed to the original Amatsuki.jp, 12% (16 requests) were made to Pbs.twimg.com and 6% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (20.6 sec) belongs to the original domain Amatsuki.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 668.6 kB (5%)

Content Size

13.6 MB

After Optimization

12.9 MB

In fact, the total size of Amatsuki.jp main page is 13.6 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. 70% of websites need less resources to load. Images take 13.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 210.6 kB

  • Original 255.8 kB
  • After minification 179.9 kB
  • After compression 45.2 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 75.9 kB, which is 30% 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 210.6 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 325.6 kB

  • Original 13.1 MB
  • After minification 12.7 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. Amatsuki images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 105.6 kB

  • Original 189.0 kB
  • After minification 179.4 kB
  • After compression 83.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 105.6 kB or 56% of the original size.

CSS Optimization

-80%

Potential reduce by 26.8 kB

  • Original 33.6 kB
  • After minification 24.7 kB
  • After compression 6.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. Amatsuki.jp needs all CSS files to be minified and compressed as it can save up to 26.8 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (36%)

Requests Now

78

After Optimization

50

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

Accessibility Review

amatsuki.jp accessibility score

65

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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.

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

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

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

amatsuki.jp best practices score

67

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

SEO Factors

amatsuki.jp SEO score

92

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

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 uses legible font sizes

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 Amatsuki.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 Amatsuki.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 data is detected on the main page of Amatsuki. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: