Tools & Wizards About Us
amass.jp screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

amass.jp

amass

Page Load Speed

5.7 sec in total

First Response

545 ms

Resources Loaded

4.8 sec

Page Rendered

323 ms

amass.jp screenshot

About Website

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

ニュース・サイト「amass」では音楽を中心にさまざまな情報をお伝えします

Visit amass.jp

Key Findings

We analyzed Amass.jp page load time and found that the first response time was 545 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

amass.jp performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.595

11/100

15%

TTI (Time to Interactive)

Value7.1 s

51/100

10%

Network Requests Diagram

amass.jp

545 ms

amass.jp

1107 ms

kihon.css

370 ms

top.css

542 ms

jquery.js

1090 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 23% of them (17 requests) were addressed to the original Amass.jp, 29% (21 requests) were made to Amassing2.sakura.ne.jp and 25% (18 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Amassing2.sakura.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 441.4 kB (31%)

Content Size

1.4 MB

After Optimization

989.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Amass.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. 55% of websites need less resources to load. Images take 692.6 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 44.3 kB

  • Original 57.6 kB
  • After minification 57.5 kB
  • After compression 13.3 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 44.3 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 5.8 kB

  • Original 692.6 kB
  • After minification 686.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. Amass images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 385.6 kB

  • Original 673.5 kB
  • After minification 670.4 kB
  • After compression 287.9 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 385.6 kB or 57% of the original size.

CSS Optimization

-80%

Potential reduce by 5.7 kB

  • Original 7.0 kB
  • After minification 4.1 kB
  • After compression 1.4 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. Amass.jp needs all CSS files to be minified and compressed as it can save up to 5.7 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

69

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

amass.jp

amass.jp

545 ms

amass.jp

amass.jp

1107 ms

kihon.css

kihon.css

370 ms

top.css

top.css

542 ms

jquery.js

jquery.js

1090 ms

listcolor.js

listcolor.js

556 ms

search.js

search.js

558 ms

js

js

70 ms

adsbygoogle.js

adsbygoogle.js

121 ms

update_top.js

update_top.js

558 ms

widget.js

widget.js

8 ms

ga.js

ga.js

88 ms

134388.jpg

134388.jpg

1128 ms

amass_logo.jpg

amass_logo.jpg

196 ms

twitter.jpg

twitter.jpg

214 ms

facebook.jpg

facebook.jpg

196 ms

mail.jpg

mail.jpg

194 ms

rss.jpg

rss.jpg

192 ms

134387.jpg

134387.jpg

1141 ms

134385.jpg

134385.jpg

1146 ms

59190.jpg

59190.jpg

1148 ms

128652.jpg

128652.jpg

1167 ms

134384.jpg

134384.jpg

1168 ms

99297.jpg

99297.jpg

1312 ms

63227.jpg

63227.jpg

1330 ms

99402.jpg

99402.jpg

1332 ms

134381.jpg

134381.jpg

1522 ms

64583.jpg

64583.jpg

1563 ms

134380.jpg

134380.jpg

1564 ms

114732.jpg

114732.jpg

1503 ms

134378.jpg

134378.jpg

1702 ms

134376.jpg

134376.jpg

1519 ms

134374.jpg

134374.jpg

1688 ms

87000.jpg

87000.jpg

1704 ms

127405.jpg

127405.jpg

1708 ms

134373.jpg

134373.jpg

1738 ms

134372.jpg

134372.jpg

1750 ms

show_ads_impl.js

show_ads_impl.js

384 ms

search_button.gif

search_button.gif

187 ms

gr.png

gr.png

286 ms

__utm.gif

__utm.gif

13 ms

update_top.php

update_top.php

507 ms

nowload.gif

nowload.gif

249 ms

all.js

all.js

58 ms

widgets.js

widgets.js

95 ms

cm

cm

41 ms

all.js

all.js

6 ms

43 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

59 ms

settings

settings

179 ms

zrt_lookup.html

zrt_lookup.html

40 ms

ads

ads

431 ms

ads

ads

363 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

31 ms

ads

ads

369 ms

ads

ads

78 ms

amass_jp

amass_jp

936 ms

134388.jpg

134388.jpg

1603 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

25 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

52 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

89 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

74 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

83 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

89 ms

_buildManifest.js

_buildManifest.js

139 ms

_ssgManifest.js

_ssgManifest.js

140 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

24 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

21 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

25 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

40 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

51 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

63 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

19 ms

Accessibility Review

amass.jp accessibility score

89

Accessibility Issues

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

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

Page has valid source maps

SEO Factors

amass.jp SEO score

100

Search Engine Optimization Advices

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

amass.jp

Open Graph data is detected on the main page of Amass. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: