8.9 sec in total
595 ms
8 sec
279 ms
Welcome to cafe24.com homepage info - get ready to check Cafe 24 best content for South Korea right away, or after learning these important things about cafe24.com
첫걸음부터 탄탄하게, 내 생각대로 펼쳐지는 온라인 비즈니스의 시작
Visit cafe24.comWe analyzed Cafe24.com page load time and found that the first response time was 595 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
cafe24.com performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value17.2 s
0/100
25%
Value16.8 s
0/100
10%
Value11,290 ms
0/100
30%
Value0.005
100/100
15%
Value30.9 s
0/100
10%
595 ms
1037 ms
1238 ms
2456 ms
1922 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 34% of them (42 requests) were addressed to the original Cafe24.com, 46% (58 requests) were made to Img.cafe24.com and 11% (14 requests) were made to Ad.cafe24.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Img.cafe24.com.
Page size can be reduced by 1.3 MB (45%)
2.9 MB
1.6 MB
In fact, the total size of Cafe24.com main page is 2.9 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 80.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 25.1 kB, which is 26% 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 80.6 kB or 84% of the original size.
Potential reduce by 51.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. Cafe 24 images are well optimized though.
Potential reduce by 833.8 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 833.8 kB or 71% of the original size.
Potential reduce by 327.0 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. Cafe24.com needs all CSS files to be minified and compressed as it can save up to 327.0 kB or 85% of the original size.
Number of requests can be reduced by 67 (55%)
122
55
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cafe 24. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
cafe24.com
595 ms
www.cafe24.com
1037 ms
common30.css
1238 ms
hosting2_abs.css
2456 ms
hosting2_main_css_sp.css
1922 ms
base.css
589 ms
hosting2_ui.js
1083 ms
common_v2.js
975 ms
googleweblog.js
396 ms
WebAnalysis.js
809 ms
WebAnalysis.js
621 ms
WebAnalysis.js
620 ms
WebAnalysis.js
622 ms
domain.comm.js
200 ms
WebAnalysis.js
623 ms
conversion.js
15 ms
jquery-ui-1.8.7.custom.css
201 ms
ga.js
15 ms
img_browser_upgrade.gif
637 ms
btn_ie_upgrade.gif
201 ms
btn_other_browser.gif
204 ms
btn_close.gif
212 ms
_init.js
203 ms
jquery-ui-1.8.7.custom.min.js
983 ms
jquery.custom.plugin.min.js
205 ms
jquery.overlay.min.js
202 ms
jquery.scrollto.min.js
399 ms
wd.ajax.min.js
400 ms
wd.json.min.js
399 ms
wd.layer.min.js
609 ms
wd.leak.min.js
400 ms
wd.util.min.js
790 ms
wd.newCafe24.min.js
598 ms
comm.min.js
599 ms
click.log.js
599 ms
member.comm.js
797 ms
img_nr.png
1367 ms
menu_cmc_2.jpg
390 ms
menu_dcenter_2.jpg
408 ms
img_rx.gif
396 ms
tmenu_server_n.png
422 ms
img_css_39.gif
596 ms
mcont_c_01.jpg
791 ms
mcont_c_02.jpg
619 ms
mcont_c_09.jpg
885 ms
mcont_c_04.jpg
794 ms
mcont_c_05.jpg
828 ms
mcont_c_06.jpg
832 ms
mcont_c_07.jpg
1182 ms
mcont_c_08.jpg
994 ms
icon_new.gif
1039 ms
btn_the_domain.gif
1043 ms
tle_3_3.jpg
1514 ms
img_hot_hosting_03.jpg
1192 ms
img_shop_solution.jpg
1248 ms
bnr_cafe24_mkt.jpg
1254 ms
supermicro_main_01.jpg
1378 ms
cafe24_main_q352.jpg
1391 ms
hp_main_03.jpg
1458 ms
img_772.jpg
1465 ms
img_773.jpg
1557 ms
img_774.jpg
1574 ms
img_775.jpg
1591 ms
item_coro_01.jpg
1667 ms
item_coro_02.jpg
1676 ms
item_coro_03.jpg
1722 ms
txt_001.jpg
1754 ms
img_001.jpg
1770 ms
login_static.html
996 ms
__utm.gif
16 ms
member.main.js
677 ms
member.login.js
882 ms
39 ms
wcslog.js
38 ms
weblog_nhosting.js
646 ms
38 ms
m
1224 ms
adMngEffect.js
196 ms
adMngCookie.js
200 ms
adMngLayer.js
197 ms
admngCSS.css
200 ms
ConclusionAD.php
577 ms
ConclusionAD.php
389 ms
ConclusionAD.php
412 ms
ConclusionAD.php
395 ms
ConclusionAD.php
398 ms
tle_cscenter_2.gif
1612 ms
tle_manual_2.gif
1696 ms
tit_manual1.gif
1699 ms
tit_manual2.gif
1552 ms
txt_mail_cafe24.gif
1567 ms
img_footer_mark.gif
1569 ms
img_jpg.jpg
1776 ms
blank.gif
692 ms
sm_518x126.jpg
1645 ms
ico_mariadb.gif
1499 ms
bg_mnsg2.gif
1489 ms
bg_mnsg3.gif
1531 ms
Hosting_1210_980x80.jpg
1661 ms
img_common.gif
1363 ms
bnr_130527_501.jpg
1575 ms
bnr_130527_507.jpg
1477 ms
img_10g_layer.jpg
2548 ms
hosting2_main_css_sp.css
1999 ms
base.css
224 ms
hosting2_ui.js
1228 ms
common_v2.js
854 ms
jquery-ui-1.8.7.custom.css
568 ms
img_rx.gif
609 ms
img_nr.png
592 ms
_init.js
203 ms
jquery-ui-1.8.7.custom.min.js
870 ms
jquery.custom.plugin.min.js
404 ms
jquery.overlay.min.js
589 ms
jquery.scrollto.min.js
595 ms
wd.ajax.min.js
596 ms
wd.json.min.js
605 ms
wd.layer.min.js
603 ms
wd.leak.min.js
789 ms
wd.util.min.js
991 ms
wd.newCafe24.min.js
796 ms
comm.min.js
804 ms
click.log.js
807 ms
member.comm.js
986 ms
member.login.js
1192 ms
cafe24.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.
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.
cafe24.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
cafe24.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cafe24.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 Cafe24.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.
cafe24.com
Open Graph description is not detected on the main page of Cafe 24. 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: