12.6 sec in total
1.6 sec
10.9 sec
121 ms
Welcome to namecheck.co.kr homepage info - get ready to check Namecheck best content for South Korea right away, or after learning these important things about namecheck.co.kr
휴대폰 본인인증 가격 문의, 즉시 견적 가능, 전문 컨설턴트의 견적 안내 및 도입 상담
Visit namecheck.co.krWe analyzed Namecheck.co.kr page load time and found that the first response time was 1.6 sec and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
namecheck.co.kr performance score
name
value
score
weighting
Value15.3 s
0/100
10%
Value24.8 s
0/100
25%
Value15.3 s
1/100
10%
Value370 ms
71/100
30%
Value0.023
100/100
15%
Value28.0 s
0/100
10%
1627 ms
765 ms
771 ms
970 ms
1160 ms
Our browser made a total of 182 requests to load all elements on the main page. We found that 99% of them (180 requests) were addressed to the original Namecheck.co.kr, 1% (2 requests) were made to Analysis.adinsight.co.kr. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Namecheck.co.kr.
Page size can be reduced by 386.6 kB (44%)
875.9 kB
489.3 kB
In fact, the total size of Namecheck.co.kr main page is 875.9 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. 35% of websites need less resources to load. Images take 458.6 kB which makes up the majority of the site volume.
Potential reduce by 25.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 25.9 kB or 80% of the original size.
Potential reduce by 36.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. Namecheck images are well optimized though.
Potential reduce by 263.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 263.4 kB or 84% of the original size.
Potential reduce by 60.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. Namecheck.co.kr needs all CSS files to be minified and compressed as it can save up to 60.8 kB or 84% of the original size.
Number of requests can be reduced by 29 (16%)
181
152
The browser has sent 181 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Namecheck. 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 from 6 to 1 for CSS and as a result speed up the page load time.
index.jsp
1627 ms
style.css
765 ms
access.css
771 ms
AC_RunActiveContent.js
970 ms
common.js
1160 ms
jquery-1.7.2.js
2350 ms
gnb_common.js
598 ms
menu.js
1031 ms
base.css
195 ms
layout.css
391 ms
board.css
388 ms
popup.css
589 ms
20150603_popup.jpg
1351 ms
img_top_logo.gif
198 ms
glb_admin.gif
195 ms
glb_l.gif
194 ms
glb_contact.gif
201 ms
glb_sitemap.gif
198 ms
bg_btm.gif
387 ms
bg_line.gif
388 ms
bg_gnb_02.png
393 ms
gnb_title_02.png
389 ms
mgnb1_off.png
398 ms
mgnb1_on.png
577 ms
gnb_bgsub.png
580 ms
c_gnb1_01_off.gif
583 ms
c_gnb1_01_on.gif
586 ms
c_gnb1_02_off.gif
595 ms
c_gnb1_02_on.gif
768 ms
c_gnb1_03_off.gif
772 ms
c_gnb1_03_on.gif
774 ms
c_gnb1_04_off.gif
780 ms
c_gnb1_04_on.gif
793 ms
c_gnb1_05_off.gif
959 ms
c_gnb1_05_on.gif
963 ms
c_gnb1_06_off.gif
966 ms
c_gnb1_06_on.gif
976 ms
c_gnb1_07_off.gif
990 ms
c_gnb1_07_on.gif
1151 ms
mgnb2_off.png
1157 ms
mgnb2_on.png
1158 ms
c_gnb2_01_off.gif
1171 ms
c_gnb2_01_on.gif
1188 ms
c_gnb2_02_off.gif
1342 ms
c_gnb2_02_on.gif
1349 ms
c_gnb2_03_off.gif
1350 ms
c_gnb2_03_on.gif
1366 ms
c_gnb2_04_off.gif
1367 ms
trs_esc.js
1192 ms
c_gnb2_04_on.gif
1350 ms
c_gnb2_05_off.gif
1350 ms
c_gnb2_05_on.gif
1355 ms
c_gnb2_06_off.gif
1357 ms
c_gnb2_06_on.gif
1373 ms
mgnb3_off.png
1207 ms
mgnb3_on.png
1349 ms
c_gnb3_01_off.gif
1346 ms
c_gnb3_01_on.gif
1353 ms
c_gnb3_02_off.gif
1349 ms
c_gnb3_02_on.gif
1189 ms
c_gnb3_03_off.gif
1210 ms
c_gnb3_03_on.gif
1346 ms
c_gnb3_04_off.gif
1344 ms
c_gnb3_04_on.gif
1343 ms
c_gnb3_05_off.gif
1170 ms
c_gnb3_05_on.gif
1190 ms
c_gnb3_06_off.gif
1213 ms
c_gnb3_06_on.gif
1338 ms
c_gnb3_07_off.gif
1326 ms
c_gnb3_07_on.gif
1171 ms
mgnb4_off.png
1167 ms
mgnb4_on.png
1191 ms
c_gnb4_01_off.gif
1210 ms
c_gnb4_01_on.gif
1319 ms
c_gnb4_02_off.gif
1158 ms
c_gnb4_02_on.gif
1164 ms
c_gnb4_03_off.gif
1163 ms
c_gnb4_03_on.gif
1181 ms
c_gnb4_04_off.gif
1195 ms
log.php
227 ms
c_gnb4_04_on.gif
1159 ms
c_gnb4_05_off.gif
1159 ms
c_gnb4_05_on.gif
1165 ms
c_gnb4_06_off.gif
1164 ms
c_gnb4_06_on.gif
1179 ms
c_gnb4_07_off.gif
1196 ms
c_gnb4_07_on.gif
1158 ms
c_gnb4_08_off.gif
1160 ms
c_gnb4_08_on.gif
1167 ms
mgnb5_off.png
1164 ms
mgnb5_on.png
1179 ms
c_gnb5_01_off.gif
1196 ms
c_gnb5_01_on.gif
1158 ms
c_gnb5_02_off.gif
1160 ms
c_gnb5_02_on.gif
1166 ms
c_gnb5_03_off.gif
1166 ms
c_gnb5_03_on.gif
1179 ms
c_gnb5_04_off.gif
1196 ms
c_gnb5_04_on.gif
1158 ms
mgnb6_off.png
1159 ms
mgnb6_on.png
1166 ms
c_gnb6_01_off.gif
1166 ms
c_gnb6_01_on.gif
1181 ms
c_gnb6_02_off.gif
1196 ms
c_gnb6_02_on.gif
1158 ms
c_gnb6_03_off.gif
1161 ms
c_gnb6_03_on.gif
1165 ms
c_gnb6_04_off.gif
1187 ms
c_gnb6_04_on.gif
1181 ms
c_gnb6_05_off.gif
1195 ms
c_gnb6_05_on.gif
1158 ms
c_gnb6_06_off.gif
1160 ms
c_gnb6_06_on.gif
1165 ms
c_gnb6_07_off.gif
1187 ms
c_gnb6_07_on.gif
1180 ms
c_gnb6_08_off.gif
1196 ms
c_gnb6_08_on.gif
1156 ms
mgnb7_off.png
1161 ms
mgnb7_on.png
1164 ms
c_gnb7_01_off.gif
1186 ms
c_gnb7_01_on.gif
1182 ms
c_gnb7_02_off.gif
1196 ms
c_gnb7_02_on.gif
1157 ms
c_gnb7_03_off.gif
1160 ms
c_gnb7_03_on.gif
1162 ms
c_gnb7_04_off.gif
1186 ms
c_gnb7_04_on.gif
1180 ms
c_gnb7_05_off.gif
1196 ms
c_gnb7_05_on.gif
1157 ms
ico1_5_off.gif
1354 ms
bg_tab5.jpg
1932 ms
tit1_5.gif
1380 ms
btn_detail5_1.gif
1181 ms
btn_detail5_3.gif
1197 ms
ico1_4_off.gif
1349 ms
bg_tab4.jpg
2059 ms
tit1_4.gif
1476 ms
btn_detail4.gif
1336 ms
ico1_6_off.png
1534 ms
bg_tab6.jpg
2016 ms
tit1_6.gif
1357 ms
btn_detail_mypin.gif
1498 ms
ico1_2_off.gif
1723 ms
bg_tab2.jpg
1938 ms
tit1_2.gif
1638 ms
btn_detail2.gif
1653 ms
ico1_3_off.png
1906 ms
bg_tab3.jpg
2318 ms
tit1_3.gif
1740 ms
btn_detail3.gif
1831 ms
ico1_1_off.png
1858 ms
bg_tab1.jpg
2034 ms
tit1_1.gif
1790 ms
btn_detail1.gif
1874 ms
btn_go.gif
1890 ms
bn1_1.gif
1880 ms
bn1_2.gif
1913 ms
bn1_3.gif
1956 ms
gnb1_9.gif
1919 ms
btn_detaill.gif
1921 ms
txt_check.gif
1936 ms
btn_regi_go.gif
1940 ms
ls1_1.gif
2004 ms
ls1_2.gif
1991 ms
bn_call.gif
1926 ms
foot_logo.gif
1859 ms
foot_menu1.gif
1827 ms
foot_menu6.gif
1788 ms
foot_menu4.gif
1841 ms
foot_menu7.gif
1740 ms
foot_menu5.gif
1726 ms
foot_family.gif
1599 ms
foot_family_1.gif
1567 ms
foot_family_3.gif
1551 ms
foot_family_4.gif
1548 ms
foot_copyright.gif
1518 ms
foot_dlink5_off.gif
1395 ms
wamark_nc_off.gif
1351 ms
ico1_5_on.gif
1358 ms
bul_ls.gif
1276 ms
bg_line2.gif
1322 ms
foot_l.gif
1322 ms
namecheck.co.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
namecheck.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
namecheck.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
KO
KO
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Namecheck.co.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 Namecheck.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.
namecheck.co.kr
Open Graph description is not detected on the main page of Namecheck. 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: