8.2 sec in total
536 ms
7.4 sec
291 ms
Click here to check amazing Shiki content for Japan. Otherwise, check out these important facts you probably never knew about shiki.jp
劇団四季オフィシャルウェブサイト。劇団四季が上演する全公演のチケットは、当ウェブサイト「SHIKI-ONLINE TICKET」より、24時間いつでもお求めいただけます。その他、上演作品の概要や最新情報を随時更新。
Visit shiki.jpWe analyzed Shiki.jp page load time and found that the first response time was 536 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
shiki.jp performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value30.2 s
0/100
25%
Value32.8 s
0/100
10%
Value410 ms
67/100
30%
Value0.009
100/100
15%
Value21.1 s
1/100
10%
536 ms
573 ms
1130 ms
616 ms
1253 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 93% of them (123 requests) were addressed to the original Shiki.jp, 2% (2 requests) were made to Ssl.google-analytics.com and 1% (1 request) were made to Mb.shiki.jp. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Shiki.jp.
Page size can be reduced by 367.4 kB (44%)
829.3 kB
461.9 kB
In fact, the total size of Shiki.jp main page is 829.3 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. 25% of websites need less resources to load. Images take 345.9 kB which makes up the majority of the site volume.
Potential reduce by 37.6 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 37.6 kB or 81% of the original size.
Potential reduce by 27.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. Shiki images are well optimized though.
Potential reduce by 197.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 197.8 kB or 63% of the original size.
Potential reduce by 104.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. Shiki.jp needs all CSS files to be minified and compressed as it can save up to 104.4 kB or 86% of the original size.
Number of requests can be reduced by 51 (40%)
128
77
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shiki. 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 5 to 1 for CSS and as a result speed up the page load time.
shiki.jp
536 ms
mb.shiki.jp
573 ms
www.shiki.jp
1130 ms
header.css
616 ms
local.css
1253 ms
local.css
984 ms
jquery.mCustomScrollbar.min.css
833 ms
jsapi
35 ms
loadLP.js
716 ms
require.js
902 ms
require_front_index_live.js
772 ms
front_index.js
891 ms
init.js
776 ms
targetingArea.js
846 ms
targetingAreaToPref.js
918 ms
targetingKeyVisualConf.js
930 ms
header_area_utf.js
931 ms
targetingKeyVisual.js
843 ms
modal_window.js
708 ms
front_stage_schedule.js
792 ms
reset.css
282 ms
loadLP.php
262 ms
img_logo.gif
158 ms
id_none.png
159 ms
loader.gif
356 ms
id_login_btn.gif
184 ms
id_next_title.png
332 ms
id_next_btn.gif
165 ms
id.png
314 ms
bg_area_set.png
315 ms
img_main_visual_1.jpg
490 ms
btn_gnav_0025.gif
363 ms
img_fukidashi.png
469 ms
btn_gnav_0065.gif
480 ms
btn_gnav_0057.gif
496 ms
btn_gnav_0011.gif
532 ms
btn_gnav_0041.gif
541 ms
btn_gnav_0028.gif
623 ms
btn_gnav_0014.gif
637 ms
btn_gnav_0077.gif
652 ms
btn_gnav_0073.gif
661 ms
btn_gnav_0079.gif
708 ms
btn_gnav_0019.gif
720 ms
btn_gnav_0045.gif
777 ms
btn_gnav_0066.gif
793 ms
btn_gnav_0016.gif
814 ms
slide_83.jpg
1155 ms
slide_104.jpg
1059 ms
slide_103.jpg
1257 ms
slide_40.jpg
1084 ms
slide_87.jpg
1102 ms
slide_98.jpg
1138 ms
slide_102.jpg
1237 ms
slide_101.jpg
1393 ms
slide_99.jpg
1261 ms
slide_93.jpg
1301 ms
slide_3.jpg
1319 ms
app.js
1403 ms
ga.js
62 ms
pix-shiki-min.js
734 ms
__utm.gif
12 ms
front_index.js
1288 ms
underscore.string.js
1271 ms
collect
56 ms
jquery-1.7.2.js
1797 ms
slider_prev.png
1312 ms
slider_next.png
1247 ms
loading.gif
1287 ms
bnr_shikiplus.jpg
1408 ms
bnr_warning.jpg
1449 ms
nav_btn_7.gif
1299 ms
nav_btn_t.gif
1247 ms
nav_btn_l.gif
1299 ms
nav_btn_5.gif
1338 ms
nav_btn_6.gif
1375 ms
nav_btn_1.gif
1363 ms
nav_btn_2.gif
1416 ms
nav_btn_8.gif
1359 ms
info_title.gif
1356 ms
event_title.gif
1374 ms
media_title.gif
1389 ms
today_title.gif
1427 ms
back_btn.gif
1400 ms
footer_btn_01.gif
1384 ms
footer_btn_04.gif
1365 ms
ecotag.php
695 ms
footer_btn_03.gif
1369 ms
footer_btn_07.gif
1145 ms
footer_btn_06.gif
1198 ms
footer_btn_05.gif
1206 ms
footer_btn_r.jpg
1183 ms
copyright.gif
1185 ms
loader.gif
1100 ms
btn_gnav_0025_on.gif
1105 ms
btn_gnav_0065_on.gif
1184 ms
btn_gnav_0057_on.gif
1183 ms
btn_gnav_0011_on.gif
1169 ms
btn_gnav_0041_on.gif
1099 ms
base_view.js
1103 ms
stage_list_top.js
1096 ms
key_visual.js
1173 ms
global_nav.js
1177 ms
tag.js
25 ms
tag
54 ms
front_index.js
1105 ms
moment.ja.js
1208 ms
underscore.js
1022 ms
base_router.js
990 ms
btn_gnav_0028_on.gif
1042 ms
btn_gnav_0014_on.gif
1050 ms
btn_gnav_0077_on.gif
1048 ms
btn_gnav_0073_on.gif
1011 ms
btn_gnav_0079_on.gif
1013 ms
btn_gnav_0019_on.gif
1049 ms
btn_gnav_0045_on.gif
1008 ms
jquery.easing.js
1021 ms
jquery.plugins.js
1014 ms
jquery.transit.js
1033 ms
jquery.cookie.js
1039 ms
btn_gnav_0066_on.gif
1056 ms
btn_gnav_0016_on.gif
998 ms
main_bg.gif
1026 ms
main_bg_inner.gif
995 ms
today_bg.gif
1043 ms
img.js
723 ms
browser.js
746 ms
const_stage_schedule.js
753 ms
const_front_index.js
696 ms
backbone.js
807 ms
jquery.slider.js
388 ms
pageTopSW.js
430 ms
id_member_info.php
413 ms
shiki.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
shiki.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
shiki.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shiki.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 Shiki.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.
shiki.jp
Open Graph data is detected on the main page of Shiki. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: