17.2 sec in total
1.1 sec
15.9 sec
249 ms
Welcome to iamgagu.com homepage info - get ready to check Iamgagu best content for South Korea right away, or after learning these important things about iamgagu.com
아이엠 디자인하우스
Visit iamgagu.comWe analyzed Iamgagu.com page load time and found that the first response time was 1.1 sec and then it took 16.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
iamgagu.com performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.607
10/100
15%
Value0
0/100
10%
1054 ms
887 ms
457 ms
7 ms
457 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 32% of them (40 requests) were addressed to the original Iamgagu.com, 65% (80 requests) were made to Iamgagu2.godohosting.com and 1% (1 request) were made to Wcs.naver.net. The less responsive or slowest element that took the longest time to load (9.4 sec) relates to the external source Iamgagu2.godohosting.com.
Page size can be reduced by 421.7 kB (10%)
4.3 MB
3.9 MB
In fact, the total size of Iamgagu.com main page is 4.3 MB. 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 4.2 MB which makes up the majority of the site volume.
Potential reduce by 52.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 52.4 kB or 89% of the original size.
Potential reduce by 313.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. Iamgagu images are well optimized though.
Potential reduce by 53.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 53.4 kB or 74% of the original size.
Potential reduce by 2.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. Iamgagu.com needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 72% of the original size.
Number of requests can be reduced by 32 (26%)
121
89
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iamgagu. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
index.php
1054 ms
common.js
887 ms
style.css
457 ms
wcslog.js
7 ms
naverCommonInflowScript.js
457 ms
ierotator.js
694 ms
ierotator.js
674 ms
mark_circle_yellow_s.gif
983 ms
iamlogo.jpg
976 ms
001_02.jpg
398 ms
top_tel.jpg
793 ms
top_search_bu_go.gif
459 ms
top_menu_login.gif
462 ms
top_menu_join.gif
735 ms
top_menu_main_cart.gif
863 ms
top_menu_main_order.gif
862 ms
top_menu_main_mypage.gif
901 ms
top_menu_main_center.gif
1189 ms
top_menu_main_community.gif
1174 ms
top_bg.gif
1249 ms
0003-1-1_01.gif
1370 ms
0003-1-1_02.gif
1363 ms
0003-1-1_03.gif
1437 ms
0003-1-1_04.gif
1646 ms
0003-1-1_05.gif
1687 ms
0003-1-1_06.gif
1644 ms
0003-1-1_07.gif
1758 ms
0003-1-1_08.gif
1824 ms
img1.jpg
3241 ms
img2.jpg
3843 ms
img3.jpg
4179 ms
img4.jpg
5067 ms
img5.jpg
4158 ms
img1.jpg
3396 ms
img2.jpg
5030 ms
img3.jpg
5016 ms
img4.jpg
5442 ms
img5.jpg
5765 ms
img1.jpg
6206 ms
img2.jpg
6434 ms
img3.jpg
6843 ms
img4.jpg
6654 ms
img5.jpg
7002 ms
index.php
1037 ms
menu_box1.gif
404 ms
012_basic.gif
402 ms
002_basic.gif
403 ms
003_basic.gif
405 ms
004_basic.gif
457 ms
005_basic.gif
791 ms
006_basic.gif
801 ms
007_basic.gif
859 ms
008_basic.gif
860 ms
009_basic.gif
918 ms
menu_banner.gif
1180 ms
menu_box3.gif
1325 ms
customer.gif
1308 ms
bank_info.gif
1308 ms
top_search_bu_go.gif
1377 ms
fotter_01.gif
1488 ms
fotter_02.gif
1682 ms
fotter_03.gif
1711 ms
fotter_04.gif
1723 ms
fotter_05.gif
1755 ms
fotter_06.gif
1766 ms
fotter_07.gif
1933 ms
fotter_08.gif
2131 ms
fotter_09.gif
2188 ms
fotter_10.gif
2229 ms
fotter_12.gif
2214 ms
bottom_add_left.gif
2225 ms
bottom_add_right.gif
2325 ms
menu_box2.gif
2572 ms
main_green_space.png
194 ms
search.gif
2583 ms
blank.php
2266 ms
footer_bg01.gif
2355 ms
bottom_add_bg.gif
2394 ms
img1.jpg
6989 ms
img2.jpg
7178 ms
img3.jpg
7594 ms
img4.jpg
7575 ms
img5.jpg
7930 ms
img6.jpg
7794 ms
photoreview.gif
6887 ms
main-t-001_01.jpg
8303 ms
main-t-001_02.jpg
8194 ms
main-t-001_03.jpg
8076 ms
main-t-001_04.jpg
8405 ms
main-t-001_05.jpg
8683 ms
cafe.gif
7797 ms
aslye-img1.jpg
8904 ms
aslye-img2.jpg
9029 ms
aslye-img3.jpg
9165 ms
aslye-img4.jpg
8686 ms
aslye-img5.jpg
9151 ms
main001_01.gif
8854 ms
main001_02.gif
9398 ms
main001_03.gif
8905 ms
main001_04.gif
8074 ms
main001_05.gif
7915 ms
iam-pi.jpg
8105 ms
main_img_01_over.png
7018 ms
main_img_01_out.png
7074 ms
main_img_02_over.png
6554 ms
main_img_02_out.png
6590 ms
main_img_03_over.png
6643 ms
main_img_03_out.png
6382 ms
main_img_04_over.png
6065 ms
main_img_04_out.png
5816 ms
main_img_05_over.png
5655 ms
main_img_05_out.png
5557 ms
main_img_06_over.png
5383 ms
main_img_06_out.png
5276 ms
m
439 ms
undefined
518 ms
0003-1_01.gif
392 ms
0003-1_02.gif
395 ms
0003-1_03.gif
450 ms
0003-1_04.gif
461 ms
0003-1_05.gif
462 ms
0003-1_06.gif
508 ms
0003-1_07.gif
783 ms
0003-1_08.gif
849 ms
iamgagu.com accessibility score
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
<frame> or <iframe> elements do not have a title
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
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.
iamgagu.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
iamgagu.com 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
N/A
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iamgagu.com 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 Iamgagu.com 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.
iamgagu.com
Open Graph description is not detected on the main page of Iamgagu. 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: