6.3 sec in total
149 ms
5.7 sec
384 ms
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.comWe 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.
ezloose.com performance score
149 ms
1460 ms
595 ms
406 ms
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 size can be reduced by 134.4 kB (32%)
420.7 kB
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.
Potential reduce by 126 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.
Potential reduce by 0 B
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.
Potential reduce by 126.4 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.
Potential reduce by 7.9 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. 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.
Number of requests can be reduced by 27 (30%)
89
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.
ezloose.com
149 ms
gogoslim.us
1460 ms
common.css
595 ms
common.js
406 ms
common_ro.js
1425 ms
AuthSSLManager.js
212 ms
AuthSSLManager.plugin.js
403 ms
ec_front_popup_opener.php
282 ms
icon_19_01.gif
400 ms
btn_prd_zoom.gif
399 ms
top_login.gif
201 ms
top_join.gif
199 ms
top_guide.gif
209 ms
top_mypage.gif
206 ms
top_cart.gif
203 ms
top_order.gif
397 ms
top_favor.gif
399 ms
search.gif
412 ms
main_left_ban.gif
411 ms
spacer.gif
416 ms
main_center_ban.gif
901 ms
main_f_text.gif
789 ms
ezloose_98.gif
1027 ms
ezloose_81.jpg
802 ms
ezloose_82.gif
612 ms
ezloose_37.jpg
1037 ms
ezloose_52.jpg
815 ms
ezloose_56.gif
1182 ms
ezloose_55.jpg
1203 ms
ezloose_54.jpg
1017 ms
ezloose_60.gif
1109 ms
ezloose_46.jpg
1221 ms
ezloose_45.jpg
1224 ms
ezloose_42.jpg
1452 ms
ezloose_85.jpg
1525 ms
ezloose_90.gif
1380 ms
ezloose_91.gif
1403 ms
ezloose_94.gif
1424 ms
ezloose_97.gif
1620 ms
maintitle1.gif
1576 ms
ezloose_16.jpg
1802 ms
ezloose_17.jpg
1626 ms
ezloose_18.jpg
1865 ms
ezloose_19.jpg
1732 ms
icon_22_01.gif
392 ms
icon_23_03.gif
392 ms
icon_20_02.gif
392 ms
icon_13_03.gif
392 ms
icon_05_01.gif
393 ms
icon_21_06.gif
572 ms
icon_01_08.gif
582 ms
icon_11_01.gif
584 ms
icon_cash.gif
400 ms
kobes.js
17 ms
ezloose_80.jpg
1763 ms
getConfig.php
399 ms
weblog.js
615 ms
realconn.php
1692 ms
ezloose_14.jpg
1637 ms
ezloose_10.jpg
1747 ms
ezloose_30.jpg
1773 ms
ezloose_29.jpg
1802 ms
ezloose_27.jpg
1765 ms
ezloose_26.jpg
1685 ms
ezloose_28.jpg
1691 ms
maintitle2.gif
1748 ms
ezloose_99.gif
1957 ms
ezloose_58.jpg
1995 ms
ezloose_53.gif
1632 ms
ezloose_57.jpg
1502 ms
ezloose_88.jpg
1486 ms
ezloose_92.gif
1550 ms
ezloose_93.gif
1548 ms
ezloose_61.gif
1466 ms
ezloose_48.gif
1470 ms
ezloose_95.gif
1742 ms
ezloose_44.jpg
1457 ms
ezloose_96.gif
1629 ms
bt_ban_center.gif
1447 ms
bt_ban_bank.gif
1462 ms
notice_title.gif
1479 ms
bt_ban01.gif
1386 ms
bt_ban02.gif
1450 ms
bt_ban03.gif
1457 ms
bt_ban04.gif
1459 ms
bt_menu.gif
1437 ms
bt_link.gif
1412 ms
top_bg.gif
1391 ms
roll_bg.gif
1427 ms
spacer.gif
1347 ms
ezloose.com SEO score
KO
N/A
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.
ezloose.com
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: