Tools & Wizards About Us
live-drum.com screenshot

Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

live-drum.com

-LIVEHOUSE DRUM(ライブハウスドラム)-

Page Load Speed

4.5 sec in total

First Response

544 ms

Resources Loaded

3.7 sec

Page Rendered

262 ms

live-drum.com screenshot

About Website

Visit live-drum.com now to see the best up-to-date Live DRUM content for Japan and also check out these interesting facts you probably never knew about live-drum.com

九州の福岡を拠点に持つライブハウスDRUMグループ(ドラムロゴス、ドラムサン、B1等)のHPです。ライブスケジュールやインディーズバンドを紹介

Visit live-drum.com

Key Findings

We analyzed Live-drum.com page load time and found that the first response time was 544 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

live-drum.com performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

index1.shtml

544 ms

main.css

176 ms

js.js

334 ms

jquery.min.js

8 ms

jquery.easing.1.3.js

340 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 85% of them (58 requests) were addressed to the original Live-drum.com, 13% (9 requests) were made to Dp13181707.lolipop.jp and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Live-drum.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.2 kB (8%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Live-drum.com main page is 1.3 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. 40% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 36.2 kB

  • Original 43.4 kB
  • After minification 38.6 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 4.8 kB, which is 11% 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 36.2 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 55.7 kB

  • Original 1.2 MB
  • After minification 1.1 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. Live DRUM images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 3.9 kB

  • Original 26.0 kB
  • After minification 26.0 kB
  • After compression 22.0 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 3.9 kB or 15% of the original size.

CSS Optimization

-37%

Potential reduce by 1.3 kB

  • Original 3.5 kB
  • After minification 3.3 kB
  • After compression 2.2 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. Live-drum.com needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (24%)

Requests Now

67

After Optimization

51

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

index1.shtml

index1.shtml

544 ms

main.css

main.css

176 ms

js.js

js.js

334 ms

jquery.min.js

jquery.min.js

8 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

340 ms

jquery.timers-1.1.2.js

jquery.timers-1.1.2.js

346 ms

jquery.galleryview-1.1.js

jquery.galleryview-1.1.js

342 ms

galleryview.css

galleryview.css

341 ms

thickbox.css

thickbox.css

361 ms

intro.css

intro.css

498 ms

0731.png

0731.png

840 ms

0626.jpg

0626.jpg

838 ms

0625.gif

0625.gif

677 ms

0624.jpg

0624.jpg

690 ms

0623.jpg

0623.jpg

691 ms

0622.jpg

0622.jpg

704 ms

0621.jpg

0621.jpg

1010 ms

0618.gif

0618.gif

865 ms

0615.jpg

0615.jpg

864 ms

header_title.jpg

header_title.jpg

203 ms

head.gif

head.gif

203 ms

logos.jpg

logos.jpg

204 ms

speace.gif

speace.gif

202 ms

b1.jpg

b1.jpg

204 ms

son.jpg

son.jpg

312 ms

b9.jpg

b9.jpg

339 ms

b7.jpg

b7.jpg

346 ms

b0.jpg

b0.jpg

349 ms

food.gif

food.gif

348 ms

band_head.gif

band_head.gif

350 ms

kyusyu_band.jpg

kyusyu_band.jpg

478 ms

other_band.jpg

other_band.jpg

507 ms

band_food.gif

band_food.gif

516 ms

livehouselink.gif

livehouselink.gif

532 ms

adult_head.gif

adult_head.gif

520 ms

adult_bottom.gif

adult_bottom.gif

521 ms

index_gallery01.jpg

index_gallery01.jpg

1295 ms

index_gallery02.jpg

index_gallery02.jpg

1003 ms

index_gallery03.jpg

index_gallery03.jpg

1200 ms

index_gallery05.jpg

index_gallery05.jpg

1370 ms

index_gallery06.jpg

index_gallery06.jpg

1076 ms

index_gallery07.jpg

index_gallery07.jpg

1383 ms

1.jpg

1.jpg

1173 ms

2.jpg

2.jpg

1251 ms

3.jpg

3.jpg

1343 ms

5.jpg

5.jpg

1374 ms

6.jpg

6.jpg

1427 ms

7.jpg

7.jpg

1461 ms

bg.jpg

bg.jpg

1319 ms

news_bg.gif

news_bg.gif

1349 ms

news_head.jpg

news_head.jpg

1353 ms

skullrose.jpg

skullrose.jpg

1361 ms

be-0_side.gif

be-0_side.gif

1407 ms

be-0_studio.jpg

be-0_studio.jpg

1434 ms

link_head.gif

link_head.gif

1487 ms

sr.jpg

sr.jpg

1520 ms

loppi.gif

loppi.gif

1522 ms

2.jpg

2.jpg

1532 ms

pia.jpg

pia.jpg

1576 ms

eventer_head.gif

eventer_head.gif

1598 ms

kyoudou.gif

kyoudou.gif

1544 ms

green_music.jpg

green_music.jpg

1562 ms

bea.gif

bea.gif

1553 ms

pointer.png

pointer.png

1561 ms

next.png

next.png

1605 ms

prev.png

prev.png

1617 ms

kyusyu_band2.jpg

kyusyu_band2.jpg

174 ms

other_band2.jpg

other_band2.jpg

173 ms

Accessibility Review

live-drum.com accessibility score

66

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

live-drum.com best practices score

58

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

live-drum.com SEO score

81

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 uses 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 Live-drum.com 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 Live-drum.com 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

live-drum.com

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