9.6 sec in total
745 ms
8.6 sec
244 ms
Click here to check amazing Operacity content for Japan. Otherwise, check out these important facts you probably never knew about operacity.jp
西新宿・初台にある複合文化施設「東京オペラシティ」。コンサートホール/リサイタルホールのコンサート情報。アートギャラリーの展覧会情報。Arts友の会情報など。
Visit operacity.jpWe analyzed Operacity.jp page load time and found that the first response time was 745 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
operacity.jp performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value4.6 s
34/100
25%
Value8.8 s
16/100
10%
Value30 ms
100/100
30%
Value0.739
6/100
15%
Value4.2 s
86/100
10%
745 ms
1138 ms
343 ms
346 ms
349 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 93% of them (89 requests) were addressed to the original Operacity.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to S.yjtag.jp. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Operacity.jp.
Page size can be reduced by 269.1 kB (12%)
2.3 MB
2.0 MB
In fact, the total size of Operacity.jp 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. 25% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 19.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. 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 19.0 kB or 79% of the original size.
Potential reduce by 84.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. Operacity images are well optimized though.
Potential reduce by 144.6 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 144.6 kB or 60% of the original size.
Potential reduce by 20.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. Operacity.jp needs all CSS files to be minified and compressed as it can save up to 20.9 kB or 79% of the original size.
Number of requests can be reduced by 49 (53%)
93
44
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Operacity. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
operacity.jp
745 ms
www.operacity.jp
1138 ms
import.css
343 ms
import.js
346 ms
mFirefox.js
349 ms
rollover.js
364 ms
jcarousellite_1.0.1.pack.js
382 ms
carousel.js
382 ms
jquery.ui.core.js
684 ms
jquery.ui.widget.js
688 ms
jquery.rf.slideshow.js
695 ms
index2.js
724 ms
index_visual.css
569 ms
index.css
763 ms
general.css
610 ms
font.css
517 ms
base.css
730 ms
jquery-1.7.min.js
902 ms
smoothscroll.js
176 ms
simplelib.js
193 ms
subwindow.js
174 ms
bg_header01.gif
173 ms
logo01.png
175 ms
logo02.png
193 ms
line01.png
173 ms
ico_home01.png
191 ms
ico_arrowr01.png
183 ms
line02.png
343 ms
btn_arts01.jpg
344 ms
btn_tokyo01.jpg
522 ms
bg_navi01.jpg
362 ms
navi01.jpg
611 ms
navi02.jpg
573 ms
base.png
514 ms
arrow_left.png
515 ms
arrow_right.png
543 ms
arrow_down.png
685 ms
bg04.gif
686 ms
bg_concert01.gif
693 ms
h2_concert01.gif
904 ms
ico_recital01.gif
763 ms
bg_art01.gif
798 ms
h2_ag01.gif
856 ms
ico_plan01.gif
856 ms
ico_stock01.gif
866 ms
ico_projectn01.gif
953 ms
bg05.gif
987 ms
ico_arrow01.gif
1026 ms
btn_calender01.jpg
1027 ms
btn_seat01.jpg
1039 ms
btn_lineup01.jpg
1083 ms
btn_award01.jpg
1141 ms
btn_arts01.jpg
1363 ms
btn_aglineup.jpg
1196 ms
ico_arrow02.gif
1194 ms
bg_h201.gif
1208 ms
btn_topics01.jpg
1260 ms
tag.js
13 ms
analytics.js
23 ms
tag
13 ms
collect
12 ms
index_visual2.xml
1172 ms
ico_art01.gif
1207 ms
ico_ch01.gif
1207 ms
btn_news01.jpg
1563 ms
ico_arrowr04.gif
1266 ms
ico_arrow05.gif
1343 ms
navi03.jpg
1221 ms
navi04.jpg
1208 ms
btn_pagetop01.gif
1189 ms
ico_home02.gif
1122 ms
ico_arrowr02.gif
1212 ms
btn_arts02.gif
1202 ms
btn_tokyo02.gif
1178 ms
logo03.gif
1180 ms
copyright01.gif
1206 ms
line03.gif
1208 ms
160305.png
1402 ms
thum160305.png
563 ms
dot_gray.png
562 ms
160312.png
2305 ms
thum160312.png
642 ms
compo2016.png
2309 ms
thumcompo2016.png
736 ms
B_C.png
2336 ms
thumB_C.png
825 ms
exh184.png
1964 ms
thum_exh184.png
1005 ms
exh185-186.png
2099 ms
thumexh.png
1572 ms
dot_red.png
1744 ms
thum160305_over.png
1923 ms
index_print.css
174 ms
conversion_async.js
42 ms
34 ms
36 ms
operacity.jp accessibility score
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
operacity.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
operacity.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Operacity.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 Operacity.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.
operacity.jp
Open Graph description is not detected on the main page of Operacity. 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: