Tools & Wizards About Us
zillers.co.kr screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

zillers.co.kr

Page Load Speed

6.9 sec in total

First Response

1 sec

Resources Loaded

5.7 sec

Page Rendered

102 ms

zillers.co.kr screenshot

About Website

Welcome to zillers.co.kr homepage info - get ready to check Zillers best content for South Korea right away, or after learning these important things about zillers.co.kr

해외직구, 국내 hit 상품 정보, 쿠폰정보

Visit zillers.co.kr

Key Findings

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

Performance Metrics

zillers.co.kr performance score

0

Network Requests Diagram

zillers.co.kr

1021 ms

animate.css

1412 ms

font-awesome.min.css

921 ms

simple-line-icons.css

694 ms

bootstrap.css

2116 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 96% of them (52 requests) were addressed to the original Zillers.co.kr, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Zillers.co.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (89%)

Content Size

2.5 MB

After Optimization

279.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Zillers.co.kr main page is 2.5 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. 40% of websites need less resources to load. Javascripts take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 119.7 kB

  • Original 131.2 kB
  • After minification 130.9 kB
  • After compression 11.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 119.7 kB or 91% of the original size.

JavaScript Optimization

-89%

Potential reduce by 1.9 MB

  • Original 2.1 MB
  • After minification 819.1 kB
  • After compression 224.5 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 1.9 MB or 89% of the original size.

CSS Optimization

-87%

Potential reduce by 288.8 kB

  • Original 332.5 kB
  • After minification 274.7 kB
  • After compression 43.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. Zillers.co.kr needs all CSS files to be minified and compressed as it can save up to 288.8 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (94%)

Requests Now

49

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zillers.co.kr

zillers.co.kr

1021 ms

animate.css

animate.css

1412 ms

font-awesome.min.css

font-awesome.min.css

921 ms

simple-line-icons.css

simple-line-icons.css

694 ms

bootstrap.css

bootstrap.css

2116 ms

font.css

font.css

477 ms

app.css

app.css

1652 ms

jquery.js

jquery.js

2660 ms

bootstrap.js

bootstrap.js

1614 ms

angular.js

angular.js

4140 ms

angular-animate.js

angular-animate.js

2354 ms

angular-aria.js

angular-aria.js

1844 ms

angular-cookies.js

angular-cookies.js

1886 ms

angular-messages.js

angular-messages.js

2074 ms

angular-resource.js

angular-resource.js

2140 ms

angular-sanitize.js

angular-sanitize.js

2305 ms

angular-touch.js

angular-touch.js

2345 ms

ng-infinite-scroll.js

ng-infinite-scroll.js

2355 ms

angular-endless-scroll.js

angular-endless-scroll.js

2534 ms

angular-material.js

angular-material.js

3992 ms

angular-ui-router.js

angular-ui-router.js

3058 ms

ngStorage.js

ngStorage.js

2590 ms

ui-utils.js

ui-utils.js

3226 ms

ui-bootstrap-tpls.js

ui-bootstrap-tpls.js

3535 ms

ocLazyLoad.js

ocLazyLoad.js

2891 ms

angular-translate.js

angular-translate.js

3369 ms

angular-translate-loader-static-files.js

angular-translate-loader-static-files.js

3293 ms

angular-translate-storage-cookie.js

angular-translate-storage-cookie.js

3457 ms

angular-translate-storage-local.js

angular-translate-storage-local.js

3530 ms

app.js

app.js

3606 ms

config.js

config.js

3702 ms

config.lazyload.js

config.lazyload.js

3765 ms

config.router.js

config.router.js

3768 ms

main.js

main.js

3845 ms

ui-load.js

ui-load.js

3932 ms

fromNow.js

fromNow.js

3999 ms

setnganimate.js

setnganimate.js

3789 ms

ui-butterbar.js

ui-butterbar.js

3620 ms

ui-focus.js

ui-focus.js

3516 ms

ui-fullscreen.js

ui-fullscreen.js

3315 ms

ui-jq.js

ui-jq.js

2831 ms

ui-module.js

ui-module.js

2637 ms

ui-nav.js

ui-nav.js

2677 ms

ui-scroll.js

ui-scroll.js

2526 ms

ui-shift.js

ui-shift.js

2517 ms

ui-toggleclass.js

ui-toggleclass.js

2393 ms

bootstrap.js

bootstrap.js

2341 ms

sourcesanspro.woff

sourcesanspro.woff

2550 ms

sourcesanspro-light.woff

sourcesanspro-light.woff

2386 ms

sourcesanspro-bold.woff

sourcesanspro-bold.woff

2345 ms

analytics.js

analytics.js

210 ms

ko.js

ko.js

241 ms

board.js

board.js

241 ms

collect

collect

21 ms

SEO Factors

zillers.co.kr SEO score

0

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zillers.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it does not match the claimed English language. Our system also found out that Zillers.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

zillers.co.kr

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