6.5 sec in total
784 ms
5.3 sec
385 ms
Click here to check amazing Hare content for South Korea. Otherwise, check out these important facts you probably never knew about hare.kr
Visit hare.krWe analyzed Hare.kr page load time and found that the first response time was 784 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
hare.kr performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value4.9 s
29/100
25%
Value7.5 s
26/100
10%
Value2,090 ms
7/100
30%
Value0.188
65/100
15%
Value17.2 s
4/100
10%
784 ms
220 ms
28 ms
355 ms
235 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hare.kr, 27% (37 requests) were made to Blogimgs.naver.net and 17% (23 requests) were made to Blogthumb2.naver.net. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Blogthumb2.naver.net.
Page size can be reduced by 1.2 MB (60%)
2.0 MB
819.8 kB
In fact, the total size of Hare.kr main page is 2.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. 70% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 395 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 395 B or 44% of the original size.
Potential reduce by 129.1 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, Hare needs image optimization as it can save up to 129.1 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 834.0 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 834.0 kB or 74% of the original size.
Potential reduce by 248.1 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. Hare.kr needs all CSS files to be minified and compressed as it can save up to 248.1 kB or 86% of the original size.
Number of requests can be reduced by 60 (45%)
134
74
The browser has sent 134 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hare. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
hare.kr
784 ms
der68
220 ms
Frameset-981964519.js
28 ms
PrologueList.nhn
355 ms
NBlogHidden.nhn
235 ms
Hidden-597428542.js
12 ms
MusicPlayer-449972894.js
32 ms
LayoutTopCommon-484882993.css
13 ms
player-846d457.css
24 ms
RemoveSubDomain-dea9950.js
27 ms
Jindo152-363950062.js
29 ms
LayoutTopCommon-730083628.js
39 ms
JindoComponent-318925938.js
48 ms
PrologueWebzine-222684942.css
45 ms
gnb_quirks_euckr.nhn
119 ms
allowSwfForChrome-7dd9772.js
42 ms
LayoutBottomCommon-902441421.js
40 ms
bg.jpg
1112 ms
spc.gif
587 ms
SAM_3217.JPG
619 ms
6c308deb8dc46382790981a4ce1862617686_ugcvideo_270P_01_16x9_logo.jpg
760 ms
btn_confirm2.gif
580 ms
con6.jpg
595 ms
blog_2560_v2.jpg
1884 ms
0005_login.png
575 ms
ico_n.gif
575 ms
blank.gif
580 ms
ico-ccl3-by-nc-nd.gif
580 ms
btn_thin_close.gif
575 ms
btn_close8.gif
576 ms
ico_file.gif
576 ms
btn_download2.gif
582 ms
btn_cancel3.gif
578 ms
btn_close3.gif
577 ms
btn_close5.gif
578 ms
btn_confirm.gif
579 ms
btn_cancel.gif
578 ms
btn_close_1.gif
578 ms
btn_viewexif.gif
580 ms
btn_originaldn.gif
579 ms
spc.gif
580 ms
tit_viewexif.gif
580 ms
ico_notice2.gif
581 ms
btn_close.gif
580 ms
btn_close3.gif
581 ms
btn_close.gif
581 ms
btn_ok.gif
581 ms
btn_close2.gif
581 ms
btn_confirm_pop2.gif
581 ms
btn_cancel_pop2.gif
581 ms
btn_close.gif
581 ms
ico_help.gif
580 ms
SAM_3362.JPG
602 ms
SAM_3263.JPG
598 ms
SAM_3279.JPG
597 ms
tuffhr.jpg
599 ms
%C5%F5%B8%F0%B7%CE%BF%EC_%B7%A3%B5%E5_%281%29.jpg
598 ms
SAM_3189.JPG
871 ms
SAM_3179.JPG
881 ms
SAM_3147.JPG
920 ms
10.PNG
1323 ms
09.PNG
1297 ms
SAM_3279.JPG
960 ms
SAM_3179.JPG
1347 ms
SAM_4597.JPG
1303 ms
SAM_3086.JPG
1355 ms
SAM_3071.JPG
1388 ms
SAM_3010.jpg
1772 ms
SAM_3217.JPG
1761 ms
SAM_3263.JPG
1804 ms
SAM_3189.JPG
1790 ms
SAM_3147.JPG
1784 ms
SAM_3136.JPG
1837 ms
SAM_3460.jpg
2240 ms
promo_npay.png
558 ms
untitled-2-der68.gif
1298 ms
0172_back.gif
538 ms
WidgetView.nhn
539 ms
WidgetListAsync.nhn
749 ms
m
627 ms
ic_play.png
48 ms
btn_blogsearch.gif
45 ms
shadow.png
46 ms
shadow02.png
45 ms
bg_not_available_word.gif
46 ms
ccl-3.gif
108 ms
0101_image.gif
47 ms
section_connect_widget-2fd595e.css
25 ms
jindo.min-78c07e0.js
30 ms
agent.ie11-6694cec.js
29 ms
BuddyConnectWidget-242001126.js
38 ms
b.gif
31 ms
%BA%F1%BF%A1%B8%A3%C1%EA+%C6%E4%C0%CC%C1%F6+%B7%CE%B0%ED.png
31 ms
b.gif
17 ms
ico_arr2.gif
18 ms
331.jpg
19 ms
%25BA%25ED%25B7%25CE%25B1%25D7%2B%25C7%25C1%25B7%25CE%25C7%25CA.JPG
25 ms
%C7%D8%C7%C7%BA%F3%B7%CE%B1%D7.jpg
27 ms
%25BA%25ED%25B7%25CE%25B1%25D7%2B%25C7%25C1%25B7%25CE%25C7%25CA%25BB%25E7%25C1%25F8%2528161%2529.png
26 ms
Untitled-1.png
26 ms
%C7%EC%B5%E5%C6%F92.png
27 ms
DSC_2890.jpg
30 ms
763.jpg
28 ms
%C7%C1%B7%CE%C7%CA.jpg
29 ms
DSC00369.jpg
38 ms
%BA%ED%B7%CE%B1%D7%C7%C1%B7%CE%C7%CA.png
38 ms
bg_skin9.gif
16 ms
btn_skin9_addn.gif
15 ms
btn_skin9_admin.png
17 ms
btn_skin9_download.png
18 ms
btn_skin9_help.png
19 ms
ExternalWidgetRender.nhn
1301 ms
ExternalWidgetRender.nhn
1336 ms
ExternalWidgetRender.nhn
1411 ms
ExternalWidgetRender.nhn
1415 ms
ExternalWidgetRender.nhn
1417 ms
ExternalWidgetRender.nhn
1435 ms
ExternalWidgetRender.nhn
1980 ms
ExternalWidgetRender.nhn
2061 ms
con6.jpg
12 ms
1439622.gif
90 ms
0153_icon.gif
9 ms
getLoginStatus.nhn
704 ms
banner_1_2.jpg
265 ms
emblem.png
959 ms
emblem_ban_01.png
649 ms
blogger.png
501 ms
%C1%A6%B8%F1_%BE%F8%C0%BD-2.jpg
131 ms
hancom_master_Kor_Emblem.jpg
131 ms
promo_npay_1603.png
23 ms
clickcrD.js
25 ms
0005_menu.png
12 ms
sp_gnb_v10.png
44 ms
%BE%DB%BD%BA%C5%E4%B8%AE%BC%AD%C6%F7%C5%CD%C1%EE%B8%B6%C5%A9.png
32 ms
%BA%EA%B7%CE%C6%E4%BC%C5%B3%CE_2%B1%E2_%C0%A7%C1%AC.png
1086 ms
hare.kr accessibility score
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
[aria-*] attributes do not match their roles
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
hare.kr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
hare.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hare.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Hare.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.
hare.kr
Open Graph description is not detected on the main page of Hare. 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: