Tools & Wizards About Us
keio.ac.jp screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

keio.ac.jp

Keio University

Page Load Speed

2.9 sec in total

First Response

375 ms

Resources Loaded

1.8 sec

Page Rendered

676 ms

keio.ac.jp screenshot

About Website

Click here to check amazing Keio content for Japan. Otherwise, check out these important facts you probably never knew about keio.ac.jp

Keio University is a leading research university committed to excellence and innovation in education, research and medicine. It is located in central Tokyo.

Visit keio.ac.jp

Key Findings

We analyzed Keio.ac.jp page load time and found that the first response time was 375 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

keio.ac.jp performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value114.3 s

0/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.0 s

77/100

10%

Network Requests Diagram

keio.ac.jp

375 ms

211 ms

fonts.css

213 ms

base.css

9 ms

module_common.css

42 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 93% of them (67 requests) were addressed to the original Keio.ac.jp, 1% (1 request) were made to Cloud.typography.com and 1% (1 request) were made to Form.keio.ac.jp. The less responsive or slowest element that took the longest time to load (844 ms) relates to the external source Form.keio.ac.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.9 MB (26%)

Content Size

41.3 MB

After Optimization

30.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Keio.ac.jp main page is 41.3 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. Only a small number of websites need less resources to load. Images take 40.7 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 53.3 kB

  • Original 61.0 kB
  • After minification 43.5 kB
  • After compression 7.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 17.5 kB, which is 29% 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 53.3 kB or 87% of the original size.

Image Optimization

-26%

Potential reduce by 10.4 MB

  • Original 40.7 MB
  • After minification 30.3 MB

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. Obviously, Keio needs image optimization as it can save up to 10.4 MB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-37%

Potential reduce by 56.7 kB

  • Original 153.1 kB
  • After minification 153.1 kB
  • After compression 96.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 56.7 kB or 37% of the original size.

CSS Optimization

-91%

Potential reduce by 320.8 kB

  • Original 353.2 kB
  • After minification 292.5 kB
  • After compression 32.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. Keio.ac.jp needs all CSS files to be minified and compressed as it can save up to 320.8 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (20%)

Requests Now

69

After Optimization

55

  • Images
  • JavaScript
  • CSS

The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Keio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

keio.ac.jp

keio.ac.jp

375 ms

211 ms

fonts.css

fonts.css

213 ms

base.css

base.css

9 ms

module_common.css

module_common.css

42 ms

module_layout.css

module_layout.css

43 ms

global.css

global.css

28 ms

index2.css

index2.css

36 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

42 ms

lib.js

lib.js

56 ms

initialize.js

initialize.js

59 ms

lang.js

lang.js

59 ms

link.js

link.js

58 ms

cn.cgi

cn.cgi

844 ms

index2.js

index2.js

57 ms

js

js

106 ms

brand

brand

58 ms

print.css

print.css

11 ms

brandjs.js

brandjs.js

20 ms

title_01.png

title_01.png

87 ms

1_top_pc_05.png

1_top_pc_05.png

75 ms

1_top_sp_05.png

1_top_sp_05.png

154 ms

1_top_pc_04.png

1_top_pc_04.png

176 ms

1_top_sp_04.png

1_top_sp_04.png

149 ms

1_top_pc_03.png

1_top_pc_03.png

161 ms

1_top_sp_03.png

1_top_sp_03.png

80 ms

1_top_pc_02.png

1_top_pc_02.png

186 ms

1_top_sp_02.png

1_top_sp_02.png

167 ms

1_top_pc_01.png

1_top_pc_01.png

299 ms

1_top_sp_01.png

1_top_sp_01.png

195 ms

menu_btn_canvas_01.gif

menu_btn_canvas_01.gif

168 ms

f-240118-1.jpg

f-240118-1.jpg

191 ms

f-240426-1.jpg

f-240426-1.jpg

191 ms

f-240418-1_1.jpg

f-240418-1_1.jpg

188 ms

f-240329-1.jpg

f-240329-1.jpg

189 ms

f-240410-1.jpg

f-240410-1.jpg

199 ms

f-2404112-1.jpg

f-2404112-1.jpg

196 ms

f-240415-1.jpg

f-240415-1.jpg

281 ms

f-231219-2.jpg

f-231219-2.jpg

282 ms

pic_93.jpg

pic_93.jpg

288 ms

pic_93_sp.jpg

pic_93_sp.jpg

196 ms

pic_92.jpg

pic_92.jpg

278 ms

pic_92_sp.jpg

pic_92_sp.jpg

283 ms

pic_91.jpg

pic_91.jpg

282 ms

pic_91_sp.jpg

pic_91_sp.jpg

301 ms

pic_90.jpg

pic_90.jpg

284 ms

pic_90_sp.jpg

pic_90_sp.jpg

288 ms

pic_01.jpg

pic_01.jpg

284 ms

pic_02.jpg

pic_02.jpg

298 ms

pic_10.jpg

pic_10.jpg

286 ms

pic_09.jpg

pic_09.jpg

305 ms

pic_05.jpg

pic_05.jpg

298 ms

pic_06.jpg

pic_06.jpg

306 ms

pic_07.jpg

pic_07.jpg

302 ms

pic_11.jpg

pic_11.jpg

301 ms

facebook_01.png

facebook_01.png

228 ms

x_01.png

x_01.png

230 ms

instagram_01.png

instagram_01.png

157 ms

youtube_01.png

youtube_01.png

155 ms

linkedin_01.png

linkedin_01.png

149 ms

footer_title_01.png

footer_title_01.png

146 ms

footer_title_01_sp.png

footer_title_01_sp.png

140 ms

title_01.png

title_01.png

134 ms

title_01_sp.png

title_01_sp.png

126 ms

search_01.png

search_01.png

127 ms

access_01.png

access_01.png

128 ms

language_01.png

language_01.png

122 ms

main_01.jpg

main_01.jpg

123 ms

main_01.jpg

main_01.jpg

122 ms

main_01.jpg

main_01.jpg

117 ms

main_01.jpg

main_01.jpg

120 ms

main_01.jpg

main_01.jpg

116 ms

Accessibility Review

keio.ac.jp accessibility score

62

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

keio.ac.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

keio.ac.jp SEO score

74

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Keio.ac.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Keio.ac.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.

Social Sharing Optimization

keio.ac.jp

Open Graph data is detected on the main page of Keio. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: