7 sec in total
822 ms
6 sec
195 ms
Visit zum.com now to see the best up-to-date ZUM content for South Korea and also check out these interesting facts you probably never knew about zum.com
세상을 읽는 검색포털 줌닷컴에서 빠르고 편리한 서비스를 만나보세요!
Visit zum.comWe analyzed Zum.com page load time and found that the first response time was 822 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
zum.com performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value8.0 s
2/100
25%
Value8.5 s
17/100
10%
Value7,010 ms
0/100
30%
Value0.001
100/100
15%
Value20.9 s
2/100
10%
822 ms
605 ms
815 ms
809 ms
812 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 6% of them (5 requests) were addressed to the original Zum.com, 23% (19 requests) were made to Lego.zumst.com and 23% (19 requests) were made to Post3.zumst.com. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source Displayad.zumst.com.
Page size can be reduced by 86.3 kB (20%)
433.0 kB
346.7 kB
In fact, the total size of Zum.com main page is 433.0 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. 45% of websites need less resources to load. Images take 325.0 kB which makes up the majority of the site volume.
Potential reduce by 56.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 56.5 kB or 77% of the original size.
Potential reduce by 20.3 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. ZUM images are well optimized though.
Potential reduce by 9.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 9.5 kB or 27% of the original size.
Number of requests can be reduced by 17 (22%)
79
62
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ZUM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
zum.com
822 ms
img_main_loading.gif
605 ms
start-efb87734baf482858255406f3dd6f70f.css
815 ms
jquery.min-a8b4710a57a4bcd481760c0d777334e0.js
809 ms
jquery-ui-1.10.4.custom.min-f5e06885d2c3586e84748344caa0424e.js
812 ms
zumwidget-parent.js
611 ms
at.js
673 ms
target
679 ms
lib.min-d64c195641c818c8e2485a7ce6ae033d.js
678 ms
start-ccb5031ce8788ab7bddd89e1183ca520.js
1002 ms
view
679 ms
view
681 ms
view
680 ms
eda652c6b6a9413784d393940eb629ca.png
592 ms
3f9ef536ac5e452f81e0675fbfd2f668.jpg
1005 ms
2d5e864beba34c56a0c67c1d7d241afb.png
595 ms
e7b8862f69154e80a6a034ccb07a41ae.png
594 ms
6006ff0b811b4e18a40b47775e2ca6bd.png
595 ms
4d9b48fdbf964b3cb6d15d36bbacb671.png
596 ms
d9696b1845344e85b02c1ef25faac149.png
602 ms
7bea7786580d482c9049e9d1c6d584ac.png
783 ms
987047bb356a4097afa9c7ab9742e124.png
787 ms
c4916293dc7c443b9141b2214d001b7a.png
788 ms
5717cf95a200432c9f9435c8a11b6327.png
790 ms
f984ddfca1de49ac8203d9092bd8bfd7.png
791 ms
3d3ce000012348e69d00769cca3aa77b.png
800 ms
eefd2aa33ef545f195be47b1e989e4db_170x249.jpg
974 ms
63d22c2261fa4ff7830c6b18fabc6243_170x85.jpg
981 ms
78d97b71e9a74c86befb42c86d0f90ff_170x85.jpg
983 ms
e0b6774a8925435d9e2a5170a410aba6_170x85.jpg
985 ms
c57647b50e6c4847bbd62863e54b8a34_170x85.jpg
987 ms
d73c5314da3e4bb5ac0b9ebfe8d5e4e6_123x75.jpg
1000 ms
3c58222111194cca9c6b530d1081c48a_123x75.jpg
1168 ms
74b9485be86646e380d72ff4cea0ef81.jpg
600 ms
6de6e3fdc7ad498eb183f6f1c878a549.jpg
1037 ms
d5f1136bd35a46bbab72e0abacb0e3ce.jpg
827 ms
25589ce7ac7c4586bd6cce75198bc59c.jpg
826 ms
7dc9c19c991a42c58591596496aba904.jpg
1037 ms
spr_zum_gnb_20150914.png
198 ms
spr_zum_main_20150820.png
411 ms
shoppingbox3rd
1068 ms
document-domain
199 ms
spr_shopping_favorite_logo_20160118.png
196 ms
spr_news_box_20151223.png
202 ms
spr_rankingbox_hubzum_list.png
198 ms
spr_icon_weather.png
372 ms
spr_hub_tabs_20151223.png
391 ms
frontpage@left_top_big
633 ms
frontpage@br_widget_big
640 ms
b54e63fccec040df863403910564ee46.png
666 ms
2f834a8ce1614f19ba1f87fb5af26a1d.gif
874 ms
document-domain
199 ms
spr_favorite_sites_20151008.png
198 ms
4ce0397226754521978ac8ad2c67a780.gif
1205 ms
shopping_box_3rd-e007acc138c1d1af2e8d10edd23d0b09.css
633 ms
67474119a03700ad7d7e73c7dcbeb822.jpg
3650 ms
c9047201e99b29937c8db2f9ad49ecf2.jpg
3786 ms
lib.min-35a5900b61dba038c74d07e656a6aa1f.js
1216 ms
Loader-7bec2746a7bd2e5fc0a8059e69d32340.js
644 ms
spr_shopping_box_20151222-5f654def9ed3031333cb70809a59f4ac.png
428 ms
analytics.js
24 ms
collect
12 ms
collect
65 ms
thumb_pc_SBTH1311_154418.jpg
622 ms
thumb_pc_SBTH1475_143312.jpg
621 ms
thumb_pc_SBTH1665_171410.jpg
626 ms
thumb_pc_SBTH1669_144942.jpg
633 ms
thumb_pc_SBTH1661_163128.jpg
638 ms
thumb_pc_SBTH1668_112322.jpg
644 ms
thumb_pc_SBTH1663_102615.jpg
1013 ms
thumb_pc_SBTH1622_140652.jpg
824 ms
thumb_pc_SBTH968_135224.jpg
830 ms
thumb_pc_SBTH1677_160901.jpg
839 ms
thumb_pc_SBTH1126_141230.jpg
848 ms
thumb_pc_SBTH1122_151032.jpg
857 ms
suggest
202 ms
suggest-b8eae6d6145df62fb01199d580c2fec8.css
199 ms
jquery.cookie.min-6ce3710b81bd4779927ff9f5e070965c.js
197 ms
require.min-7658ede0c2d75c0accd529c5b9d2302e.js
212 ms
suggest-10b05e6593e407b3e3cafe30deb4bfc3.js
211 ms
rankingBox
302 ms
zum.com accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
The document uses <meta http-equiv="refresh">
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
zum.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
zum.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zum.com 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 Zum.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.
zum.com
Open Graph data is detected on the main page of ZUM. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: