Tools & Wizards About Us
barrieflowers.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

barrieflowers.net

Flower Delivery Barrie, ON | Flower Shop Barrie - Florist Barrie

Page Load Speed

2.9 sec in total

First Response

533 ms

Resources Loaded

1.9 sec

Page Rendered

412 ms

barrieflowers.net screenshot

About Website

Welcome to barrieflowers.net homepage info - get ready to check Barrie Flower S best content right away, or after learning these important things about barrieflowers.net

Order Barrie flower delivery from www.barrieflowers.net - Best Online Florist Barrie. We have the largets rage of flowers Barrie for all occasions.

Visit barrieflowers.net

Key Findings

We analyzed Barrieflowers.net page load time and found that the first response time was 533 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

barrieflowers.net performance score

0

Network Requests Diagram

www.barrieflowers.net

533 ms

webfont.js

13 ms

styles.css

176 ms

widgets.css

62 ms

cloud-zoom.css

59 ms

Our browser made a total of 121 requests to load all elements on the main page. We found that 69% of them (84 requests) were addressed to the original Barrieflowers.net, 10% (12 requests) were made to Maps.googleapis.com and 5% (6 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (649 ms) relates to the external source Deadseacosmetics.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (54%)

Content Size

2.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Barrieflowers.net main page is 2.2 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. 55% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 103.9 kB

  • Original 114.4 kB
  • After minification 79.0 kB
  • After compression 10.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 35.4 kB, which is 31% 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 103.9 kB or 91% of the original size.

Image Optimization

-7%

Potential reduce by 49.1 kB

  • Original 700.2 kB
  • After minification 651.2 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. Barrie Flower S images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 896.0 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 337.7 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 896.0 kB or 73% of the original size.

CSS Optimization

-87%

Potential reduce by 140.2 kB

  • Original 161.1 kB
  • After minification 106.8 kB
  • After compression 20.9 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. Barrieflowers.net needs all CSS files to be minified and compressed as it can save up to 140.2 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (44%)

Requests Now

117

After Optimization

65

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.barrieflowers.net

www.barrieflowers.net

533 ms

webfont.js

webfont.js

13 ms

styles.css

styles.css

176 ms

widgets.css

widgets.css

62 ms

cloud-zoom.css

cloud-zoom.css

59 ms

common_skin.css

common_skin.css

56 ms

skin.css

skin.css

56 ms

menu_standard.css

menu_standard.css

90 ms

prototype.js

prototype.js

216 ms

ccard.js

ccard.js

100 ms

validation.js

validation.js

158 ms

builder.js

builder.js

120 ms

effects.js

effects.js

186 ms

dragdrop.js

dragdrop.js

133 ms

controls.js

controls.js

179 ms

slider.js

slider.js

163 ms

js.js

js.js

187 ms

form.js

form.js

193 ms

menu.js

menu.js

200 ms

translate.js

translate.js

210 ms

cookies.js

cookies.js

239 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

279 ms

cloud-zoom.1.0.2.min.js

cloud-zoom.1.0.2.min.js

239 ms

jquery-noconflict.js

jquery-noconflict.js

241 ms

tools.tabs-1.0.4.min.js

tools.tabs-1.0.4.min.js

240 ms

jquery.cycle.2.999.js

jquery.cycle.2.999.js

242 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

242 ms

css

css

23 ms

css

css

13 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

6 ms

bg.png

bg.png

66 ms

logo.png

logo.png

46 ms

banner_01.jpg

banner_01.jpg

76 ms

banner_02.jpg

banner_02.jpg

56 ms

banner_03.jpg

banner_03.jpg

75 ms

banner_04.jpg

banner_04.jpg

47 ms

6.jpg

6.jpg

73 ms

make_a_wish.jpg

make_a_wish.jpg

80 ms

sale.png

sale.png

81 ms

upsy_daisy.jpg

upsy_daisy.jpg

102 ms

file_36_2.jpg

file_36_2.jpg

109 ms

file_39_12.jpg

file_39_12.jpg

109 ms

basket_full_of_wishes.jpg

basket_full_of_wishes.jpg

107 ms

pap_1.jpg

pap_1.jpg

115 ms

file_34_7.jpg

file_34_7.jpg

114 ms

arrive_in_style.jpg

arrive_in_style.jpg

132 ms

ppink.jpg

ppink.jpg

139 ms

ss.jpg

ss.jpg

143 ms

file_39_2.jpg

file_39_2.jpg

137 ms

wgcdnrsd.jpg

wgcdnrsd.jpg

140 ms

wgcdncsd.jpg

wgcdncsd.jpg

144 ms

file_1.jpg

file_1.jpg

161 ms

garden_romance.jpg

garden_romance.jpg

173 ms

06n300b.jpg

06n300b.jpg

169 ms

hw0_328349.jpg

hw0_328349.jpg

170 ms

3.jpg

3.jpg

173 ms

file_44_5.jpg

file_44_5.jpg

173 ms

tf43_02_wh.jpg

tf43_02_wh.jpg

188 ms

10v130b.jpg

10v130b.jpg

198 ms

tf43_01_wh.jpg

tf43_01_wh.jpg

199 ms

file_2_1.jpg

file_2_1.jpg

200 ms

file_35_1.jpg

file_35_1.jpg

201 ms

tfweb629.jpg

tfweb629.jpg

203 ms

roses.jpg

roses.jpg

215 ms

file_38.jpg

file_38.jpg

227 ms

ga.js

ga.js

8 ms

tfweb501.jpg

tfweb501.jpg

222 ms

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

24 ms

__utm.gif

__utm.gif

12 ms

facebook.png

facebook.png

196 ms

zopim.com

zopim.com

211 ms

twitter.png

twitter.png

193 ms

googleplus.png

googleplus.png

185 ms

visa.png

visa.png

197 ms

mastercard.png

mastercard.png

193 ms

discover.png

discover.png

197 ms

am.png

am.png

198 ms

paypal.png

paypal.png

195 ms

bg-top.png

bg-top.png

190 ms

icons.png

icons.png

192 ms

widget_v2.135.js

widget_v2.135.js

20 ms

print.css

print.css

118 ms

piwik.js

piwik.js

649 ms

ic-toplinks-account.png

ic-toplinks-account.png

37 ms

ic-toplinks-wishlist.png

ic-toplinks-wishlist.png

39 ms

ic-toplinks-log.png

ic-toplinks-log.png

37 ms

ic-toplinks-signup.png

ic-toplinks-signup.png

40 ms

pix.png

pix.png

39 ms

navbar-red.png

navbar-red.png

39 ms

menu-bullet.gif

menu-bullet.gif

118 ms

slideshow-arrows.png

slideshow-arrows.png

118 ms

grid-item-shadow.png

grid-item-shadow.png

117 ms

embed

embed

185 ms

footer.png

footer.png

85 ms

footer-bg-plus.png

footer-bg-plus.png

85 ms

__utm.gif

__utm.gif

76 ms

js

js

48 ms

init_embed.js

init_embed.js

36 ms

common.js

common.js

46 ms

map.js

map.js

63 ms

google4.png

google4.png

30 ms

overlay.js

overlay.js

29 ms

util.js

util.js

69 ms

onion.js

onion.js

67 ms

search_impl.js

search_impl.js

29 ms

stats.js

stats.js

27 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

55 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

34 ms

transparent.png

transparent.png

31 ms

kh

kh

131 ms

controls.js

controls.js

13 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

79 ms

css

css

80 ms

entity11.png

entity11.png

51 ms

vt

vt

83 ms

vt

vt

72 ms

vt

vt

70 ms

vt

vt

78 ms

vt

vt

78 ms

mapcnt6.png

mapcnt6.png

23 ms

tmapctrl.png

tmapctrl.png

33 ms

SEO Factors

barrieflowers.net SEO score

0

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 Barrieflowers.net 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 Barrieflowers.net 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

barrieflowers.net

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