24.4 sec in total
5.5 sec
18.7 sec
194 ms
Click here to check amazing 100 content. Otherwise, check out these important facts you probably never knew about 100.or.kr
Visit 100.or.krWe analyzed 100.or.kr page load time and found that the first response time was 5.5 sec and then it took 18.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
100.or.kr performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value14.6 s
0/100
25%
Value14.7 s
1/100
10%
Value230 ms
86/100
30%
Value0.298
40/100
15%
Value10.7 s
22/100
10%
5481 ms
404 ms
405 ms
459 ms
461 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that all of those requests were addressed to 100.or.kr and no external sources were called. The less responsive or slowest element that took the longest time to load (8.1 sec) belongs to the original domain 100.or.kr.
Page size can be reduced by 519.6 kB (84%)
621.0 kB
101.4 kB
In fact, the total size of 100.or.kr main page is 621.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. 25% of websites need less resources to load. Javascripts take 510.8 kB which makes up the majority of the site volume.
Potential reduce by 24.5 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 12.3 kB, which is 43% 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 24.5 kB or 86% of the original size.
Potential reduce by 425.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 425.3 kB or 83% of the original size.
Potential reduce by 69.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. 100.or.kr needs all CSS files to be minified and compressed as it can save up to 69.8 kB or 86% of the original size.
Number of requests can be reduced by 67 (61%)
109
42
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 100. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
100.or.kr
5481 ms
style.css
404 ms
common.js
405 ms
embed.js
459 ms
menu.js
461 ms
tab2.js
474 ms
ajax.js
801 ms
common.js
869 ms
jquery-1.3.2.js
5426 ms
jquery.ui.all.js
5027 ms
calendar.js
991 ms
tinyfader.js
985 ms
base.css
991 ms
common.css
1266 ms
board.css
1488 ms
contents1.css
2168 ms
logo_sw.gif
433 ms
line_tmenu.gif
462 ms
tmenu1.gif
460 ms
tmenu2.gif
459 ms
tmenu3.gif
462 ms
tmenu4.gif
521 ms
tmenu5.gif
884 ms
btn_household.gif
858 ms
menu1.gif
865 ms
bg_submenu.gif
914 ms
menu1_1.gif
974 ms
menu1_2.gif
918 ms
menu1_4.gif
1255 ms
menu1_3.gif
1265 ms
menu2.gif
1289 ms
menu2_1.gif
1370 ms
menu2_2.gif
1369 ms
menu2_3.gif
1381 ms
menu2_4.gif
1712 ms
menu3.gif
1752 ms
menu3_1.gif
1781 ms
menu3_2.gif
1782 ms
menu3_3.gif
1797 ms
menu3_4.gif
1818 ms
menu3_5.gif
2166 ms
menu3_6.gif
2209 ms
menu4.gif
2193 ms
menu4_1.gif
2231 ms
menu4_2.gif
3055 ms
menu4_3.gif
2339 ms
menu6.gif
2573 ms
menu6_2.gif
2662 ms
menu6_4.gif
2679 ms
menu6_8.gif
2742 ms
menu6_3.gif
2805 ms
menu6_7.gif
2968 ms
blank.html
2641 ms
menu7.gif
2688 ms
menu7_4.gif
2699 ms
menu7_2.gif
2814 ms
main_visual1.jpg
8138 ms
main_visual2.jpg
7201 ms
main_visual3.jpg
6544 ms
main_btn1.gif
2733 ms
main_btn2.gif
2727 ms
main_btn3.gif
2766 ms
main_btn4.gif
3081 ms
main_btn5.gif
3106 ms
tit1.gif
2832 ms
tab1.gif
3149 ms
img_famliy1.gif
3254 ms
tab2.gif
3168 ms
img_famliy2.gif
3451 ms
tab3.gif
3564 ms
img_famliy3.gif
3753 ms
tab4.gif
3578 ms
img_famliy4.gif
4063 ms
tab5.gif
4004 ms
img_famliy5.gif
4560 ms
tab6.gif
4425 ms
img_famliy6.gif
4600 ms
tab7.gif
4560 ms
img_famliy7.gif
4936 ms
tit2.gif
5006 ms
img_saving.gif
4943 ms
btn_more.gif
4979 ms
tit3_new.gif
4964 ms
tit4.gif
5056 ms
tit5.gif
5058 ms
img_mainwebzin.gif
5260 ms
ico_new.gif
5108 ms
main_bn_1510_3.gif
5088 ms
main_bn_1510_4.gif
5112 ms
main_bn_1510_1.gif
5059 ms
main_bn_1510_2.gif
5380 ms
footer_logo.gif
5281 ms
fmenu1.gif
5010 ms
fmenu2.gif
5046 ms
fmenu3.gif
5015 ms
fmenu4.gif
4987 ms
txt_address.gif
4934 ms
txt_copyright.gif
4977 ms
bg_mvisual.gif
6478 ms
tab_visual1.gif
5319 ms
tab_visual2.gif
4615 ms
tab_visual3.gif
4593 ms
bg_icon1.gif
4510 ms
bg_icon2.gif
4249 ms
tab_visual1_on.gif
4157 ms
tab1_on.gif
4088 ms
dot_notice.gif
4019 ms
line_footer.gif
3732 ms
tab_visual2_on.gif
3724 ms
tab_visual3_on.gif
1429 ms
100.or.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
100.or.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
Page has valid source maps
100.or.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
N/A
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 100.or.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 100.or.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.
100.or.kr
Open Graph description is not detected on the main page of 100. 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: