Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ezloose.com

고고슬림

Page Load Speed

6.3 sec in total

First Response

149 ms

Resources Loaded

5.7 sec

Page Rendered

384 ms

ezloose.com screenshot

About Website

Visit ezloose.com now to see the best up-to-date Ezloose content and also check out these interesting facts you probably never knew about ezloose.com

Visit ezloose.com

Key Findings

We analyzed Ezloose.com page load time and found that the first response time was 149 ms and then it took 6.1 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

ezloose.com performance score

0

Network Requests Diagram

ezloose.com

149 ms

gogoslim.us

1460 ms

common.css

595 ms

common.js

406 ms

common_ro.js

1425 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ezloose.com, 83% (75 requests) were made to Gogoslim.us and 10% (9 requests) were made to Img0001.echosting.cafe24.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Gogoslim.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 134.4 kB (32%)

Content Size

420.7 kB

After Optimization

286.3 kB

In fact, the total size of Ezloose.com main page is 420.7 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. 35% of websites need less resources to load. Images take 252.1 kB which makes up the majority of the site volume.

HTML Optimization

-39%

Potential reduce by 126 B

  • Original 325 B
  • After minification 278 B
  • After compression 199 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. This page needs HTML code to be minified as it can gain 47 B, which is 14% 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 126 B or 39% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 252.1 kB
  • After minification 252.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. Ezloose images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 126.4 kB

  • Original 159.4 kB
  • After minification 127.6 kB
  • After compression 33.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 126.4 kB or 79% of the original size.

CSS Optimization

-89%

Potential reduce by 7.9 kB

  • Original 8.9 kB
  • After minification 7.5 kB
  • After compression 956 B

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. Ezloose.com needs all CSS files to be minified and compressed as it can save up to 7.9 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (30%)

Requests Now

89

After Optimization

62

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

SEO Factors

ezloose.com SEO score

0

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

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