4.8 sec in total
761 ms
3.2 sec
840 ms
Visit tokyo-toden-diary.jp now to see the best up-to-date Tokyo Toden Diary content for Japan and also check out these interesting facts you probably never knew about tokyo-toden-diary.jp
10月1日は「荒川線の日」。そして今年は、都電が市電として誕生して105周年の年。東京都交通局では「東京都電diary」と題し、皆さんの思い出エピソードを募集しました。
Visit tokyo-toden-diary.jpWe analyzed Tokyo-toden-diary.jp page load time and found that the first response time was 761 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
tokyo-toden-diary.jp performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value31.6 s
0/100
25%
Value12.4 s
3/100
10%
Value190 ms
90/100
30%
Value0
100/100
15%
Value17.3 s
4/100
10%
761 ms
13 ms
24 ms
184 ms
349 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 84% of them (38 requests) were addressed to the original Tokyo-toden-diary.jp, 4% (2 requests) were made to Maxcdn.bootstrapcdn.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Tokyo-toden-diary.jp.
Page size can be reduced by 161.1 kB (3%)
5.8 MB
5.6 MB
In fact, the total size of Tokyo-toden-diary.jp main page is 5.8 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. 50% of websites need less resources to load. Images take 5.6 MB which makes up the majority of the site volume.
Potential reduce by 24.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 24.0 kB or 72% of the original size.
Potential reduce by 96.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. Tokyo Toden Diary images are well optimized though.
Potential reduce by 39.4 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 39.4 kB or 36% of the original size.
Potential reduce by 1.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. Tokyo-toden-diary.jp needs all CSS files to be minified and compressed as it can save up to 1.2 kB or 19% of the original size.
Number of requests can be reduced by 12 (27%)
44
32
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tokyo Toden Diary. 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.
tokyo-toden-diary.jp
761 ms
font-awesome.min.css
13 ms
font-awesome.min.css
24 ms
reset.css
184 ms
layout.css
349 ms
form.css
353 ms
new2.css
363 ms
typesquare.js
246 ms
jquery.min.js
14 ms
jquery.libs.js
446 ms
jquery.pjax.js
450 ms
main3.js
444 ms
jquery.imageScroll.js
649 ms
analytics.js
69 ms
head_logo.gif
195 ms
logo.png
439 ms
2.jpg
1087 ms
1.png
545 ms
3.jpg
878 ms
4.png
438 ms
6.png
1246 ms
7.png
1089 ms
5.png
588 ms
02-306x350.png
729 ms
01.png
1669 ms
1125-256x350.png
923 ms
01.png
1412 ms
1129-256x350-259x350.png
1108 ms
02.jpg
1456 ms
1121-306x350.png
1272 ms
02.png
1847 ms
0220-259x350.png
1426 ms
02.jpg
1465 ms
8.png
1593 ms
00001.png
1608 ms
name_banner.png
1637 ms
en_tekist.png
1649 ms
toden_title.png
1769 ms
f_logo.gif
1789 ms
collect
72 ms
ico_footer.gif
1631 ms
cover1.jpg
1589 ms
cover2.jpg
1603 ms
cover3.jpg
1707 ms
js
64 ms
tokyo-toden-diary.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
tokyo-toden-diary.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
tokyo-toden-diary.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Tokyo-toden-diary.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 Tokyo-toden-diary.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-toden-diary.jp
Open Graph data is detected on the main page of Tokyo Toden Diary. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: