6.5 sec in total
537 ms
5.8 sec
206 ms
Click here to check amazing ZART content for Japan. Otherwise, check out these important facts you probably never knew about zart.jp
静岡市内最大規模の10スクリーン、新静岡セノバ9Fの都市型シネマコンプレックス
Visit zart.jpWe analyzed Zart.jp page load time and found that the first response time was 537 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
zart.jp performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value25.4 s
0/100
25%
Value19.9 s
0/100
10%
Value14,230 ms
0/100
30%
Value0.37
29/100
15%
Value26.9 s
0/100
10%
537 ms
1097 ms
330 ms
496 ms
498 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 55% of them (54 requests) were addressed to the original Zart.jp, 19% (19 requests) were made to Shizukatsu.sakura.ne.jp and 18% (18 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Shizukatsu.sakura.ne.jp.
Page size can be reduced by 244.8 kB (5%)
4.9 MB
4.6 MB
In fact, the total size of Zart.jp main page is 4.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. 60% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 16.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 16.6 kB or 71% of the original size.
Potential reduce by 69.3 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. ZART images are well optimized though.
Potential reduce by 127.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 127.8 kB or 62% of the original size.
Potential reduce by 31.2 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. Zart.jp needs all CSS files to be minified and compressed as it can save up to 31.2 kB or 83% of the original size.
Number of requests can be reduced by 45 (47%)
96
51
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ZART. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
zart.jp
537 ms
zart.jp
1097 ms
top.css
330 ms
default.css
496 ms
nivo-slider.css
498 ms
sp.css
683 ms
smoothscroll.js
512 ms
jquery_min_2.1.4.js
1369 ms
common.js
526 ms
swfobject.js
660 ms
jquery.nivo.slider.pack.js
663 ms
widgets.js
92 ms
conversion.js
88 ms
ga.js
42 ms
zart-bocchi1.jpg
1989 ms
bg_zart.jpg
175 ms
bg_footer.jpg
175 ms
bg_header.jpg
184 ms
zart_logo.png
183 ms
tickets.gif
178 ms
bg_screen.jpg
179 ms
bg_screen_img.jpg
349 ms
loading.gif
349 ms
rank01.png
368 ms
line-eq.gif
368 ms
rank02.png
370 ms
line-up.gif
368 ms
rank03.png
535 ms
new.gif
534 ms
rank04.png
546 ms
line-dw.gif
545 ms
rank05.png
548 ms
bnr_sound_pc.jpg
716 ms
bnr_atten_01.png
700 ms
bnr_atten_02.png
699 ms
bnr_atten_03.png
718 ms
icon_schedule.png
718 ms
icon_coming.png
723 ms
icon_yoyaku.png
864 ms
bnr_benz.jpg
1124 ms
bnr_luluca.jpg
1662 ms
mailmagazine.png
888 ms
mobile.jpg
888 ms
zuuka.jpg
898 ms
p.jpg
1030 ms
bnr_zartstyle.jpg
1058 ms
bnr_shiz-ori.jpg
1228 ms
mailmagazine.png
1074 ms
mobile.png
1196 ms
zart-dearfamily.jpg
1351 ms
zart-blue.jpg
1728 ms
zart-ikoku.jpg
1573 ms
zart-madmax.jpg
1733 ms
zart-takagisan.jpg
1453 ms
zart-abudeka.jpg
1847 ms
zart-umamusume.jpg
2467 ms
zart-conan2024.jpg
2406 ms
2023omoiyari-01.jpg
2574 ms
2023omoiyari-02.jpg
2582 ms
2023omoiyari-03.jpg
2509 ms
2023omoiyari-04.jpg
2637 ms
zart-parking.jpg
2577 ms
202405abu-deka.jpg
2641 ms
202404conan.jpg
2674 ms
202405takagi3.jpg
2744 ms
202405umamusume.jpg
2746 ms
202405madmax.jpg
2752 ms
bg_ranking.jpg
1213 ms
bg_navi.jpg
1235 ms
56 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
73 ms
__utm.gif
13 ms
collect
47 ms
51 ms
settings
99 ms
news_bottom.gif
1121 ms
news_ttl.gif
1233 ms
bg_news.gif
1279 ms
arrow_news.gif
1276 ms
arrow_newslink.gif
1277 ms
arrow_footernavi.gif
1278 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
22 ms
cinecity_zart
1025 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
26 ms
runtime-b1c52fd0a13ead5fcf6b.js
42 ms
modules-96ebc7ac3ad66d681a3d.js
82 ms
main-babd9234dc048fb47339.js
91 ms
_app-a9c9f1a99e4414675fb1.js
126 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
132 ms
_buildManifest.js
148 ms
_ssgManifest.js
148 ms
8526.0c32a8f0cfc5749221a3.js
22 ms
7651.a95a6a76dc7859214377.js
25 ms
8283.f3e5048cca7cef5eed7f.js
22 ms
3077.44bfeb00af01bc4020f6.js
41 ms
1362.42d432e02f7980bca032.js
55 ms
4956.c4e51ef593974b9db0bb.js
81 ms
5893.d500bd2a89ded806aa73.js
25 ms
bullets.gif
168 ms
zart.jp accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
zart.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
zart.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
![]()
JA
![]()
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zart.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 Zart.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
zart.jp
Open Graph description is not detected on the main page of ZART. 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: