7.9 sec in total
864 ms
6.8 sec
213 ms
Welcome to yokolang.co.kr homepage info - get ready to check Yokolang best content right away, or after learning these important things about yokolang.co.kr
???? ?Ϻ????ΰ? ?Ϻ?????? ?Ϻ?????? ?Ϻ???? ?Ϻ???ȸȭ ?Ϻ???? ?Ͼ??ΰ?
Visit yokolang.co.krWe analyzed Yokolang.co.kr page load time and found that the first response time was 864 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
yokolang.co.kr performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value8.2 s
2/100
25%
Value6.3 s
42/100
10%
Value30 ms
100/100
30%
Value1.141
1/100
15%
Value3.4 s
93/100
10%
864 ms
836 ms
548 ms
1125 ms
277 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that all of those requests were addressed to Yokolang.co.kr and no external sources were called. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Yokolang.co.kr.
Page size can be reduced by 35.3 kB (2%)
1.9 MB
1.9 MB
In fact, the total size of Yokolang.co.kr main page is 1.9 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. 30% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 394 B
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 394 B or 50% of the original size.
Potential reduce by 501 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. Yokolang images are well optimized though.
Potential reduce by 34.4 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 34.4 kB or 83% of the original size.
Number of requests can be reduced by 25 (37%)
68
43
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yokolang. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
yokolang.co.kr
864 ms
SPMAIN.asp
836 ms
CMMoveWin.js
548 ms
CMSC.js
1125 ms
CMDrag.js
277 ms
bgBack.jpg
1957 ms
bgTop.jpg
1935 ms
imgLogo.jpg
278 ms
imgLangFamilyGo.gif
539 ms
btnLogin5.gif
554 ms
btnTopSubMem.jpg
555 ms
btnTopSubSide.jpg
559 ms
btnTopSub1.jpg
807 ms
btnTopSub2.jpg
830 ms
imgTopBtn1.jpg
831 ms
btnTop1.jpg
838 ms
btnTop3.jpg
1083 ms
btnTop2.jpg
1115 ms
btnTop4.jpg
1114 ms
btnTop5.jpg
1123 ms
btnTop6.jpg
1354 ms
imgTopBtn2.jpg
1392 ms
bgMain_M.jpg
3914 ms
imgMain.jpg
3070 ms
btnMainFaq1.jpg
1623 ms
imgMainFaqLine1.jpg
1670 ms
btnMainFaq2.jpg
1885 ms
imgMainFaqLine2.jpg
1936 ms
btnMainFaq3.jpg
2148 ms
btnMainFaq4.jpg
2205 ms
txtMainSample1.gif
2210 ms
txtMainSample2.gif
2232 ms
imgMainSample1.jpg
2413 ms
imgMainSample2.jpg
2481 ms
txtMainSample3.gif
2485 ms
txtMainSample4.gif
2512 ms
imgMainSample3.jpg
2682 ms
imgMainSample4.jpg
2757 ms
imgPhone4.jpg
2759 ms
imgMainAfterTitle.jpg
2791 ms
imgMainAfter.jpg
3228 ms
SPLoading.asp
2768 ms
imgOnAir2.gif
2511 ms
imgPoint51.gif
2528 ms
imgToday.gif
2784 ms
bgPopTL.gif
2782 ms
bgPopTR.gif
2562 ms
imgPop.gif
2549 ms
bgPopBL.gif
2694 ms
bgPopBR.gif
2794 ms
imgBottomLine.jpg
2551 ms
imgLogo2.jpg
2550 ms
imgBottom.jpg
2561 ms
txtFamilySite.gif
2682 ms
bgPopTL2.gif
2564 ms
imgPlay3.gif
2527 ms
bgPopTMH2.gif
2329 ms
bgPopTMB2.gif
2295 ms
bgPopTMS2.gif
2199 ms
bgPopTR2.gif
2272 ms
bgPopSBL2.gif
2268 ms
imgNull.gif
2254 ms
bgPopSBR2.gif
2092 ms
bgPopT.gif
2049 ms
bgPopML.gif
2148 ms
bgPopMR.gif
2254 ms
bgPopB.gif
2077 ms
bgFamilySite.gif
2009 ms
imgProgress.gif
1484 ms
yokolang.co.kr 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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.
yokolang.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
yokolang.co.kr 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
EL
N/A
KS_C_5601-1987
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yokolang.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Greek 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 Yokolang.co.kr main page’s claimed encoding is ks_c_5601-1987. 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.
yokolang.co.kr
Open Graph description is not detected on the main page of Yokolang. 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: