Tools & Wizards About Us
store.hansalim.or.kr screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

store.hansalim.or.kr

한살림 인터넷 장보기 통합검색

Page Load Speed

10.5 sec in total

First Response

3 sec

Resources Loaded

7.2 sec

Page Rendered

228 ms

store.hansalim.or.kr screenshot

About Website

Click here to check amazing Store Hansalim content for South Korea. Otherwise, check out these important facts you probably never knew about store.hansalim.or.kr

가까운 한살림 매장을 손쉽게 찾아보세요. 매장별 전화번호, 주소, 약도 등의 자세한 정보와 함께 매장에서 진행하는 이벤트도 확인하실 수 있습니다.

Visit store.hansalim.or.kr

Key Findings

We analyzed Store.hansalim.or.kr page load time and found that the first response time was 3 sec and then it took 7.5 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

store.hansalim.or.kr performance score

0

Network Requests Diagram

store.hansalim.or.kr

2998 ms

css

27 ms

css

39 ms

reset.css

402 ms

style.css

927 ms

Our browser made a total of 147 requests to load all elements on the main page. We found that 36% of them (53 requests) were addressed to the original Store.hansalim.or.kr, 44% (65 requests) were made to Maps.google.com and 7% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Store.hansalim.or.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (31%)

Content Size

3.2 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Store.hansalim.or.kr main page is 3.2 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. 75% 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 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 278.8 kB

  • Original 319.4 kB
  • After minification 317.4 kB
  • After compression 40.5 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. 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 278.8 kB or 87% of the original size.

Image Optimization

-4%

Potential reduce by 71.3 kB

  • Original 2.0 MB
  • After minification 1.9 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. Store Hansalim images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 554.1 kB

  • Original 810.4 kB
  • After minification 769.6 kB
  • After compression 256.3 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 554.1 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 113.0 kB

  • Original 134.3 kB
  • After minification 110.0 kB
  • After compression 21.3 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. Store.hansalim.or.kr needs all CSS files to be minified and compressed as it can save up to 113.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (40%)

Requests Now

140

After Optimization

84

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

store.hansalim.or.kr

store.hansalim.or.kr

2998 ms

css

css

27 ms

css

css

39 ms

reset.css

reset.css

402 ms

style.css

style.css

927 ms

style-adventure.css

style-adventure.css

456 ms

prettyPhoto.css

prettyPhoto.css

779 ms

font-awesome.min.css

font-awesome.min.css

777 ms

jquery.js

jquery.js

1533 ms

jquery-migrate.min.js

jquery-migrate.min.js

855 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1174 ms

jquery.scrollTo-1.4.2-min.js

jquery.scrollTo-1.4.2-min.js

1241 ms

custom.js

custom.js

1370 ms

core.min.js

core.min.js

1312 ms

widget.min.js

widget.min.js

1573 ms

mouse.min.js

mouse.min.js

1683 ms

jquery.ui.slider.js

jquery.ui.slider.js

1991 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

1819 ms

single-loader.js

single-loader.js

1989 ms

js

js

24 ms

gmap3.min.js

gmap3.min.js

2453 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

2278 ms

ajax.js

ajax.js

2325 ms

main.js

main.js

2449 ms

style.css

style.css

2491 ms

masonry.min.js

masonry.min.js

766 ms

analytics.js

analytics.js

29 ms

cardboard.jpg

cardboard.jpg

718 ms

top-bg.png

top-bg.png

1816 ms

post-bg.jpg

post-bg.jpg

500 ms

logo.png

logo.png

765 ms

%EC%9D%BC%EC%9A%94%EC%9D%BC.png

%EC%9D%BC%EC%9A%94%EC%9D%BC.png

558 ms

%EC%8B%A0%EC%84%A0%EC%9C%A1.png

%EC%8B%A0%EC%84%A0%EC%9C%A1.png

727 ms

%EC%A6%89%EC%84%9D%EB%B9%B5.png

%EC%A6%89%EC%84%9D%EB%B9%B5.png

944 ms

%EC%A6%89%EC%84%9D%EB%96%A1.png

%EC%A6%89%EC%84%9D%EB%96%A1.png

955 ms

%EC%83%88%EB%A7%A4%EC%9E%A5.png

%EC%83%88%EB%A7%A4%EC%9E%A5.png

1132 ms

hansalim-button.png

hansalim-button.png

1165 ms

shop-button.png

shop-button.png

1167 ms

mapnav-bg.png

mapnav-bg.png

2358 ms

mapnav-prev.png

mapnav-prev.png

1394 ms

mapnav-next.png

mapnav-next.png

1521 ms

search-big.png

search-big.png

1553 ms

store.png

store.png

3712 ms

mapnav-bg-shadow.png

mapnav-bg-shadow.png

1785 ms

hr.png

hr.png

1975 ms

linkid.js

linkid.js

18 ms

AIM.png

AIM.png

2027 ms

Apple.png

Apple.png

2222 ms

facebook.png

facebook.png

2224 ms

cook.png

cook.png

2415 ms

twitter.png

twitter.png

2469 ms

rss.png

rss.png

2730 ms

ok.png

ok.png

2733 ms

arrow_top_16x16.png

arrow_top_16x16.png

2781 ms

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

6 ms

EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf

EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf

8 ms

collect

collect

4 ms

collect

collect

61 ms

common.js

common.js

79 ms

util.js

util.js

38 ms

geocoder.js

geocoder.js

36 ms

map.js

map.js

32 ms

marker.js

marker.js

32 ms

ajaxmap.gif

ajaxmap.gif

2647 ms

menu-arrow.png

menu-arrow.png

2700 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

281 ms

GeocodeService.Search

GeocodeService.Search

166 ms

onion.js

onion.js

25 ms

openhand_8_8.cur

openhand_8_8.cur

18 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

142 ms

stats.js

stats.js

9 ms

controls.js

controls.js

77 ms

transparent.png

transparent.png

22 ms

css

css

41 ms

google4.png

google4.png

35 ms

pin-2.png

pin-2.png

2591 ms

supermarket.png

supermarket.png

2643 ms

mapcnt6.png

mapcnt6.png

39 ms

sv5.png

sv5.png

34 ms

tmapctrl.png

tmapctrl.png

26 ms

cb_scout5.png

cb_scout5.png

30 ms

tmapctrl4.png

tmapctrl4.png

26 ms

arrow-down.png

arrow-down.png

29 ms

imgs8.png

imgs8.png

28 ms

vt

vt

13 ms

vt

vt

27 ms

vt

vt

15 ms

vt

vt

20 ms

vt

vt

18 ms

vt

vt

17 ms

vt

vt

17 ms

vt

vt

18 ms

vt

vt

23 ms

vt

vt

19 ms

vt

vt

22 ms

vt

vt

22 ms

vt

vt

22 ms

vt

vt

23 ms

vt

vt

26 ms

vt

vt

25 ms

vt

vt

25 ms

vt

vt

25 ms

vt

vt

27 ms

vt

vt

27 ms

vt

vt

44 ms

vt

vt

44 ms

vt

vt

44 ms

vt

vt

27 ms

vt

vt

45 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

15 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

18 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

17 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

19 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

76 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

27 ms

vt

vt

26 ms

vt

vt

22 ms

vt

vt

22 ms

vt

vt

23 ms

vt

vt

22 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

52 ms

vt

vt

25 ms

vt

vt

13 ms

vt

vt

33 ms

vt

vt

12 ms

vt

vt

18 ms

vt

vt

32 ms

vt

vt

15 ms

vt

vt

36 ms

vt

vt

24 ms

vt

vt

41 ms

vt

vt

40 ms

vt

vt

56 ms

vt

vt

59 ms

vt

vt

66 ms

vt

vt

50 ms

vt

vt

68 ms

vt

vt

53 ms

vt

vt

80 ms

vt

vt

82 ms

vt

vt

87 ms

vt

vt

72 ms

vt

vt

90 ms

vt

vt

82 ms

vt

vt

103 ms

vt

vt

111 ms

vt

vt

107 ms

SEO Factors

store.hansalim.or.kr SEO score

0

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    KO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Store.hansalim.or.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 Store.hansalim.or.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

store.hansalim.or.kr

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