8.3 sec in total
851 ms
7.1 sec
363 ms
Click here to check amazing Nntt Jac content for Japan. Otherwise, check out these important facts you probably never knew about nntt.jac.go.jp
新国立劇場のオフィシャルサイトです。新国立劇場では、オペラ、バレエ、ダンス、演劇など最高水準の現代舞台芸術を発信し続けます。
Visit nntt.jac.go.jpWe analyzed Nntt.jac.go.jp page load time and found that the first response time was 851 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
nntt.jac.go.jp performance score
name
value
score
weighting
Value8.9 s
0/100
10%
Value10.0 s
0/100
25%
Value29.1 s
0/100
10%
Value1,070 ms
25/100
30%
Value0.563
12/100
15%
Value16.5 s
5/100
10%
851 ms
469 ms
490 ms
500 ms
499 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 82% of them (80 requests) were addressed to the original Nntt.jac.go.jp, 7% (7 requests) were made to Google.com and 3% (3 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Nntt.jac.go.jp.
Page size can be reduced by 540.2 kB (28%)
1.9 MB
1.4 MB
In fact, the total size of Nntt.jac.go.jp main page is 1.9 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. 35% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 37.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 7.8 kB, which is 17% 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.0 kB or 82% of the original size.
Potential reduce by 31.4 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. Nntt Jac images are well optimized though.
Potential reduce by 284.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 284.8 kB or 66% of the original size.
Potential reduce by 186.9 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. Nntt.jac.go.jp needs all CSS files to be minified and compressed as it can save up to 186.9 kB or 88% of the original size.
Number of requests can be reduced by 34 (36%)
95
61
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nntt Jac. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
nntt.jac.go.jp
851 ms
base.css
469 ms
layout.css
490 ms
contents.css
500 ms
tablet.css
499 ms
smartphone.css
546 ms
notosansjapanese.css
25 ms
colorbox.css
522 ms
home.css
1241 ms
jquery.js
1290 ms
jquery.plugin.js
858 ms
common.js
1048 ms
underscore.js
1248 ms
json2.js
1040 ms
backbone.js
1483 ms
extend.Date.js
1370 ms
Calendar.js
1368 ms
daily_calendar.js
1561 ms
jquery.bxslider.js
1790 ms
jquery.colorbox.js
1620 ms
home.js
1836 ms
google_analytics.js
1683 ms
ga_social_tracking.js
1793 ms
ga_twitter.js
1887 ms
ga_facebook.js
1952 ms
sidebar_partner.js
2018 ms
google_search.js
2118 ms
footer.js
1981 ms
ga.js
28 ms
widgets.js
12 ms
pc_cmn_logo01.png
306 ms
cmn_genre_nav02_10.png
328 ms
cmn_genre_nav02_1.png
397 ms
cmn_genre_nav02_2.png
466 ms
cmn_genre_nav02_3.png
565 ms
cmn_genre_nav02_4.png
565 ms
cmn_genre_nav02_9.png
634 ms
cmn_genre_nav02_6.png
656 ms
cmn_genre_nav02_8.png
717 ms
cmn_genre_nav02_11.png
832 ms
cmn_genre_nav02_12.png
898 ms
cmn_genre_nav02.png
932 ms
cmn_genre_nav01_10.png
964 ms
cmn_genre_nav01_1.png
985 ms
cmn_genre_nav01_2.png
1053 ms
cmn_genre_nav01_3.png
1199 ms
cmn_genre_nav01_4.png
1215 ms
home_theatre_ph01.jpg
1552 ms
home_theatre_ph02.jpg
1624 ms
home_theatre_ph03.jpg
1617 ms
home_theatre_ph04.jpg
1594 ms
home_theatre_ph05.jpg
1924 ms
home_theatre_ph06.jpg
2117 ms
cmn_partner_logo02_6.png
1882 ms
cmn_partner_logo02_1.png
1925 ms
cmn_partner_logo02_2.png
1959 ms
cmn_partner_logo02_3.png
1983 ms
cmn_partner_logo02_4.png
2217 ms
cmn_partner_logo02_5.png
2253 ms
all.js
149 ms
cmn_partner_logo01.png
2132 ms
162 ms
xd_arbiter.php
151 ms
xd_arbiter.php
275 ms
cse.js
68 ms
cmn_link_ic05.png
2100 ms
cmn_ic02.png
2091 ms
cmn_link_ic06.png
2219 ms
cmn_ic04.png
2325 ms
cmn_link_ic08.png
2337 ms
topcalendar.json
3280 ms
ping
107 ms
cse.js
115 ms
news.json
2357 ms
visual.json
2340 ms
cmn_ic05.png
2440 ms
jsapi
37 ms
default+en.css
5 ms
default.css
48 ms
default+en.I.js
17 ms
home_bg01.jpg
4040 ms
default.css
50 ms
async-ads.js
65 ms
google_custom_search_watermark.gif
45 ms
small-logo.png
16 ms
cmn_bg01.png
2558 ms
cmn_link_ic01.png
2408 ms
cmn_jasrac_logo01.png
2363 ms
cmn_bn01.jpg
2510 ms
cmn_link_ic02.png
2597 ms
sp_cmn_logo01.png
2483 ms
cmn_partner_logo03.png
2557 ms
cmn_loading_ic02.gif
2553 ms
cmn_loading_ic01.gif
2675 ms
cmn_search_ic01.png
2661 ms
daily_calendar_tmpl.html
187 ms
cmn_slide_bt03.png
167 ms
cmn_slide_bt04.png
331 ms
nntt.jac.go.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
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
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
nntt.jac.go.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
nntt.jac.go.jp SEO score
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nntt.jac.go.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 Nntt.jac.go.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.
nntt.jac.go.jp
Open Graph data is detected on the main page of Nntt Jac. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: