Tools & Wizards About Us
winterparkfloral.com screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

winterparkfloral.com

Welcome | WoodStem Floral

Page Load Speed

893 ms in total

First Response

88 ms

Resources Loaded

739 ms

Page Rendered

66 ms

winterparkfloral.com screenshot

About Website

Click here to check amazing Winterpark Floral content. Otherwise, check out these important facts you probably never knew about winterparkfloral.com

Colorado Wedding Florist

Visit winterparkfloral.com

Key Findings

We analyzed Winterparkfloral.com page load time and found that the first response time was 88 ms and then it took 805 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

winterparkfloral.com performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.3 s

32/100

10%

Network Requests Diagram

www.winterparkfloral.com

88 ms

originTrials.41d7301a.bundle.min.js

38 ms

minified.js

46 ms

focus-within-polyfill.js

84 ms

polyfill.min.js

37 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Winterparkfloral.com, 43% (19 requests) were made to Static.parastorage.com and 27% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (405 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 788.1 kB (64%)

Content Size

1.2 MB

After Optimization

445.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Winterparkfloral.com main page is 1.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. 30% of websites need less resources to load. HTML takes 958.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 780.4 kB

  • Original 958.1 kB
  • After minification 956.6 kB
  • After compression 177.7 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 780.4 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 4.9 kB

  • Original 51.2 kB
  • After minification 46.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. Winterpark Floral images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 224.4 kB
  • After minification 224.4 kB
  • After compression 221.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.

Requests Breakdown

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

Requests Now

25

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.winterparkfloral.com

www.winterparkfloral.com

88 ms

originTrials.41d7301a.bundle.min.js

originTrials.41d7301a.bundle.min.js

38 ms

minified.js

minified.js

46 ms

focus-within-polyfill.js

focus-within-polyfill.js

84 ms

polyfill.min.js

polyfill.min.js

37 ms

thunderbolt-commons.ec68bee9.bundle.min.js

thunderbolt-commons.ec68bee9.bundle.min.js

23 ms

main.f286c407.bundle.min.js

main.f286c407.bundle.min.js

61 ms

lodash.min.js

lodash.min.js

61 ms

react.production.min.js

react.production.min.js

22 ms

react-dom.production.min.js

react-dom.production.min.js

124 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

122 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

123 ms

Woodstem_logo_black.png

Woodstem_logo_black.png

289 ms

bundle.min.js

bundle.min.js

72 ms

11062b_a6d154bfda6d4921baa3cdf6b615a9db~mv2_d_5184_3456_s_4_2.jpg

11062b_a6d154bfda6d4921baa3cdf6b615a9db~mv2_d_5184_3456_s_4_2.jpg

41 ms

722f9c_89582ad435b14648a7e60bb81f08bbe4~mv2.jpg

722f9c_89582ad435b14648a7e60bb81f08bbe4~mv2.jpg

205 ms

11062b_a6d154bfda6d4921baa3cdf6b615a9db~mv2_d_5184_3456_s_4_2.jpg

11062b_a6d154bfda6d4921baa3cdf6b615a9db~mv2_d_5184_3456_s_4_2.jpg

148 ms

Rustic%20Wedding%20Chic.png

Rustic%20Wedding%20Chic.png

244 ms

Wedding%20Chicks%20Badge.png

Wedding%20Chicks%20Badge.png

209 ms

Rocky%20Mountain%20Bride%20Magazine.png

Rocky%20Mountain%20Bride%20Magazine.png

201 ms

Couture%20Colorado%20Blog.png

Couture%20Colorado%20Blog.png

404 ms

Mountainside-Bride-Badge-WEB-300x300.png

Mountainside-Bride-Badge-WEB-300x300.png

405 ms

130 ms

130 ms

131 ms

130 ms

129 ms

127 ms

163 ms

172 ms

170 ms

170 ms

166 ms

164 ms

61bd362e-7162-46bd-b67e-28f366c4afbe.woff

61bd362e-7162-46bd-b67e-28f366c4afbe.woff

11 ms

9362bca5-b362-4543-a051-2129e2def911.woff

9362bca5-b362-4543-a051-2129e2def911.woff

16 ms

BrandonGrotesqueCondW05-Lt.woff

BrandonGrotesqueCondW05-Lt.woff

17 ms

deprecation-en.v5.html

deprecation-en.v5.html

6 ms

bolt-performance

bolt-performance

18 ms

deprecation-style.v5.css

deprecation-style.v5.css

5 ms

right-arrow.svg

right-arrow.svg

13 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

4 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

5 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

4 ms

Accessibility Review

winterparkfloral.com accessibility score

100

Accessibility Issues

Best Practices

winterparkfloral.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

winterparkfloral.com SEO score

96

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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

winterparkfloral.com

Open Graph data is detected on the main page of Winterpark Floral. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: