Tools & Wizards About Us
coolmes.net screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

coolmes.net

Coolmes Commercial Kitchen Equipment MFG. Co.,Ltd. _Kitchen supplies

Page Load Speed

10.2 sec in total

First Response

1 sec

Resources Loaded

8.5 sec

Page Rendered

662 ms

coolmes.net screenshot

About Website

Visit coolmes.net now to see the best up-to-date Coolmes content and also check out these interesting facts you probably never knew about coolmes.net

Coolmes Commercial Kitchen Equipment MFG. Co.,Ltd. Established in 1994, Coolmes Commercial Kitchen Equipment MFG. Co.,Ltd. locates in Xingfu Kitchen Equipment Industrial Park which is granted as “Chin...

Visit coolmes.net

Key Findings

We analyzed Coolmes.net page load time and found that the first response time was 1 sec and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

coolmes.net performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value16.3 s

0/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value21.6 s

1/100

10%

Network Requests Diagram

coolmes.net

1003 ms

www.coolmes.net

1109 ms

animate.css,iconfont.css,bootstrap.min.css,response.min.css

322 ms

site_impt_r.css

336 ms

ftmpl_impt_8d247079-4127-4c6b-9c2f-1b874d040e80.css

336 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 17% of them (15 requests) were addressed to the original Coolmes.net, 47% (42 requests) were made to Img201.yun300.cn and 18% (16 requests) were made to Static.yun300.cn. The less responsive or slowest element that took the longest time to load (6.3 sec) belongs to the original domain Coolmes.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 750.0 kB (8%)

Content Size

9.6 MB

After Optimization

8.8 MB

  • HTML
  • Images
  • CSS

In fact, the total size of Coolmes.net main page is 9.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 8.9 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 184.7 kB

  • Original 200.2 kB
  • After minification 165.0 kB
  • After compression 15.5 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 35.2 kB, which is 18% 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 184.7 kB or 92% of the original size.

Image Optimization

-2%

Potential reduce by 207.6 kB

  • Original 8.9 MB
  • After minification 8.7 MB

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. Coolmes images are well optimized though.

CSS Optimization

-78%

Potential reduce by 357.7 kB

  • Original 456.7 kB
  • After minification 436.1 kB
  • After compression 99.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. Coolmes.net needs all CSS files to be minified and compressed as it can save up to 357.7 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (26%)

Requests Now

81

After Optimization

60

  • Images
  • JavaScript
  • CSS

The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Coolmes. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

coolmes.net

coolmes.net

1003 ms

www.coolmes.net

www.coolmes.net

1109 ms

animate.css,iconfont.css,bootstrap.min.css,response.min.css

animate.css,iconfont.css,bootstrap.min.css,response.min.css

322 ms

site_impt_r.css

site_impt_r.css

336 ms

ftmpl_impt_8d247079-4127-4c6b-9c2f-1b874d040e80.css

ftmpl_impt_8d247079-4127-4c6b-9c2f-1b874d040e80.css

336 ms

page_impt_home.css

page_impt_home.css

340 ms

interwords_en.min.js,handle.min.js,libs.min.js,render.min.js

interwords_en.min.js,handle.min.js,libs.min.js,render.min.js

338 ms

q1.png

q1.png

83 ms

NGo0j2UjTIuEGYixJYkHGg.jpg

NGo0j2UjTIuEGYixJYkHGg.jpg

3130 ms

rBQBG1zeRF-EZ6WeAAAAALtrhrs312.png

rBQBG1zeRF-EZ6WeAAAAALtrhrs312.png

227 ms

ypPVPUKXTNedl00SFkOnsQ.jpg

ypPVPUKXTNedl00SFkOnsQ.jpg

3687 ms

pf_wCldFRdOdfxxJ0pgFkQ.jpg

pf_wCldFRdOdfxxJ0pgFkQ.jpg

1387 ms

mdqxQrJMQwKOSJVnUv9I1w.jpg

mdqxQrJMQwKOSJVnUv9I1w.jpg

4413 ms

r2KnjsgXQNyxDlzTAXsnUQ.jpg

r2KnjsgXQNyxDlzTAXsnUQ.jpg

6331 ms

PvLV632RSxmY58U_Tlz4kQ.jpg

PvLV632RSxmY58U_Tlz4kQ.jpg

1539 ms

rBQBHVzeREuEL1FvAAAAAB_7d88582.png

rBQBHVzeREuEL1FvAAAAAB_7d88582.png

227 ms

f.jpg

f.jpg

130 ms

s.jpg

s.jpg

130 ms

1_16.jpg

1_16.jpg

133 ms

1_19.jpg

1_19.jpg

131 ms

1_20.jpg

1_20.jpg

132 ms

1_21.jpg

1_21.jpg

131 ms

4987e.jpg

4987e.jpg

133 ms

c90.png

c90.png

135 ms

c70.png

c70.png

134 ms

c8.jpg

c8.jpg

133 ms

bgpro.jpg

bgpro.jpg

140 ms

elAFjp2VS3C3DG1DkTFlvg.jpg

elAFjp2VS3C3DG1DkTFlvg.jpg

134 ms

eBA5pzpYSZeZxVdx7dJa9w.jpg

eBA5pzpYSZeZxVdx7dJa9w.jpg

135 ms

anAzNkcgStGHmmuN9hr0Dw.jpg

anAzNkcgStGHmmuN9hr0Dw.jpg

137 ms

ToyQyEF5TiyT8lMVpOSteQ.jpg

ToyQyEF5TiyT8lMVpOSteQ.jpg

136 ms

tFk4xaNwR1u7MohixjQnsw.jpg

tFk4xaNwR1u7MohixjQnsw.jpg

138 ms

xDloVt9ERU6aMdlnQ0o-fA.jpg

xDloVt9ERU6aMdlnQ0o-fA.jpg

140 ms

d3.jpg

d3.jpg

138 ms

d7.jpg

d7.jpg

140 ms

d1.jpg

d1.jpg

142 ms

d6.jpg

d6.jpg

140 ms

d4.jpg

d4.jpg

140 ms

d2.jpg

d2.jpg

144 ms

d5.jpg

d5.jpg

142 ms

d8.jpg

d8.jpg

144 ms

loo.jpg

loo.jpg

142 ms

98a281e7b102.jpg

98a281e7b102.jpg

143 ms

rBQBG1ytZJ6EHSI7AAAAAOVKkQw624.png

rBQBG1ytZJ6EHSI7AAAAAOVKkQw624.png

198 ms

iconfont.woff

iconfont.woff

12 ms

iconfont.woff

iconfont.woff

532 ms

utils.min.js

utils.min.js

231 ms

1_27.jpg

1_27.jpg

19 ms

swiper.min.js

swiper.min.js

220 ms

response.js

response.js

2266 ms

db.jpg

db.jpg

23 ms

common.js

common.js

1643 ms

rBQBG1zeRF-EZ6WeAAAAALtrhrs312.png

rBQBG1zeRF-EZ6WeAAAAALtrhrs312.png

19 ms

rBQBHVzeREuEL1FvAAAAAB_7d88582.png

rBQBHVzeREuEL1FvAAAAAB_7d88582.png

19 ms

rBQBG1ytZJ6EHSI7AAAAAOVKkQw624.png

rBQBG1ytZJ6EHSI7AAAAAOVKkQw624.png

19 ms

portalResSearch_total-02.min.js

portalResSearch_total-02.min.js

4 ms

portalResProduct_list-01.min.js

portalResProduct_list-01.min.js

7 ms

portalResPublic_websiteShare-01.min.js

portalResPublic_websiteShare-01.min.js

6 ms

jquery.mediaQuery.min.js

jquery.mediaQuery.min.js

6 ms

iShare.min.js

iShare.min.js

13 ms

jquery.md5.min.js

jquery.md5.min.js

4 ms

jquery.confirm.min.js

jquery.confirm.min.js

6 ms

jquery.message.min.js

jquery.message.min.js

8 ms

jquery.fileDownload.min.js

jquery.fileDownload.min.js

7 ms

jquery.qrcode.min.js

jquery.qrcode.min.js

5 ms

clipboard.min.js

clipboard.min.js

7 ms

iconfont.ttf

iconfont.ttf

230 ms

iconfont.svg

iconfont.svg

458 ms

share-facebook.png

share-facebook.png

742 ms

share-linkedin.png

share-linkedin.png

740 ms

share-twitter.png

share-twitter.png

745 ms

share-tumblr.png

share-tumblr.png

743 ms

share-pinterest.png

share-pinterest.png

768 ms

initPagination.min.js

initPagination.min.js

14 ms

swiper4.4.2.min.js

swiper4.4.2.min.js

5 ms

pagination.min.js

pagination.min.js

7 ms

BystjyEXSvOM9piEzQZFzQ.jpg

BystjyEXSvOM9piEzQZFzQ.jpg

372 ms

CY4wrFpcSd2j9iU-3MCKsA.jpg

CY4wrFpcSd2j9iU-3MCKsA.jpg

29 ms

eimSy__CTEmZIuBGqP9q-A.jpg

eimSy__CTEmZIuBGqP9q-A.jpg

26 ms

HugQSUnVTk2exhw5ZSdd5A.jpg

HugQSUnVTk2exhw5ZSdd5A.jpg

29 ms

bffGoJUQQceQ-eJpCabduQ.jpg

bffGoJUQQceQ-eJpCabduQ.jpg

26 ms

sLt4HtM-Qay01yjEHCsGWw.jpg

sLt4HtM-Qay01yjEHCsGWw.jpg

30 ms

7oaZD8vDTDOOpu85GFkkfA.jpg

7oaZD8vDTDOOpu85GFkkfA.jpg

28 ms

kmTvGYzYT4ypDhSJgHI4KA.jpg

kmTvGYzYT4ypDhSJgHI4KA.jpg

29 ms

n-eAekE8TaWzv1tpqO0vQQ.jpg

n-eAekE8TaWzv1tpqO0vQQ.jpg

18 ms

GcKpBDuCRim59WBSfDlGEg.jpg

GcKpBDuCRim59WBSfDlGEg.jpg

17 ms

IaQaLhrRREulr-ydbUsZ3A.jpg

IaQaLhrRREulr-ydbUsZ3A.jpg

9 ms

5yffqw8zTSq-NnmTH4BdwA.jpg

5yffqw8zTSq-NnmTH4BdwA.jpg

10 ms

240Ys9RLRd-bM0djdbjtMQ.jpg

240Ys9RLRd-bM0djdbjtMQ.jpg

10 ms

0p8dCGvwSQaJZa6QsVnXqg.jpg

0p8dCGvwSQaJZa6QsVnXqg.jpg

10 ms

Accessibility Review

coolmes.net accessibility score

65

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

coolmes.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

coolmes.net SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Coolmes.net can be misinterpreted by Google and other search engines. Our service has detected that English 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 Coolmes.net 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.

Social Sharing Optimization

coolmes.net

Open Graph description is not detected on the main page of Coolmes. 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: