5.6 sec in total
550 ms
4.8 sec
225 ms
Click here to check amazing Tokyo Doken content for Japan. Otherwise, check out these important facts you probably never knew about tokyo-doken.or.jp
Visit tokyo-doken.or.jpWe analyzed Tokyo-doken.or.jp page load time and found that the first response time was 550 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
tokyo-doken.or.jp performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value8.0 s
2/100
25%
Value17.8 s
0/100
10%
Value90 ms
99/100
30%
Value0.005
100/100
15%
Value9.0 s
34/100
10%
550 ms
1492 ms
359 ms
374 ms
739 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 81% of them (89 requests) were addressed to the original Tokyo-doken.or.jp, 10% (11 requests) were made to Pbs.twimg.com and 5% (5 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Tokyo-doken.or.jp.
Page size can be reduced by 142.1 kB (14%)
998.1 kB
856.0 kB
In fact, the total size of Tokyo-doken.or.jp main page is 998.1 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. 45% of websites need less resources to load. Images take 872.1 kB which makes up the majority of the site volume.
Potential reduce by 27.7 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.1 kB, which is 21% 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 27.7 kB or 82% of the original size.
Potential reduce by 59.8 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. Tokyo Doken images are well optimized though.
Potential reduce by 46.2 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 46.2 kB or 57% of the original size.
Potential reduce by 8.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. Tokyo-doken.or.jp needs all CSS files to be minified and compressed as it can save up to 8.4 kB or 76% of the original size.
Number of requests can be reduced by 17 (16%)
106
89
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tokyo Doken. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
tokyo-doken.or.jp
550 ms
pc_index.php
1492 ms
jquery-1.2.3.min.js
359 ms
menu.js
374 ms
jquery.js
739 ms
yuga.js
379 ms
basic2013.css
409 ms
style.css
535 ms
15style.css
557 ms
dokenannai2016-300x188.jpg
364 ms
wall.jpg
211 ms
logo.jpg
356 ms
telNo.png
188 ms
arrow_right_s.png
190 ms
korea.gif
194 ms
title_news.jpg
294 ms
banner_work_boshu_01.gif
371 ms
more.png
380 ms
sub_sasayaki.jpg
386 ms
news_sasayaki.jpg
420 ms
news_twitter.jpg
459 ms
sub_shigotoNET.jpg
542 ms
sub_shikaku.jpg
548 ms
doken-top.png
2282 ms
shibu-title.png
588 ms
btnAdachi.png
646 ms
btnArakawa.png
645 ms
btnItabashi.png
740 ms
btnEdogawa.png
741 ms
btnOta.png
771 ms
btnKatsushika.png
808 ms
btnKita.png
853 ms
btnKiyoseKurume.png
900 ms
btnKoto.png
899 ms
btnKoganeiKokubunji.png
963 ms
btnKodaira.png
966 ms
btnKomae.png
1061 ms
btnShibuya.png
1077 ms
btnShinjyuku.png
1081 ms
btnSuginami.png
1155 ms
btnSumida.png
1126 ms
btnSetagaya.png
1268 ms
btnTaito.png
1253 ms
btnTamaInagi.png
1260 ms
btnTamaseibu.png
1277 ms
widgets.js
87 ms
ga.js
4 ms
__utm.gif
11 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
137 ms
btnChofu.png
1209 ms
btnToshima.png
1248 ms
btnNakano.png
1256 ms
btnNishitama.png
1285 ms
btnNishitokyo.png
1243 ms
syndication
78 ms
337356060140662784
236 ms
btnNerima.png
1249 ms
btnHachioji.png
1258 ms
btnHigashimurayama.png
1255 ms
btnHino.png
1235 ms
btnFuchukunitachi.png
1298 ms
btnBunkyo.png
1318 ms
btnMachida.png
1331 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
31 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
100 ms
btnMitakamusashino.png
1232 ms
btnMinato.png
1260 ms
icon_twitter_normal.jpg
233 ms
default_profile_0_normal.png
68 ms
QE8-nACh_normal.png
257 ms
nqB6Om5V_normal.jpg
336 ms
___002_normal.jpg
333 ms
E-sh5j0a_normal.jpg
400 ms
CYVasE9UEAAom7Q.jpg:small
369 ms
CWtuSSQUwAA_E1X.jpg:small
366 ms
CSnnwDaUcAAsbWT.jpg:small
345 ms
CQnizQqUkAAv54m.jpg:small
472 ms
CQnizQyUkAA5-vJ.jpg:small
480 ms
CQnizQ2VAAAztwS.jpg:small
498 ms
btnMurayamayamato.png
1298 ms
btnMeguro.png
1283 ms
btnSpace360.png
1288 ms
btn_spacer_mini.png
1223 ms
btn_spacer.png
1245 ms
btnSpace135.png
1324 ms
osusumePlate.png
1313 ms
contents01.png
1244 ms
contents02.png
1240 ms
contents03.png
1271 ms
contents04.png
1339 ms
contents05.png
1296 ms
jot.html
30 ms
contents06.png
1264 ms
contents07.png
1246 ms
contents08.png
1275 ms
contents09.png
1297 ms
contents10.png
1315 ms
footer.jpg
1257 ms
panffBtn.png
1410 ms
shibuBtn.png
1250 ms
kensetsuBtn.png
1251 ms
top_kanyu.jpg
1239 ms
kanyu_btn.png
1235 ms
shiryou_btn.png
1274 ms
banner_keisan.png
1262 ms
banner01.png
1418 ms
banner02.png
1205 ms
banner03.png
1252 ms
banner04.png
1238 ms
more_on.png
1280 ms
tokyo-doken.or.jp accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
tokyo-doken.or.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
Browser errors were logged to the console
tokyo-doken.or.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 uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokyo-doken.or.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tokyo-doken.or.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.
tokyo-doken.or.jp
Open Graph description is not detected on the main page of Tokyo Doken. 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: