10.3 sec in total
1 sec
8.2 sec
1.1 sec
Click here to check amazing Hohoo content for South Korea. Otherwise, check out these important facts you probably never knew about hohoo.co.kr
Visit hohoo.co.krWe analyzed Hohoo.co.kr page load time and found that the first response time was 1 sec and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hohoo.co.kr performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value9.8 s
0/100
25%
Value10.0 s
9/100
10%
Value830 ms
35/100
30%
Value0.387
27/100
15%
Value16.2 s
5/100
10%
1007 ms
787 ms
7 ms
1216 ms
814 ms
Our browser made a total of 182 requests to load all elements on the main page. We found that 86% of them (157 requests) were addressed to the original Hohoo.co.kr, 4% (7 requests) were made to Facebook.com and 2% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Hohoo.co.kr.
Page size can be reduced by 1.2 MB (20%)
6.0 MB
4.8 MB
In fact, the total size of Hohoo.co.kr main page is 6.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.2 MB which makes up the majority of the site volume.
Potential reduce by 89.4 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 24.0 kB, which is 23% 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 89.4 kB or 86% of the original size.
Potential reduce by 550.4 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, Hohoo needs image optimization as it can save up to 550.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 314.2 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 314.2 kB or 68% of the original size.
Potential reduce by 236.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. Hohoo.co.kr needs all CSS files to be minified and compressed as it can save up to 236.1 kB or 83% of the original size.
Number of requests can be reduced by 91 (51%)
179
88
The browser has sent 179 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hohoo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
hohoo.co.kr
1007 ms
common.css
787 ms
wcslog.js
7 ms
jquery-1.7.2.min.js
1216 ms
flash.js
814 ms
rightbanner.js
594 ms
bookmark.js
403 ms
main.css
586 ms
shopRbanner.html
620 ms
header.1.css
784 ms
mcommon.js
625 ms
jquery.easing.1.3.min.js
635 ms
jquery.sliderkit.1.9.2.pack.js
791 ms
menu.1.css
789 ms
jquery.mousewheel.min.js
803 ms
footer.1.css
608 ms
product_list.js
634 ms
detailpage.js
790 ms
Log_script_logsid.html
790 ms
cookie.js
805 ms
btn_favorite.gif
446 ms
btn_webhome.gif
574 ms
btn_login.gif
575 ms
btn_join.gif
588 ms
btn_cart.gif
589 ms
btn_mypage.gif
608 ms
btn_order.gif
622 ms
top_logo.gif
767 ms
btn_search.gif
771 ms
top_ban01.jpg
785 ms
top_ban02.jpg
985 ms
top_cate_all.gif
802 ms
top_cate01_off.gif
821 ms
top_cate02_off.gif
962 ms
top_cate03_off.gif
966 ms
top_cate04_off.gif
980 ms
top_cate05_off.gif
998 ms
hohoo_main_banner_01.gif
1631 ms
hohoo_main_banner_02.gif
1749 ms
hohoo_main_banner_03.gif
2152 ms
hohoo_main_banner_04.jpg
1966 ms
hohoo_main_banner_05.jpg
1576 ms
left_cate01_off.gif
1189 ms
left_cate02_off.gif
1385 ms
left_cate03_off.gif
1581 ms
left_cate04_off.gif
1762 ms
left_cate05_off.gif
1615 ms
left_cate06_off.gif
1663 ms
left_cate07_off.gif
1764 ms
left_cate08_off.gif
1794 ms
left_cate09_off.gif
1768 ms
left_cate10_off.gif
1672 ms
left_cate11_off.gif
1779 ms
left_cate12_off.gif
1789 ms
left_cate13_off.gif
1791 ms
scroll.css
1751 ms
left_cate14_off.gif
1826 ms
title_bbs.gif
1782 ms
left_bbs01_off.gif
1789 ms
left_bbs02_off.gif
1804 ms
left_bbs03_off.gif
1804 ms
left_bbs04_off.gif
1784 ms
left_bbs05_off.gif
1840 ms
0010070000582.gif
1790 ms
view_shopdetail.gif
1788 ms
0010070000572.gif
2006 ms
0010030001962.gif
2003 ms
ban1.jpg
1984 ms
tit_best.gif
1830 ms
0030060007842.jpg
2607 ms
0030070006982.jpg
2022 ms
0130050000482.jpg
2020 ms
0130050000472.jpg
2268 ms
0030070006622.gif
2592 ms
0130050000452.jpg
1611 ms
0130050000462.jpg
1624 ms
0030070006492.jpg
1617 ms
21
1566 ms
23
1650 ms
0130020000352.gif
1624 ms
2
1618 ms
0030070006402.gif
1632 ms
0030070006392.gif
1649 ms
24
1630 ms
0030070005882.jpg
1619 ms
ban2.gif
1688 ms
0030070007432.jpg
2328 ms
0030070007422.jpg
2251 ms
0030070007412.jpg
2440 ms
0030060007822.jpg
1628 ms
0030060007812.jpg
1898 ms
0030070007392.jpg
2001 ms
fbevents.js
141 ms
ZwVvBEhJmdg
131 ms
m
532 ms
[sr].gif
667 ms
0030070007382.jpg
1931 ms
mslog.js
930 ms
www-embed-player-vflQrT_sR.css
89 ms
www-embed-player.js
131 ms
base.js
232 ms
195 ms
193 ms
206 ms
441 ms
438 ms
437 ms
439 ms
0030070007372.jpg
2133 ms
0030070007362.jpg
2024 ms
0030070007352.jpg
2015 ms
0030070005412.jpg
2180 ms
0030070007292.jpg
2196 ms
0030070007282.jpg
2136 ms
0030020003422.jpg
2443 ms
0030070007252.jpg
2126 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
128 ms
ad_status.js
126 ms
0030070007242.jpg
1976 ms
0030070006722.jpg
1992 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
154 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
165 ms
0030070006712.jpg
1989 ms
ban3.jpg
1991 ms
Conf_hohoo.js
587 ms
0130030000302.jpg
1888 ms
ban4.gif
1962 ms
0130010000392.gif
1979 ms
ms.log
417 ms
0040010000062.gif
1793 ms
0040010000052.gif
1795 ms
0040010000032.gif
1888 ms
ban5.jpg
1894 ms
tit_new.gif
1775 ms
0310030000252.gif
1787 ms
0070060000032.gif
1785 ms
0030070006752.gif
1728 ms
[sr].gif
848 ms
emd_pt.js
853 ms
0030070007032.gif
1723 ms
0030070007012.gif
1758 ms
0030070006992.jpg
1970 ms
0030070005522.gif
1787 ms
0030060003882.gif
1727 ms
0030070005572.gif
1610 ms
0030070005602.gif
1699 ms
0030070005622.gif
1479 ms
0030010001362.gif
1406 ms
event_ban01_off.jpg
1397 ms
event_ban02_off.jpg
1224 ms
ban_cc.gif
1324 ms
HTTP_s.js
1029 ms
ban_bank.gif
1348 ms
tit_notice.gif
1365 ms
quick_btn01_off.gif
1307 ms
quick_btn02_off.gif
1225 ms
quick_btn03_off.gif
1210 ms
ban_event.gif
1318 ms
bt_menu1.gif
1352 ms
bt_menu2.gif
1279 ms
bt_menu3.gif
1221 ms
bt_menu4.gif
1208 ms
bt_menu5.gif
1199 ms
bt_menu6.gif
1322 ms
bt_menu7.gif
1255 ms
bt_menu8.gif
1199 ms
copy.gif
1202 ms
btn_bizinfo.gif
1191 ms
mtag.gif
1192 ms
ban_facebook.gif
1318 ms
ban_social.gif
1245 ms
ban_grade.png
1198 ms
top_bg.gif
1205 ms
bg_allcate.gif
1196 ms
bbs_dot.gif
1196 ms
quick_line.gif
1325 ms
bottom_bg.gif
1243 ms
bt_menu_bar.gif
1198 ms
btn.gif
1191 ms
main_bar_off.png
1191 ms
main_bar_on.png
1192 ms
btn_arrow.png
1224 ms
hohoo.co.kr accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
hohoo.co.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
Page has valid source maps
hohoo.co.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Image elements do not have [alt] attributes
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
KO
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hohoo.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Hohoo.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.
hohoo.co.kr
Open Graph description is not detected on the main page of Hohoo. 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: