Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

keio.jp

keio.jp - 過去のリクエスト

Page Load Speed

6.7 sec in total

First Response

403 ms

Resources Loaded

6.2 sec

Page Rendered

123 ms

keio.jp screenshot

About Website

Visit keio.jp now to see the best up-to-date Keio content for Japan and also check out these interesting facts you probably never knew about keio.jp

慶應義塾共通認証システム / Keio Single Sign-On System

Visit keio.jp

Key Findings

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

Performance Metrics

keio.jp performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

21/100

25%

SI (Speed Index)

Value5.7 s

52/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

keio.jp

403 ms

844 ms

MultiFactor

598 ms

jquery-ui-1.10.2.custom.min.css

784 ms

login.css

607 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 8% of them (1 request) were addressed to the original Keio.jp, 83% (10 requests) were made to Auth.keio.jp and 8% (1 request) were made to Portal.keio.jp. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Auth.keio.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 264.7 kB (69%)

Content Size

381.5 kB

After Optimization

116.8 kB

In fact, the total size of Keio.jp main page is 381.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. Only 5% of websites need less resources to load. Javascripts take 322.5 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 3.5 kB

  • Original 4.8 kB
  • After minification 3.2 kB
  • After compression 1.3 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 1.7 kB, which is 34% 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 3.5 kB or 73% of the original size.

Image Optimization

-25%

Potential reduce by 4.7 kB

  • Original 18.7 kB
  • After minification 14.0 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. Obviously, Keio needs image optimization as it can save up to 4.7 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 228.2 kB

  • Original 322.5 kB
  • After minification 321.9 kB
  • After compression 94.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 228.2 kB or 71% of the original size.

CSS Optimization

-80%

Potential reduce by 28.3 kB

  • Original 35.5 kB
  • After minification 32.3 kB
  • After compression 7.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. Keio.jp needs all CSS files to be minified and compressed as it can save up to 28.3 kB or 80% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

9

After Optimization

9

The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Keio. According to our analytics all requests are already optimized.

Accessibility Review

keio.jp accessibility score

90

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

keio.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.jp SEO score

83

Search Engine Optimization Advices

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Keio.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 Keio.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

Open Graph description is not detected on the main page of Keio. 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: