8.2 sec in total
315 ms
7.1 sec
805 ms
Welcome to jandi.com homepage info - get ready to check JANDI best content for Taiwan right away, or after learning these important things about jandi.com
협업툴 잔디와 함께라면 실시간 협업부터 효과적인 멤버관리, 안전한 정보 자산화, 효율적인 업무 자동화로 기업 생산성이 크게 향상됩니다.
Visit jandi.comWe analyzed Jandi.com page load time and found that the first response time was 315 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
jandi.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value23.8 s
0/100
25%
Value10.2 s
8/100
10%
Value2,390 ms
5/100
30%
Value0.021
100/100
15%
Value22.4 s
1/100
10%
315 ms
640 ms
156 ms
441 ms
589 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 85% of them (125 requests) were addressed to the original Jandi.com, 2% (3 requests) were made to Google-analytics.com and 1% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Jandi.com.
Page size can be reduced by 459.0 kB (15%)
3.0 MB
2.6 MB
In fact, the total size of Jandi.com main page is 3.0 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. 65% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 40.4 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. This page needs HTML code to be minified as it can gain 7.1 kB, 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 40.4 kB or 78% 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. JANDI images are well optimized though.
Potential reduce by 418.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 418.6 kB or 62% of the original size.
Number of requests can be reduced by 16 (12%)
131
115
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JANDI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
jandi.com
315 ms
www.jandi.com
640 ms
156 ms
29f72126.vendor.css
441 ms
fa4862be.app.css
589 ms
2660210232.js
557 ms
09b491ad.vendor.js
1175 ms
08a18523.app.js
1091 ms
611db25d.Roboto-Regular-webfont.woff
295 ms
7eaa5267.Roboto-Medium-webfont.woff
295 ms
a7b25c4e.Roboto-Light-webfont.woff
1048 ms
0ce000e8.Roboto-Bold-webfont.woff
1060 ms
e154ea04.NotoSansKR-Regular-Hestia.woff
1668 ms
fd87be6b.NotoSansKR-Medium-Hestia.woff
1526 ms
207dc685.NotoSansKR-Light-Hestia.woff
1557 ms
25c86c2f.NotoSansKR-Bold-Hestia.woff
1525 ms
ngc16.nsm-corp.com
1586 ms
analytics.js
534 ms
mixpanel-2.2.min.js
489 ms
fbds.js
629 ms
fbevents.js
688 ms
web
1080 ms
ns.html
361 ms
gtm.js
426 ms
wcslog.js
1170 ms
3b6b5fe6.jandi-logotype-navy.svg
195 ms
5fc1e2d6.jandi-logotype.svg
192 ms
265bf6b8.mrj-profile.png
371 ms
376b16be.jnd-main-adv-desktop-device-kr.png
371 ms
2ec50b4c.jnd-main-adv-desktop-device-en.png
507 ms
65109724.jnd-main-adv-desktop-device-sc.png
507 ms
c4e8147e.jnd-main-adv-desktop-device-tc.png
632 ms
a067ad6d.jnd-main-adv-desktop-conversation-kr.png
633 ms
e11545de.jnd-main-adv-desktop-conversation-en.png
788 ms
e278611a.jnd-main-adv-desktop-conversation-sc.png
788 ms
ff7fa3ca.jnd-main-adv-desktop-conversation-tc.png
659 ms
2fb3bc64.jnd-main-adv-desktop-input.png
763 ms
8cd0c89a.jnd-main-adv-desktop-input-comment-kr.png
766 ms
8aaff69c.jnd-main-adv-desktop-input-comment-en.png
766 ms
65a4d722.jnd-main-adv-desktop-input-comment-sc.png
813 ms
54f78668.jnd-main-adv-desktop-input-comment-tc.png
907 ms
adae7ae0.jnd-main-adv-mobile-device-kr.png
911 ms
dcb72559.jnd-main-adv-mobile-device-en.png
912 ms
95215e70.jnd-main-adv-mobile-device-sc.png
929 ms
3f7fe5aa.jnd-main-adv-mobile-device-tc.png
931 ms
df33920e.jnd-main-adv-mobile-conversation-kr.png
968 ms
e3e30428.jnd-main-adv-mobile-conversation-en.png
1053 ms
d614d3ab.jnd-main-adv-mobile-conversation-sc.png
1056 ms
8ad54bb2.jnd-main-adv-mobile-conversation-tc.png
1058 ms
b70e2c97.jnd-main-adv02-desktop-device-kr.png
1075 ms
1cecc1c6.jnd-main-adv02-desktop-device-en.png
1077 ms
24c1f926.jnd-main-adv02-desktop-device-sc.png
1122 ms
8ea3a429.jnd-main-adv02-desktop-device-tc.png
1198 ms
0fc76124.jnd-main-adv02-desktop-conversation-kr.png
1201 ms
9c8f9a86.jnd-main-adv02-desktop-conversation-en.png
1203 ms
51599104.jnd-main-adv02-desktop-conversation-sc.png
1364 ms
web
668 ms
ed0ae6dc.jandi-icon.ttf
1291 ms
110 ms
collect
79 ms
637d8917.jnd-main-adv02-desktop-conversation-tc.png
1093 ms
c36cc886.jnd-main-adv02-desktop-folder01-kr.png
1140 ms
collect
144 ms
108 ms
66 ms
collect
29 ms
collect
27 ms
ga-audiences
71 ms
1fd589f6.jnd-main-adv02-desktop-folder01-en.png
986 ms
b137868b.jnd-main-adv02-desktop-folder01-sc.png
988 ms
ga-audiences
80 ms
61b8bd11.jnd-main-adv02-desktop-folder01-tc.png
966 ms
436ec51c.jnd-main-adv02-desktop-folder02-kr.png
1018 ms
da43d7ea.jnd-main-adv02-desktop-folder02-en.png
1000 ms
9c7748d3.jnd-main-adv02-desktop-folder02-sc.png
1005 ms
320b33dd.jnd-main-adv02-desktop-folder02-tc.png
997 ms
384bc700.jnd-main-adv03-desktop-device-kr.png
892 ms
8cc09b97.jnd-main-adv03-desktop-device-en.png
972 ms
254004a9.jnd-main-adv03-desktop-device-sc.png
1017 ms
987d7a1a.jnd-main-adv03-desktop-device-tc.png
994 ms
27b58a6b.jnd-main-adv03-desktop-conversation-kr.png
896 ms
da8e4407.jnd-main-adv03-desktop-conversation-en.png
898 ms
ce492dff.jnd-main-adv03-desktop-conversation-sc.png
902 ms
8a9e899b.jnd-main-adv03-desktop-conversation-tc.png
966 ms
aed85626.jnd-main-adv03-desktop-device-hpanel.png
1010 ms
d8382d31.jnd-main-adv03-desktop-device-right-kr.png
984 ms
754182b2.jnd-main-adv03-desktop-device-right-en.png
896 ms
a02a2aa0.jnd-main-adv03-desktop-device-right-sc.png
899 ms
a02a2aa0.jnd-main-adv03-desktop-device-right-tc.png
901 ms
dce0c0ae.jnd-main-adv03-desktop-device-right-conversation-kr.png
977 ms
348dc33d.jnd-main-adv03-desktop-device-right-conversation-en.png
1014 ms
ae144c9d.jnd-main-adv03-desktop-device-right-conversation-sc.png
976 ms
07dea48e.jnd-main-adv03-desktop-device-right-conversation-tc.png
895 ms
b813365f.jnd-main-adv04-search-panel-bg-kr.png
899 ms
22770ad0.jnd-main-adv04-search-panel-bg-en.png
901 ms
ec4a169f.jnd-main-adv04-search-panel-bg-sc.png
987 ms
d3bfaaba.jnd-main-adv04-search-panel-bg-tc.png
1010 ms
b5cbd1f4.jnd-main-adv04-search-panel-edit-opt00-kr.png
965 ms
2cd5e1dc.jnd-main-adv04-search-panel-edit-opt00-en.png
895 ms
38bc7169.jnd-main-adv04-search-panel-edit-opt00-sc.png
898 ms
e8d883a5.jnd-main-adv04-search-panel-edit-opt00-tc.png
901 ms
99041cbe.jnd-main-adv04-search-panel-edit-opt01-kr.png
938 ms
edbad6d7.jnd-main-adv04-search-panel-edit-opt01-en.png
891 ms
55adf61b.jnd-main-adv04-search-panel-edit-opt01-sc.png
887 ms
fbed98f2.jnd-main-adv04-search-panel-edit-opt01-tc.png
888 ms
385b829f.jnd-main-adv04-search-panel-edit-opt02-kr.png
881 ms
e669df7e.jnd-main-adv04-search-panel-edit-opt02-en.png
870 ms
58b85e37.jnd-main-adv04-search-panel-edit-opt02-sc.png
939 ms
0261a603.jnd-main-adv04-search-panel-edit-opt02-tc.png
883 ms
08f6eea0.jnd-main-adv04-search-panel-edit-opt03-kr.png
882 ms
5ddad4cf.jnd-main-adv04-search-panel-edit-opt03-en.png
881 ms
4361868f.jnd-main-adv04-search-panel-edit-opt03-sc.png
881 ms
0d242cf9.jnd-main-adv04-search-panel-edit-opt03-tc.png
881 ms
d8d5fbd4.jnd-main-adv04-search-panel-edit-opt04-kr.png
934 ms
d557c9f7.jnd-main-adv04-search-panel-edit-opt04-en.png
883 ms
d5821b60.jnd-main-adv04-search-panel-edit-opt04-sc.png
881 ms
d5821b60.jnd-main-adv04-search-panel-edit-opt04-tc.png
881 ms
06e6b954.jnd-main-adv04-search-result-all.png
880 ms
36e7ee00.jnd-main-adv04-search-result-pdf.png
881 ms
d3bab99b.jnd-main-adv04-search-opt01-dropdown-kr.png
932 ms
e53ab254.jnd-main-adv04-search-opt01-dropdown-en.png
888 ms
dcaf9f4d.jnd-main-adv04-search-opt01-dropdown-sc.png
907 ms
f5cf6a55.jnd-main-adv04-search-opt01-dropdown-tc.png
881 ms
4c23edec.jnd-main-adv04-search-opt03-dropdown-kr.png
880 ms
5176d030.jnd-main-adv04-search-opt03-dropdown-en.png
882 ms
934e297b.jnd-main-adv04-search-opt03-dropdown-sc.png
923 ms
bbe7e820.jnd-main-adv04-search-opt03-dropdown-tc.png
887 ms
a5639d8f.jnd-main-carousel-profile-01a.png
886 ms
26110bbf.jnd-main-carousel-profile-01b.png
888 ms
74bdabd3.jnd-main-carousel-profile-01c.png
886 ms
ae2758e0.jnd-main-carousel-profile-02.png
900 ms
d95180c8.jnd-main-carousel-profile-03a.png
913 ms
95f1337f.jnd-main-carousel-profile-03b.png
888 ms
c91daa4d.jnd-main-download-mobile-kr.png
889 ms
6e110d7d.jnd-main-download-mobile-en.png
887 ms
bccc500e.jnd-main-download-mobile-sc.png
887 ms
c0e6d2e3.jnd-main-download-mobile-tc.png
909 ms
a149f13f.jnd-main-download-desktop-kr.png
1048 ms
e8096f90.jnd-main-download-desktop-en.png
1033 ms
9bbb98fc.jnd-main-download-desktop-sc.png
888 ms
7c9b22b3.jnd-main-download-desktop-tc.png
1035 ms
1f02fc5f.jnd-main-download-web.png
889 ms
3bf5ee03.jandi-index-header-bg.jpg
1857 ms
592ddf11.jandi-sign-up-divider.png
1192 ms
bfcd74df.footer-social-icons.png
899 ms
yt1d5jat
35 ms
intercom.bcfdf787.js
40 ms
jandi.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-*] attributes do not have valid values
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
jandi.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
jandi.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
{{
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jandi.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it does not match the claimed language. Our system also found out that Jandi.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.
jandi.com
Open Graph data is detected on the main page of JANDI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: