Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

klaytn.com

Kaia

Page Load Speed

6 sec in total

First Response

403 ms

Resources Loaded

4.4 sec

Page Rendered

1.2 sec

About Website

Visit klaytn.com now to see the best up-to-date Klaytn content for South Korea and also check out these interesting facts you probably never knew about klaytn.com

Visit klaytn.com

Key Findings

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

Performance Metrics

klaytn.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value3,270 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value22.9 s

1/100

10%

Network Requests Diagram

klaytn.com

403 ms

klaytn.com

779 ms

klaytn.foundation

1019 ms

kaia.io

41 ms

www.kaia.io

1404 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Klaytn.com, 39% (42 requests) were made to Cdn.prod.website-files.com and 24% (26 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Kaia.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 375.3 kB (3%)

Content Size

13.0 MB

After Optimization

12.7 MB

In fact, the total size of Klaytn.com main page is 13.0 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 12.3 MB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 191.4 kB

  • Original 299.2 kB
  • After minification 298.5 kB
  • After compression 107.8 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 191.4 kB or 64% of the original size.

Image Optimization

-1%

Potential reduce by 149.7 kB

  • Original 12.3 MB
  • After minification 12.2 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. Klaytn images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 34.1 kB

  • Original 301.6 kB
  • After minification 301.4 kB
  • After compression 267.5 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 34.1 kB or 11% of the original size.

CSS Optimization

-0%

Potential reduce by 11 B

  • Original 100.3 kB
  • After minification 100.3 kB
  • After compression 100.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. Klaytn.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (45%)

Requests Now

82

After Optimization

45

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

Accessibility Review

klaytn.com accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

<frame> or <iframe> elements do not have a title

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

klaytn.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

klaytn.com SEO score

78

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

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 Klaytn.com 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 Klaytn.com 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 Klaytn. 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: