Tools & Wizards About Us
jnpenglish.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

jnpenglish.com

Jung & People English

Page Load Speed

15.1 sec in total

First Response

596 ms

Resources Loaded

14.3 sec

Page Rendered

253 ms

jnpenglish.com screenshot

About Website

Click here to check amazing Jnp English content for South Korea. Otherwise, check out these important facts you probably never knew about jnpenglish.com

Jung & People English 웹사이트에 오신 것을 환영합니다.

Visit jnpenglish.com

Key Findings

We analyzed Jnpenglish.com page load time and found that the first response time was 596 ms and then it took 14.5 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

jnpenglish.com performance score

0

Network Requests Diagram

jnpenglish.com

596 ms

www.jnpenglish.com

2592 ms

jquery-1.4.2.min.js

2763 ms

EchoScriptV2.js

638 ms

31 ms

Our browser made a total of 139 requests to load all elements on the main page. We found that 86% of them (120 requests) were addressed to the original Jnpenglish.com, 4% (6 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Maxst.icons8.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Jnpenglish.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 550.0 kB (84%)

Content Size

652.8 kB

After Optimization

102.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Jnpenglish.com main page is 652.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. CSS take 513.9 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 3.6 kB

  • Original 5.6 kB
  • After minification 5.4 kB
  • After compression 1.9 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 3.6 kB or 65% of the original size.

JavaScript Optimization

-72%

Potential reduce by 96.0 kB

  • Original 133.4 kB
  • After minification 123.3 kB
  • After compression 37.3 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 96.0 kB or 72% of the original size.

CSS Optimization

-88%

Potential reduce by 450.4 kB

  • Original 513.9 kB
  • After minification 460.7 kB
  • After compression 63.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. Jnpenglish.com needs all CSS files to be minified and compressed as it can save up to 450.4 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (35%)

Requests Now

79

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jnpenglish.com

jnpenglish.com

596 ms

www.jnpenglish.com

www.jnpenglish.com

2592 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

2763 ms

EchoScriptV2.js

EchoScriptV2.js

638 ms

31 ms

MainPageFrAction.do

MainPageFrAction.do

1174 ms

28 ms

26 ms

default.css

default.css

1269 ms

jquery.ui.all.css

jquery.ui.all.css

2385 ms

prototype.js

prototype.js

3124 ms

jquery-1.7.1.js

jquery-1.7.1.js

1535 ms

jquery.ui.core.js

jquery.ui.core.js

2432 ms

jquery.ui.widget.js

jquery.ui.widget.js

573 ms

jquery.ui.datepicker.js

jquery.ui.datepicker.js

955 ms

jquery.ui.datepicker-ko.js

jquery.ui.datepicker-ko.js

1180 ms

lib.common.js

lib.common.js

1564 ms

utils.js

utils.js

1486 ms

message.js

message.js

1704 ms

event.js

event.js

1731 ms

calendar.js

calendar.js

1758 ms

common.js

common.js

1922 ms

common_message.js

common_message.js

1930 ms

function.js

function.js

1953 ms

image.js

image.js

2138 ms

list.js

list.js

2129 ms

write.js

write.js

2150 ms

cookie.js

cookie.js

2329 ms

LmsDwr.js

LmsDwr.js

2353 ms

engine.js

engine.js

2351 ms

util.js

util.js

2525 ms

popup.js

popup.js

2550 ms

upload.js

upload.js

2572 ms

common.js

common.js

4581 ms

fckeditor.js

fckeditor.js

2645 ms

main.js

main.js

2725 ms

display.js

display.js

2755 ms

check.js

check.js

2793 ms

string.js

string.js

2884 ms

ui.js

ui.js

2925 ms

line-awesome.min.css

line-awesome.min.css

150 ms

bootstrap.min.css

bootstrap.min.css

3322 ms

owl.carousel.min.css

owl.carousel.min.css

3016 ms

owl.theme.default.min.css

owl.theme.default.min.css

3100 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

7 ms

conversion.js

conversion.js

72 ms

basic_style.css

basic_style.css

2765 ms

menu.css

menu.css

2674 ms

home_style.css

home_style.css

2376 ms

animate.min.css

animate.min.css

2323 ms

aos.css

aos.css

2062 ms

bootstrap.min.js

bootstrap.min.js

1980 ms

owl.carousel.min.js

owl.carousel.min.js

1987 ms

imageMapResizer.min.js

imageMapResizer.min.js

1987 ms

js_cont.js

js_cont.js

1832 ms

aos.js

aos.js

1957 ms

date_time.js

date_time.js

1941 ms

jquery.ui.base.css

jquery.ui.base.css

1336 ms

jquery.ui.theme.css

jquery.ui.theme.css

1352 ms

jquery.ui.core.css

jquery.ui.core.css

198 ms

jquery.ui.resizable.css

jquery.ui.resizable.css

221 ms

jquery.ui.selectable.css

jquery.ui.selectable.css

219 ms

jquery.ui.accordion.css

jquery.ui.accordion.css

198 ms

jquery.ui.autocomplete.css

jquery.ui.autocomplete.css

217 ms

jquery.ui.button.css

jquery.ui.button.css

399 ms

jquery.ui.dialog.css

jquery.ui.dialog.css

399 ms

jquery.ui.slider.css

jquery.ui.slider.css

417 ms

jquery.ui.tabs.css

jquery.ui.tabs.css

444 ms

jquery.ui.datepicker.css

jquery.ui.datepicker.css

445 ms

jquery.ui.progressbar.css

jquery.ui.progressbar.css

2597 ms

NotoSerif-Web.css

NotoSerif-Web.css

46 ms

mark_rec_yellow_s.gif

mark_rec_yellow_s.gif

985 ms

btn_close.gif

btn_close.gif

1155 ms

logo.jpg

logo.jpg

1154 ms

ico_01.png

ico_01.png

260 ms

ico_02.png

ico_02.png

259 ms

ico_03.png

ico_03.png

207 ms

ico_04.png

ico_04.png

207 ms

main_bg_01.jpg

main_bg_01.jpg

1153 ms

main_bg_02.jpg

main_bg_02.jpg

1153 ms

ico_05.png

ico_05.png

418 ms

ico_06.png

ico_06.png

440 ms

ico_07.png

ico_07.png

623 ms

link_btn.png

link_btn.png

663 ms

fun_logo.png

fun_logo.png

816 ms

jeong_01.png

jeong_01.png

1151 ms

jeong_02.png

jeong_02.png

1152 ms

kb_logo.png

kb_logo.png

1151 ms

Goodcontent_h46.png

Goodcontent_h46.png

1151 ms

NotoSerif-Web.css

NotoSerif-Web.css

17 ms

MainPageFrAction.do

MainPageFrAction.do

810 ms

bg_login_box.png

bg_login_box.png

1066 ms

blit_01.jpg

blit_01.jpg

1066 ms

NotoSansKR-Regular.woff

NotoSansKR-Regular.woff

87 ms

NotoSansKR-Medium.woff

NotoSansKR-Medium.woff

461 ms

NotoSansKR-Light.woff

NotoSansKR-Light.woff

150 ms

NotoSansKR-Thin.woff

NotoSansKR-Thin.woff

594 ms

NotoSansKR-Bold.woff

NotoSansKR-Bold.woff

407 ms

NotoSansKR-Black.woff

NotoSansKR-Black.woff

192 ms

la-solid-900.woff

la-solid-900.woff

64 ms

la-regular-400.woff

la-regular-400.woff

63 ms

arrow_01.png

arrow_01.png

1011 ms

banner_bg_01.jpg

banner_bg_01.jpg

1011 ms

banner_bg_02.jpg

banner_bg_02.jpg

1010 ms

fun_bg.png

fun_bg.png

1012 ms

trs_esc.js

trs_esc.js

903 ms

default.css

default.css

261 ms

jquery.ui.all.css

jquery.ui.all.css

259 ms

prototype.js

prototype.js

263 ms

jquery-1.7.1.js

jquery-1.7.1.js

260 ms

jquery.ui.core.js

jquery.ui.core.js

260 ms

jquery.ui.widget.js

jquery.ui.widget.js

261 ms

jquery.ui.datepicker.js

jquery.ui.datepicker.js

258 ms

jquery.ui.datepicker-ko.js

jquery.ui.datepicker-ko.js

260 ms

lib.common.js

lib.common.js

260 ms

utils.js

utils.js

260 ms

message.js

message.js

261 ms

event.js

event.js

260 ms

calendar.js

calendar.js

260 ms

common.js

common.js

259 ms

common_message.js

common_message.js

259 ms

function.js

function.js

259 ms

image.js

image.js

259 ms

list.js

list.js

259 ms

write.js

write.js

258 ms

cookie.js

cookie.js

257 ms

LmsDwr.js

LmsDwr.js

255 ms

engine.js

engine.js

256 ms

39 ms

StatsConnectAction.do

StatsConnectAction.do

4 ms

util.js

util.js

0 ms

popup.js

popup.js

4 ms

upload.js

upload.js

2 ms

common.js

common.js

2 ms

fckeditor.js

fckeditor.js

3 ms

main.js

main.js

2 ms

display.js

display.js

2 ms

check.js

check.js

2 ms

ico_new.gif

ico_new.gif

4 ms

SEO Factors

jnpenglish.com 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 Jnpenglish.com 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 Jnpenglish.com 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

jnpenglish.com

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