9.8 sec in total
144 ms
9.4 sec
225 ms
Visit flowers.ms now to see the best up-to-date Flowers content for United States and also check out these interesting facts you probably never knew about flowers.ms
FTD florist online delivery flowers. Same day delivery by FTD florists. We can assure you the highest quality and service. Flowers delivery is what we do best. We make it easy to orde flowers for all ...
Visit flowers.msWe analyzed Flowers.ms page load time and found that the first response time was 144 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
flowers.ms performance score
name
value
score
weighting
Value1.7 s
91/100
10%
Value5.0 s
27/100
25%
Value2.6 s
97/100
10%
Value1,860 ms
9/100
30%
Value0.019
100/100
15%
Value5.1 s
75/100
10%
144 ms
841 ms
87 ms
66 ms
64 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 15% of them (10 requests) were addressed to the original Flowers.ms, 62% (41 requests) were made to Folimg.com and 8% (5 requests) were made to Shopperapproved.com. The less responsive or slowest element that took the longest time to load (7.2 sec) belongs to the original domain Flowers.ms.
Page size can be reduced by 532.9 kB (38%)
1.4 MB
866.1 kB
In fact, the total size of Flowers.ms main page is 1.4 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. 60% of websites need less resources to load. Images take 732.1 kB which makes up the majority of the site volume.
Potential reduce by 61.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 18.4 kB, which is 25% 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 61.0 kB or 84% of the original size.
Potential reduce by 60.6 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. Flowers images are well optimized though.
Potential reduce by 364.6 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 364.6 kB or 68% of the original size.
Potential reduce by 46.7 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. Flowers.ms needs all CSS files to be minified and compressed as it can save up to 46.7 kB or 85% of the original size.
Number of requests can be reduced by 30 (50%)
60
30
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flowers. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
flowers.ms
144 ms
www.flowers.ms
841 ms
javascript.jscript
87 ms
prototype.js
66 ms
effects.js
64 ms
lib.js
66 ms
opt_in.js
63 ms
custom.css
7167 ms
satelliteLib-0acc6bba87ae1dc9bdcc742d5cc46ad0c1bd1152.js
9 ms
tracking_system.jscript
97 ms
satellite-52fbad1899943605b60000f6.js
4 ms
bg_body.gif
206 ms
504945484848526565.gif
115 ms
track_website.cgi
151 ms
63.gif
109 ms
imageload
110 ms
bg_header.gif
14 ms
bg_search.gif
15 ms
nav_banner_2_504945484848526565.gif
14 ms
nav_banner_4_504945484848526565.gif
15 ms
nav_banner_5_504945484848526565.gif
15 ms
button_close.gif
15 ms
16 ms
18 ms
16 ms
18 ms
16 ms
27 ms
43 ms
29 ms
26 ms
27 ms
30 ms
30 ms
button_submit.gif
28 ms
button_bestsellers.gif
22 ms
button_holidays.gif
24 ms
button_occasions.gif
23 ms
button_products.gif
24 ms
topnav_submenu_dot.gif
214 ms
button_aboutus.gif
25 ms
button_siteserv.gif
24 ms
bg_main.jpg
234 ms
button_holidays_side.gif
25 ms
button_occasions_side.gif
25 ms
button_products_side.gif
26 ms
button_best_side.gif
25 ms
button_siteserv_side.gif
26 ms
popup_bg_gold.gif
26 ms
imageload
365 ms
button_order_now.gif
16 ms
lower_nav_divider.gif
9 ms
ga.js
10 ms
conversion.js
19 ms
__utm.gif
22 ms
_FTD21-0004AA.js
406 ms
_FTD21-0004AA.js
15 ms
float.js
16 ms
s-code-contents-bf919ebc8bd5fd7b810d08b6196a19e9c94bee07.js
17 ms
white-mini-icon-br.gif
11 ms
back-mini-icon-br.png
145 ms
jquery.noconflict.js
20 ms
s62313949004746
42 ms
index.html
241 ms
index.html
807 ms
track_website.cgi
106 ms
flowers.ms accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
flowers.ms best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
flowers.ms SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flowers.ms 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), while the claimed language is English. Our system also found out that Flowers.ms 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.
flowers.ms
Open Graph description is not detected on the main page of Flowers. 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: