2.8 sec in total
39 ms
2.4 sec
380 ms
Welcome to 01.com homepage info - get ready to check 01 best content for South Korea right away, or after learning these important things about 01.com
Visit 01.comWe analyzed 01.com page load time and found that the first response time was 39 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
01.com performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value3.0 s
79/100
25%
Value2.4 s
98/100
10%
Value130 ms
96/100
30%
Value0.029
100/100
15%
Value2.9 s
96/100
10%
39 ms
572 ms
35 ms
52 ms
62 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 01.com, 85% (108 requests) were made to Zmailcloud.com and 5% (6 requests) were made to Assets.zendesk.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source 140afacabbf434ee3fc5-2393f6f90babc42b21de269dffbb2627.ssl.cf2.rackcdn.com.
Page size can be reduced by 935.2 kB (61%)
1.5 MB
607.1 kB
In fact, the total size of 01.com main page is 1.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. 55% of websites need less resources to load. Javascripts take 847.0 kB which makes up the majority of the site volume.
Potential reduce by 55.6 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 55.6 kB or 71% of the original size.
Potential reduce by 24.0 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. 01 images are well optimized though.
Potential reduce by 562.6 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 562.6 kB or 66% of the original size.
Potential reduce by 292.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. 01.com needs all CSS files to be minified and compressed as it can save up to 292.9 kB or 84% of the original size.
Number of requests can be reduced by 90 (73%)
123
33
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 01. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 57 to 1 for CSS and as a result speed up the page load time.
01.com
39 ms
zmailcloud.com
572 ms
wp-emoji-release.min.js
35 ms
easy-tooltip.css
52 ms
q-a-plus.css
62 ms
wordpress_file_upload_style.css
85 ms
wordpress_file_upload_style_safe.css
50 ms
jquery-ui.css
95 ms
jquery-ui-timepicker-addon.min.css
90 ms
jquery.js
112 ms
jquery-migrate.min.js
102 ms
json2.js
97 ms
wordpress_file_upload_functions.js
106 ms
external-tracking.min.js
103 ms
widgetkit.css
105 ms
style.css
136 ms
style.css
144 ms
style.css
144 ms
style.css
151 ms
style.css
150 ms
style.css
152 ms
lightbox.css
159 ms
mediaelementplayer.css
164 ms
style.css
163 ms
style.css
168 ms
style.css
169 ms
style.css
170 ms
style.css
199 ms
style.css
198 ms
style.css
205 ms
style.css
202 ms
style.css
203 ms
style.css
205 ms
spotlight.css
220 ms
style.css
219 ms
jquery.plugins.js
215 ms
accordion.js
215 ms
lazyloader.js
218 ms
addthis_widget.js
96 ms
zenbox.js
197 ms
zqn2ijh.js
259 ms
prettyPhoto.css
215 ms
base.css
212 ms
layout.css
202 ms
menus.css
205 ms
modules.css
189 ms
tools.css
165 ms
system.css
181 ms
extensions.css
176 ms
custom.css
174 ms
blue.css
177 ms
nobile.css
174 ms
droidsans.css
167 ms
style.css
149 ms
responsive.css
150 ms
print.css
144 ms
nobile.css
142 ms
droidsans.css
140 ms
output.css
138 ms
lazyloader.js
140 ms
lazyloader.js
145 ms
lazyloader.js
160 ms
twitter.js
155 ms
warp.js
181 ms
responsive.js
151 ms
accordionmenu.js
186 ms
dropdownmenu.js
163 ms
template.js
164 ms
search.js
176 ms
effect.min.js
173 ms
effect-pulsate.min.js
170 ms
q-a-plus.js
172 ms
ratings.js
163 ms
core.min.js
166 ms
widget.min.js
167 ms
mouse.min.js
168 ms
slider.min.js
155 ms
datepicker.min.js
180 ms
jquery-ui-timepicker-addon.min.js
176 ms
wp-embed.min.js
174 ms
lightbox.js
179 ms
mediaelement-and-player.js
135 ms
spotlight.js
98 ms
ga.js
116 ms
base.css
116 ms
layout.css
160 ms
menus.css
158 ms
modules.css
162 ms
tools.css
160 ms
system.css
157 ms
system.css
161 ms
system-all.css
164 ms
custom.css
167 ms
responsive.css
172 ms
print.css
171 ms
__utm.gif
19 ms
zmc_brandpromise.png
671 ms
frontpage_priceblock.png
1272 ms
zmc_freetrial_widget.png
1269 ms
blue_bg.jpg
115 ms
zmc_logo_web.png
138 ms
menubar.png
135 ms
lock.png
134 ms
zmc_frontpagebanner.png
139 ms
zmc_overview_thumb.png
337 ms
nav.png
363 ms
serchbox_separator.png
371 ms
searchbox_magnifier.png
372 ms
zmc_overview_thumb_sm.png
371 ms
module_corner.png
358 ms
totop_scroller.png
456 ms
menu_line_item.png
465 ms
DroidSans-webfont.woff
471 ms
nobile-webfont.woff
463 ms
zenbox.css
120 ms
tab_support_right.png
301 ms
close_big.png
435 ms
loading.html
466 ms
,
109 ms
slideshow.js
288 ms
300lo.json
273 ms
magnifier.png
217 ms
menu_dropdown_level3.png
266 ms
sh.07f0d9bf220d07a763adad1e.html
109 ms
zmc_banner3.png
54 ms
load_large.gif
31 ms
widget_v2.134.js
30 ms
01.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
01.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
01.com SEO score
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 doesn't use legible font sizes
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 01.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that 01.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.
01.com
Open Graph description is not detected on the main page of 01. 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: