Tools & Wizards About Us
thirdstage.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

thirdstage.com

サードステージ

Page Load Speed

4.8 sec in total

First Response

583 ms

Resources Loaded

3.9 sec

Page Rendered

303 ms

thirdstage.com screenshot

About Website

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

サードステージ公式ページへようこそ！鴻上尚史の最新公演情報・出演情報、サードステージ通信販売、ワークショップなどをご案内しています。

Visit thirdstage.com

Key Findings

We analyzed Thirdstage.com page load time and found that the first response time was 583 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 70% of websites can load faster.

Performance Metrics

thirdstage.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value16.8 s

0/100

25%

SI (Speed Index)

Value17.2 s

0/100

10%

TBT (Total Blocking Time)

Value26,760 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.181

67/100

15%

TTI (Time to Interactive)

Value43.7 s

0/100

10%

Network Requests Diagram

thirdstage.com

583 ms

style.css

183 ms

thickbox.css

355 ms

slider-pro.css

354 ms

add_style.css

363 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 77% of them (80 requests) were addressed to the original Thirdstage.com, 20% (21 requests) were made to Platform.twitter.com and 3% (3 requests) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Thirdstage.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (45%)

Content Size

2.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 37.3 kB

  • Original 44.1 kB
  • After minification 27.1 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 17.0 kB, which is 39% 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 37.3 kB or 85% of the original size.

Image Optimization

-46%

Potential reduce by 961.0 kB

  • Original 2.1 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. Obviously, Thirdstage needs image optimization as it can save up to 961.0 kB or 46% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-20%

Potential reduce by 20.2 kB

  • Original 102.2 kB
  • After minification 101.2 kB
  • After compression 82.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 20.2 kB or 20% of the original size.

CSS Optimization

-29%

Potential reduce by 4.1 kB

  • Original 14.1 kB
  • After minification 13.9 kB
  • After compression 10.0 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. Thirdstage.com needs all CSS files to be minified and compressed as it can save up to 4.1 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (42%)

Requests Now

102

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thirdstage.com

thirdstage.com

583 ms

style.css

style.css

183 ms

thickbox.css

thickbox.css

355 ms

slider-pro.css

slider-pro.css

354 ms

add_style.css

add_style.css

363 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

548 ms

jquery.cookie.js

jquery.cookie.js

368 ms

flatheights.js

flatheights.js

373 ms

thickbox.js

thickbox.js

530 ms

jquery.sliderPro.min.js

jquery.sliderPro.min.js

706 ms

functions_index.js

functions_index.js

544 ms

functions.js

functions.js

545 ms

logo.png

logo.png

565 ms

58.png

58.png

1408 ms

60.png

60.png

2533 ms

44.png

44.png

1450 ms

52.png

52.png

1638 ms

center_asahi.jpg

center_asahi.jpg

943 ms

acacia2023thirdcenter.jpg

acacia2023thirdcenter.jpg

1057 ms

latest-news.png

latest-news.png

1122 ms

whatsnew.png

whatsnew.png

1282 ms

onlineshop-banner.png

onlineshop-banner.png

1311 ms

nav01.png

nav01.png

560 ms

widgets.js

widgets.js

45 ms

onlineshop.png

onlineshop.png

1409 ms

item55.jpg

item55.jpg

1496 ms

icon-new.gif

icon-new.gif

1583 ms

item56.jpg

item56.jpg

1585 ms

item46.jpg

item46.jpg

1630 ms

item48.jpg

item48.jpg

1685 ms

item52.jpg

item52.jpg

1761 ms

item50.jpg

item50.jpg

1761 ms

item51.jpg

item51.jpg

1813 ms

item40.jpg

item40.jpg

1818 ms

item16.jpg

item16.jpg

1893 ms

more-item.jpg

more-item.jpg

1956 ms

workshop2024lab.jpg

workshop2024lab.jpg

1957 ms

lecturebanner.jpg

lecturebanner.jpg

1995 ms

nav02.png

nav02.png

559 ms

nav03.png

nav03.png

559 ms

nav04.png

nav04.png

558 ms

instractor.jpg

instractor.jpg

2000 ms

englishsite.jpg

englishsite.jpg

1883 ms

lesson.jpg

lesson.jpg

1765 ms

newadd.jpg

newadd.jpg

1765 ms

dora_bnr.jpg

dora_bnr.jpg

1815 ms

bh_bnr2020.jpg

bh_bnr2020.jpg

1820 ms

bh_lb.jpg

bh_lb.jpg

1879 ms

asahi2014b.jpg

asahi2014b.jpg

1767 ms

kifushamu-right.jpg

kifushamu-right.jpg

1753 ms

daisanbutai_s6.jpg

daisanbutai_s6.jpg

1821 ms

mail-banner200.png

mail-banner200.png

1809 ms

thirdstageM-head.png

thirdstageM-head.png

1873 ms

thirdstageM-button.jpg

thirdstageM-button.jpg

1764 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

148 ms

settings

settings

71 ms

news.html

news.html

1533 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

22 ms

thirdstage_M

thirdstage_M

824 ms

kyokou

kyokou

104 ms

feed.php

feed.php

1639 ms

kyokou-head.png

kyokou-head.png

1431 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

22 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

50 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

68 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

81 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

81 ms

%5Bslug%5D-bbaf0ad3c99bb35955c4.js

%5Bslug%5D-bbaf0ad3c99bb35955c4.js

112 ms

_buildManifest.js

_buildManifest.js

129 ms

_ssgManifest.js

_ssgManifest.js

130 ms

kyokou-button.jpg

kyokou-button.jpg

1344 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

22 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

20 ms

body-bg.jpg

body-bg.jpg

1339 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

22 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

37 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

44 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

60 ms

6426.c62f237d2be1a2371308.js

6426.c62f237d2be1a2371308.js

18 ms

html-bg.jpg

html-bg.jpg

1242 ms

wrap-bg.jpg

wrap-bg.jpg

1304 ms

container.jpg

container.jpg

1287 ms

whatnew-bottom.png

whatnew-bottom.png

1317 ms

banner-line.gif

banner-line.gif

1242 ms

onlineshop-bottom.png

onlineshop-bottom.png

1240 ms

info-box-middle.gif

info-box-middle.gif

1244 ms

info-box-head.png

info-box-head.png

1260 ms

info-box-bottom.png

info-box-bottom.png

1234 ms

nav.png

nav.png

1242 ms

nav-arrow.gif

nav-arrow.gif

1239 ms

thirdstageM-body.jpg

thirdstageM-body.jpg

1188 ms

thirdstageM-foot.jpg

thirdstageM-foot.jpg

1239 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

39 ms

kyokou-body.jpg

kyokou-body.jpg

1176 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

23 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

24 ms

kyokou-foot.jpg

kyokou-foot.jpg

1144 ms

footer-body.gif

footer-body.gif

1221 ms

footer-head.jpg

footer-head.jpg

1193 ms

loadingAnimation.gif

loadingAnimation.gif

1178 ms

openhand.cur

openhand.cur

1178 ms

news.css

news.css

789 ms

jquery.js

jquery.js

815 ms

news.js

news.js

884 ms

Accessibility Review

thirdstage.com accessibility score

55

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

thirdstage.com best practices score

50

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

thirdstage.com SEO score

62

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thirdstage.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 Thirdstage.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

thirdstage.com

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