Tools & Wizards About Us
livehouse.tv screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

livehouse.tv

ライブハウス情報サイト（出演方法、レンタル、貸切、キャパなど） / 全国のライブハウス情報サイト　livehouse.tv

Page Load Speed

4.7 sec in total

First Response

524 ms

Resources Loaded

3.9 sec

Page Rendered

224 ms

livehouse.tv screenshot

About Website

Welcome to livehouse.tv homepage info - get ready to check Livehouse best content right away, or after learning these important things about livehouse.tv

ライブハウス情報サイト（出演方法、レンタル、貸切、キャパなど）のページ。会場へのアクセス、キャパ、駐車場、最寄りのコンビニ、コインロッカー情報まで調べることができます。

Visit livehouse.tv

Key Findings

We analyzed Livehouse.tv page load time and found that the first response time was 524 ms and then it took 4.2 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

livehouse.tv performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value1,000 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

livehouse.tv

524 ms

livehouse.tv

944 ms

gtm.js

90 ms

bootstrap.min.css

78 ms

livehouse_200.png

1071 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Livehouse.tv, 34% (18 requests) were made to Platform.twitter.com and 28% (15 requests) were made to S.wordpress.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Yellowspan.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 109.2 kB (12%)

Content Size

918.9 kB

After Optimization

809.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Livehouse.tv main page is 918.9 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. 45% of websites need less resources to load. Images take 788.7 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 21.8 kB

  • Original 28.9 kB
  • After minification 25.2 kB
  • After compression 7.0 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 3.7 kB, which is 13% 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 21.8 kB or 76% of the original size.

Image Optimization

-5%

Potential reduce by 39.0 kB

  • Original 788.7 kB
  • After minification 749.7 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. Livehouse images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 48.3 kB

  • Original 99.1 kB
  • After minification 99.1 kB
  • After compression 50.8 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 48.3 kB or 49% of the original size.

CSS Optimization

-1%

Potential reduce by 14 B

  • Original 2.3 kB
  • After minification 2.3 kB
  • After compression 2.3 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. Livehouse.tv has all CSS files already compressed.

Requests Breakdown

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

Requests Now

51

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

livehouse.tv

livehouse.tv

524 ms

livehouse.tv

livehouse.tv

944 ms

gtm.js

gtm.js

90 ms

bootstrap.min.css

bootstrap.min.css

78 ms

livehouse_200.png

livehouse_200.png

1071 ms

62 ms

1228.jpg

1228.jpg

2128 ms

169 ms

122 ms

167 ms

veats.jp

veats.jp

66 ms

422170_394681453878308_1786413487_n.jpg

422170_394681453878308_1786413487_n.jpg

1771 ms

widgets.js

widgets.js

103 ms

30 ms

loader.min.js

loader.min.js

138 ms

popper.min.js

popper.min.js

15 ms

bootstrap.min.js

bootstrap.min.js

24 ms

icn_facebook.png

icn_facebook.png

946 ms

icn_twitter.png

icn_twitter.png

958 ms

27 ms

130 ms

157 ms

113 ms

125 ms

50 ms

173 ms

274 ms

134 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

60 ms

settings

settings

70 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

23 ms

livehousetv

livehousetv

69 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

25 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

50 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

77 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

88 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

103 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

107 ms

_buildManifest.js

_buildManifest.js

133 ms

_ssgManifest.js

_ssgManifest.js

134 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

25 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

19 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

22 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

38 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

46 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

85 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

26 ms

share

share

243 ms

widget.1.23.2.0.css

widget.1.23.2.0.css

246 ms

button.1.23.2.0.js

button.1.23.2.0.js

279 ms

sentry.1.23.2.0.js

sentry.1.23.2.0.js

265 ms

torimochi.js

torimochi.js

10 ms

line_60_v3.png

line_60_v3.png

17 ms

Accessibility Review

livehouse.tv accessibility score

97

Accessibility Issues

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

livehouse.tv best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

livehouse.tv SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Livehouse.tv can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Livehouse.tv 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

livehouse.tv

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