5.8 sec in total
984 ms
4.5 sec
283 ms
Click here to check amazing Cmfood content. Otherwise, check out these important facts you probably never knew about cmfood.com
Visit cmfood.comWe analyzed Cmfood.com page load time and found that the first response time was 984 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
cmfood.com performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value3.3 s
71/100
25%
Value3.7 s
85/100
10%
Value2,540 ms
4/100
30%
Value0
100/100
15%
Value9.8 s
28/100
10%
984 ms
201 ms
384 ms
404 ms
1241 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 48% of them (25 requests) were addressed to the original Cmfood.com, 46% (24 requests) were made to Img.echosting.cafe24.com and 4% (2 requests) were made to Login2.cafe24ssl.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Cmfood.com.
Page size can be reduced by 50.6 kB (11%)
451.9 kB
401.4 kB
In fact, the total size of Cmfood.com main page is 451.9 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. 35% of websites need less resources to load. Images take 400.2 kB which makes up the majority of the site volume.
Potential reduce by 32.9 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 32.9 kB or 87% of the original size.
Potential reduce by 8.5 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. Cmfood images are well optimized though.
Potential reduce by 9.2 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 9.2 kB or 67% of the original size.
Number of requests can be reduced by 26 (51%)
51
25
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cmfood. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
cmfood.com
984 ms
common.js
201 ms
cid.generate.js
384 ms
optimizer.php
404 ms
AuthSSLManager.js
1241 ms
AuthSSLManager.plugin.js
1253 ms
optimizer.php
996 ms
h2_login.gif
397 ms
7a2b99a59af20f80de0563b953cedb7d_7_top.jpg
222 ms
78858392880db399d5dd9c71c149d560.jpg
3148 ms
86_shop1_199301.jpg
604 ms
85_shop1_732789.jpg
422 ms
84_shop1_187491.jpg
608 ms
83_shop1_352814.jpg
820 ms
82_shop1_442207.jpg
1502 ms
16_shop1_537407.jpg
798 ms
15_shop1_522466.jpg
1506 ms
14_shop1_199517.jpg
1504 ms
13_shop1_784658.jpg
1506 ms
12_shop1_409859.jpg
1507 ms
11_shop1_787219.jpg
1508 ms
10_shop1_500564.jpg
1511 ms
9_shop1_323462.jpg
1507 ms
7a2b99a59af20f80de0563b953cedb7d_7_bottom.jpg
1508 ms
8bdd21949e515676b6ab68af6a002da1.jpg
1509 ms
e0b335e7dba69ef1411f9d02306dae86.jpg
1569 ms
txt_login_id.gif
397 ms
txt_login_pw.gif
397 ms
ico_access.gif
397 ms
btn_login_login.gif
397 ms
btn_desktop.gif
405 ms
btn_zoom_header.gif
582 ms
h2_product_1st.gif
593 ms
btn_prd_zoom.gif
593 ms
ico_product_recommended.gif
592 ms
ico_product_new.gif
595 ms
btn_bag.gif
604 ms
btn_option.gif
778 ms
h2_product_2nd.gif
787 ms
logo_cafe24.png
788 ms
h2_today.gif
787 ms
btn_todayprev.gif
791 ms
btn_todaynext.gif
805 ms
btn_pagetop_side.gif
1494 ms
bg_category_li.gif
1479 ms
bg_h2_title1.gif
1480 ms
bg_h2_title2.gif
1479 ms
bg_footer.gif
1481 ms
bg_basketCount.gif
1481 ms
weblog.js
601 ms
async
231 ms
SubCategory
215 ms
cmfood.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
cmfood.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
cmfood.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cmfood.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 Cmfood.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.
cmfood.com
Open Graph description is not detected on the main page of Cmfood. 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: