Tools & Wizards About Us
richardsflorist.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

richardsflorist.com

  Richards Florist - Local Florist | Farmington, ME

Page Load Speed

8.9 sec in total

First Response

3.2 sec

Resources Loaded

5 sec

Page Rendered

596 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 3.2 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

richardsflorist.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value1,200 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.195

63/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

richardsflorist.com

3227 ms

styles-m.css

68 ms

styles-l.css

91 ms

require.min.js

110 ms

requirejs-min-resolver.min.js

110 ms

Our browser made a total of 157 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Richardsflorist.com, 76% (119 requests) were made to Assets.floranext.com and 24% (37 requests) were made to Image.floranext.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Richardsflorist.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 183.5 kB (36%)

Content Size

513.8 kB

After Optimization

330.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-92%

Potential reduce by 172.4 kB

  • Original 187.2 kB
  • After minification 153.0 kB
  • After compression 14.8 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 34.1 kB, which is 18% 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 172.4 kB or 92% of the original size.

Image Optimization

-0%

Potential reduce by 12 B

  • Original 10.7 kB
  • After minification 10.7 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. Richards Florist images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 11.1 kB

  • Original 196.7 kB
  • After minification 195.9 kB
  • After compression 185.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 12 B

  • Original 119.3 kB
  • After minification 119.3 kB
  • After compression 119.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 102 (69%)

Requests Now

148

After Optimization

46

  • 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 103 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

richardsflorist.com

richardsflorist.com

3227 ms

styles-m.css

styles-m.css

68 ms

styles-l.css

styles-l.css

91 ms

require.min.js

require.min.js

110 ms

requirejs-min-resolver.min.js

requirejs-min-resolver.min.js

110 ms

mixins.min.js

mixins.min.js

112 ms

requirejs-config.min.js

requirejs-config.min.js

108 ms

x800_1491353264_RF%20CC.jpg.webp

x800_1491353264_RF%20CC.jpg.webp

428 ms

jquery.min.js

jquery.min.js

21 ms

common.min.js

common.min.js

19 ms

dataPost.min.js

dataPost.min.js

19 ms

bootstrap.min.js

bootstrap.min.js

20 ms

app.min.js

app.min.js

34 ms

form-key-provider.min.js

form-key-provider.min.js

41 ms

mage-translation-dictionary.min.js

mage-translation-dictionary.min.js

39 ms

theme.min.js

theme.min.js

38 ms

opensans-400.woff

opensans-400.woff

56 ms

opensans-300.woff

opensans-300.woff

38 ms

opensans-600.woff

opensans-600.woff

32 ms

opensans-700.woff

opensans-700.woff

58 ms

template.min.js

template.min.js

45 ms

confirm.min.js

confirm.min.js

33 ms

widget.min.js

widget.min.js

30 ms

jquery-migrate.min.js

jquery-migrate.min.js

29 ms

domReady.min.js

domReady.min.js

45 ms

main.min.js

main.min.js

44 ms

bootstrap.min.js

bootstrap.min.js

41 ms

jquery-mixin.min.js

jquery-mixin.min.js

44 ms

text.min.js

text.min.js

36 ms

smart-keyboard-handler.min.js

smart-keyboard-handler.min.js

37 ms

mage.min.js

mage.min.js

57 ms

ie-class-fixer.min.js

ie-class-fixer.min.js

63 ms

types.min.js

types.min.js

50 ms

layout.min.js

layout.min.js

57 ms

underscore.min.js

underscore.min.js

44 ms

translate.min.js

translate.min.js

42 ms

modal.min.js

modal.min.js

71 ms

version.min.js

version.min.js

68 ms

knockout.min.js

knockout.min.js

49 ms

knockout-es5.min.js

knockout-es5.min.js

49 ms

engine.min.js

engine.min.js

59 ms

bootstrap.min.js

bootstrap.min.js

57 ms

bootstrap.min.js

bootstrap.min.js

94 ms

wrapper.min.js

wrapper.min.js

67 ms

observable_array.min.js

observable_array.min.js

63 ms

bound-nodes.min.js

bound-nodes.min.js

66 ms

scripts.min.js

scripts.min.js

85 ms

main.min.js

main.min.js

87 ms

registry.min.js

registry.min.js

72 ms

console-logger.min.js

console-logger.min.js

69 ms

Lato-Regular.woff

Lato-Regular.woff

80 ms

flora-base-icons.woff

flora-base-icons.woff

71 ms

Blank-Theme-Icons.woff

Blank-Theme-Icons.woff

71 ms

key-codes.min.js

key-codes.min.js

48 ms

core.min.js

core.min.js

68 ms

z-index.min.js

z-index.min.js

67 ms

knockout-repeat.min.js

knockout-repeat.min.js

86 ms

knockout-fast-foreach.min.js

knockout-fast-foreach.min.js

78 ms

renderer.min.js

renderer.min.js

106 ms

resizable.min.js

resizable.min.js

95 ms

i18n.min.js

i18n.min.js

114 ms

scope.min.js

scope.min.js

124 ms

range.min.js

range.min.js

127 ms

mage-init.min.js

mage-init.min.js

141 ms

keyboard.min.js

keyboard.min.js

143 ms

optgroup.min.js

optgroup.min.js

157 ms

after-render.min.js

after-render.min.js

163 ms

autoselect.min.js

autoselect.min.js

173 ms

datepicker.min.js

datepicker.min.js

187 ms

outer_click.min.js

outer_click.min.js

191 ms

fadeVisible.min.js

fadeVisible.min.js

211 ms

collapsible.min.js

collapsible.min.js

217 ms

staticChecked.min.js

staticChecked.min.js

227 ms

simple-checked.min.js

simple-checked.min.js

235 ms

bind-html.min.js

bind-html.min.js

253 ms

tooltip.min.js

tooltip.min.js

241 ms

observable_source.min.js

observable_source.min.js

252 ms

0e099aef-ba2b-48a2-b5f7-4ce0afbb3d29.jpg.webp

0e099aef-ba2b-48a2-b5f7-4ce0afbb3d29.jpg.webp

31 ms

unnamed_670ea0df9d1b3.jpg.webp

unnamed_670ea0df9d1b3.jpg.webp

398 ms

joyofrosesbouquet_1.jpeg.webp

joyofrosesbouquet_1.jpeg.webp

374 ms

bestillmyheart-dozenredroses_1.jpeg.webp

bestillmyheart-dozenredroses_1.jpeg.webp

264 ms

teleflora_sfestivepinesbouquet_1.jpeg.webp

teleflora_sfestivepinesbouquet_1.jpeg.webp

393 ms

0.32202600_1553707761_1.jpeg.webp

0.32202600_1553707761_1.jpeg.webp

212 ms

blue_1.jpg.webp

blue_1.jpg.webp

421 ms

pumpkin2_1.jpg.webp

pumpkin2_1.jpg.webp

424 ms

pumpkin_1.jpg.webp

pumpkin_1.jpg.webp

639 ms

burst_1.jpg.webp

burst_1.jpg.webp

557 ms

sugar_maples_1.jpg.webp

sugar_maples_1.jpg.webp

743 ms

havens_3_1.jpg.webp

havens_3_1.jpg.webp

783 ms

havens_1.jpg.webp

havens_1.jpg.webp

667 ms

deal_1_1.jpg.webp

deal_1_1.jpg.webp

787 ms

13181b_beautiful-in-blue-bouquet_1.jpg.webp

13181b_beautiful-in-blue-bouquet_1.jpg.webp

947 ms

awesomealstromeria.jpg.webp

awesomealstromeria.jpg.webp

642 ms

bowlofbeauty.jpg.webp

bowlofbeauty.jpg.webp

646 ms

HW0_372793.jpg.webp

HW0_372793.jpg.webp

651 ms

HW0_372734.jpg.webp

HW0_372734.jpg.webp

845 ms

HW0_372923.jpg.webp

HW0_372923.jpg.webp

1042 ms

HW0_372650.jpg.webp

HW0_372650.jpg.webp

919 ms

HW0_372706.jpg.webp

HW0_372706.jpg.webp

1139 ms

HW0_372727.jpg.webp

HW0_372727.jpg.webp

1014 ms

HW0_372710.jpg.webp

HW0_372710.jpg.webp

1044 ms

HW0_372731.jpg.webp

HW0_372731.jpg.webp

922 ms

HW0_372714.jpg.webp

HW0_372714.jpg.webp

924 ms

HW0_372702.jpg.webp

HW0_372702.jpg.webp

1237 ms

HW0_372719.jpg.webp

HW0_372719.jpg.webp

1321 ms

HW0_372671.jpg.webp

HW0_372671.jpg.webp

1017 ms

wrap_1_1.jpg.webp

wrap_1_1.jpg.webp

1244 ms

coastal_1.jpg.webp

coastal_1.jpg.webp

1202 ms

wishes_1.jpg.webp

wishes_1.jpg.webp

1421 ms

HW0_372649.jpg.webp

HW0_372649.jpg.webp

1485 ms

junk_1.jpg.webp

junk_1.jpg.webp

1575 ms

deal_1.jpg.webp

deal_1.jpg.webp

1402 ms

events.min.js

events.min.js

249 ms

logo-basic-floranext-white.webp

logo-basic-floranext-white.webp

253 ms

autocomplete.min.js

autocomplete.min.js

251 ms

local.min.js

local.min.js

271 ms

logger.min.js

logger.min.js

255 ms

entry-factory.min.js

entry-factory.min.js

275 ms

CC-companies_64bef2f6c4f94_66c8b76bdb333.png

CC-companies_64bef2f6c4f94_66c8b76bdb333.png

1505 ms

console-output-handler.min.js

console-output-handler.min.js

262 ms

formatter.min.js

formatter.min.js

268 ms

message-pool.min.js

message-pool.min.js

270 ms

levels-pool.min.js

levels-pool.min.js

271 ms

logger-utils.min.js

logger-utils.min.js

268 ms

arrays.min.js

arrays.min.js

271 ms

compare.min.js

compare.min.js

264 ms

misc.min.js

misc.min.js

250 ms

objects.min.js

objects.min.js

254 ms

strings.min.js

strings.min.js

242 ms

template.min.js

template.min.js

242 ms

data.min.js

data.min.js

237 ms

disable-selection.min.js

disable-selection.min.js

219 ms

focusable.min.js

focusable.min.js

220 ms

form.min.js

form.min.js

227 ms

ie.min.js

ie.min.js

224 ms

keycode.min.js

keycode.min.js

204 ms

labels.min.js

labels.min.js

190 ms

jquery-patch.min.js

jquery-patch.min.js

193 ms

plugin.min.js

plugin.min.js

168 ms

safe-active-element.min.js

safe-active-element.min.js

186 ms

safe-blur.min.js

safe-blur.min.js

169 ms

scroll-parent.min.js

scroll-parent.min.js

169 ms

tabbable.min.js

tabbable.min.js

160 ms

unique-id.min.js

unique-id.min.js

159 ms

async.min.js

async.min.js

147 ms

loader.min.js

loader.min.js

166 ms

js-translation.json

js-translation.json

148 ms

class.min.js

class.min.js

143 ms

entry.min.js

entry.min.js

105 ms

modal-popup.html

modal-popup.html

104 ms

moment.min.js

moment.min.js

117 ms

modal-custom.html

modal-custom.html

99 ms

modal-slide.html

modal-slide.html

100 ms

dom-observer.min.js

dom-observer.min.js

37 ms

bindings.min.js

bindings.min.js

40 ms

tooltip.html

tooltip.html

25 ms

print.css

print.css

16 ms

Accessibility Review

richardsflorist.com accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

richardsflorist.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

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: