2 sec in total
201 ms
1.7 sec
192 ms
Click here to check amazing Rokka content. Otherwise, check out these important facts you probably never knew about rokka.jp
横浜市交通局資産活用ポータルサイト。横浜市営地下鉄の駅をもっと便利に楽しく。駅ナカ周辺情報サイト。
Visit rokka.jpWe analyzed Rokka.jp page load time and found that the first response time was 201 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
rokka.jp performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value9.2 s
1/100
25%
Value8.4 s
19/100
10%
Value130 ms
96/100
30%
Value0.219
57/100
15%
Value9.3 s
31/100
10%
201 ms
474 ms
260 ms
435 ms
252 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Rokka.jp, 90% (44 requests) were made to Yokohamakotsu-shisan.jp and 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (478 ms) relates to the external source Yokohamakotsu-shisan.jp.
Page size can be reduced by 331.9 kB (47%)
710.5 kB
378.6 kB
In fact, the total size of Rokka.jp main page is 710.5 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. 35% of websites need less resources to load. Javascripts take 428.9 kB which makes up the majority of the site volume.
Potential reduce by 11.2 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 11.2 kB or 73% of the original size.
Potential reduce by 19.5 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. Rokka images are well optimized though.
Potential reduce by 241.1 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 241.1 kB or 56% of the original size.
Potential reduce by 60.1 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. Rokka.jp needs all CSS files to be minified and compressed as it can save up to 60.1 kB or 84% of the original size.
Number of requests can be reduced by 12 (26%)
47
35
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rokka. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
rokka.jp
201 ms
yokohamakotsu-shisan.jp
474 ms
jquery.js
260 ms
jquery-ui.min.js
435 ms
jquery.lightbox-0.5.js
252 ms
jquery.peak.js
197 ms
jquery.inc.js
198 ms
js
55 ms
js
61 ms
jquery-ui.css
271 ms
jquery.lightbox-0.5.css
270 ms
base.css
328 ms
smartphone.css
313 ms
ga.js
66 ms
layout.css
78 ms
title.gif
87 ms
headlink.gif
84 ms
mainmenu_01.gif
86 ms
mainmenu_03.gif
87 ms
mainmenu_04.gif
83 ms
mainmenu_02.gif
92 ms
mainmenu_05.gif
145 ms
welcome.jpg
208 ms
title_toppage_map.jpg
217 ms
title_toppage_search_from_line.gif
152 ms
fullmap.gif
218 ms
blank.gif
157 ms
title_toppage_search_from_name.gif
207 ms
tabtitle_blueline.gif
217 ms
tabtitle_greenline.gif
223 ms
banner_contact_us_3168.gif
269 ms
title_news.gif
271 ms
link_pastnews.gif
283 ms
title_info.gif
282 ms
link_pastinfo.gif
283 ms
banner_eventspace.gif
288 ms
banner_lease.gif
331 ms
title_related.gif
333 ms
kotsukyoku.gif
347 ms
hamaeco-card.png
478 ms
mainmenu_01_ro.gif
349 ms
__utm.gif
32 ms
bg.gif
379 ms
header.jpg
354 ms
menu_bg.gif
357 ms
main_bg.gif
374 ms
marker_blueline.png
376 ms
marker_greenline.png
417 ms
print.css
67 ms
rokka.jp accessibility score
rokka.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
rokka.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 Rokka.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 Rokka.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.
rokka.jp
Open Graph description is not detected on the main page of Rokka. 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: