Tools & Wizards About Us
livecircle.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

livecircle.jp

セットリスト・ライブ情報 | ライブサークル(LiveCircle)

Page Load Speed

5.7 sec in total

First Response

492 ms

Resources Loaded

4.7 sec

Page Rendered

575 ms

livecircle.jp screenshot

About Website

Click here to check amazing Live Circle content. Otherwise, check out these important facts you probably never knew about livecircle.jp

ライブサークルはセトリ(セットリスト)、ツアー、ライブ会場、アーティスト情報を掲載している音楽サイトです。ほぼ毎日更新中！

Visit livecircle.jp

Key Findings

We analyzed Livecircle.jp page load time and found that the first response time was 492 ms and then it took 5.2 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

livecircle.jp performance score

0

Network Requests Diagram

livecircle.jp

492 ms

www.livecircle.jp

1491 ms

v5_style.css

776 ms

formsbttn.css

650 ms

thickbox.css

337 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 26% of them (29 requests) were addressed to the original Livecircle.jp, 7% (8 requests) were made to Apis.google.com and 6% (7 requests) were made to C.betrad.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Livecircle.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 948.0 kB (71%)

Content Size

1.3 MB

After Optimization

381.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Livecircle.jp 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. 65% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 83.8 kB

  • Original 102.6 kB
  • After minification 101.8 kB
  • After compression 18.8 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 83.8 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 4.8 kB

  • Original 83.4 kB
  • After minification 78.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. Live Circle images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 785.7 kB

  • Original 1.1 MB
  • After minification 869.7 kB
  • After compression 271.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 785.7 kB or 74% of the original size.

CSS Optimization

-86%

Potential reduce by 73.7 kB

  • Original 86.1 kB
  • After minification 66.2 kB
  • After compression 12.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. Livecircle.jp needs all CSS files to be minified and compressed as it can save up to 73.7 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 70 (64%)

Requests Now

110

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

livecircle.jp

livecircle.jp

492 ms

www.livecircle.jp

www.livecircle.jp

1491 ms

v5_style.css

v5_style.css

776 ms

formsbttn.css

formsbttn.css

650 ms

thickbox.css

thickbox.css

337 ms

common.js

common.js

503 ms

prototype.js

prototype.js

1546 ms

jquery-latest.js

jquery-latest.js

2173 ms

thickbox.js

thickbox.js

854 ms

initcompletion.js

initcompletion.js

980 ms

complete.js

complete.js

1131 ms

ecl.js

ecl.js

1457 ms

show_ads.js

show_ads.js

17 ms

searchbox.js

searchbox.js

515 ms

bookmark_button.js

bookmark_button.js

311 ms

widgets.js

widgets.js

4 ms

ga.js

ga.js

39 ms

ir

ir

194 ms

button-only@2x.png

button-only@2x.png

176 ms

ir

ir

249 ms

ir

ir

192 ms

ir

ir

251 ms

ir

ir

249 ms

LC-Logo.png

LC-Logo.png

573 ms

rss.png

rss.png

337 ms

all.js

all.js

169 ms

shade1098.png

shade1098.png

334 ms

user.png

user.png

340 ms

horizonBlue.png

horizonBlue.png

394 ms

ca-pub-9620832686855223.js

ca-pub-9620832686855223.js

140 ms

zrt_lookup.html

zrt_lookup.html

139 ms

show_ads_impl.js

show_ads_impl.js

73 ms

__utm.gif

__utm.gif

77 ms

page_white_text.png

page_white_text.png

443 ms

s_icon_hall.gif

s_icon_hall.gif

613 ms

s_icon_arena.gif

s_icon_arena.gif

613 ms

s_icon_livehouse.gif

s_icon_livehouse.gif

644 ms

s_icon_eventspace.gif

s_icon_eventspace.gif

677 ms

s_icon_other.gif

s_icon_other.gif

696 ms

s_icon_cafe.gif

s_icon_cafe.gif

982 ms

s_icon_stadium.gif

s_icon_stadium.gif

993 ms

button_right.gif

button_right.gif

985 ms

button_left.gif

button_left.gif

1077 ms

ads

ads

337 ms

osd.js

osd.js

16 ms

ads

ads

334 ms

51kYVcW8pCL._SL160_.jpg

51kYVcW8pCL._SL160_.jpg

26 ms

417PxU9mUwL._SL160_.jpg

417PxU9mUwL._SL160_.jpg

25 ms

61PU6ITmppL._SL160_.jpg

61PU6ITmppL._SL160_.jpg

26 ms

51ZbR9NrDIL._SL160_.jpg

51ZbR9NrDIL._SL160_.jpg

23 ms

ads

ads

294 ms

131 ms

286 ms

41wt9lfv5hL._SL160_.jpg

41wt9lfv5hL._SL160_.jpg

44 ms

xd_arbiter.php

xd_arbiter.php

89 ms

xd_arbiter.php

xd_arbiter.php

261 ms

plusone.js

plusone.js

116 ms

btn.js

btn.js

66 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

51 ms

loadingAnimation.gif

loadingAnimation.gif

872 ms

button

button

106 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

27 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

65 ms

like.php

like.php

159 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

35 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

35 ms

fastbutton

fastbutton

136 ms

button.css

button.css

133 ms

shared.js

shared.js

156 ms

button.js

button.js

157 ms

s_0RRh1fUB2a_1188515087.html

s_0RRh1fUB2a_1188515087.html

153 ms

postmessageRelay

postmessageRelay

125 ms

s_0R5ahSIaHS_1792782484.html

s_0R5ahSIaHS_1792782484.html

103 ms

reset.css

reset.css

80 ms

entry-button.css

entry-button.css

79 ms

8i5wLKr4CIi.js

8i5wLKr4CIi.js

227 ms

s_0RRh1fUB2a_1188515087.html

s_0RRh1fUB2a_1188515087.html

89 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

232 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

49 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

49 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

124 ms

pocket_button.png

pocket_button.png

24 ms

bbtn-l_v3.png

bbtn-l_v3.png

18 ms

adServer.bs

adServer.bs

454 ms

creative_add_on.js

creative_add_on.js

175 ms

adServer.bs

adServer.bs

170 ms

creative_add_on.js

creative_add_on.js

185 ms

adServer.bs

adServer.bs

443 ms

creative_add_on.js

creative_add_on.js

181 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

72 ms

rpc:shindig_random.js

rpc:shindig_random.js

64 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

jot.html

jot.html

2 ms

ebHtml5PoliteBanner.js

ebHtml5PoliteBanner.js

310 ms

surly.js

surly.js

82 ms

surly.js

surly.js

76 ms

dvtp_src.js

dvtp_src.js

34 ms

ba.html

ba.html

92 ms

4.gif

4.gif

190 ms

dvtp_src_internal26.js

dvtp_src_internal26.js

6 ms

t2tv7.html

t2tv7.html

197 ms

visit.js

visit.js

214 ms

visit.js

visit.js

151 ms

2532.js

2532.js

21 ms

box_19_top-right.png

box_19_top-right.png

26 ms

backup.jpg

backup.jpg

41 ms

backup.jpg

backup.jpg

75 ms

ci.png

ci.png

17 ms

avs581.js

avs581.js

6 ms

event.jpg

event.jpg

56 ms

avs5639.js

avs5639.js

6 ms

event.gif

event.gif

79 ms

event.jpg

event.jpg

61 ms

SEO Factors

livecircle.jp SEO score

0

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

livecircle.jp

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