Tools & Wizards About Us
wfloral.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

wfloral.com

W Floral Studio | Luxury Floral Gifts & GTA Delivery

Page Load Speed

2.2 sec in total

First Response

176 ms

Resources Loaded

2 sec

Page Rendered

74 ms

wfloral.com screenshot

About Website

Click here to check amazing W Floral content for Canada. Otherwise, check out these important facts you probably never knew about wfloral.com

W Floral Studio offers luxurious floral gifts and bespoke bouquets, perfect for any occasion. Our handcrafted arrangements are available for local delivery, ensuring your thoughtful gesture arrives be...

Visit wfloral.com

Key Findings

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

Performance Metrics

wfloral.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value3,450 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value24.8 s

0/100

10%

Network Requests Diagram

www.wfloral.com

176 ms

originTrials.41d7301a.bundle.min.js

60 ms

minified.js

60 ms

focus-within-polyfill.js

103 ms

polyfill.min.js

337 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Wfloral.com, 38% (23 requests) were made to Static.wixstatic.com and 35% (21 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 922.4 kB (61%)

Content Size

1.5 MB

After Optimization

589.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wfloral.com main page is 1.5 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. 45% of websites need less resources to load. HTML takes 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 826.1 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 180.1 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 826.1 kB or 82% of the original size.

Image Optimization

-32%

Potential reduce by 96.1 kB

  • Original 301.1 kB
  • After minification 205.0 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. Obviously, W Floral needs image optimization as it can save up to 96.1 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 190 B

  • Original 204.3 kB
  • After minification 204.3 kB
  • After compression 204.1 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 10 (26%)

Requests Now

38

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.wfloral.com

www.wfloral.com

176 ms

originTrials.41d7301a.bundle.min.js

originTrials.41d7301a.bundle.min.js

60 ms

minified.js

minified.js

60 ms

focus-within-polyfill.js

focus-within-polyfill.js

103 ms

polyfill.min.js

polyfill.min.js

337 ms

thunderbolt-commons.eb770ee8.bundle.min.js

thunderbolt-commons.eb770ee8.bundle.min.js

70 ms

main.578f27a3.bundle.min.js

main.578f27a3.bundle.min.js

76 ms

lodash.min.js

lodash.min.js

75 ms

react.production.min.js

react.production.min.js

73 ms

react-dom.production.min.js

react-dom.production.min.js

75 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

75 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

74 ms

1.png

1.png

280 ms

fc9b34_2f5be45fb2e642bdbd5f428814c53239~mv2.jpg

fc9b34_2f5be45fb2e642bdbd5f428814c53239~mv2.jpg

416 ms

fc9b34_4d3b6062e8e34152b4ae73e1b3466867~mv2.jpg

fc9b34_4d3b6062e8e34152b4ae73e1b3466867~mv2.jpg

491 ms

fc9b34_ac20e07a65d04801b73c253d1ccdea35~mv2.jpg

fc9b34_ac20e07a65d04801b73c253d1ccdea35~mv2.jpg

534 ms

fc9b34_c68bab0c33864f529bab0b0fb92ca4f4~mv2.png

fc9b34_c68bab0c33864f529bab0b0fb92ca4f4~mv2.png

442 ms

fc9b34_80a34f3f206f418889ad3b1890ec8545~mv2.jpg

fc9b34_80a34f3f206f418889ad3b1890ec8545~mv2.jpg

427 ms

fc9b34_aa0196a7090048269ed10e7b367b668c~mv2.png

fc9b34_aa0196a7090048269ed10e7b367b668c~mv2.png

536 ms

2.png

2.png

590 ms

0E1A2630_Original_edited_edited.png

0E1A2630_Original_edited_edited.png

606 ms

0E1A8933.jpg

0E1A8933.jpg

640 ms

IMG_9332_JPG.jpg

IMG_9332_JPG.jpg

647 ms

fc9b34_186c6d15fc514e9d9dd432f3a706c1e1~mv2.jpg

fc9b34_186c6d15fc514e9d9dd432f3a706c1e1~mv2.jpg

779 ms

fc9b34_12ae3be4f9674e57839bfa978094da92~mv2.jpg

fc9b34_12ae3be4f9674e57839bfa978094da92~mv2.jpg

780 ms

fc9b34_d1f10204563e4b999e699c375ba529f1~mv2.jpg

fc9b34_d1f10204563e4b999e699c375ba529f1~mv2.jpg

797 ms

fc9b34_0e56c58840374a04926fb2590d2e8c0c~mv2_d_2048_1365_s_2.jpg

fc9b34_0e56c58840374a04926fb2590d2e8c0c~mv2_d_2048_1365_s_2.jpg

869 ms

fc9b34_b1e6fa58eae34b5190b27da23c96f463~mv2_d_2047_1535_s_2.jpg

fc9b34_b1e6fa58eae34b5190b27da23c96f463~mv2_d_2047_1535_s_2.jpg

1001 ms

image.png

image.png

890 ms

image.png

image.png

1072 ms

FDR%20Badge%20White.png

FDR%20Badge%20White.png

990 ms

image.png

image.png

1013 ms

image.png

image.png

1121 ms

image.png

image.png

1150 ms

231619887340__pic_hd.jpg

231619887340__pic_hd.jpg

1118 ms

bundle.min.js

bundle.min.js

204 ms

388ef902-2c31-4818-abb1-a40dcd81f6d6.woff

388ef902-2c31-4818-abb1-a40dcd81f6d6.woff

17 ms

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

17 ms

9VWMTeb5jtXkNoTv949NpRsxEYwM7FgeyaSgU71cLG0.woff

9VWMTeb5jtXkNoTv949NpRsxEYwM7FgeyaSgU71cLG0.woff

30 ms

aDjpMND83pDErGXlVEr-SRsxEYwM7FgeyaSgU71cLG0.woff

aDjpMND83pDErGXlVEr-SRsxEYwM7FgeyaSgU71cLG0.woff

16 ms

AvenirLTW05-35Light.woff

AvenirLTW05-35Light.woff

28 ms

c5749443-93da-4592-b794-42f28d62ef72.woff

c5749443-93da-4592-b794-42f28d62ef72.woff

16 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

29 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

57 ms

51 ms

28 ms

34 ms

31 ms

32 ms

30 ms

83 ms

95 ms

96 ms

84 ms

99 ms

106 ms

deprecation-en.v5.html

deprecation-en.v5.html

16 ms

bolt-performance

bolt-performance

37 ms

deprecation-style.v5.css

deprecation-style.v5.css

14 ms

right-arrow.svg

right-arrow.svg

14 ms

Accessibility Review

wfloral.com accessibility score

89

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

wfloral.com SEO score

90

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

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

wfloral.com

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