6.5 sec in total
1.1 sec
5.3 sec
122 ms
Click here to check amazing Cutflower content for United States. Otherwise, check out these important facts you probably never knew about cutflower.com
flowers, roses, wholesale, direct, import, wedding
Visit cutflower.comWe analyzed Cutflower.com page load time and found that the first response time was 1.1 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
cutflower.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value9.5 s
0/100
25%
Value14.8 s
1/100
10%
Value3,680 ms
1/100
30%
Value0.173
69/100
15%
Value22.6 s
1/100
10%
1096 ms
2450 ms
397 ms
397 ms
351 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 46% of them (25 requests) were addressed to the original Cutflower.com, 19% (10 requests) were made to Static.xx.fbcdn.net and 7% (4 requests) were made to Cdn.livechatinc.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Cutflower.com.
Page size can be reduced by 493.1 kB (32%)
1.6 MB
1.1 MB
In fact, the total size of Cutflower.com main page is 1.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. 40% of websites need less resources to load. Images take 887.9 kB which makes up the majority of the site volume.
Potential reduce by 23.0 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 23.0 kB or 73% of the original size.
Potential reduce by 8.8 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. Cutflower images are well optimized though.
Potential reduce by 447.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 447.8 kB or 72% of the original size.
Potential reduce by 13.5 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. Cutflower.com needs all CSS files to be minified and compressed as it can save up to 13.5 kB or 85% of the original size.
Number of requests can be reduced by 21 (44%)
48
27
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cutflower. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
cutflower.com
1096 ms
www.cutflower.com
2450 ms
style.css
397 ms
gen_validatorv2.js
397 ms
xlaabsolutenm.asp
351 ms
urchin.js
21 ms
cutflower_header960.jpg
199 ms
blank.gif
99 ms
title_joinMailing.gif
153 ms
constantcontactprivacy2.gif
149 ms
hometitle_flowergallery.gif
198 ms
black_arrow_trans.gif
197 ms
black_arrow.gif
199 ms
hometitle_resources.gif
201 ms
Facebook.png
205 ms
Instagram.png
296 ms
Twitter.png
250 ms
Youtube.png
252 ms
cutflower_footer960.png
250 ms
all.js
70 ms
cutflower_background960.gif
244 ms
117 ms
xd_arbiter.php
72 ms
xd_arbiter.php
127 ms
home-collage4.jpg
309 ms
__utm.gif
13 ms
tracking.js
86 ms
like_box.php
96 ms
script_data.js
97 ms
hDvwL1_H7g-.css
78 ms
udqjbTyb5Ue.css
98 ms
FAHeNGXgPup.js
134 ms
FJmpeSpHpjS.js
163 ms
0wM5s1Khldu.js
131 ms
1bNoFZUdlYZ.js
130 ms
localization.en.0.3632191afe35222a6b78c04d457adc0d_5f7c1632cb6349fedc5161adbd6fbcc8.js
47 ms
ping
77 ms
006.png
29 ms
open_chat.cgi
63 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
66 ms
livechat-modern_7cf45543dc.ttf
48 ms
embedded.20160310142511.js
189 ms
1896915_745023478861263_1356180438_n.jpg
77 ms
wL6VQj7Ab77.png
18 ms
s7jcwEQH7Sx.png
20 ms
I6-MnjEovm5.js
20 ms
pQrUxxo5oQp.js
36 ms
home-collage1.jpg
794 ms
home-collage2.jpg
694 ms
home-collage3.jpg
793 ms
home-collage5.jpg
393 ms
home-collage6.jpg
899 ms
wkfQbvfT_02e2IWO3yYueQ.woff
23 ms
KT3KS9Aol4WfR6Vas8kNcg.woff
27 ms
cutflower.com 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
button, link, and menuitem elements do not have accessible names.
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
cutflower.com 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
cutflower.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cutflower.com 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 Cutflower.com main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
cutflower.com
Open Graph description is not detected on the main page of Cutflower. 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: