Access i-challenge.co.kr. 아이챌린지 호비 - 매달 자라는 아이, 매달 다르게

i-challenge.co.kr screenshot

21

Performance

Renders faster than
39% of other websites
82

Accessibility

Visual factors better than
that of 52% of websites
83

Best Practices

More advanced features
available than in
55% of websites
93

SEO

Google-friendlier than
83% of websites

First Response

418 ms

Resources Loaded

21.8 sec

Page Rendered

411 ms

i-challenge.co.kr screenshot

About Website

Click here to check amazing I Challenge content for South Korea. Otherwise, check out these important facts you probably never knew about i-challenge.co.kr

우리 아이의 첫 습관 교육, 아이챌린지로 시작하세요.

Visit i-challenge.co.kr

Key Findings

We analyzed I-challenge.co.kr page load time and found that the first response time was 418 ms and then it took 22.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value25.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value52.3 s

0/100

25%

SI (Speed Index)

Value49.3 s

0/100

10%

TBT (Total Blocking Time)

Value1,230 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value74.7 s

0/100

10%

i-challenge.co.kr

418 ms

index.asp

2334 ms

detail.css

582 ms

jquery.min.js

1957 ms

jquery.bxslider.min.js

993 ms

Our browser made a total of 325 requests to load all elements on the main page. We found that 19% of them (62 requests) were addressed to the original I-challenge.co.kr, 65% (210 requests) were made to Pic.neungyule.com and 4% (13 requests) were made to Front.neungyule.com. The less responsive or slowest element that took the longest time to load (5.6 sec) relates to the external source Pic.neungyule.com.

Content Size

31.4 MB

After Optimization

29.7 MB

In fact, the total size of I-challenge.co.kr main page is 31.4 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 29.8 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 131.9 kB

Original 151.5 kB
After minification 121.8 kB
After compression 19.6 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 29.7 kB, which is 20% 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 131.9 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 702.6 kB

Original 29.8 MB
After minification 29.1 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. I Challenge images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 483.1 kB

Original 954.1 kB
After minification 914.6 kB
After compression 471.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 483.1 kB or 51% of the original size.

CSS Optimization

-86%

Potential reduce by 397.3 kB

Original 460.7 kB
After minification 388.2 kB
After compression 63.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. I-challenge.co.kr needs all CSS files to be minified and compressed as it can save up to 397.3 kB or 86% of the original size.

Requests Now

306

After Optimization

248

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

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.

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links do not have descriptive text

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

KO
Language Claimed

KO
Encoding

EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I-challenge.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that I-challenge.co.kr main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

i-challenge.co.kr

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