8.5 sec in total
439 ms
7.1 sec
1 sec
Click here to check amazing Dooray content for South Korea. Otherwise, check out these important facts you probably never knew about dooray.com
NHN 두레이는 프로젝트 협업을 기반으로 메신저, 메일, 전자결재까지 기업에 필요한 모든 협업을 올인원으로 제공합니다.
Visit dooray.comWe analyzed Dooray.com page load time and found that the first response time was 439 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
dooray.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value29.8 s
0/100
25%
Value18.5 s
0/100
10%
Value4,270 ms
1/100
30%
Value0.083
94/100
15%
Value20.5 s
2/100
10%
439 ms
704 ms
175 ms
525 ms
525 ms
Our browser made a total of 192 requests to load all elements on the main page. We found that 77% of them (148 requests) were addressed to the original Dooray.com, 3% (6 requests) were made to Astg.widerplanet.com and 3% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Cdn.megadata.co.kr.
Page size can be reduced by 456.0 kB (19%)
2.4 MB
2.0 MB
In fact, the total size of Dooray.com main page is 2.4 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. 70% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 167.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 167.6 kB or 75% of the original size.
Potential reduce by 167.4 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. Obviously, Dooray needs image optimization as it can save up to 167.4 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 119.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 119.6 kB or 11% of the original size.
Potential reduce by 1.5 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. Dooray.com has all CSS files already compressed.
Number of requests can be reduced by 58 (32%)
181
123
The browser has sent 181 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dooray. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
dooray.com
439 ms
dooray.com
704 ms
main
175 ms
525 ms
notosanskr.min.css
525 ms
notosansjp.min.css
1270 ms
199bb13ad7d12682.css
557 ms
b76dbbae6f2975e7.css
699 ms
polyfills-c67a75d1b6f99dc8.js
891 ms
webpack-4b70e6c85fe7cf89.js
728 ms
framework-81dde9df421d4db3.js
1113 ms
main-6bb0efad3b262c3c.js
947 ms
_app-2f021527f527b8ea.js
891 ms
8082-4b86a50d50a93495.js
910 ms
3231-0600b5cb94c54527.js
1068 ms
7656-263a0d5d689629f6.js
1069 ms
2947-651fe14c0ebc138d.js
1090 ms
7641-8967ff643168ecfc.js
1590 ms
index-0ba30be6614834d3.js
1242 ms
_buildManifest.js
1244 ms
_ssgManifest.js
1420 ms
js
57 ms
kp.js
214 ms
wcslog.js
94 ms
adn_tags_2.1.3.js
20 ms
wp_astg_4.0.js
43 ms
gtm.js
136 ms
logo.65170a62.svg
236 ms
arrow-down-black.83ca9ee8.svg
237 ms
service-project.ed046aef.svg
237 ms
service-messenger.ac3ef92c.svg
238 ms
service-mail.3600b148.svg
235 ms
service-meeting.f917c687.svg
505 ms
service-drive.36d87ef3.svg
502 ms
service-wiki.c405e63d.svg
506 ms
service-calendar.a1bc83d0.svg
505 ms
service-contacts.9d56d4c7.svg
505 ms
service-workflow.27058b62.svg
503 ms
service-board.af05e751.svg
673 ms
service-resource.44c9fb66.svg
680 ms
service-schedule.45ce4284.svg
675 ms
play.f9600713.svg
681 ms
blog.21490846.svg
687 ms
language.368dca20.svg
683 ms
banner-prev.45d0627d.svg
845 ms
banner-next.aee2efb8.svg
849 ms
presentation-prev.621a51d7.svg
860 ms
presentation-next.8d11cf24.svg
861 ms
shield.168971fa.svg
868 ms
isoiec27001.87f68f40.svg
876 ms
ismsp.555cd6a8.svg
1023 ms
isoiec29100.8ad6cb4b.svg
1029 ms
csap.25f46bf4.svg
1051 ms
isoiec27017.6f9fccab.svg
1047 ms
csa.1c30976b.svg
1059 ms
isoiec27018.6db05020.svg
1064 ms
isoiec27701.cf215f46.svg
1197 ms
isoiec27799.72cd7dff.svg
1201 ms
bok@2x.86395b9c.png
1222 ms
etri@2x.bdec5aa0.png
1237 ms
dpg@2x.075765cf.png
1130 ms
snu@2x.8d81a8f6.png
1139 ms
analytics.js
167 ms
fbevents.js
166 ms
ct2.html
154 ms
enp_tracker_self_hosted.min.js
2142 ms
bstrk.1.js
1301 ms
dablena.min.js
365 ms
insight.min.js
218 ms
storage
791 ms
wpc.php
805 ms
kaist@2x.71309ccb.png
1138 ms
ktl@2x.a5e79c20.png
1139 ms
nst@2x.aa0bb473.png
1168 ms
nrc@2x.10f4d3dc.png
1183 ms
js
102 ms
js
268 ms
kist@2x.5f79b18e.png
1151 ms
polyfill.min.js
208 ms
925002735055813
177 ms
collect
168 ms
collect
185 ms
kitech@2x.05f297bd.png
1097 ms
ibs@2x.3c176f83.png
1044 ms
geps@2x.065b35af.png
1046 ms
nia@2x.ab83f892.png
1082 ms
nipa@2x.d1b6c52a.png
1095 ms
energy@2x.eb5400db.png
1111 ms
js
93 ms
ebs@2x.696b8ae1.png
1124 ms
dablena-6GKFTLXT.js
86 ms
77 ms
87 ms
30 ms
jto@2x.288ea040.png
1045 ms
jdc@2x.497c6179.png
1047 ms
26 ms
kic@2x.a02e6014.png
1086 ms
suwonudc@2x.1930a891.png
1100 ms
upa@2x.b3d9e644.png
1121 ms
gif@2x.e28db4f6.png
1133 ms
23 ms
kofak@2x.441a822e.png
1046 ms
science@2x.cc85fad7.png
1048 ms
kfe@2x.a2146ed5.png
1088 ms
kasi@2x.de069686.png
1101 ms
auri@2x.2bfed14e.png
1123 ms
jbnu@2x.617b09dc.png
1131 ms
ssu@2x.e3c18abf.png
1037 ms
dgist@2x.bdc8f538.png
1041 ms
pixel
39 ms
usersync
660 ms
WIDER
32 ms
storage
189 ms
gnu@2x.fd586cd3.png
1077 ms
kias@2x.1bdf8518.png
1084 ms
kdi@2x.10fce1e9.png
1115 ms
bc@2x.112ef2e9.png
1130 ms
wpg.php
182 ms
pixel
16 ms
innopolis@2x.190d84c2.png
1038 ms
kipa@2x.ae76fe25.png
1042 ms
nrf@2x.ba0e4100.png
1086 ms
nikom@2x.6e2f30ce.png
1086 ms
komsa@2x.2b2fedb3.png
1118 ms
spri@2x.e6812fe2.png
1131 ms
kaf@2x.f410951d.png
1040 ms
schoolkeepa@2x.7a05f4e0.png
1046 ms
kriso@2x.5ce6572b.png
1086 ms
dile@2x.c8ad425a.png
1084 ms
kipf@2x.419dcfd4.png
1113 ms
logger.v4.1.js
415 ms
kpfis@2x.6cc3f310.png
1132 ms
jquery.js
28 ms
pcy@2x.1293d3ab.png
1040 ms
koroad@2x.d88f455f.png
1047 ms
hyundai@2x.8436fc85.png
1086 ms
adn_health_jsonp_chk.ad
216 ms
hancom@2x.563a1d32.png
1085 ms
hdc@2x.c056b503.png
1113 ms
oilbank@2x.9bc87530.png
1131 ms
gsneotek@2x.d9a38eb2.png
1041 ms
kbbank@2x.5b5def9d.png
1047 ms
nhn@2x.97824645.png
1087 ms
wpp.php
176 ms
dhflour@2x.86ac673b.png
1085 ms
iparking@2x.e48e9027.png
1110 ms
adn_check_1.0.2.ad
191 ms
yuhankimberly@2x.77ca37ab.png
1111 ms
wpg_a.php
181 ms
gopizza@2x.491e9110.png
1059 ms
phc@2x.75fcabfe.png
1047 ms
gravity@2x.332f08e2.png
1087 ms
estsecurity@2x.a71ea92f.png
1085 ms
wisdomhouse@2x.e1c2a804.png
1109 ms
match2
1040 ms
pixel
900 ms
cyber@2x.88c11875.png
1097 ms
payco@2x.b136d0a3.png
1053 ms
bugs@2x.1460ed16.png
1068 ms
infomax@2x.adf14996.png
1087 ms
hanafind@2x.7e56440e.png
1085 ms
poscoinc@2x.63d77c8f.png
1109 ms
woorihom@2x.6ea3b1f6.png
1082 ms
wconcept@2x.da1a774d.png
1054 ms
incruit@2x.832445f4.png
1087 ms
myrealtrip@2x.31d7780a.png
1087 ms
ybtour@2x.c21ae9e5.png
1085 ms
jejupass@2x.77419828.png
1091 ms
drtour@2x.a98156f8.png
1084 ms
duckil@2x.14912729.png
1055 ms
namhai@2x.1d627ffa.png
1096 ms
inavi@2x.682a1981.png
1087 ms
tmonet@2x.b51bc0e3.png
1084 ms
piolink@2x.75b4e52f.png
1080 ms
roundmedia@2x.52bc3393.png
1068 ms
sentbe@2x.edf60914.png
1070 ms
shoemarker@2x.7c7a6a88.png
1110 ms
dantee@2x.37f286d1.png
1086 ms
btg@2x.20c342f9.png
1085 ms
artisee@2x.77d3b35a.png
1068 ms
ilooda@2x.175c94b3.png
1056 ms
aton@2x.90500ae8.png
1077 ms
sogood@2x.ce19b9fe.png
1123 ms
innowireless@2x.cee499ce.png
1085 ms
smilegate@2x.9101888a.png
1085 ms
pixelb
178 ms
jininfra@2x.2ee55e23.png
1057 ms
contact.ae6afd7e.png
1058 ms
logo-footer.e7056307.svg
1081 ms
logo-company.16c14414.svg
1130 ms
getuid
177 ms
dooray.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
dooray.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
dooray.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 uses legible font sizes
![]()
KO
![]()
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dooray.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 Dooray.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.
dooray.com
Open Graph data is detected on the main page of Dooray. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: