Tools & Wizards About Us
hunnet.co.kr screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    78% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

hunnet.co.kr

(주)휴앤넷시스템

Page Load Speed

8 sec in total

First Response

704 ms

Resources Loaded

7.2 sec

Page Rendered

108 ms

hunnet.co.kr screenshot

About Website

Welcome to hunnet.co.kr homepage info - get ready to check Hunnet best content right away, or after learning these important things about hunnet.co.kr

HUNNET

Visit hunnet.co.kr

Key Findings

We analyzed Hunnet.co.kr page load time and found that the first response time was 704 ms and then it took 7.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

hunnet.co.kr performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value4.9 s

77/100

10%

Network Requests Diagram

hunnet.co.kr

704 ms

main.asp

739 ms

hunnet.css

462 ms

jquery-1.8.2.min.js

2818 ms

jquery_UX.js

479 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 115.9 kB (38%)

Content Size

304.9 kB

After Optimization

189.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hunnet.co.kr main page is 304.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. 15% of websites need less resources to load. Images take 170.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 11.2 kB

  • Original 14.4 kB
  • After minification 11.7 kB
  • After compression 3.1 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 2.6 kB, which is 18% 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 11.2 kB or 78% of the original size.

Image Optimization

-14%

Potential reduce by 23.9 kB

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

JavaScript Optimization

-65%

Potential reduce by 64.4 kB

  • Original 99.3 kB
  • After minification 98.0 kB
  • After compression 34.9 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 64.4 kB or 65% of the original size.

CSS Optimization

-78%

Potential reduce by 16.3 kB

  • Original 21.0 kB
  • After minification 18.0 kB
  • After compression 4.7 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. Hunnet.co.kr needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (66%)

Requests Now

73

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hunnet.co.kr

hunnet.co.kr

704 ms

main.asp

main.asp

739 ms

hunnet.css

hunnet.css

462 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

2818 ms

jquery_UX.js

jquery_UX.js

479 ms

gnb.js

gnb.js

482 ms

main.js

main.js

722 ms

master.css

master.css

232 ms

layout.css

layout.css

481 ms

main.css

main.css

490 ms

body_bg.gif

body_bg.gif

243 ms

header_bg.gif

header_bg.gif

238 ms

header_menu01.gif

header_menu01.gif

241 ms

header_menu02.gif

header_menu02.gif

246 ms

header_menu03.gif

header_menu03.gif

247 ms

header_menu04.gif

header_menu04.gif

244 ms

logo.gif

logo.gif

466 ms

gnb_menubg.gif

gnb_menubg.gif

475 ms

menu1_on.gif

menu1_on.gif

480 ms

menu1_sub1_on.gif

menu1_sub1_on.gif

483 ms

menu1_sub2_off.gif

menu1_sub2_off.gif

485 ms

menu1_sub3_off.gif

menu1_sub3_off.gif

487 ms

menu1_sub4_off.gif

menu1_sub4_off.gif

695 ms

menu1_sub5_off.gif

menu1_sub5_off.gif

710 ms

menu1_sub6_off.gif

menu1_sub6_off.gif

718 ms

menu2_off.gif

menu2_off.gif

721 ms

menu2_sub1_off.gif

menu2_sub1_off.gif

725 ms

menu2_sub2_off.gif

menu2_sub2_off.gif

728 ms

menu2_sub3_off.gif

menu2_sub3_off.gif

926 ms

menu3_off.gif

menu3_off.gif

945 ms

menu3_sub1_off.gif

menu3_sub1_off.gif

957 ms

menu3_sub2_off.gif

menu3_sub2_off.gif

958 ms

menu4_off.gif

menu4_off.gif

965 ms

menu4_sub1_off.gif

menu4_sub1_off.gif

969 ms

menu4_sub2_off.gif

menu4_sub2_off.gif

1157 ms

menu4_sub3_off.gif

menu4_sub3_off.gif

1180 ms

menu5_off.gif

menu5_off.gif

1194 ms

menu5_sub1_off.gif

menu5_sub1_off.gif

1197 ms

menu5_sub3_off.gif

menu5_sub3_off.gif

1205 ms

menu5_sub4_off.gif

menu5_sub4_off.gif

1209 ms

main_coverbg.gif

main_coverbg.gif

1386 ms

cover_pre.png

cover_pre.png

1416 ms

cover_next.png

cover_next.png

1432 ms

main_visiul01.jpg

main_visiul01.jpg

2621 ms

main_visiul02.jpg

main_visiul02.jpg

2402 ms

main_visiul03.jpg

main_visiul03.jpg

2635 ms

btn_visiul.png

btn_visiul.png

1382 ms

main_newsnotice_tit.gif

main_newsnotice_tit.gif

1416 ms

main_newsnotice_default.jpg

main_newsnotice_default.jpg

1670 ms

main_bnr01.gif

main_bnr01.gif

1608 ms

main_bnr02.gif

main_bnr02.gif

1647 ms

main_tit0101.gif

main_tit0101.gif

1837 ms

main_tit0102.gif

main_tit0102.gif

1663 ms

main_tit0103.gif

main_tit0103.gif

1676 ms

main_img01.gif

main_img01.gif

1833 ms

main_tit0201.gif

main_tit0201.gif

1881 ms

main_tit0202.gif

main_tit0202.gif

1905 ms

main_tit0203.gif

main_tit0203.gif

2056 ms

main_img02.gif

main_img02.gif

1903 ms

main_tit0301.gif

main_tit0301.gif

1918 ms

main_tit0302.gif

main_tit0302.gif

1930 ms

main_tit0303.gif

main_tit0303.gif

2053 ms

main_img03.gif

main_img03.gif

2109 ms

main_peoson_tit.gif

main_peoson_tit.gif

2136 ms

main_order_tit.gif

main_order_tit.gif

1941 ms

main_bnr_hotTrend[3].gif

main_bnr_hotTrend[3].gif

2186 ms

%EB%B0%B0%EB%84%88.jpg

%EB%B0%B0%EB%84%88.jpg

1942 ms

footer_address.gif

footer_address.gif

2044 ms

footer_address_main.gif

footer_address_main.gif

2104 ms

footer_logo.gif

footer_logo.gif

2133 ms

main_leftbg.gif

main_leftbg.gif

1947 ms

main_newsnotice_bg.gif

main_newsnotice_bg.gif

1959 ms

main_bnr_boxbg.gif

main_bnr_boxbg.gif

2037 ms

main_bnr_boxbg.gif

main_bnr_boxbg.gif

2108 ms

footer_bg.gif

footer_bg.gif

2134 ms

btn_visiul_ov.png

btn_visiul_ov.png

2133 ms

Accessibility Review

hunnet.co.kr accessibility score

70

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

hunnet.co.kr 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

hunnet.co.kr SEO score

50

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

hunnet.co.kr

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