Tools & Wizards About Us
richardsflorist.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

richardsflorist.com

  Richards Florist - Local Florist | Farmington, ME

Page Load Speed

3.7 sec in total

First Response

988 ms

Resources Loaded

2.3 sec

Page Rendered

465 ms

richardsflorist.com screenshot

About Website

Click here to check amazing Richards Florist content. Otherwise, check out these important facts you probably never knew about richardsflorist.com

Local florist in Farmington, ME - Same day flower delivery on top quality custom arrangements and much more in Farmington, ME. Call Today! 100% satisfaction guarantee.

Visit richardsflorist.com

Key Findings

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

Performance Metrics

richardsflorist.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value2,480 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.082

94/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

richardsflorist.com

988 ms

calendar.css

39 ms

styles-m.css

62 ms

styles-l.css

102 ms

require.min.js

120 ms

Our browser made a total of 158 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Richardsflorist.com, 85% (134 requests) were made to Assets.floranext.com and 12% (19 requests) were made to Image.floranext.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Image.floranext.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.1 kB (24%)

Content Size

544.2 kB

After Optimization

412.1 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Richardsflorist.com main page is 544.2 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 291.5 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 121.7 kB

  • Original 135.6 kB
  • After minification 116.3 kB
  • After compression 13.9 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 19.3 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 121.7 kB or 90% of the original size.

JavaScript Optimization

-3%

Potential reduce by 9.5 kB

  • Original 291.5 kB
  • After minification 291.1 kB
  • After compression 282.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 926 B

  • Original 117.1 kB
  • After minification 117.1 kB
  • After compression 116.2 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. Richardsflorist.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 121 (82%)

Requests Now

148

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Richards 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 119 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

richardsflorist.com

richardsflorist.com

988 ms

calendar.css

calendar.css

39 ms

styles-m.css

styles-m.css

62 ms

styles-l.css

styles-l.css

102 ms

require.min.js

require.min.js

120 ms

requirejs-min-resolver.min.js

requirejs-min-resolver.min.js

120 ms

mixins.min.js

mixins.min.js

98 ms

requirejs-config.min.js

requirejs-config.min.js

124 ms

polyfill.min.js

polyfill.min.js

129 ms

x800_1491353264_RF%20CC.jpg

x800_1491353264_RF%20CC.jpg

485 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

33 ms

common.min.js

common.min.js

32 ms

dataPost.min.js

dataPost.min.js

32 ms

bootstrap.min.js

bootstrap.min.js

30 ms

jquery.min.js

jquery.min.js

30 ms

translate-inline.min.js

translate-inline.min.js

27 ms

mage-translation-dictionary.min.js

mage-translation-dictionary.min.js

89 ms

responsive.min.js

responsive.min.js

110 ms

theme.min.js

theme.min.js

86 ms

opensans-400.woff

opensans-400.woff

86 ms

opensans-300.woff

opensans-300.woff

86 ms

opensans-600.woff

opensans-600.woff

85 ms

opensans-700.woff

opensans-700.woff

103 ms

js

js

173 ms

logo-basic-floranext-white.webp

logo-basic-floranext-white.webp

93 ms

6fd6c546-a4ca-4251-8a0f-451f1b4af233.jpg.webp

6fd6c546-a4ca-4251-8a0f-451f1b4af233.jpg.webp

384 ms

joyofrosesbouquet_1.jpeg.webp

joyofrosesbouquet_1.jpeg.webp

334 ms

bestillmyheart-dozenredroses_1.jpeg.webp

bestillmyheart-dozenredroses_1.jpeg.webp

328 ms

pink_dozen_1.jpg.webp

pink_dozen_1.jpg.webp

295 ms

yours_truley_bouquet_1.jpg.webp

yours_truley_bouquet_1.jpg.webp

548 ms

0.79628300_1554309895_1.jpeg.webp

0.79628300_1554309895_1.jpeg.webp

558 ms

3_dozen_1.jpg.webp

3_dozen_1.jpg.webp

530 ms

preciouspinktulips_1.png.webp

preciouspinktulips_1.png.webp

570 ms

HW0_372793.jpg.webp

HW0_372793.jpg.webp

384 ms

HW0_372792.jpg.webp

HW0_372792.jpg.webp

385 ms

download_1__1.jpg.webp

download_1__1.jpg.webp

569 ms

single_orchid_1.jpg.webp

single_orchid_1.jpg.webp

777 ms

t91-3a_1.jpg.webp

t91-3a_1.jpg.webp

728 ms

0.50780000_1549505121_1.jpeg.webp

0.50780000_1549505121_1.jpeg.webp

722 ms

deal_1_1.jpg.webp

deal_1_1.jpg.webp

954 ms

HW0_372649.jpg.webp

HW0_372649.jpg.webp

963 ms

basketdishgarden.jpg.webp

basketdishgarden.jpg.webp

817 ms

deal_1.jpg.webp

deal_1.jpg.webp

1013 ms

Lato-Regular.woff

Lato-Regular.woff

101 ms

domReady.min.js

domReady.min.js

90 ms

jquery.min.js

jquery.min.js

86 ms

template.min.js

template.min.js

108 ms

translate.min.js

translate.min.js

107 ms

jquery-migrate.min.js

jquery-migrate.min.js

93 ms

main.min.js

main.min.js

93 ms

bootstrap.min.js

bootstrap.min.js

92 ms

confirm.min.js

confirm.min.js

93 ms

widget.min.js

widget.min.js

107 ms

dialog.min.js

dialog.min.js

116 ms

jquery-ui.min.js

jquery-ui.min.js

103 ms

flora-base-icons.woff

flora-base-icons.woff

61 ms

Blank-Theme-Icons.woff

Blank-Theme-Icons.woff

62 ms

smart-keyboard-handler.min.js

smart-keyboard-handler.min.js

68 ms

mage.min.js

mage.min.js

69 ms

ie-class-fixer.min.js

ie-class-fixer.min.js

79 ms

text.min.js

text.min.js

70 ms

tabs.min.js

tabs.min.js

46 ms

matchMedia.min.js

matchMedia.min.js

33 ms

knockout.min.js

knockout.min.js

33 ms

knockout-es5.min.js

knockout-es5.min.js

41 ms

underscore.min.js

underscore.min.js

38 ms

engine.min.js

engine.min.js

26 ms

bootstrap.min.js

bootstrap.min.js

27 ms

bootstrap.min.js

bootstrap.min.js

64 ms

bootstrap.min.js

bootstrap.min.js

64 ms

observable_array.min.js

observable_array.min.js

66 ms

bound-nodes.min.js

bound-nodes.min.js

65 ms

scripts.min.js

scripts.min.js

59 ms

modal.min.js

modal.min.js

63 ms

modal-mixin.min.js

modal-mixin.min.js

61 ms

button.min.js

button.min.js

58 ms

draggable.min.js

draggable.min.js

62 ms

position.min.js

position.min.js

60 ms

resizable.min.js

resizable.min.js

59 ms

core.min.js

core.min.js

110 ms

collapsible.min.js

collapsible.min.js

109 ms

knockout-repeat.min.js

knockout-repeat.min.js

62 ms

knockout-fast-foreach.min.js

knockout-fast-foreach.min.js

63 ms

observable_source.min.js

observable_source.min.js

51 ms

renderer.min.js

renderer.min.js

50 ms

console-logger.min.js

console-logger.min.js

51 ms

js

js

115 ms

analytics.js

analytics.js

59 ms

resizable.min.js

resizable.min.js

31 ms

i18n.min.js

i18n.min.js

30 ms

scope.min.js

scope.min.js

30 ms

range.min.js

range.min.js

52 ms

mage-init.min.js

mage-init.min.js

52 ms

keyboard.min.js

keyboard.min.js

51 ms

optgroup.min.js

optgroup.min.js

52 ms

after-render.min.js

after-render.min.js

52 ms

autoselect.min.js

autoselect.min.js

83 ms

datepicker.min.js

datepicker.min.js

53 ms

outer_click.min.js

outer_click.min.js

53 ms

fadeVisible.min.js

fadeVisible.min.js

81 ms

collapsible.min.js

collapsible.min.js

78 ms

staticChecked.min.js

staticChecked.min.js

81 ms

simple-checked.min.js

simple-checked.min.js

82 ms

bind-html.min.js

bind-html.min.js

84 ms

tooltip.min.js

tooltip.min.js

82 ms

color-picker.min.js

color-picker.min.js

84 ms

autocomplete.min.js

autocomplete.min.js

83 ms

format.min.js

format.min.js

91 ms

jqueryTooltip.min.js

jqueryTooltip.min.js

89 ms

bootstrap-datepicker.min.js

bootstrap-datepicker.min.js

90 ms

wrapper.min.js

wrapper.min.js

92 ms

events.min.js

events.min.js

88 ms

es6-collections.min.js

es6-collections.min.js

88 ms

key-codes.min.js

key-codes.min.js

84 ms

mouse.min.js

mouse.min.js

81 ms

jquery.storageapi.extended.min.js

jquery.storageapi.extended.min.js

105 ms

class.min.js

class.min.js

98 ms

local.min.js

local.min.js

97 ms

async.min.js

async.min.js

101 ms

registry.min.js

registry.min.js

104 ms

loader.min.js

loader.min.js

117 ms

logger.min.js

logger.min.js

135 ms

entry-factory.min.js

entry-factory.min.js

153 ms

console-output-handler.min.js

console-output-handler.min.js

172 ms

formatter.min.js

formatter.min.js

189 ms

message-pool.min.js

message-pool.min.js

190 ms

levels-pool.min.js

levels-pool.min.js

208 ms

logger-utils.min.js

logger-utils.min.js

204 ms

slider.min.js

slider.min.js

220 ms

collect

collect

27 ms

calendar.min.js

calendar.min.js

206 ms

moment.min.js

moment.min.js

214 ms

main.min.js

main.min.js

222 ms

misc-mixin.min.js

misc-mixin.min.js

222 ms

spectrum.min.js

spectrum.min.js

238 ms

tinycolor.min.js

tinycolor.min.js

238 ms

datepicker.min.js

datepicker.min.js

252 ms

jquery.cookie.min.js

jquery.cookie.min.js

230 ms

jquery.storageapi.min.js

jquery.storageapi.min.js

226 ms

dom-observer.min.js

dom-observer.min.js

239 ms

bindings.min.js

bindings.min.js

233 ms

entry.min.js

entry.min.js

173 ms

js-translation.json

js-translation.json

180 ms

template.min.js

template.min.js

157 ms

arrays.min.js

arrays.min.js

80 ms

compare.min.js

compare.min.js

76 ms

misc.min.js

misc.min.js

101 ms

objects.min.js

objects.min.js

89 ms

strings.min.js

strings.min.js

97 ms

modal-popup.html

modal-popup.html

86 ms

bootstrap-datepicker.min.js

bootstrap-datepicker.min.js

75 ms

modal-popup.html

modal-popup.html

72 ms

modal-slide.html

modal-slide.html

64 ms

MutationObserver.min.js

MutationObserver.min.js

52 ms

modal-custom.html

modal-custom.html

27 ms

FormData.min.js

FormData.min.js

29 ms

tooltip.html

tooltip.html

19 ms

print.css

print.css

16 ms

Accessibility Review

richardsflorist.com accessibility score

96

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.

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

richardsflorist.com best practices score

58

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

richardsflorist.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 Richardsflorist.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 Richardsflorist.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

richardsflorist.com

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