Tools & Wizards About Us
easypay.co.kr screenshot

Report Summary

  • 0

    Performance

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

easypay.co.kr

한국정보통신 이지페이

Page Load Speed

11.1 sec in total

First Response

770 ms

Resources Loaded

10.2 sec

Page Rendered

132 ms

easypay.co.kr screenshot

About Website

Visit easypay.co.kr now to see the best up-to-date Easypay content for South Korea and also check out these interesting facts you probably never knew about easypay.co.kr

Easypay, 이지페이, easypay, EasyPay

Visit easypay.co.kr

Key Findings

We analyzed Easypay.co.kr page load time and found that the first response time was 770 ms and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

easypay.co.kr performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.514

15/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

easypay.co.kr

770 ms

www.easypay.co.kr

1239 ms

MainAction.do

408 ms

jquery-1.11.3.min.js

770 ms

common.js

574 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 96% of them (68 requests) were addressed to the original Easypay.co.kr, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (7.2 sec) belongs to the original domain Easypay.co.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 209.8 kB (70%)

Content Size

298.9 kB

After Optimization

89.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Easypay.co.kr main page is 298.9 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. 20% of websites need less resources to load. Javascripts take 233.2 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 897 B

  • Original 1.6 kB
  • After minification 1.5 kB
  • After compression 661 B

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 897 B or 58% of the original size.

Image Optimization

-32%

Potential reduce by 4.2 kB

  • Original 12.9 kB
  • After minification 8.7 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, Easypay needs image optimization as it can save up to 4.2 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 162.5 kB

  • Original 233.2 kB
  • After minification 201.2 kB
  • After compression 70.8 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 162.5 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 42.2 kB

  • Original 51.1 kB
  • After minification 45.7 kB
  • After compression 8.9 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. Easypay.co.kr needs all CSS files to be minified and compressed as it can save up to 42.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (32%)

Requests Now

69

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

easypay.co.kr

easypay.co.kr

770 ms

www.easypay.co.kr

www.easypay.co.kr

1239 ms

MainAction.do

MainAction.do

408 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

770 ms

common.js

common.js

574 ms

main-visual.js

main-visual.js

576 ms

jquery.easing.min.js

jquery.easing.min.js

582 ms

calendar.js

calendar.js

787 ms

jquery.simplemodal-1.4.4.js

jquery.simplemodal-1.4.4.js

810 ms

easypay_common.js

easypay_common.js

947 ms

html5.js

html5.js

766 ms

kicc_right_mouse_diable.js

kicc_right_mouse_diable.js

780 ms

goole_analytics.js

goole_analytics.js

956 ms

import.css

import.css

963 ms

down.gif

down.gif

203 ms

drop2.gif

drop2.gif

202 ms

arrow.gif

arrow.gif

202 ms

left2.gif

left2.gif

346 ms

right1.gif

right1.gif

360 ms

right2.gif

right2.gif

372 ms

close.gif

close.gif

387 ms

left1.gif

left1.gif

393 ms

loading02.gif

loading02.gif

400 ms

logo.gif

logo.gif

533 ms

gnb_btn01.gif

gnb_btn01.gif

551 ms

gnb_btn02.gif

gnb_btn02.gif

565 ms

gnb_btn03.gif

gnb_btn03.gif

579 ms

gnb_btn04.gif

gnb_btn04.gif

589 ms

event_box.png

event_box.png

598 ms

mv_rollbt_stop.png

mv_rollbt_stop.png

788 ms

mv_rollbt_on.png

mv_rollbt_on.png

788 ms

mv_rollbt.png

mv_rollbt.png

789 ms

mv_rollingimg3.jpg

mv_rollingimg3.jpg

7009 ms

mv_rollingimg1.jpg

mv_rollingimg1.jpg

6732 ms

mv_rollingimg2.jpg

mv_rollingimg2.jpg

7155 ms

main_inquiry_title.gif

main_inquiry_title.gif

978 ms

main_notice_title.gif

main_notice_title.gif

974 ms

main_notice_more.gif

main_notice_more.gif

980 ms

main_faq_title.gif

main_faq_title.gif

1162 ms

main_qna_title.gif

main_qna_title.gif

1170 ms

%EC%9D%B4%EC%A7%80%ED%8E%98%EC%9D%B4_%EB%A6%AC%EC%8A%A4%ED%8A%B8.jpg

%EC%9D%B4%EC%A7%80%ED%8E%98%EC%9D%B4_%EB%A6%AC%EC%8A%A4%ED%8A%B8.jpg

1177 ms

main_easypay_story.gif

main_easypay_story.gif

1349 ms

main_story_more.gif

main_story_more.gif

1360 ms

main_contact_title.gif

main_contact_title.gif

1370 ms

main_remote_title.gif

main_remote_title.gif

1536 ms

main_tax_title.gif

main_tax_title.gif

1536 ms

foot_logo.gif

foot_logo.gif

1546 ms

analytics.js

analytics.js

16 ms

default.css

default.css

1553 ms

common.css

common.css

1573 ms

content.css

content.css

1586 ms

collect

collect

13 ms

main.css

main.css

1715 ms

js

js

61 ms

bg_gnbline_long.gif

bg_gnbline_long.gif

194 ms

main_con1_icon1.gif

main_con1_icon1.gif

193 ms

main_con1_icon2.gif

main_con1_icon2.gif

188 ms

main_con1_icon3.gif

main_con1_icon3.gif

375 ms

main_con1_icon4.gif

main_con1_icon4.gif

383 ms

main_inq_bg.gif

main_inq_bg.gif

386 ms

main_inq_icon1.gif

main_inq_icon1.gif

563 ms

main_inq_icon2.gif

main_inq_icon2.gif

575 ms

main_inq_icon3.gif

main_inq_icon3.gif

578 ms

main_inq_icon4.gif

main_inq_icon4.gif

750 ms

main_faq_bg.gif

main_faq_bg.gif

766 ms

main_qna_bg.gif

main_qna_bg.gif

771 ms

main_contact_bg.gif

main_contact_bg.gif

937 ms

main_remote_bg.gif

main_remote_bg.gif

958 ms

main_tax_bg.gif

main_tax_bg.gif

963 ms

bg_footerline.gif

bg_footerline.gif

1124 ms

mv_rollbt_on.png

mv_rollbt_on.png

224 ms

Accessibility Review

easypay.co.kr accessibility score

75

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

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

Best Practices

easypay.co.kr best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Page has valid source maps

SEO Factors

easypay.co.kr SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    KO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Easypay.co.kr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Korean. Our system also found out that Easypay.co.kr 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

easypay.co.kr

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