Tools & Wizards About Us
endrum.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% 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

  • 92

    SEO

    Google-friendlier than
    74% of websites

endrum.com

ENDRUM エンドラム／遠藤 徳光オフィシャルサイト

Page Load Speed

7.7 sec in total

First Response

3 sec

Resources Loaded

4.5 sec

Page Rendered

150 ms

endrum.com screenshot

About Website

Welcome to endrum.com homepage info - get ready to check ENDRUM best content for Japan right away, or after learning these important things about endrum.com

ENDRUM エンドラム／代表 遠藤徳光が発信する音楽関連情報サイトです。レコーディング、ライブサポート、ドラムレッスン、音楽制作などを行っています。

Visit endrum.com

Key Findings

We analyzed Endrum.com page load time and found that the first response time was 3 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

endrum.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value6.5 s

58/100

10%

Network Requests Diagram

endrum.com

3012 ms

reset.css

168 ms

common.css

325 ms

layout.css

328 ms

index.css

339 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 66% of them (21 requests) were addressed to the original Endrum.com, 13% (4 requests) were made to F.vimeocdn.com and 6% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Endrum.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 391.1 kB (39%)

Content Size

999.3 kB

After Optimization

608.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Endrum.com main page is 999.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 497.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 5.7 kB

  • Original 7.9 kB
  • After minification 6.4 kB
  • After compression 2.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 1.5 kB, which is 19% 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 5.7 kB or 72% of the original size.

Image Optimization

-7%

Potential reduce by 35.4 kB

  • Original 497.0 kB
  • After minification 461.6 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. ENDRUM images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 231.8 kB

  • Original 360.4 kB
  • After minification 360.4 kB
  • After compression 128.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 231.8 kB or 64% of the original size.

CSS Optimization

-88%

Potential reduce by 118.2 kB

  • Original 133.9 kB
  • After minification 124.2 kB
  • After compression 15.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. Endrum.com needs all CSS files to be minified and compressed as it can save up to 118.2 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (23%)

Requests Now

30

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

endrum.com

endrum.com

3012 ms

reset.css

reset.css

168 ms

common.css

common.css

325 ms

layout.css

layout.css

328 ms

index.css

index.css

339 ms

141187254

141187254

79 ms

logo-1.png

logo-1.png

373 ms

visual.jpg

visual.jpg

1493 ms

nav-1.png

nav-1.png

370 ms

nav-2.png

nav-2.png

487 ms

nav-3.png

nav-3.png

488 ms

nav-4.png

nav-4.png

512 ms

nav-5.png

nav-5.png

521 ms

nav-6.png

nav-6.png

530 ms

nav-7.png

nav-7.png

646 ms

nav-8.png

nav-8.png

658 ms

news-title.png

news-title.png

668 ms

photo-2.jpg

photo-2.jpg

829 ms

player.js

player.js

92 ms

player.css

player.css

62 ms

ga.js

ga.js

31 ms

vuid.min.js

vuid.min.js

58 ms

__utm.gif

__utm.gif

24 ms

proxy.html

proxy.html

32 ms

analytics.js

analytics.js

23 ms

main-base-bg.png

main-base-bg.png

364 ms

main-bg.png

main-bg.png

468 ms

news-bg.png

news-bg.png

484 ms

listmark-1.png

listmark-1.png

492 ms

collect

collect

14 ms

default-blue_60x60.png

default-blue_60x60.png

32 ms

544705644.jpg

544705644.jpg

94 ms

Accessibility Review

endrum.com accessibility score

89

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

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

endrum.com SEO score

92

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

endrum.com

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