Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 94

    SEO

    Google-friendlier than
    90% of websites

kegg.jp

KEGG: Kyoto Encyclopedia of Genes and Genomes

Page Load Speed

5.2 sec in total

First Response

983 ms

Resources Loaded

4.1 sec

Page Rendered

99 ms

kegg.jp screenshot

About Website

Welcome to kegg.jp homepage info - get ready to check KEGG best content for Japan right away, or after learning these important things about kegg.jp

KEGG (Kyoto Encyclopedia of Genes and Genomes) is a bioinformatics resource for linking genomes to life and the environment

Visit kegg.jp

Key Findings

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

Performance Metrics

kegg.jp performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

kegg.jp

983 ms

www.kegg.jp

770 ms

kegg_top.css

386 ms

jquery-1.8.3.js

1946 ms

launcher.js

598 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that all of those requests were addressed to Kegg.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Kegg.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 239.8 kB (84%)

Content Size

286.7 kB

After Optimization

47.0 kB

In fact, the total size of Kegg.jp main page is 286.7 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 271.5 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 7.9 kB

  • Original 11.4 kB
  • After minification 10.7 kB
  • After compression 3.5 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 7.9 kB or 69% of the original size.

JavaScript Optimization

-84%

Potential reduce by 229.0 kB

  • Original 271.5 kB
  • After minification 148.1 kB
  • After compression 42.6 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 229.0 kB or 84% of the original size.

CSS Optimization

-77%

Potential reduce by 2.9 kB

  • Original 3.8 kB
  • After minification 3.4 kB
  • After compression 894 B

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. Kegg.jp needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 77% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

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

Accessibility Review

kegg.jp accessibility score

86

Accessibility Issues

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

Form elements do not have associated labels

Best Practices

kegg.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

kegg.jp SEO score

94

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kegg.jp can be misinterpreted by Google and other search engines. Our service has detected that English 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 Kegg.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 KEGG. 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: