8.5 sec in total
1.3 sec
7 sec
117 ms
Visit 123.or.kr now to see the best up-to-date 123 content and also check out these interesting facts you probably never knew about 123.or.kr
Visit 123.or.krWe analyzed 123.or.kr page load time and found that the first response time was 1.3 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
123.or.kr performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value8.2 s
2/100
25%
Value12.4 s
3/100
10%
Value90 ms
99/100
30%
Value0.059
98/100
15%
Value8.4 s
39/100
10%
1319 ms
1022 ms
456 ms
466 ms
471 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that all of those requests were addressed to 123.or.kr and no external sources were called. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain 123.or.kr.
Page size can be reduced by 668.1 kB (77%)
869.5 kB
201.4 kB
In fact, the total size of 123.or.kr main page is 869.5 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. Javascripts take 728.9 kB which makes up the majority of the site volume.
Potential reduce by 38.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 38.9 kB or 82% of the original size.
Potential reduce by 415 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. Obviously, 123 needs image optimization as it can save up to 415 B or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 554.6 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 554.6 kB or 76% of the original size.
Potential reduce by 74.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. 123.or.kr needs all CSS files to be minified and compressed as it can save up to 74.2 kB or 81% of the original size.
Number of requests can be reduced by 74 (58%)
128
54
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 123. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 58 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
123.or.kr
1319 ms
jquery.min.js
1022 ms
ajax.js
456 ms
dnd.js
466 ms
right_scroll.js
471 ms
calendar.js
532 ms
commentJavascript.php
586 ms
jquery.tools.min.js
1585 ms
jquery.droppy.js
697 ms
jquery.WolfHarufacebookNav.js
703 ms
jcarousellite_1.0.1.min.js
796 ms
default.js
781 ms
fileJavascript.php
926 ms
XQuared.js
1171 ms
SpringnotePlugin.js
978 ms
EditorResizePlugin.js
1060 ms
MacroPlugin.js
1155 ms
IFrameMacroPlugin.js
1176 ms
FlashMovieMacroPlugin.js
1217 ms
AC_OETags.js
1325 ms
swfupload.js
1617 ms
swfupload.queue.js
1403 ms
FileUploadPlugin.js
1372 ms
CustomStylePlugin.js
1418 ms
xq_ui.css
1854 ms
xq_custom.css
1571 ms
styleMain.css
1636 ms
jquery.easing.1.3.min.js
1442 ms
jquery.mousewheel.min.js
1587 ms
jquery.sliderkit.1.9.2.pack.js
1623 ms
sliderkit-core.css
1667 ms
Browser.js
233 ms
DomTree.js
279 ms
Base.js
768 ms
W3.js
437 ms
Gecko.js
436 ms
Webkit.js
487 ms
Trident.js
528 ms
Factory.js
513 ms
Base.js
639 ms
W3.js
663 ms
Gecko.js
718 ms
Webkit.js
748 ms
Trident.js
793 ms
Factory.js
843 ms
Base.js
889 ms
Factory.js
949 ms
FlashMovieMacro.js
982 ms
IFrameMacro.js
964 ms
JavascriptMacro.js
1058 ms
EditHistory.js
1046 ms
Base.js
1114 ms
RichTable.js
1180 ms
Timer.js
1160 ms
Layer.js
1215 ms
Base.js
1248 ms
Control.js
1323 ms
Toolbar.js
1339 ms
_templates.js
1357 ms
Json2.js
1411 ms
Shortcut.js
1431 ms
Editor.js
1634 ms
Messages.js
1551 ms
default.css
199 ms
layout.css
268 ms
gnb.php
238 ms
etc.css
205 ms
dimension.css
227 ms
color.css
234 ms
table.css
395 ms
form.css
408 ms
border.css
452 ms
styleBBS.css
464 ms
new_bbs.css
469 ms
thisSite.latest.css
529 ms
link.css
591 ms
list.css
610 ms
WolfHarufacebookNav.css
679 ms
star.gif
200 ms
f_ico_bar01px.gif
267 ms
994d312f68a980017cb94a069a98f8410.jpg
237 ms
topMenuSide.jpg
206 ms
5ab75f91116e47c7d393185baa02ce140.gif
228 ms
sub_right_back.png
233 ms
t_ico_tri.gif
397 ms
83b235a236002c7bfbc73f72f26227840.gif
408 ms
e23da4cb6201a81efcc9833099de46cb0.gif
453 ms
cd0f367bc5a85815148c4a5ce70c7c6e0.gif
463 ms
198db7595981827ba493a5ede90e53830.gif
470 ms
2614421f8e4bf504ed7e018d1372715b0.gif
531 ms
c13cbdbc578f135fe1e1db5d063b8aff0.jpg
791 ms
preBt.gif
611 ms
s_64b878d17836d07d30e781d50877fff70.jpg
677 ms
c_btn_detailView.gif
693 ms
c_btn_online.gif
702 ms
s_5eb7425e816caeae79d90ab0d066ada80.jpg
795 ms
s_0b18286e9fd70541446fcbefd26ed8809.jpg
814 ms
nextBt.gif
904 ms
040924a32e3c2a466800335fb0f2a80e0.jpg
924 ms
bdd766363429aac15c9c14b1de8590660.jpg
938 ms
0fd0be4b4ceaf3ab5f3a0623f9776ca00.jpg
988 ms
c_title_notice.jpg
1061 ms
default.gif
1018 ms
c_btn_more.jpg
1129 ms
c_title_consult.jpg
1155 ms
reply1.gif
1175 ms
0d1dde57071e6c4a4e6ced6ddcd7ab6e0.jpg
1187 ms
31a6498220ca54e06a21af4041a176e40.gif
1220 ms
d96b320080d2f820ed6805fc632da7950.gif
1326 ms
d7d8f29fa730dc2818e8d30f764cff380.gif
1355 ms
bc2e4bd1035acff2eb4eba9e9258b2250.gif
1386 ms
ec0437813e0af1c93893979aaf71f7060.gif
1409 ms
5eb928db137db926505abf901b789f090.jpg
1386 ms
3ab0ee86a62507ab9f8c47006b4f82300.gif
1416 ms
f_btn_info_off.gif
1401 ms
f_btn_worker_off.gif
1383 ms
f_btn_personal_off.gif
1396 ms
f_btn_consult_off.gif
1359 ms
f_btn_rough_off.gif
1415 ms
994d312f68a980017cb94a069a98f8411.jpg
1367 ms
designedBy.jpg
1417 ms
mainBack.jpg
1379 ms
containerBack.jpg
1410 ms
m_tab_bg.gif
1390 ms
m_tab_allow_off.gif
1366 ms
m_tab_all_bg.gif
1352 ms
m_effect_dot.gif
1375 ms
preBt01.gif
1359 ms
nextBt01.gif
1344 ms
rightTop.jpg
1381 ms
m_tab_allow_on.gif
1336 ms
123.or.kr accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
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.
123.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
123.or.kr SEO score
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
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 123.or.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that 123.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.
123.or.kr
Open Graph description is not detected on the main page of 123. 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: