13.3 sec in total
1.6 sec
11.3 sec
374 ms
Click here to check amazing Jejube content for South Korea. Otherwise, check out these important facts you probably never knew about jejube.com
제주배닷컴 홈페이지입니다.
Visit jejube.comWe analyzed Jejube.com page load time and found that the first response time was 1.6 sec and then it took 11.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
jejube.com performance score
name
value
score
weighting
Value12.4 s
0/100
10%
Value16.3 s
0/100
25%
Value26.4 s
0/100
10%
Value290 ms
80/100
30%
Value0.917
3/100
15%
Value36.4 s
0/100
10%
1603 ms
393 ms
985 ms
1181 ms
1394 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 62% of them (100 requests) were addressed to the original Jejube.com, 25% (41 requests) were made to Static.xx.fbcdn.net and 3% (5 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Jejube.com.
Page size can be reduced by 497.9 kB (18%)
2.8 MB
2.3 MB
In fact, the total size of Jejube.com main page is 2.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 53.8 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 53.8 kB or 79% of the original size.
Potential reduce by 42.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. Jejube images are well optimized though.
Potential reduce by 372.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 372.6 kB or 69% of the original size.
Potential reduce by 29.3 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. Jejube.com needs all CSS files to be minified and compressed as it can save up to 29.3 kB or 77% of the original size.
Number of requests can be reduced by 89 (56%)
158
69
The browser has sent 158 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jejube. 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 22 to 1 for CSS and as a result speed up the page load time.
jejube.com
1603 ms
main.css
393 ms
jquery.min.js
985 ms
jquery.tools.min.js
1181 ms
jquery-ui.min.js
1394 ms
jquery.cookie.js
403 ms
base.js
985 ms
main.js
806 ms
jquery.carouFredSel-6.2.0-packed.js
1013 ms
escrowValid.js
1425 ms
wcslog.js
843 ms
base.css
809 ms
common.css
992 ms
mainLayout.css
991 ms
foot.css
1014 ms
board.css
1190 ms
button.css
1201 ms
form.css
1387 ms
pagenate.css
1389 ms
moveMent.css
1398 ms
slider.css
1406 ms
dateinput.css
1578 ms
escrowValid.js
1387 ms
logo.png
403 ms
kor.gif
401 ms
chn.gif
404 ms
top_ad_140418.png
598 ms
ad_02.gif
405 ms
menu01_off.gif
406 ms
menu03_off.gif
798 ms
menu02_off.gif
801 ms
menu04_off.gif
797 ms
menu05_off.gif
803 ms
menu06_off.gif
806 ms
menu07_off.gif
990 ms
allMenu.gif
1189 ms
quick_top.gif
1198 ms
quick_01.gif
1203 ms
quick_02.gif
1202 ms
quick_03.gif
1205 ms
quick_04.gif
1389 ms
quick_05.gif
1580 ms
quick_btm.gif
1597 ms
info_btn01.png
1596 ms
info_btn02.png
1598 ms
001.gif
1601 ms
010.gif
1784 ms
003.gif
1974 ms
007.gif
1994 ms
002.gif
1998 ms
006.gif
2000 ms
011.gif
2005 ms
009.gif
2184 ms
pop_10.jpg
3160 ms
table_5.jpg
3697 ms
pop_7.jpg
3399 ms
popup2.jpg
3383 ms
3_1.jpg
3190 ms
m_popup.jpg
3392 ms
sdk.js
33 ms
gtp1.acecounter.com
654 ms
146 ms
xd_arbiter.php
35 ms
xd_arbiter.php
47 ms
acecounter_V70.js
3359 ms
popup3_2.png
4281 ms
schedule_txt01.gif
3474 ms
schedule_txt02.gif
3474 ms
schedule_txt03.gif
3472 ms
schedule_btn01.gif
3649 ms
schedule_btn02.gif
3454 ms
cs.png
3588 ms
bank_Info.jpg
3593 ms
btn_1.jpg
3454 ms
btn_2.jpg
3696 ms
btn_3.jpg
3582 ms
btn_4.jpg
3498 ms
btn_5.jpg
3593 ms
btn_6.jpg
3587 ms
banner_title.gif
3703 ms
banner1.png
4360 ms
banner2.png
3796 ms
notice_on.gif
3497 ms
qna_off.gif
3584 ms
after_off.gif
3600 ms
faq_off.gif
3701 ms
result_off.gif
3880 ms
more.gif
3790 ms
comment_btn.gif
3606 ms
b_logo.png
3604 ms
escro.gif
3695 ms
top_bg.gif
3879 ms
depth_02.gif
3948 ms
info_bg.gif
3994 ms
infoLine.gif
2816 ms
bg_new.jpg
3990 ms
schedule_bg.png
2704 ms
middle_line.gif
2886 ms
link_bg.jpg
3163 ms
notice_bar.gif
2679 ms
gtp1.acecounter.com
489 ms
m
614 ms
notice_tab_bg.gif
2611 ms
notice_dot.gif
2698 ms
comment_bg01.gif
2800 ms
comment_bg02.gif
2895 ms
page.php
124 ms
Fas0LsYw_Az.css
43 ms
QAAstqgzWat.css
48 ms
H-3J1LvP6vt.css
48 ms
_rx8naC75Dy.js
52 ms
b94UUzHjapV.js
81 ms
0wM5s1Khldu.js
47 ms
ezSeJz80WmZ.js
78 ms
6kb4qPGfoPa.js
78 ms
hQyBJD7FRta.js
75 ms
cqQsIE_csiw.js
73 ms
lbnyQhD5B8P.js
74 ms
Q4A0UyjU8W2.js
77 ms
TTCre3391I0.js
78 ms
12523174_566944203460799_129870941782701669_n.png
180 ms
271 ms
178 ms
12642445_566942160127670_1378340224496464079_n.png
18 ms
wL6VQj7Ab77.png
15 ms
s7jcwEQH7Sx.png
14 ms
t-wz8gw1xG1.png
15 ms
comment_bar.gif
2630 ms
comment_bg03.gif
2714 ms
footer_bg.gif
2710 ms
I6-MnjEovm5.js
15 ms
f6T91Deal_q.js
16 ms
sprite.png
2882 ms
css;base64,
4 ms
Czh0gDTFcBt.css
20 ms
_T7d7xauhps.css
6 ms
w129cOTQGP0.css
20 ms
bABqVu3Jz3Y.css
12 ms
Nmb3gbin69g.css
13 ms
5WkMwH07wQW.css
22 ms
UgGuPz6YNmu.css
29 ms
njO1TPvGzoR.js
28 ms
b_6HNn_J2BZ.js
35 ms
B9x7unvN8Hn.js
34 ms
OCkothPJhqg.js
37 ms
D6JJJzT-tB6.js
33 ms
ThxFh2GztJe.js
35 ms
_UYztdBNTjs.js
36 ms
VpVLc1dkyZp.js
37 ms
DULOQLY-aiv.js
36 ms
-AWXRi4rrMJ.js
36 ms
12795382_576923535796199_7596665553037960233_n.jpg
44 ms
safe_image.php
242 ms
tIFXiEZJgab.js
89 ms
12594414_576918959129990_1765850381_n.jpg
71 ms
12402740_576899132465306_892552905_n.jpg
71 ms
QDwYpIaRyfG.png
8 ms
Fl1c2TVhCj-.png
11 ms
sOQnlBB68lt.png
7 ms
l5aPruN9xMM.png
11 ms
Cg43IrsPc7P.png
5 ms
jejube.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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
jejube.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
jejube.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Jejube.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 Jejube.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.
jejube.com
Open Graph description is not detected on the main page of Jejube. 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: