9.5 sec in total
2.1 sec
7.3 sec
171 ms
Visit ysenb.kr now to see the best up-to-date Ysenb content and also check out these interesting facts you probably never knew about ysenb.kr
Visit ysenb.krWe analyzed Ysenb.kr page load time and found that the first response time was 2.1 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ysenb.kr performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value9.7 s
0/100
25%
Value6.4 s
40/100
10%
Value80 ms
99/100
30%
Value0.61
10/100
15%
Value8.1 s
41/100
10%
2074 ms
600 ms
523 ms
1647 ms
598 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 90% of them (70 requests) were addressed to the original Ysenb.kr, 6% (5 requests) were made to Gtp11.acecounter.com and 3% (2 requests) were made to Ysenb.co.kr. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Ysenb.co.kr.
Page size can be reduced by 131.6 kB (39%)
336.7 kB
205.1 kB
In fact, the total size of Ysenb.kr main page is 336.7 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. 30% of websites need less resources to load. Images take 177.0 kB which makes up the majority of the site volume.
Potential reduce by 12.4 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 12.4 kB or 65% of the original size.
Potential reduce by 17.6 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. Ysenb images are well optimized though.
Potential reduce by 84.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 84.8 kB or 70% of the original size.
Potential reduce by 16.8 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. Ysenb.kr needs all CSS files to be minified and compressed as it can save up to 16.8 kB or 89% of the original size.
Number of requests can be reduced by 34 (44%)
77
43
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ysenb. 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 as a result speed up the page load time.
www.ysenb.co.kr
2074 ms
gtp11.acecounter.com
600 ms
main_50002.php
523 ms
main.php
1647 ms
gtp11.acecounter.com
598 ms
design_01.css
354 ms
common.js
403 ms
design_01.js
419 ms
menu.js
430 ms
jquery-1.5.1.min.js
603 ms
jquery-ui.min.js
68 ms
member_01.gif
236 ms
member_line.gif
220 ms
member_02.gif
236 ms
member_03.gif
221 ms
member_04.gif
237 ms
member_add.gif
400 ms
flag_chi.jpg
444 ms
bna2.jpg
838 ms
title_01.gif
425 ms
btn_more.gif
435 ms
dot.gif
440 ms
btn_service01.gif
599 ms
btn_service02.gif
627 ms
btn_service03.gif
631 ms
tab01_ov.gif
637 ms
tab02.gif
644 ms
btn_more2.gif
813 ms
dot2.gif
828 ms
btn_yes.gif
826 ms
tab01.gif
835 ms
tab02_ov.gif
844 ms
call.jpg
1011 ms
btn_service04.gif
1022 ms
btn_service05.gif
1029 ms
btn_service06.gif
1034 ms
copy.gif
1041 ms
pop_01.gif
1044 ms
pop_line.gif
1212 ms
pop_02.gif
1217 ms
pop_03.gif
1232 ms
pop_04.gif
1234 ms
footer_rogo.gif
1238 ms
pop_05.gif
1240 ms
phone_top_01.png
1405 ms
phone_close.png
1397 ms
phone_close_btn.png
1231 ms
phone_left.png
1222 ms
phone_title_01.jpg
1211 ms
phone_name.png
1218 ms
phone_number.png
1382 ms
phone_interest.png
1372 ms
gtp11.acecounter.com
466 ms
gtp11.acecounter.com
426 ms
main_50002.php
1135 ms
gtp11.acecounter.com
433 ms
phone_sex.png
1244 ms
phone_age.png
1217 ms
phone_btn01_o.gif
1208 ms
phone_btn02.gif
1216 ms
phone_btn03.gif
1372 ms
phone_right.png
1219 ms
phone_foot_left.png
1216 ms
phone_do_btn.gif
1210 ms
phone_foot_right.png
1210 ms
phone_top_02.png
1212 ms
phone_title_02.jpg
1389 ms
phone_sns_text03.png
1192 ms
phone_btn01.gif
1210 ms
phone_btn02_o.gif
1207 ms
phone_title_03.jpg
1212 ms
phone_sns_text01.png
1213 ms
phone_sns_text02.png
1218 ms
phone_btn03_o.gif
1214 ms
body_bg.gif
1212 ms
board_bg.gif
1214 ms
phone_bg1.gif
1217 ms
phone_foot_center.png
1355 ms
ysenb.kr accessibility score
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
ysenb.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
ysenb.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ysenb.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Ysenb.kr 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.
ysenb.kr
Open Graph description is not detected on the main page of Ysenb. 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: