1.7 sec in total
88 ms
1.4 sec
234 ms
Click here to check amazing Status 01 content for South Korea. Otherwise, check out these important facts you probably never knew about status.01.com
Visit status.01.comWe analyzed Status.01.com page load time and found that the first response time was 88 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
status.01.com performance score
name
value
score
weighting
Value2.4 s
69/100
10%
Value2.8 s
82/100
25%
Value2.4 s
98/100
10%
Value70 ms
99/100
30%
Value0.029
100/100
15%
Value2.9 s
96/100
10%
88 ms
5 ms
550 ms
22 ms
17 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Status.01.com, 87% (107 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 (550 ms) relates to the external source Zmailcloud.com.
Page size can be reduced by 898.8 kB (69%)
1.3 MB
398.0 kB
In fact, the total size of Status.01.com main page is 1.3 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. 45% of websites need less resources to load. Javascripts take 827.0 kB which makes up the majority of the site volume.
Potential reduce by 54.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 54.5 kB or 71% of the original size.
Potential reduce by 4.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. Status 01 images are well optimized though.
Potential reduce by 547.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 547.4 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. Status.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 99 (83%)
119
20
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Status 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.
status.01.com
88 ms
5 ms
550 ms
wp-emoji-release.min.js
22 ms
easy-tooltip.css
17 ms
q-a-plus.css
19 ms
wordpress_file_upload_style.css
35 ms
wordpress_file_upload_style_safe.css
19 ms
jquery-ui.css
57 ms
jquery-ui-timepicker-addon.min.css
38 ms
jquery.js
58 ms
jquery-migrate.min.js
52 ms
json2.js
54 ms
wordpress_file_upload_functions.js
72 ms
external-tracking.min.js
71 ms
widgetkit.css
77 ms
style.css
78 ms
style.css
85 ms
style.css
86 ms
style.css
79 ms
style.css
87 ms
style.css
89 ms
lightbox.css
87 ms
mediaelementplayer.css
92 ms
style.css
96 ms
style.css
94 ms
style.css
94 ms
style.css
98 ms
style.css
103 ms
style.css
101 ms
style.css
105 ms
style.css
105 ms
style.css
106 ms
style.css
107 ms
spotlight.css
111 ms
style.css
113 ms
jquery.plugins.js
116 ms
accordion.js
115 ms
lazyloader.js
118 ms
addthis_widget.js
139 ms
zenbox.js
136 ms
zqn2ijh.js
367 ms
prettyPhoto.css
116 ms
base.css
115 ms
layout.css
116 ms
menus.css
114 ms
modules.css
112 ms
tools.css
98 ms
system.css
100 ms
extensions.css
88 ms
custom.css
88 ms
blue.css
73 ms
nobile.css
71 ms
droidsans.css
70 ms
style.css
70 ms
responsive.css
72 ms
print.css
68 ms
nobile.css
65 ms
droidsans.css
65 ms
output.css
70 ms
lazyloader.js
70 ms
lazyloader.js
69 ms
lazyloader.js
68 ms
twitter.js
70 ms
warp.js
84 ms
responsive.js
89 ms
accordionmenu.js
81 ms
dropdownmenu.js
79 ms
template.js
82 ms
search.js
82 ms
effect.min.js
81 ms
effect-pulsate.min.js
89 ms
q-a-plus.js
89 ms
ratings.js
84 ms
core.min.js
89 ms
widget.min.js
88 ms
mouse.min.js
86 ms
slider.min.js
88 ms
datepicker.min.js
89 ms
jquery-ui-timepicker-addon.min.js
88 ms
wp-embed.min.js
86 ms
lightbox.js
87 ms
mediaelement-and-player.js
62 ms
spotlight.js
68 ms
ga.js
82 ms
base.css
64 ms
layout.css
64 ms
menus.css
64 ms
modules.css
66 ms
tools.css
68 ms
system.css
71 ms
system.css
68 ms
system-all.css
68 ms
custom.css
99 ms
responsive.css
71 ms
print.css
72 ms
__utm.gif
38 ms
zmc_brandpromise.png
441 ms
blue_bg.jpg
22 ms
zmc_logo_web.png
91 ms
menubar.png
91 ms
lock.png
90 ms
box_info.png
90 ms
zebra_list.png
89 ms
box_hint.png
90 ms
line_dotted.png
98 ms
normal.png
99 ms
serchbox_separator.png
95 ms
searchbox_magnifier.png
99 ms
module_corner.png
81 ms
totop_scroller.png
79 ms
menu_line_item.png
86 ms
DroidSans-webfont.woff
93 ms
nobile-webfont.woff
87 ms
zenbox.css
87 ms
widget_v2.134.js
135 ms
tab_support_right.png
113 ms
close_big.png
114 ms
loading.html
107 ms
menu_dropdown_level3.png
49 ms
300lo.json
206 ms
load_large.gif
193 ms
sh.07f0d9bf220d07a763adad1e.html
164 ms
status.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
status.01.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
status.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 Status.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 Status.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.
status.01.com
Open Graph description is not detected on the main page of Status 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: