1.6 sec in total
69 ms
1.3 sec
219 ms
Welcome to florist.com homepage info - get ready to check Florist best content for United States right away, or after learning these important things about florist.com
Order fresh flowers online with same day delivery or visit local FTD florists. Shop for flowers, sweets, gifts and gift baskets by occasion & season.
Visit florist.comWe analyzed Florist.com page load time and found that the first response time was 69 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
florist.com performance score
69 ms
151 ms
434 ms
87 ms
124 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 11% of them (9 requests) were addressed to the original Florist.com, 73% (58 requests) were made to Ftdimg.com and 6% (5 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (434 ms) belongs to the original domain Florist.com.
Page size can be reduced by 934.9 kB (47%)
2.0 MB
1.1 MB
In fact, the total size of Florist.com main page is 2.0 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. 50% of websites need less resources to load. Javascripts take 978.5 kB which makes up the majority of the site volume.
Potential reduce by 74.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. This page needs HTML code to be minified as it can gain 15.1 kB, which is 17% 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 74.0 kB or 82% of the original size.
Potential reduce by 44.2 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. Florist images are well optimized though.
Potential reduce by 706.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 706.0 kB or 72% of the original size.
Potential reduce by 110.8 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. Florist.com needs all CSS files to be minified and compressed as it can save up to 110.8 kB or 83% of the original size.
Number of requests can be reduced by 26 (34%)
77
51
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Florist. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
florist.com
69 ms
www.florist.com
151 ms
434 ms
satelliteLib-58f76622904defe25922d2a5765723d2334530cd.js
87 ms
compressed20160314.js
124 ms
migrate.js
111 ms
compressed-jcarousel20160314.js
113 ms
compressed-calendar20160314.js
116 ms
design2007.css
210 ms
ftd.css
102 ms
tabs.css
96 ms
jquery.cycle.all.min.js
205 ms
effects.js
203 ms
carousel.js
207 ms
homepage.js
240 ms
omniture.js
194 ms
satellite-5303d835b2356adc7c0001f3.js
13 ms
satellite-531789260a2c24b6c30001f5.js
23 ms
airlock.min.js
22 ms
analytics.js
155 ms
floristComLogo_92x410.jpg
70 ms
button_sign_in.gif
46 ms
button_close_small_x.jpg
40 ms
homepage_florist_images.png
110 ms
nhp-btnArrow-smGr.png
109 ms
spacer.gif
40 ms
tabDropIcon-green.png
40 ms
tabIcon-arrow.png
40 ms
florist_slide_flowers.jpg
40 ms
florist_slide_birthday_alt.jpg
42 ms
florist_slide_getwell.jpg
42 ms
florist_slide_anniversary.jpg
42 ms
florist_slide_sympathy.jpg
43 ms
go-btn-green.png
43 ms
ftd_sameday_finder_close.gif
43 ms
FC1307527_filmstrip2_102213.jpg
43 ms
cleardot.gif
44 ms
FC1307527_filmstrip1_102213.jpg
47 ms
vp_ms_trustmark.png
44 ms
outdatedbrow_close.png
44 ms
internetexplorer.png
44 ms
chrome.png
44 ms
safari.png
45 ms
firefox.png
44 ms
counter.gif
100 ms
zfModalHeadLogo-sm.jpg
35 ms
ajax-loader.gif
35 ms
florist_slide_1_031714_nav.png
65 ms
florist_slide_2_031714_nav.png
65 ms
florist_slide_getwell_nav.png
60 ms
florist_slide_4_031714_nav.png
98 ms
florist_slide_5_031714_nav.png
113 ms
zip-finder-bg.png
95 ms
collect
14 ms
film_prev_4across_1.gif
88 ms
film_next_4across_1.gif
87 ms
FMTP_176x220.jpg
114 ms
C6-4863_176x220.jpg
253 ms
FLFM_176x220.jpg
113 ms
C3-4793_176x220.jpg
83 ms
FKRP_176x220.jpg
106 ms
FFDL_176x220.jpg
213 ms
FPPA_176x220.jpg
255 ms
C12-3434_176x220.jpg
212 ms
SMRB_176x220.jpg
212 ms
FFGD_176x220.jpg
127 ms
FFGR_176x220.jpg
215 ms
C12-4792_176x220.jpg
213 ms
FRR4_176x220.jpg
212 ms
C12-4400_176x220.jpg
213 ms
C16-4839_176x220.jpg
250 ms
sli-rac.0.4.css
79 ms
sli-rac.css
95 ms
sli-rac.config.js
10 ms
satellite-53babe747d4631fca30002af.html
61 ms
sli-rac.stub.0.4.js
10 ms
film_prev_4across_2.gif
55 ms
film_next_4across_2.gif
56 ms
activityi;src=1667271;type=globa166;cat=unive623;ord=4141156016848.9814
35 ms
s88366554635576
38 ms
florist.com SEO score
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Florist.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 Florist.com main page’s claimed encoding is iso-8859-1. 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.
florist.com
Open Graph description is not detected on the main page of Florist. 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: