Tools & Wizards About Us
flower.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

flower.com

Flower.com

Page Load Speed

1.2 sec in total

First Response

88 ms

Resources Loaded

698 ms

Page Rendered

443 ms

flower.com screenshot

About Website

Welcome to flower.com homepage info - get ready to check Flower best content for United States right away, or after learning these important things about flower.com

Flower Delivery at Flower.com. Send flowers and gifts online for same day flower delivery nationwide. Flower.com is the home of the perfect flower delivery so send flowers today. Fresh Flowers

Visit flower.com

Key Findings

We analyzed Flower.com page load time and found that the first response time was 88 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

flower.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value3.7 s

86/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

flower.com

88 ms

home.asp

253 ms

bootstrap.min.css

12 ms

styles.css

22 ms

styles1.css

7 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 47% of them (27 requests) were addressed to the original Flower.com, 21% (12 requests) were made to El-p.src-akamai.net and 16% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (253 ms) belongs to the original domain Flower.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 297.7 kB (12%)

Content Size

2.4 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flower.com main page is 2.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. 75% 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 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 28.0 kB

  • Original 35.3 kB
  • After minification 30.5 kB
  • After compression 7.4 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 4.8 kB, which is 14% 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 28.0 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 10.8 kB

  • Original 2.0 MB
  • After minification 2.0 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. Flower images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 69.6 kB

  • Original 121.4 kB
  • After minification 120.7 kB
  • After compression 51.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 69.6 kB or 57% of the original size.

CSS Optimization

-83%

Potential reduce by 189.3 kB

  • Original 227.1 kB
  • After minification 206.4 kB
  • After compression 37.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. Flower.com needs all CSS files to be minified and compressed as it can save up to 189.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (30%)

Requests Now

47

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flower.com

flower.com

88 ms

home.asp

home.asp

253 ms

bootstrap.min.css

bootstrap.min.css

12 ms

styles.css

styles.css

22 ms

styles1.css

styles1.css

7 ms

skin.css

skin.css

23 ms

font-awesome.min.css

font-awesome.min.css

19 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

17 ms

css

css

25 ms

css

css

40 ms

2559.jpg

2559.jpg

165 ms

2270.jpg

2270.jpg

154 ms

8013.jpg

8013.jpg

174 ms

4896.jpg

4896.jpg

148 ms

8071.jpg

8071.jpg

155 ms

4784.jpg

4784.jpg

148 ms

1850.jpg

1850.jpg

155 ms

4796.jpg

4796.jpg

152 ms

6528.jpg

6528.jpg

151 ms

9303.jpg

9303.jpg

224 ms

7966.jpg

7966.jpg

224 ms

3590.jpg

3590.jpg

221 ms

fl_logo-ani.gif

fl_logo-ani.gif

19 ms

flowers-large.jpg

flowers-large.jpg

24 ms

sympathy-flowers-large.jpg

sympathy-flowers-large.jpg

19 ms

flower-baskets-large.jpg

flower-baskets-large.jpg

22 ms

birthday_480x360.jpg

birthday_480x360.jpg

22 ms

funeral_480x360.jpg

funeral_480x360.jpg

23 ms

get_well_480x360.jpg

get_well_480x360.jpg

24 ms

love_480x360.jpg

love_480x360.jpg

25 ms

storefront.jpg

storefront.jpg

56 ms

2015_winter-sale1.jpg

2015_winter-sale1.jpg

56 ms

jquery.js

jquery.js

18 ms

bootstrap.min.js

bootstrap.min.js

17 ms

fd_script.js

fd_script.js

16 ms

gjs.aspx

gjs.aspx

50 ms

master_card.png

master_card.png

48 ms

visa_card.png

visa_card.png

43 ms

paypal.png

paypal.png

46 ms

american_express_card.png

american_express_card.png

43 ms

discover_network_card.png

discover_network_card.png

43 ms

ga.js

ga.js

96 ms

ODelI1aHBYDBqgeIAH2zlEY6Fu39Tt9XkmtSosaMoEA.ttf

ODelI1aHBYDBqgeIAH2zlEY6Fu39Tt9XkmtSosaMoEA.ttf

29 ms

toadOcfmlt9b38dHJxOBGPS42wKzre0cxmO5m5GyTsY.ttf

toadOcfmlt9b38dHJxOBGPS42wKzre0cxmO5m5GyTsY.ttf

38 ms

toadOcfmlt9b38dHJxOBGNF-01od694vbXd2r4ICkqU.ttf

toadOcfmlt9b38dHJxOBGNF-01od694vbXd2r4ICkqU.ttf

74 ms

toadOcfmlt9b38dHJxOBGBRq_IsDXucKYMk4-diqPEc.ttf

toadOcfmlt9b38dHJxOBGBRq_IsDXucKYMk4-diqPEc.ttf

76 ms

toadOcfmlt9b38dHJxOBGLlcMrNrsnL9dgADnXgYJjs.ttf

toadOcfmlt9b38dHJxOBGLlcMrNrsnL9dgADnXgYJjs.ttf

74 ms

toadOcfmlt9b38dHJxOBGAB1T86lWSAA4YH0UgcWDqc.ttf

toadOcfmlt9b38dHJxOBGAB1T86lWSAA4YH0UgcWDqc.ttf

74 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

181 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

160 ms

bH7276GfdCjMjApa_dkG6SZ2oysoEQEeKwjgmXLRnTc.ttf

bH7276GfdCjMjApa_dkG6SZ2oysoEQEeKwjgmXLRnTc.ttf

74 ms

lXoKq2PC8Z_S1wl-BwvrB-vvDin1pK8aKteLpeZ5c0A.ttf

lXoKq2PC8Z_S1wl-BwvrB-vvDin1pK8aKteLpeZ5c0A.ttf

73 ms

HqHm7BVC_nzzTui2lzQTDSZ2oysoEQEeKwjgmXLRnTc.ttf

HqHm7BVC_nzzTui2lzQTDSZ2oysoEQEeKwjgmXLRnTc.ttf

74 ms

__utm.gif

__utm.gif

15 ms

rollover.core.js

rollover.core.js

10 ms

AltSealInfo.aspx

AltSealInfo.aspx

14 ms

MP952415869a_Seal_BLX.png

MP952415869a_Seal_BLX.png

5 ms

Static.aspx

Static.aspx

57 ms

Accessibility Review

flower.com accessibility score

82

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.

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

Image elements do not have [alt] attributes

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

flower.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

flower.com SEO score

89

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flower.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Flower.com main page’s claimed encoding is . 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.

Social Sharing Optimization

flower.com

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