Tools & Wizards About Us
flowersbyemily.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

flowersbyemily.com

  Flowers by Emily - Leawood, KS 66211

Page Load Speed

4.5 sec in total

First Response

1.3 sec

Resources Loaded

2.9 sec

Page Rendered

360 ms

flowersbyemily.com screenshot

About Website

Welcome to flowersbyemily.com homepage info - get ready to check Flowers By Emily best content right away, or after learning these important things about flowersbyemily.com

Leawood, KS florist for over 12 years. Everyday deliveries, succulent gardens, weddings and events are our specialties.

Visit flowersbyemily.com

Key Findings

We analyzed Flowersbyemily.com page load time and found that the first response time was 1.3 sec and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

flowersbyemily.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.082

94/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

flowersbyemily.com

1270 ms

styles-m.css

43 ms

styles-l.css

87 ms

require.min.js

122 ms

requirejs-min-resolver.min.js

119 ms

Our browser made a total of 175 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Flowersbyemily.com, 92% (161 requests) were made to Assets.floranext.com and 7% (13 requests) were made to Image.floranext.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Image.floranext.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 109.1 kB (17%)

Content Size

629.0 kB

After Optimization

519.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flowersbyemily.com main page is 629.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. 65% of websites need less resources to load. Javascripts take 315.2 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 95.6 kB

  • Original 106.2 kB
  • After minification 93.1 kB
  • After compression 10.6 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 13.1 kB, which is 12% 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 95.6 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 86.9 kB
  • After minification 86.9 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 By Emily images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 12.8 kB

  • Original 315.2 kB
  • After minification 314.7 kB
  • After compression 302.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 591 B

  • Original 120.7 kB
  • After minification 120.7 kB
  • After compression 120.1 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. Flowersbyemily.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 144 (87%)

Requests Now

166

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flowersbyemily.com

flowersbyemily.com

1270 ms

styles-m.css

styles-m.css

43 ms

styles-l.css

styles-l.css

87 ms

require.min.js

require.min.js

122 ms

requirejs-min-resolver.min.js

requirejs-min-resolver.min.js

119 ms

mixins.min.js

mixins.min.js

117 ms

requirejs-config.min.js

requirejs-config.min.js

116 ms

polyfill.min.js

polyfill.min.js

119 ms

x800_1686863116_0.42124700_1686863115_64940fefbdf0c.png.webp

x800_1686863116_0.42124700_1686863115_64940fefbdf0c.png.webp

422 ms

logo-basic-floranext-black.webp

logo-basic-floranext-black.webp

387 ms

banner_6496242bc9359.jpg.webp

banner_6496242bc9359.jpg.webp

723 ms

seasonal_mixed_arrangement_668ec06731965.jpg.webp

seasonal_mixed_arrangement_668ec06731965.jpg.webp

503 ms

seasonal_mixed_arrangement_668ec0a1bf350.jpg.webp

seasonal_mixed_arrangement_668ec0a1bf350.jpg.webp

397 ms

seasonal_mixed_arrangement_668ec0e1bbc81.jpg.webp

seasonal_mixed_arrangement_668ec0e1bbc81.jpg.webp

573 ms

seasonal_mixed_arrangement_668ec11438ec4.jpg.webp

seasonal_mixed_arrangement_668ec11438ec4.jpg.webp

375 ms

monthly_flowers_package_668ec44ab16ad.jpg.webp

monthly_flowers_package_668ec44ab16ad.jpg.webp

838 ms

img-6187_1.jpg.webp

img-6187_1.jpg.webp

859 ms

img_5576_66a3c90496c67.jpg.webp

img_5576_66a3c90496c67.jpg.webp

792 ms

img_6189_663bd92b99f25.jpg.webp

img_6189_663bd92b99f25.jpg.webp

805 ms

img_7647_1.jpg.webp

img_7647_1.jpg.webp

923 ms

img_7129_66c3b1abaef34.jpg.webp

img_7129_66c3b1abaef34.jpg.webp

1126 ms

img_9734.jpg

img_9734.jpg

1312 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

52 ms

common.min.js

common.min.js

26 ms

dataPost.min.js

dataPost.min.js

29 ms

bootstrap.min.js

bootstrap.min.js

30 ms

jquery.min.js

jquery.min.js

29 ms

translate-inline.min.js

translate-inline.min.js

49 ms

mage-translation-dictionary.min.js

mage-translation-dictionary.min.js

51 ms

responsive.min.js

responsive.min.js

50 ms

theme.min.js

theme.min.js

48 ms

opensans-400.woff

opensans-400.woff

165 ms

opensans-300.woff

opensans-300.woff

415 ms

opensans-600.woff

opensans-600.woff

165 ms

opensans-700.woff

opensans-700.woff

164 ms

Lato-Regular.woff

Lato-Regular.woff

167 ms

domReady.min.js

domReady.min.js

165 ms

template.min.js

template.min.js

144 ms

confirm.min.js

confirm.min.js

141 ms

widget.min.js

widget.min.js

144 ms

main.min.js

main.min.js

142 ms

bootstrap.min.js

bootstrap.min.js

143 ms

jquery-migrate.min.js

jquery-migrate.min.js

127 ms

jquery.min.js

jquery.min.js

120 ms

owl.carousel.min.js

owl.carousel.min.js

48 ms

flora-base-icons.woff

flora-base-icons.woff

48 ms

Blank-Theme-Icons.woff

Blank-Theme-Icons.woff

46 ms

translate.min.js

translate.min.js

80 ms

smart-keyboard-handler.min.js

smart-keyboard-handler.min.js

79 ms

mage.min.js

mage.min.js

77 ms

ie-class-fixer.min.js

ie-class-fixer.min.js

77 ms

text.min.js

text.min.js

78 ms

tabs.min.js

tabs.min.js

77 ms

underscore.min.js

underscore.min.js

75 ms

modal.min.js

modal.min.js

75 ms

knockout.min.js

knockout.min.js

76 ms

knockout-es5.min.js

knockout-es5.min.js

74 ms

dialog.min.js

dialog.min.js

60 ms

jquery-ui.min.js

jquery-ui.min.js

61 ms

matchMedia.min.js

matchMedia.min.js

81 ms

scripts.min.js

scripts.min.js

82 ms

engine.min.js

engine.min.js

81 ms

bootstrap.min.js

bootstrap.min.js

84 ms

bootstrap.min.js

bootstrap.min.js

82 ms

observable_array.min.js

observable_array.min.js

94 ms

bound-nodes.min.js

bound-nodes.min.js

92 ms

core.min.js

core.min.js

51 ms

collapsible.min.js

collapsible.min.js

34 ms

key-codes.min.js

key-codes.min.js

47 ms

button.min.js

button.min.js

44 ms

draggable.min.js

draggable.min.js

44 ms

position.min.js

position.min.js

50 ms

resizable.min.js

resizable.min.js

61 ms

autocomplete.min.js

autocomplete.min.js

71 ms

knockout-repeat.min.js

knockout-repeat.min.js

88 ms

knockout-fast-foreach.min.js

knockout-fast-foreach.min.js

112 ms

observable_source.min.js

observable_source.min.js

103 ms

renderer.min.js

renderer.min.js

122 ms

console-logger.min.js

console-logger.min.js

128 ms

resizable.min.js

resizable.min.js

152 ms

i18n.min.js

i18n.min.js

146 ms

scope.min.js

scope.min.js

170 ms

range.min.js

range.min.js

166 ms

mage-init.min.js

mage-init.min.js

189 ms

keyboard.min.js

keyboard.min.js

192 ms

optgroup.min.js

optgroup.min.js

209 ms

after-render.min.js

after-render.min.js

208 ms

autoselect.min.js

autoselect.min.js

229 ms

datepicker.min.js

datepicker.min.js

228 ms

outer_click.min.js

outer_click.min.js

247 ms

fadeVisible.min.js

fadeVisible.min.js

246 ms

collapsible.min.js

collapsible.min.js

267 ms

staticChecked.min.js

staticChecked.min.js

266 ms

simple-checked.min.js

simple-checked.min.js

287 ms

bind-html.min.js

bind-html.min.js

282 ms

wrapper.min.js

wrapper.min.js

307 ms

events.min.js

events.min.js

304 ms

es6-collections.min.js

es6-collections.min.js

308 ms

jquery.storageapi.extended.min.js

jquery.storageapi.extended.min.js

311 ms

tooltip.min.js

tooltip.min.js

297 ms

mouse.min.js

mouse.min.js

310 ms

class.min.js

class.min.js

224 ms

loader.min.js

loader.min.js

203 ms

local.min.js

local.min.js

201 ms

logger.min.js

logger.min.js

206 ms

entry-factory.min.js

entry-factory.min.js

219 ms

console-output-handler.min.js

console-output-handler.min.js

212 ms

formatter.min.js

formatter.min.js

215 ms

message-pool.min.js

message-pool.min.js

212 ms

levels-pool.min.js

levels-pool.min.js

208 ms

logger-utils.min.js

logger-utils.min.js

223 ms

async.min.js

async.min.js

223 ms

registry.min.js

registry.min.js

221 ms

slider.min.js

slider.min.js

203 ms

main.min.js

main.min.js

168 ms

calendar.min.js

calendar.min.js

133 ms

moment.min.js

moment.min.js

153 ms

modal-popup.html

modal-popup.html

120 ms

js-translation.json

js-translation.json

97 ms

modal-slide.html

modal-slide.html

109 ms

modal-custom.html

modal-custom.html

100 ms

jquery.cookie.min.js

jquery.cookie.min.js

86 ms

jquery.storageapi.min.js

jquery.storageapi.min.js

85 ms

template.min.js

template.min.js

57 ms

entry.min.js

entry.min.js

63 ms

datepicker.min.js

datepicker.min.js

64 ms

timepicker.min.js

timepicker.min.js

64 ms

dom-observer.min.js

dom-observer.min.js

59 ms

bindings.min.js

bindings.min.js

60 ms

arrays.min.js

arrays.min.js

55 ms

compare.min.js

compare.min.js

71 ms

misc.min.js

misc.min.js

56 ms

objects.min.js

objects.min.js

52 ms

strings.min.js

strings.min.js

57 ms

MutationObserver.min.js

MutationObserver.min.js

35 ms

FormData.min.js

FormData.min.js

19 ms

tooltip.html

tooltip.html

21 ms

print.css

print.css

23 ms

loader.min.js

loader.min.js

35 ms

page-cache.min.js

page-cache.min.js

18 ms

app.min.js

app.min.js

18 ms

form-mini.min.js

form-mini.min.js

34 ms

navigation-menu.min.js

navigation-menu.min.js

30 ms

validation.min.js

validation.min.js

43 ms

trim-input.min.js

trim-input.min.js

43 ms

cookies.min.js

cookies.min.js

43 ms

section-config.min.js

section-config.min.js

40 ms

invalidation-processor.min.js

invalidation-processor.min.js

40 ms

customer-data.min.js

customer-data.min.js

34 ms

customer-data-mixin.min.js

customer-data-mixin.min.js

44 ms

types.min.js

types.min.js

27 ms

layout.min.js

layout.min.js

27 ms

menu.min.js

menu.min.js

37 ms

validation.min.js

validation.min.js

24 ms

url.min.js

url.min.js

41 ms

storage.min.js

storage.min.js

19 ms

element.min.js

element.min.js

39 ms

minicart.min.js

minicart.min.js

29 ms

final-price.min.js

final-price.min.js

26 ms

messages.min.js

messages.min.js

33 ms

storage-manager.min.js

storage-manager.min.js

33 ms

jquery.validate.min.js

jquery.validate.min.js

35 ms

reCaptcha.min.js

reCaptcha.min.js

24 ms

reCaptcha-mixin.min.js

reCaptcha-mixin.min.js

27 ms

collection.min.js

collection.min.js

32 ms

links.min.js

links.min.js

19 ms

escaper.min.js

escaper.min.js

46 ms

storage-service.min.js

storage-service.min.js

23 ms

jquery.metadata.min.js

jquery.metadata.min.js

42 ms

registry.min.js

registry.min.js

41 ms

ids-storage.min.js

ids-storage.min.js

43 ms

data-storage.min.js

data-storage.min.js

42 ms

ids-storage-compare.min.js

ids-storage-compare.min.js

41 ms

website-rule.min.js

website-rule.min.js

42 ms

query-builder.min.js

query-builder.min.js

18 ms

Accessibility Review

flowersbyemily.com accessibility score

98

Accessibility Issues

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

flowersbyemily.com best practices score

75

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

flowersbyemily.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flowersbyemily.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 Flowersbyemily.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

flowersbyemily.com

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