8.7 sec in total
1.5 sec
7 sec
250 ms
Visit atmoll.com now to see the best up-to-date Atmoll content and also check out these interesting facts you probably never knew about atmoll.com
Visit atmoll.comWe analyzed Atmoll.com page load time and found that the first response time was 1.5 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.
atmoll.com performance score
1482 ms
488 ms
57 ms
755 ms
1511 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 95% of them (98 requests) were addressed to the original Atmoll.com, 2% (2 requests) were made to Img.cafe24.com and 1% (1 request) were made to Wcs.naver.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Atmoll.com.
Page size can be reduced by 55.2 kB (50%)
111.4 kB
56.2 kB
In fact, the total size of Atmoll.com main page is 111.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. 30% of websites need less resources to load. Images take 57.9 kB which makes up the majority of the site volume.
Potential reduce by 20.6 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 4.1 kB, which is 16% 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 20.6 kB or 78% of the original size.
Potential reduce by 16.0 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, Atmoll needs image optimization as it can save up to 16.0 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 18.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 18.6 kB or 68% of the original size.
Number of requests can be reduced by 21 (21%)
102
81
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Atmoll. 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.
atmoll.com
1482 ms
cid.generate.js
488 ms
wcslog.js
57 ms
optimizer.php
755 ms
optimizer.php
1511 ms
txt_prog_001.gif
735 ms
img_loading_bar.gif
1225 ms
825203f1b216911340eca5a3f7cfb7ca.jpg
756 ms
top_menu1.gif
247 ms
top_menu2.gif
480 ms
top_menu3.gif
482 ms
top_menu4.gif
491 ms
top_menu5.gif
503 ms
top_menu6.gif
730 ms
top_ban01.gif
1054 ms
top_ban02.gif
1054 ms
top_ban03.gif
1056 ms
topmenu_bg.gif
1178 ms
top_favorites.gif
1054 ms
top_4mbar.gif
1177 ms
top_4m1.gif
1188 ms
top_4m2.gif
1196 ms
top_4m3.gif
1221 ms
top_4m4.gif
1235 ms
search_bg.gif
1412 ms
search_btn.gif
1406 ms
fullmenu_bg.gif
1945 ms
d4eb6436ff82b1767fc307a8d35321b2.JPG
2142 ms
shop1_43_menu_615676.gif
1464 ms
b1.gif
1474 ms
b2.gif
1643 ms
b3.gif
1691 ms
b4.gif
1719 ms
b5.gif
1727 ms
b6.gif
1857 ms
b7.gif
1909 ms
b8.gif
1963 ms
b9.gif
1970 ms
b10.gif
2075 ms
b11.gif
2140 ms
b12.gif
2176 ms
m
521 ms
b13.gif
2181 ms
b14.gif
1986 ms
b15.gif
1852 ms
b16.gif
1909 ms
b17.gif
1904 ms
b18.gif
1917 ms
b19.gif
1727 ms
bx.gif
1716 ms
weblog.js
716 ms
async
1606 ms
SubCategory
1615 ms
bbs1.gif
1628 ms
qna.gif
1518 ms
bbs10.gif
1631 ms
bbs2.gif
1690 ms
bbs6.gif
1713 ms
moving_notice.gif
1689 ms
blot_3text.gif
1693 ms
ban04.gif
1761 ms
ban05.gif
1838 ms
main01.jpg
1844 ms
main02.jpg
1880 ms
ban06.gif
1485 ms
ban07.gif
1456 ms
ban08.gif
1621 ms
ban09.gif
1661 ms
weekly_over.gif
1784 ms
ban10.gif
2252 ms
customer_title.gif
1605 ms
9547dff0a27e223f5190b3631e4112f5.gif
1610 ms
bt_qban1.gif
1625 ms
bt_qban2.gif
1546 ms
bt_qban3.gif
1643 ms
btbbs_title.gif
1672 ms
btbbs_bg.gif
1657 ms
bt_pban1.gif
1643 ms
bt_pban2.gif
1642 ms
bt_pban3.gif
1678 ms
bt_pban4.gif
1645 ms
bt_pban5.gif
1675 ms
bt_pban6.gif
1666 ms
bt_pban7.gif
1647 ms
bt_bg.gif
1771 ms
bt_menu1.gif
1694 ms
bt_menu2.gif
1670 ms
bt_menu3.gif
1665 ms
bt_menu4.gif
1670 ms
bt_menu5.gif
1736 ms
bt_menu6.gif
1793 ms
ban_cafe24.gif
1693 ms
saup.gif
1670 ms
8a05613ed83902bcb9b441c09caedced.GIF
1644 ms
lban01.gif
1651 ms
lban02.gif
1712 ms
rban_favorites.gif
1584 ms
rban_top.gif
1579 ms
today_bg.gif
1611 ms
today_title.gif
1535 ms
today_up.gif
1486 ms
today_down.gif
1527 ms
today_bt.gif
1582 ms
atmoll.com SEO score
EN
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Atmoll.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Korean language. Our system also found out that Atmoll.com 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.
atmoll.com
Open Graph description is not detected on the main page of Atmoll. 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: