Tools & Wizards About Us
cutt.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

cutt.com

Page Load Speed

82.1 sec in total

First Response

6.4 sec

Resources Loaded

74.6 sec

Page Rendered

1.1 sec

cutt.com screenshot

About Website

Welcome to cutt.com homepage info - get ready to check Cutt best content for China right away, or after learning these important things about cutt.com

简网，苹果（IOS）、安卓（android）移动客户端（APP）生成工具。无需编程，无需APP外包，无需APP开发，3分钟创建自己的APP。

Visit cutt.com

Key Findings

We analyzed Cutt.com page load time and found that the first response time was 6.4 sec and then it took 75.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 11 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

cutt.com performance score

0

Network Requests Diagram

www.cutt.com

6420 ms

1761 ms

wp-emoji-release.min.js

676 ms

formidablepro.css

1505 ms

style.css

1845 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 79% of them (87 requests) were addressed to the original Cutt.com, 6% (7 requests) were made to Hb.crm2.qq.com and 4% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Cutt.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 299.7 kB (45%)

Content Size

670.0 kB

After Optimization

370.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cutt.com main page is 670.0 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. 45% of websites need less resources to load. Images take 276.4 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 7.9 kB

  • Original 11.0 kB
  • After minification 8.7 kB
  • After compression 3.2 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 2.4 kB, which is 21% 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 7.9 kB or 71% of the original size.

Image Optimization

-14%

Potential reduce by 38.7 kB

  • Original 276.4 kB
  • After minification 237.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. Obviously, Cutt needs image optimization as it can save up to 38.7 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-49%

Potential reduce by 100.5 kB

  • Original 204.5 kB
  • After minification 193.9 kB
  • After compression 104.0 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 100.5 kB or 49% of the original size.

CSS Optimization

-86%

Potential reduce by 152.7 kB

  • Original 178.1 kB
  • After minification 137.0 kB
  • After compression 25.4 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. Cutt.com needs all CSS files to be minified and compressed as it can save up to 152.7 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (57%)

Requests Now

90

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cutt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.cutt.com

www.cutt.com

6420 ms

1761 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

676 ms

formidablepro.css

formidablepro.css

1505 ms

style.css

style.css

1845 ms

masterslider.main.css

masterslider.main.css

1847 ms

custom.css

custom.css

2834 ms

glyphicons.css

glyphicons.css

4173 ms

themo_animations.css

themo_animations.css

1395 ms

bootstrap.min.css

bootstrap.min.css

4317 ms

ekko-lightbox.min.css

ekko-lightbox.min.css

1901 ms

ekko-dark.css

ekko-dark.css

2265 ms

flexslider.css

flexslider.css

2667 ms

app.css

app.css

4255 ms

header.css

header.css

2689 ms

responsive.css

responsive.css

3787 ms

jquery.js

jquery.js

5494 ms

jquery-migrate.min.js

jquery-migrate.min.js

3533 ms

modernizr-2.7.0.min.js

modernizr-2.7.0.min.js

4271 ms

jquery.backstretch.min.js

jquery.backstretch.min.js

4198 ms

wpa.php

wpa.php

830 ms

init.js

init.js

3579 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

3743 ms

jquery.stellar.min.js

jquery.stellar.min.js

3905 ms

main.js

main.js

3925 ms

bootstrap.min.js

bootstrap.min.js

3967 ms

application.js

application.js

3854 ms

ekko-lightbox.min.js

ekko-lightbox.min.js

4006 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

4295 ms

masonry.min.js

masonry.min.js

4696 ms

jquery.scrollUp.min.js

jquery.scrollUp.min.js

4196 ms

jquery.smooth-scroll.min.js

jquery.smooth-scroll.min.js

4231 ms

jquery.ba-bbq.js

jquery.ba-bbq.js

4696 ms

waypoints.min.js

waypoints.min.js

4460 ms

headhesive.min.js

headhesive.min.js

4514 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

5153 ms

retina.min.js

retina.min.js

4731 ms

wp-embed.min.js

wp-embed.min.js

4787 ms

jquery.placeholder.js

jquery.placeholder.js

4891 ms

formidable.min.js

formidable.min.js

5250 ms

css

css

26 ms

hm.js

hm.js

5555 ms

logo.png

logo.png

330 ms

part01_new-200x180.png

part01_new-200x180.png

1118 ms

part02_new-200x180.png

part02_new-200x180.png

789 ms

part03_new-200x180.png

part03_new-200x180.png

1035 ms

service01-360x298.png

service01-360x298.png

1407 ms

service02-360x280.png

service02-360x280.png

2227 ms

service03-360x298.png

service03-360x298.png

1686 ms

product_01-200x140.png

product_01-200x140.png

1051 ms

product_02-200x140.png

product_02-200x140.png

1315 ms

product_03-200x140.png

product_03-200x140.png

1405 ms

product_04-200x140.png

product_04-200x140.png

1407 ms

product_05-200x140.png

product_05-200x140.png

1591 ms

product_06-200x140.png

product_06-200x140.png

1683 ms

product_07-200x140.png

product_07-200x140.png

1688 ms

product__08-200x140.png

product__08-200x140.png

1689 ms

product_09-200x140.png

product_09-200x140.png

1930 ms

tour_01-360x459.png

tour_01-360x459.png

4107 ms

tour_02-360x459.png

tour_02-360x459.png

3027 ms

tour_03-360x459.png

tour_03-360x459.png

3316 ms

tour_04-360x459.png

tour_04-360x459.png

3313 ms

tour_05-360x459.png

tour_05-360x459.png

4430 ms

tour_06-360x459.png

tour_06-360x459.png

3726 ms

tour_07-360x459.png

tour_07-360x459.png

3967 ms

tour_08-360x459.png

tour_08-360x459.png

4666 ms

tour_09-360x459.png

tour_09-360x459.png

10347 ms

num_area-300x119.png

num_area-300x119.png

4278 ms

num_download-300x119.png

num_download-300x119.png

4500 ms

num_team-300x119.png

num_team-300x119.png

5144 ms

App001-255x458.png

App001-255x458.png

18676 ms

app02-255x458.png

app02-255x458.png

11378 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

35 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

89 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

91 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

89 ms

App003-255x458.png

App003-255x458.png

13401 ms

App004-255x458.png

App004-255x458.png

10134 ms

glyphicons-regular.woff

glyphicons-regular.woff

20367 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

12169 ms

Panel.js

Panel.js

944 ms

localStorage.js

localStorage.js

984 ms

App005-255x458.png

App005-255x458.png

20155 ms

App006-255x458.png

App006-255x458.png

19998 ms

App007-255x458.png

App007-255x458.png

19770 ms

ajax_loader.gif

ajax_loader.gif

13050 ms

service03_bg-1920x556.png

service03_bg-1920x556.png

20449 ms

tour01_bg-1920x1080.jpg

tour01_bg-1920x1080.jpg

20433 ms

tour02_bg-1920x829.jpg

tour02_bg-1920x829.jpg

20362 ms

contains.js

contains.js

341 ms

ico_loading.gif

ico_loading.gif

20169 ms

num_bg-1920x446.png

num_bg-1920x446.png

20080 ms

qq_bg3.png

qq_bg3.png

20079 ms

r.cgi

r.cgi

1091 ms

ta.php

ta.php

605 ms

crmqq.php

crmqq.php

17000 ms

wpa_first_heart_beat.php

wpa_first_heart_beat.php

691 ms

hm.gif

hm.gif

437 ms

glyphicons-regular.ttf

glyphicons-regular.ttf

18510 ms

hb.crm2.qq.com

hb.crm2.qq.com

1149 ms

hb.crm2.qq.com

hb.crm2.qq.com

1633 ms

hb.crm2.qq.com

hb.crm2.qq.com

1155 ms

banner_old-1920x600.png

banner_old-1920x600.png

20266 ms

top.png

top.png

384 ms

flexslider-icon.woff

flexslider-icon.woff

712 ms

hm.gif

hm.gif

1749 ms

hb.crm2.qq.com

hb.crm2.qq.com

3594 ms

hb.crm2.qq.com

hb.crm2.qq.com

627 ms

hb.crm2.qq.com

hb.crm2.qq.com

1451 ms

hb.crm2.qq.com

hb.crm2.qq.com

1221 ms

SEO Factors

cutt.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cutt.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Cutt.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.

Social Sharing Optimization

cutt.com

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