Tools & Wizards About Us
jejurentcar.co.kr screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

jejurentcar.co.kr

제주렌트카 본사 - 제주도렌트카 실시간 예약, 렌터카 가격비교

Page Load Speed

14.4 sec in total

First Response

2.5 sec

Resources Loaded

11.4 sec

Page Rendered

455 ms

jejurentcar.co.kr screenshot

About Website

Click here to check amazing Jejurentcar content for South Korea. Otherwise, check out these important facts you probably never knew about jejurentcar.co.kr

제주렌트카 대한민국 국내 1호 렌트카! 제주공항 셔틀 1분! 당일예약, 실시간 예약.결제, since 1978

Visit jejurentcar.co.kr

Key Findings

We analyzed Jejurentcar.co.kr page load time and found that the first response time was 2.5 sec and then it took 11.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

jejurentcar.co.kr performance score

0

Network Requests Diagram

jejurentcar.co.kr

2518 ms

common.css

1077 ms

main.css

891 ms

jquery.min.js

31 ms

jquery-ui.min.js

52 ms

Our browser made a total of 131 requests to load all elements on the main page. We found that 68% of them (89 requests) were addressed to the original Jejurentcar.co.kr, 5% (7 requests) were made to I1.daumcdn.net and 5% (6 requests) were made to Map3.daumcdn.net. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Jejurentcar.co.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.6 MB (54%)

Content Size

8.5 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jejurentcar.co.kr main page is 8.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. 50% of websites need less resources to load. Images take 7.9 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 106.4 kB

  • Original 128.7 kB
  • After minification 115.0 kB
  • After compression 22.3 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 13.8 kB, which is 11% 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 106.4 kB or 83% of the original size.

Image Optimization

-53%

Potential reduce by 4.2 MB

  • Original 7.9 MB
  • After minification 3.8 MB

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, Jejurentcar needs image optimization as it can save up to 4.2 MB or 53% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 288.4 kB

  • Original 393.2 kB
  • After minification 338.6 kB
  • After compression 104.8 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 288.4 kB or 73% of the original size.

CSS Optimization

-89%

Potential reduce by 68.9 kB

  • Original 77.3 kB
  • After minification 57.0 kB
  • After compression 8.4 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. Jejurentcar.co.kr needs all CSS files to be minified and compressed as it can save up to 68.9 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (19%)

Requests Now

126

After Optimization

102

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jejurentcar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

jejurentcar.co.kr

jejurentcar.co.kr

2518 ms

common.css

common.css

1077 ms

main.css

main.css

891 ms

jquery.min.js

jquery.min.js

31 ms

jquery-ui.min.js

jquery-ui.min.js

52 ms

nav.js

nav.js

961 ms

main_vis.css

main_vis.css

1290 ms

main_vis.js

main_vis.js

1133 ms

date2.js

date2.js

1333 ms

jquery.datePicker0406.js

jquery.datePicker0406.js

1921 ms

datePicker_0406.css

datePicker_0406.css

1294 ms

php.default.min.js

php.default.min.js

2477 ms

NanumGothic-Regular.woff

NanumGothic-Regular.woff

104 ms

NanumGothic-Bold.woff

NanumGothic-Bold.woff

133 ms

NanumGothic-ExtraBold.woff

NanumGothic-ExtraBold.woff

213 ms

reveal.css

reveal.css

359 ms

jquery.reveal.js

jquery.reveal.js

324 ms

postcode.js

postcode.js

677 ms

wcslog.js

wcslog.js

5 ms

close.png

close.png

702 ms

gnb_bg.png

gnb_bg.png

239 ms

top_fb.jpg

top_fb.jpg

242 ms

top_tw.jpg

top_tw.jpg

276 ms

top_bm.jpg

top_bm.jpg

217 ms

logo.png

logo.png

501 ms

eq900_bg.jpg

eq900_bg.jpg

2498 ms

ioniq_bg.jpg

ioniq_bg.jpg

2371 ms

102601bg.jpg

102601bg.jpg

4354 ms

102602bg.jpg

102602bg.jpg

4174 ms

02_bg.jpg

02_bg.jpg

832 ms

03_bg.jpg

03_bg.jpg

3012 ms

eq900_text.png

eq900_text.png

1107 ms

ioniq_car.png

ioniq_car.png

1950 ms

ioniq_txt.png

ioniq_txt.png

2238 ms

102601txt.png

102601txt.png

2526 ms

102601img.png

102601img.png

2802 ms

car2.png

car2.png

2726 ms

car2_2.png

car2_2.png

2800 ms

2img.png

2img.png

2957 ms

txt2.png

txt2.png

3077 ms

txt2_2.png

txt2_2.png

3016 ms

txt2_3.png

txt2_3.png

3208 ms

3img.png

3img.png

3521 ms

3txt.png

3txt.png

3231 ms

3txt_2.png

3txt_2.png

3351 ms

3txt_3.png

3txt_3.png

3446 ms

102602img.png

102602img.png

3683 ms

102602txt.png

102602txt.png

3631 ms

main2bg3_.png

main2bg3_.png

4389 ms

op_ico_01.png

op_ico_01.png

3771 ms

op_ico_02.png

op_ico_02.png

3915 ms

op_ico_03.png

op_ico_03.png

3905 ms

op_ico_04.png

op_ico_04.png

4020 ms

op_ico_05.png

op_ico_05.png

4129 ms

ban_mr_01.jpg

ban_mr_01.jpg

5056 ms

ban_mr_02.jpg

ban_mr_02.jpg

4199 ms

151201.js

151201.js

1752 ms

btn_mr.jpg

btn_mr.jpg

4151 ms

ban_fb.jpg

ban_fb.jpg

4180 ms

ban_wv.jpg

ban_wv.jpg

4291 ms

ban_member.jpg

ban_member.jpg

4321 ms

ban_service.jpg

ban_service.jpg

4076 ms

ban_fb2.jpg

ban_fb2.jpg

3794 ms

ban_qna.jpg

ban_qna.jpg

3552 ms

maps.php

maps.php

2833 ms

bmaps.php

bmaps.php

2555 ms

acecounter_V70.js

acecounter_V70.js

2467 ms

ban_info.jpg

ban_info.jpg

2358 ms

btn_ok.jpg

btn_ok.jpg

2373 ms

modal20.png

modal20.png

2316 ms

foot_customer.png

foot_customer.png

2207 ms

copy_btn.gif

copy_btn.gif

2273 ms

exit.png

exit.png

2115 ms

btn_login_t2.jpg

btn_login_t2.jpg

2130 ms

login_join2.jpg

login_join2.jpg

2207 ms

login_id2.jpg

login_id2.jpg

2216 ms

login_pw2.jpg

login_pw2.jpg

2127 ms

btn_login_t3.jpg

btn_login_t3.jpg

2064 ms

btn_board_ok.jpg

btn_board_ok.jpg

1963 ms

btn_bres.jpg

btn_bres.jpg

1932 ms

login_etc.png

login_etc.png

1918 ms

rent_b_pop_0201002.png

rent_b_pop_0201002.png

2164 ms

icon_rongterm.png

icon_rongterm.png

1833 ms

2deps_bg.png

2deps_bg.png

1782 ms

bg02.jpg

bg02.jpg

1703 ms

join_tit_bull.jpg

join_tit_bull.jpg

1703 ms

copy_tw.png

copy_tw.png

1633 ms

copy_fb.png

copy_fb.png

1606 ms

login_tit.jpg

login_tit.jpg

1618 ms

pw_bg.png

pw_bg.png

1701 ms

res_tit.jpg

res_tit.jpg

1501 ms

maps3.js

maps3.js

728 ms

ngc2.nsm-corp.com

ngc2.nsm-corp.com

466 ms

m

m

660 ms

trs_esc.js

trs_esc.js

1016 ms

open.js

open.js

918 ms

services.js

services.js

837 ms

log.php

log.php

249 ms

arrow.png

arrow.png

239 ms

left_arr.png

left_arr.png

241 ms

right_arr.png

right_arr.png

276 ms

play_overOFF.png

play_overOFF.png

217 ms

main_vis.css

main_vis.css

255 ms

cal_left3.png

cal_left3.png

224 ms

cal_right3.png

cal_right3.png

432 ms

transparent.gif

transparent.gif

35 ms

715.png

715.png

1292 ms

716.png

716.png

1346 ms

717.png

717.png

1072 ms

addr2coord

addr2coord

244 ms

addr2coord

addr2coord

469 ms

715.png

715.png

1283 ms

715.png

715.png

1337 ms

loading_n.png

loading_n.png

7 ms

m_bi.png

m_bi.png

7 ms

scalebar.png

scalebar.png

8 ms

openhand.cur.ico

openhand.cur.ico

6 ms

717.png

717.png

1085 ms

717.png

717.png

1087 ms

716.png

716.png

1337 ms

716.png

716.png

1131 ms

714.png

714.png

1079 ms

default_marker.png

default_marker.png

6 ms

715.png

715.png

1111 ms

715.png

715.png

1112 ms

715.png

715.png

898 ms

714.png

714.png

1090 ms

714.png

714.png

909 ms

716.png

716.png

1121 ms

716.png

716.png

898 ms

716.png

716.png

957 ms

SEO Factors

jejurentcar.co.kr SEO score

0

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    N/A

  • Encoding

    EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jejurentcar.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Jejurentcar.co.kr main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

jejurentcar.co.kr

Open Graph description is not detected on the main page of Jejurentcar. 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: