10.4 sec in total
1.1 sec
9 sec
162 ms
Visit lkam.co.kr now to see the best up-to-date Lkam content and also check out these interesting facts you probably never knew about lkam.co.kr
Visit lkam.co.krWe analyzed Lkam.co.kr page load time and found that the first response time was 1.1 sec and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lkam.co.kr performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value11.8 s
0/100
25%
Value7.7 s
24/100
10%
Value1,920 ms
8/100
30%
Value0.434
22/100
15%
Value14.4 s
9/100
10%
1148 ms
394 ms
397 ms
593 ms
2352 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 96% of them (64 requests) were addressed to the original Lkam.co.kr, 3% (2 requests) were made to Munchkin.marketo.net and 1% (1 request) were made to 211-jcd-267.mktoresp.com. The less responsive or slowest element that took the longest time to load (5.9 sec) belongs to the original domain Lkam.co.kr.
Page size can be reduced by 110.8 kB (32%)
346.0 kB
235.2 kB
In fact, the total size of Lkam.co.kr main page is 346.0 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. 15% of websites need less resources to load. Images take 215.0 kB which makes up the majority of the site volume.
Potential reduce by 12.7 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 2.0 kB, which is 12% 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 12.7 kB or 74% of the original size.
Potential reduce by 25.5 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, Lkam needs image optimization as it can save up to 25.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 66.5 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 66.5 kB or 63% of the original size.
Potential reduce by 6.2 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. Lkam.co.kr needs all CSS files to be minified and compressed as it can save up to 6.2 kB or 75% of the original size.
Number of requests can be reduced by 37 (56%)
66
29
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lkam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
lkam.co.kr
1148 ms
baseReset.css
394 ms
defaultLayout.css
397 ms
defaultIndex.css
593 ms
jquery-1.7.1.min.js
2352 ms
jcarousellite_1.0.1.pack.js
983 ms
defaultIndex.js
594 ms
defaultScript.js
588 ms
munchkin.js
53 ms
cm_wrap_bg.gif
226 ms
cm_header_bg.gif
210 ms
cm_header_logo.gif
203 ms
cm_header_gnb_line_bg.gif
204 ms
cm_header_gnb_btn_01.gif
201 ms
cm_header_gnb_sub_11.gif
205 ms
cm_header_gnb_sub_12.gif
400 ms
cm_header_gnb_sub_13.gif
401 ms
cm_header_gnb_sub_14.gif
402 ms
cm_header_gnb_sub_15.gif
402 ms
cm_header_gnb_sub_16.gif
404 ms
cm_header_gnb_sub_17.gif
425 ms
cm_header_gnb_btn_02.gif
598 ms
cm_header_gnb_sub_21.gif
601 ms
cm_header_gnb_sub_22.gif
603 ms
cm_header_gnb_btn_03.gif
599 ms
cm_header_gnb_sub_31.gif
607 ms
cm_header_gnb_sub_32.gif
626 ms
cm_header_etc_dot.gif
790 ms
cm_header_etc_link_01.gif
797 ms
cm_header_etc_link_02.gif
799 ms
cm_header_etc_link_03.gif
800 ms
cm_container_bg.png
804 ms
btn_live_stop.png
826 ms
btn_live_prev.png
984 ms
nav_visual_on.png
993 ms
nav_visual_off.png
994 ms
btn_live_next.png
994 ms
mn_intro_img.jpg
4991 ms
mn_intro_img2.jpg
5867 ms
mn_intro_img3.jpg
5862 ms
mn_latest_title_bg.gif
1191 ms
mn_latest_btn_01_ov.gif
1193 ms
mn_latest_more_btn.gif
1192 ms
munchkin.js
3 ms
visitWebPage
152 ms
mn_latest_btn_02.gif
1196 ms
btn_sc_prev.png
1197 ms
btnBnrOn.png
1195 ms
btnBnrOff.png
1392 ms
btn_sc_next.png
1389 ms
mn_bottom_content_scroll_01.gif
1570 ms
mn_bottom_content_scroll_02.gif
1593 ms
mn_bottom_content_scroll_03.gif
1592 ms
mn_fund_title.gif
1590 ms
mn_fund_sub_title_01.gif
1791 ms
mn_fund_sub_title_02.gif
1788 ms
mn_fund_sub_title_03.gif
1770 ms
mn_fund_more_btn.gif
1845 ms
cm_footer_bg.gif
1830 ms
cm_footer_logo.gif
1793 ms
cm_footer_address.gif
1987 ms
cm_footer_copyright.gif
1997 ms
cm_footer_info_link_01.gif
1992 ms
cm_footer_info_link_02.gif
2185 ms
wamark.jpg
2175 ms
nav_visual_off.gif
212 ms
nav_visual_on.gif
222 ms
lkam.co.kr accessibility score
lkam.co.kr 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
Page has valid source maps
lkam.co.kr 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
N/A
KO
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lkam.co.kr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Korean. Our system also found out that Lkam.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.
lkam.co.kr
Open Graph description is not detected on the main page of Lkam. 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: