13 sec in total
1.7 sec
10.7 sec
538 ms
Visit 2sol.co.kr now to see the best up-to-date 2 Sol content for South Korea and also check out these interesting facts you probably never knew about 2sol.co.kr
이솔,화장품,건강한화장품,프로폴리스수딩솔루션
Visit 2sol.co.krWe analyzed 2sol.co.kr page load time and found that the first response time was 1.7 sec and then it took 11.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
2sol.co.kr performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value37.9 s
0/100
25%
Value25.8 s
0/100
10%
Value1,110 ms
23/100
30%
Value0.836
4/100
15%
Value44.7 s
0/100
10%
1712 ms
545 ms
549 ms
561 ms
555 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 51% of them (45 requests) were addressed to the original 2sol.co.kr, 35% (31 requests) were made to Dkflthf123.cdn-nhncommerce.com and 15% (13 requests) were made to Godomall.speedycdn.net. The less responsive or slowest element that took the longest time to load (4.6 sec) relates to the external source Godomall.speedycdn.net.
Page size can be reduced by 540.2 kB (4%)
12.0 MB
11.5 MB
In fact, the total size of 2sol.co.kr main page is 12.0 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. 55% of websites need less resources to load. Images take 11.8 MB which makes up the majority of the site volume.
Potential reduce by 88.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 24.2 kB, which is 24% 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 88.6 kB or 86% of the original size.
Potential reduce by 408.7 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. 2 Sol images are well optimized though.
Potential reduce by 33.7 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 33.7 kB or 26% of the original size.
Potential reduce by 9.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. 2sol.co.kr needs all CSS files to be minified and compressed as it can save up to 9.3 kB or 22% of the original size.
Number of requests can be reduced by 27 (33%)
83
56
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2 Sol. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.2sol.co.kr
1712 ms
reset.css
545 ms
common.css
549 ms
layer.css
561 ms
layout.css
555 ms
list.css
564 ms
button.css
717 ms
main.css
1084 ms
chosen.css
1088 ms
custom.css
1104 ms
gd_gettext.js
1108 ms
jquery.min.js
1307 ms
underscore-min.js
1247 ms
jquery.validate.min.js
1623 ms
additional-methods.min.js
1626 ms
numeral.min.js
1633 ms
accounting.min.js
1635 ms
money.min.js
1791 ms
chosen.jquery.min.js
1843 ms
placeholders.jquery.min.js
2174 ms
clipboard.min.js
2182 ms
jquery.vticker.js
2192 ms
gd_ui.js
2208 ms
gd_common.js
2332 ms
gd_visit.js
2384 ms
jquery.cookie.js
2709 ms
gd_popup.js
2728 ms
gd_plus_review.js
2758 ms
slick.js
2825 ms
gd_plus_review.css
2725 ms
07ec8879ad7e89e7d9e515ba20c2ca28_68465.png
1213 ms
1710100001_main_067.jpg
1371 ms
top_login_icn.png
1251 ms
top_myp_icn.png
1193 ms
main_sch_btn.png
1216 ms
d589de6cf74f3c275f8c19ea17b56943_56676.jpg
2382 ms
cec19490273d77583a886e929a644812_55422.jpg
1876 ms
931271b8750e7fe1c21af535c91782cf_98777.jpg
1958 ms
icon_basket_cart.png
1385 ms
layer_godetail_btn.png
1412 ms
44488056b538eff66d98fb8785edece4_80996.png
2201 ms
1710120034_main_096.jpg
1766 ms
1804240002_main_066.jpg
1800 ms
1710110017_main_016.jpg
1958 ms
1710120016_main_052.jpg
2185 ms
7c619d6502d26ffa6b7c3e88af0bf874_83422.png
2086 ms
5ae4aa82f9e0b4c365288ce92fd91b60_97243.png
2151 ms
dafd15f9d5e5774c52b9ee151059c0f8_32126.png
2337 ms
023b141515cc64ebd092dd3978f60394_45057.png
2296 ms
5241110fe9712e7df6c4d7d4e35923c0_15713.png
2354 ms
0a6c136d77785d6eb5711f035740f46e_27793.png
2570 ms
7c311e76699cf23d7b6c47b7f8cf9448_46078.png
2396 ms
dfa7b5a1a13d24def196041857571c12_91484.png
2505 ms
bfc5d3d4d49654195634a40072f1a5bc_31711.png
2529 ms
682ecbabbab8def12c57a8c4767b19c6_90987.png
2546 ms
logo_kftc.png
2582 ms
scroll-banner-right01.jpg
2587 ms
btn_scroll_prev.png
4558 ms
btn_scroll_next.png
4559 ms
btn_scroll_top.png
4560 ms
2103040045_main_060.jpg
1388 ms
2103040016_main_080.jpg
1446 ms
1710120018_main_096.jpg
1460 ms
1912240001_main_077.jpg
1464 ms
1710120034_main_096.jpg
1466 ms
1803230003_main_02.jpg
1553 ms
1804240003_main_041.jpg
1580 ms
2012080001_main_036.jpg
1650 ms
740f09e29f6a78cd380
4564 ms
223761568c0d2a00637
4554 ms
9d5598934684f63d199
4567 ms
45d67c0d748d754c139
4559 ms
top_cart_icn.png
350 ms
btn_allmenu_close.png
523 ms
btn_top_search.png
559 ms
NotoSansKR-Regular.otf
1792 ms
NotoSansKR-Medium.otf
1798 ms
NotoSansKR-Light.otf
1898 ms
NotoSansKR-Bold.otf
2294 ms
NotoSansKR-Black.otf
2497 ms
main_review_under_arr.png
1041 ms
more_plus_icn.png
1591 ms
insta_arr.png
2068 ms
popup_ps.php
2457 ms
plus_review_popup.php
4417 ms
GettyImages-jv13486559_174638.jpg
944 ms
623a3effb14b1bbf20130b9813d5d5f5_164210.jpg
826 ms
check_off_small.png
184 ms
layer-close.png
551 ms
2sol.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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
[id] attributes on active, focusable elements are not unique
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
2sol.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
2sol.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
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 2sol.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 2sol.co.kr 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.
2sol.co.kr
Open Graph data is detected on the main page of 2 Sol. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: