13.8 sec in total
2.2 sec
11.3 sec
342 ms
Click here to check amazing Inodea content. Otherwise, check out these important facts you probably never knew about inodea.co.kr
무료 홈페이지제작 및 유지관리 와 검색엔진 최적화 월 9,900원. 빌더 호스팅 이용 시 맞춤형으로 회사 및 홍보용 반응형 홈페이지를 제작해 드립니다.
Visit inodea.co.krWe analyzed Inodea.co.kr page load time and found that the first response time was 2.2 sec and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
inodea.co.kr performance score
name
value
score
weighting
Value4.1 s
20/100
10%
Value6.2 s
11/100
25%
Value7.0 s
32/100
10%
Value1,290 ms
18/100
30%
Value0.045
99/100
15%
Value17.3 s
4/100
10%
2194 ms
6 ms
403 ms
404 ms
466 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 99% of them (93 requests) were addressed to the original Inodea.co.kr, 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Inodea.co.kr.
Page size can be reduced by 403.6 kB (46%)
874.4 kB
470.8 kB
In fact, the total size of Inodea.co.kr main page is 874.4 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. Images take 588.4 kB which makes up the majority of the site volume.
Potential reduce by 139.2 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 28.4 kB, which is 19% 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 139.2 kB or 93% of the original size.
Potential reduce by 148.9 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. Obviously, Inodea needs image optimization as it can save up to 148.9 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 90.2 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 90.2 kB or 85% of the original size.
Potential reduce by 25.3 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. Inodea.co.kr needs all CSS files to be minified and compressed as it can save up to 25.3 kB or 84% of the original size.
Number of requests can be reduced by 42 (47%)
90
48
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inodea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
inodea.co.kr
2194 ms
jquery.min.js
6 ms
ino_rp.js
403 ms
ino_rp.css
404 ms
reset.css
466 ms
base.css
703 ms
main.css
702 ms
fla.js
805 ms
scrolltopcontrol.js
895 ms
logo_top.jpg
1814 ms
top_svc.jpg
1744 ms
top_home.gif
1175 ms
top_gab.gif
1040 ms
top_login.gif
1141 ms
top_addsvc_01.gif
1357 ms
top_addsvc.gif
1558 ms
top_customer.gif
1675 ms
menu01_r.png
1619 ms
menu02_r.png
1760 ms
menu03_r.png
1936 ms
jquery.sidr.dark.css
1963 ms
commjquery-1.7.1.min.js
2098 ms
jquery.sidr.min.js
2096 ms
jquery.pageslide.css
2084 ms
jquery.pageslide.js
2376 ms
menu04_r.png
2400 ms
menu05_r.png
2430 ms
menu06_r.png
2523 ms
menu07_r.png
2546 ms
menu08_r.png
2560 ms
menu10_r.png
2796 ms
rp_top_left_menu.png
2860 ms
logo_top.jpg
3353 ms
flexslider_full.css
2716 ms
jquery.flexslider.js
3661 ms
mainimg_00.jpg
3872 ms
mainimg_01.jpg
4235 ms
bt_login_new.gif
3107 ms
main_info.jpg
4559 ms
index.js
3921 ms
dom_search.js
3310 ms
b_search.gif
3759 ms
space.gif
3818 ms
new.gif
3811 ms
NanumBarunGothic.woff
3704 ms
secret.gif
3673 ms
old.gif
3741 ms
inodea_sns_s.js
3883 ms
top_menu_bg.jpg
3873 ms
new.gif
3647 ms
reply.gif
3604 ms
old.gif
3673 ms
iptn_660.gif
4292 ms
qr_bg.jpg
4106 ms
ptp_bt02_on.jpg
4228 ms
ptp_bt03_on.jpg
4149 ms
ptp_reg.jpg
4108 ms
old.gif
3661 ms
iptn_678.gif
4601 ms
iptn_670.gif
4313 ms
iptn_669.gif
4461 ms
iptn_668.gif
4614 ms
iptn_666.gif
4703 ms
iptn_665.gif
4605 ms
iptn_657.gif
5149 ms
iptn_646.gif
5145 ms
m_ptp_232.gif
4633 ms
iptn_641.gif
4773 ms
m_ptp_229.gif
4795 ms
fb_bbs.png
4203 ms
tw_bbs.png
4478 ms
naver_blog.jpg
4461 ms
ino_qr.php
3854 ms
ino_qr.php
3981 ms
ino_qr.php
4049 ms
ino_qr.php
3993 ms
ino_qr.php
3940 ms
ino_qr.php
4021 ms
ino_qr.php
4108 ms
ino_qr.php
3964 ms
ino_qr.php
4042 ms
ino_qr.php
4003 ms
ino_qr.php
3960 ms
ino_qr.php
3893 ms
772 ms
iptn_null_320.jpg
4520 ms
iptn_674.gif
4434 ms
bt_l.gif
3978 ms
bt_r.gif
3967 ms
mobile_bg.jpg
4015 ms
3704 ms
page_top.png
3756 ms
arr_l40.png
241 ms
arr_r40.png
476 ms
inodea.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
Form elements do not have associated labels
Links do not have a discernible name
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
inodea.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
inodea.co.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
KO
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inodea.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean 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 Inodea.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.
inodea.co.kr
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: