6.1 sec in total
985 ms
4.5 sec
633 ms
Visit todai.tv now to see the best up-to-date Todai content for Japan and also check out these interesting facts you probably never knew about todai.tv
東京大学で開催された公開講座や講演会、シンポジウムなどの動画を学内外の皆さまにお届けする大学公式Webサイトです。
Visit todai.tvWe analyzed Todai.tv page load time and found that the first response time was 985 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.
todai.tv performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value9.7 s
0/100
25%
Value16.1 s
0/100
10%
Value8,430 ms
0/100
30%
Value0.192
64/100
15%
Value19.1 s
3/100
10%
985 ms
709 ms
387 ms
403 ms
7 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 43% of them (36 requests) were addressed to the original Todai.tv, 12% (10 requests) were made to Pbs.twimg.com and 10% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Todai.tv.
Page size can be reduced by 144.0 kB (5%)
3.2 MB
3.1 MB
In fact, the total size of Todai.tv main page is 3.2 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 3.1 MB which makes up the majority of the site volume.
Potential reduce by 38.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. This page needs HTML code to be minified as it can gain 14.3 kB, which is 30% 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 38.0 kB or 79% of the original size.
Potential reduce by 53.1 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. Todai images are well optimized though.
Potential reduce by 26.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 26.1 kB or 48% of the original size.
Potential reduce by 26.7 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. Todai.tv needs all CSS files to be minified and compressed as it can save up to 26.7 kB or 85% of the original size.
Number of requests can be reduced by 28 (35%)
80
52
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Todai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
todai.tv
985 ms
base-cachekey-3bcd326496e670392ca2810c9005787a.css
709 ms
resourceplone.app.jquerytools.dateinput-cachekey-78422b9c8bcac297425312e53f96fa79.css
387 ms
resourcecollective.z3cform.datagridfielddatagridfield-cachekey-8f83e0d234264eae96d1055dc56802ce.css
403 ms
cssreset-min.css
7 ms
themeut.tv.sitecommoncssstyles-cachekey-b6f899ed105dfc2281d0fd550cef891c.css
649 ms
ploneCustom-cachekey-da12eedc0786a12c03013b9b5c62fed1.css
709 ms
at-cachekey-e98d268508ed920b54f02c392b565f63.kss
756 ms
resourceplone.app.jquery-cachekey-304238f857fb451d90fbdb8853b617a3.js
1722 ms
resourceplone.formwidget.autocompletejquery.autocomplete.min-cachekey-b8a477c9db6594d76c6f3e7e6b5bac69.js
1559 ms
swfobject.js
1086 ms
jquery.strobemediaplayback.js
1289 ms
36x60.png
597 ms
bg_header.png
225 ms
logo.png
432 ms
416dd017-3203-4b8a-a004-d4679d298dc4.jpeg
673 ms
5ae0201d-6e47-4396-8351-7b5ca001e972.jpeg
449 ms
c87f6467-d3e7-465c-ace5-495fe592d462.jpeg
467 ms
d8377a48-446c-4f3c-b8fe-e823747349c6.jpeg
448 ms
a089436e-2c69-4951-b21e-7b5d5cc2a189.jpeg
688 ms
d2c92b03-938f-4a58-a2cb-2cd95125c984.jpeg
918 ms
7c4fd889-ae73-4c92-986c-fbbc95d3d605.jpeg
911 ms
6eaa90cf-f0e6-4901-abdb-60b8bfbcc27a.jpeg
916 ms
31054e6b-2172-4862-828a-9d1349e6ba9a.jpeg
887 ms
716f9477-8acd-43a9-8016-727e1498b298.jpeg
1093 ms
1c300606-4ebf-48df-874f-1c5c562da5b7.jpeg
1108 ms
f0481152-320b-4c29-b3a8-8254812045bc.jpeg
1308 ms
964b8b98-ee9c-4409-a5c4-389eb04bf18f.jpeg
1282 ms
718094c3-39b3-49a7-b08f-c97aa7a9f4bf.jpeg
1285 ms
278bb2fc-8cc2-45d4-aff1-bf0f0e78a768.jpeg
1336 ms
icon-lock-green.png
1470 ms
btn-search-small.png
1496 ms
icon-arrow-r-white.png
1661 ms
logo-todai-gray.png
1662 ms
spinner.gif
1723 ms
icon-calendar-gray.png
1737 ms
icon-person-gray.png
1820 ms
widgets.js
10 ms
plusone.js
88 ms
ga.js
44 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
22 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
31 ms
__utm.gif
19 ms
like.php
190 ms
syndication
127 ms
558419770140131328
257 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
25 ms
cb=gapi.loaded_0
29 ms
cb=gapi.loaded_1
63 ms
fastbutton
129 ms
postmessageRelay
45 ms
3193398744-postmessagerelay.js
35 ms
rpc:shindig_random.js
37 ms
cb=gapi.loaded_0
16 ms
cb=gapi.loaded_1
12 ms
grlryt2bdKIyfMSOhzd1eA.woff
49 ms
cb=gapi.loaded_0
11 ms
Dt46LmMjzaB.js
344 ms
LVx-xkvaJ0b.png
379 ms
proxy.jpg
221 ms
proxy.jpg
34 ms
proxy.jpg
37 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
11 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
15 ms
bWnBLT5R_normal.png
251 ms
aLlhgCpG_normal.jpg
275 ms
5BD0qvYB_normal.jpg
364 ms
UwEP1G0j_normal.png
355 ms
twitter_______normal.jpg
360 ms
Cd0tktVUsAAKLpY.jpg:small
460 ms
CdqAGCIUkAEjbQB.jpg:small
455 ms
Cdl-EVrUMAAA9S4.jpg:small
463 ms
CdkHICoUYAAYOGR.jpg:small
613 ms
Cdemxv_UEAE64vw.jpg:small
600 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
31 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
40 ms
36x60.png
340 ms
proxy.jpg
215 ms
proxy.jpg
67 ms
proxy.jpg
43 ms
jot.html
4 ms
mobile-cachekey-8a010fa832192e4a2902fa824d885777.css
186 ms
__utm.gif
4 ms
todai.tv 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
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
todai.tv 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
Missing source maps for large first-party JavaScript
todai.tv SEO score
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Todai.tv 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 Todai.tv 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.
todai.tv
Open Graph data is detected on the main page of Todai. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: