Tools & Wizards About Us
whitehorseflowers.ca screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

whitehorseflowers.ca

  Whitehorse YT Florist - White Horse Flowers Etc.

Page Load Speed

4.5 sec in total

First Response

757 ms

Resources Loaded

3.3 sec

Page Rendered

477 ms

whitehorseflowers.ca screenshot

About Website

Click here to check amazing Whitehorse Flowers content. Otherwise, check out these important facts you probably never knew about whitehorseflowers.ca

Whitehorse Florist- 100% Satisfaction Guaranteed. Buy bouquets, roses, lilies, daisies, and more!

Visit whitehorseflowers.ca

Key Findings

We analyzed Whitehorseflowers.ca page load time and found that the first response time was 757 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

whitehorseflowers.ca performance score

0

Network Requests Diagram

whitehorseflowers.ca

757 ms

css

31 ms

css

43 ms

jquery-1.7.min.js

52 ms

superfish.js

50 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Whitehorseflowers.ca, 38% (42 requests) were made to Assets1.floranext.com and 20% (22 requests) were made to Image.floranext.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Image.floranext.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 597.3 kB (11%)

Content Size

5.6 MB

After Optimization

5.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whitehorseflowers.ca main page is 5.6 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. 65% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 90.2 kB

  • Original 101.5 kB
  • After minification 68.9 kB
  • After compression 11.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 32.6 kB, which is 32% 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 90.2 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 535 B

  • Original 4.6 MB
  • After minification 4.6 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. Whitehorse Flowers images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 354.5 kB

  • Original 678.8 kB
  • After minification 622.4 kB
  • After compression 324.3 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 354.5 kB or 52% of the original size.

CSS Optimization

-80%

Potential reduce by 152.1 kB

  • Original 191.1 kB
  • After minification 188.7 kB
  • After compression 39.0 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. Whitehorseflowers.ca needs all CSS files to be minified and compressed as it can save up to 152.1 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (53%)

Requests Now

100

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whitehorseflowers.ca

whitehorseflowers.ca

757 ms

css

css

31 ms

css

css

43 ms

jquery-1.7.min.js

jquery-1.7.min.js

52 ms

superfish.js

superfish.js

50 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

67 ms

jquery.mobile.customized.min.js

jquery.mobile.customized.min.js

67 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

73 ms

prototype.js

prototype.js

73 ms

prototype_updates.js

prototype_updates.js

81 ms

ccard.js

ccard.js

80 ms

validation.js

validation.js

84 ms

builder.js

builder.js

85 ms

effects.js

effects.js

80 ms

dragdrop.js

dragdrop.js

87 ms

controls.js

controls.js

81 ms

slider.js

slider.js

88 ms

js.js

js.js

99 ms

form.js

form.js

92 ms

menu.js

menu.js

98 ms

translate.js

translate.js

101 ms

cookies.js

cookies.js

102 ms

popUp.min.js

popUp.min.js

103 ms

loader.min.js

loader.min.js

110 ms

top_nav_menu.js

top_nav_menu.js

116 ms

carousel.js

carousel.js

117 ms

droptool.js

droptool.js

119 ms

droptool.min.js

droptool.min.js

121 ms

scripts.js

scripts.js

116 ms

styles.css

styles.css

126 ms

responsive.css

responsive.css

136 ms

superfish.css

superfish.css

132 ms

widgets.css

widgets.css

139 ms

font-awesome.min.css

font-awesome.min.css

136 ms

styles-clear-text.css

styles-clear-text.css

135 ms

bright_green_scheme.css

bright_green_scheme.css

144 ms

abanner.css

abanner.css

146 ms

easy_cms.css

easy_cms.css

146 ms

frontpage.css

frontpage.css

150 ms

css

css

13 ms

x800_1567639954_0.82952400_1567639953.png

x800_1567639954_0.82952400_1567639953.png

640 ms

embed

embed

620 ms

417 ms

4bd51ec9-bbaf-4c60-9570-99cd515875ae.jpg

4bd51ec9-bbaf-4c60-9570-99cd515875ae.jpg

1412 ms

2af62ba5-5120-4696-ae06-37fe34df9775.jpg

2af62ba5-5120-4696-ae06-37fe34df9775.jpg

603 ms

081916f5-b7dc-4bc5-9162-fefad573cec5.jpg

081916f5-b7dc-4bc5-9162-fefad573cec5.jpg

590 ms

rosyrewards.jpg

rosyrewards.jpg

1015 ms

img_98141_1__1.jpg

img_98141_1__1.jpg

1017 ms

img_13521_1__1.jpg

img_13521_1__1.jpg

864 ms

0.01498700_1549930934_1.jpeg

0.01498700_1549930934_1.jpeg

1045 ms

0.23893100_1549931045_1.jpeg

0.23893100_1549931045_1.jpeg

1050 ms

0.22415200_1549931104_1.jpeg

0.22415200_1549931104_1.jpeg

1310 ms

0.94326800_1549931292_1.jpeg

0.94326800_1549931292_1.jpeg

1246 ms

0.30855100_1549931425_1.jpeg

0.30855100_1549931425_1.jpeg

1419 ms

0.07487200_1549931637_1.jpeg

0.07487200_1549931637_1.jpeg

1373 ms

heavenlyhandtied.jpg

heavenlyhandtied.jpg

1506 ms

mixeddozen.jpg

mixeddozen.jpg

1488 ms

fitforaqueen.jpg

fitforaqueen.jpg

1678 ms

wildandwow.jpg

wildandwow.jpg

1781 ms

thanksforsayingyes.jpg

thanksforsayingyes.jpg

1931 ms

theboxeddozen.jpg

theboxeddozen.jpg

1767 ms

thesinglerose.jpg

thesinglerose.jpg

1896 ms

heavenlyhalfdozen.jpg

heavenlyhalfdozen.jpg

1925 ms

goldenrosy.jpg

goldenrosy.jpg

2055 ms

369 ms

sprites.png

sprites.png

27 ms

desc_sprite.png

desc_sprite.png

42 ms

ajax-loader-tr.gif

ajax-loader-tr.gif

42 ms

footer_logo.png

footer_logo.png

26 ms

footer_logo.png

footer_logo.png

25 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

18 ms

mem5YaGs126MiZpBA-UN7rgOUuhs.ttf

mem5YaGs126MiZpBA-UN7rgOUuhs.ttf

24 ms

mem8YaGs126MiZpBA-UFVZ0e.ttf

mem8YaGs126MiZpBA-UFVZ0e.ttf

26 ms

mem5YaGs126MiZpBA-UN_r8OUuhs.ttf

mem5YaGs126MiZpBA-UN_r8OUuhs.ttf

27 ms

print.css

print.css

19 ms

js

js

14 ms

init_embed.js

init_embed.js

18 ms

common.js

common.js

33 ms

util.js

util.js

46 ms

map.js

map.js

43 ms

google4.png

google4.png

20 ms

overlay.js

overlay.js

17 ms

onion.js

onion.js

15 ms

search_impl.js

search_impl.js

15 ms

openhand_8_8.cur

openhand_8_8.cur

70 ms

kh

kh

106 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

31 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

18 ms

vt

vt

148 ms

vt

vt

120 ms

vt

vt

126 ms

vt

vt

170 ms

vt

vt

131 ms

vt

vt

155 ms

vt

vt

145 ms

vt

vt

155 ms

vt

vt

162 ms

vt

vt

172 ms

vt

vt

174 ms

vt

vt

179 ms

vt

vt

220 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

13 ms

QuotaService.RecordEvent

QuotaService.RecordEvent

15 ms

controls.js

controls.js

5 ms

QuotaService.RecordEvent

QuotaService.RecordEvent

43 ms

css

css

31 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

8 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

9 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

9 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

9 ms

SEO Factors

whitehorseflowers.ca 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 Whitehorseflowers.ca 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 Whitehorseflowers.ca 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

whitehorseflowers.ca

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