10.9 sec in total
1.2 sec
9.6 sec
202 ms
Visit imistory.com now to see the best up-to-date Imistory content and also check out these interesting facts you probably never knew about imistory.com
『 이미스토리 』9년간 지켜온 믿음과 신용의 쇼핑몰 이미스토리 !!
Visit imistory.comWe analyzed Imistory.com page load time and found that the first response time was 1.2 sec and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
imistory.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value4.7 s
34/100
25%
Value4.2 s
78/100
10%
Value830 ms
35/100
30%
Value0.066
97/100
15%
Value7.1 s
51/100
10%
1154 ms
990 ms
454 ms
37 ms
458 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 80% of them (65 requests) were addressed to the original Imistory.com, 12% (10 requests) were made to This2157tr.godo.co.kr and 6% (5 requests) were made to Imistory.co.kr. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain Imistory.com.
Page size can be reduced by 207.0 kB (14%)
1.5 MB
1.3 MB
In fact, the total size of Imistory.com main page is 1.5 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. 25% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 66.0 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 66.0 kB or 89% of the original size.
Potential reduce by 80.3 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. Imistory 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 76% of the original size.
Potential reduce by 7.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. Imistory.com needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 83% of the original size.
Number of requests can be reduced by 20 (26%)
78
58
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imistory. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
index.php
1154 ms
common.js
990 ms
style.css
454 ms
jquery.min.js
37 ms
jquery.easing.1.3.min.js
458 ms
jquery.mousewheel.min.js
458 ms
jquery.sliderkit.1.9.2.pack.js
461 ms
slidermain.css
837 ms
freerun.jpg
2015 ms
topm_login.gif
904 ms
topm_join.gif
905 ms
topm_order.gif
955 ms
topm_cart.gif
1358 ms
topm_mypage.gif
1348 ms
topm_fav.gif
1356 ms
top_menu_01.gif
1351 ms
top_menu_02.gif
1378 ms
top_menu_03.gif
1801 ms
top_menu_04.gif
1769 ms
top_menu_05.gif
1800 ms
top_menu_06.gif
1801 ms
logo.gif
2883 ms
brand.js
689 ms
cate_01.gif
696 ms
cate_02.gif
749 ms
cate_03.gif
755 ms
cate_04.gif
756 ms
cate_05.gif
835 ms
cate_06.gif
1134 ms
cate_07.gif
1205 ms
cate_08.gif
1201 ms
btn_search.gif
2003 ms
m_main01.jpg
3691 ms
m_main03.jpg
3831 ms
q_01.png
812 ms
jquery.scrollfollow.js
1035 ms
q_02.png
864 ms
q_03.png
864 ms
q_04.png
875 ms
q_05.png
923 ms
theme_bu_left.gif
1822 ms
theme_bu_right.gif
1960 ms
ban_center01.jpg
2902 ms
ban_center02.jpg
2793 ms
ban_center03.jpg
2749 ms
ban_center04.jpg
3374 ms
ban_center05.jpg
4048 ms
main_index.gif
3494 ms
2807 ms
bg_maintop.gif
3178 ms
1451899101_s_0.jpg
3452 ms
1446519601_s_0.jpg
3587 ms
1446086748_s_0.jpg
3475 ms
1419505033000_s.jpg
3815 ms
1426834034_s_0.jpg
3904 ms
1427181749000_s.jpg
4046 ms
1450781152_s_0.jpg
4116 ms
1450772071_s_0.jpg
4294 ms
1451875961_s_0.jpg
4204 ms
1427180517_s_0.jpg
4478 ms
1427181859_s_0.jpg
4580 ms
1450786251_s_0.jpg
4715 ms
blank.php
4261 ms
1407833333_s_0.jpg
4570 ms
1419386471_s_0.jpg
4661 ms
1405563260_s_0.jpg
4835 ms
1367472084000_s.jpg
4803 ms
1397200208_s_0.jpg
4441 ms
1395651221_s_0.jpg
4642 ms
1382074298_s_0.jpg
4873 ms
1393313777_s_0.jpg
4675 ms
1389428159_s_0.jpg
4743 ms
1383620044_s_0.jpg
4659 ms
1388110486_s_0.jpg
4843 ms
1380273110_s_0.jpg
4720 ms
1393295519_s_0.jpg
4168 ms
1320315366_s_0.jpg
4168 ms
1341405044_s_0.jpg
3916 ms
1395488825_s_0.jpg
4126 ms
icon_soldout
3709 ms
btn.gif
3686 ms
imistory.com 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
Links do not have a discernible name
imistory.com 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
imistory.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
KO
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imistory.com 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 Imistory.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.
imistory.com
Open Graph description is not detected on the main page of Imistory. 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: