Tools & Wizards About Us
flowerwatch.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

flowerwatch.com

FlowerWatch: Taking quality & vaselife to a new level

Page Load Speed

8.5 sec in total

First Response

317 ms

Resources Loaded

5.8 sec

Page Rendered

2.4 sec

flowerwatch.com screenshot

About Website

Visit flowerwatch.com now to see the best up-to-date Flower Watch content and also check out these interesting facts you probably never knew about flowerwatch.com

Standardization is transforming the flower industry worldwide. By adopting science-based, achievable, and measurable norms, your company can join the transformation.

Visit flowerwatch.com

Key Findings

We analyzed Flowerwatch.com page load time and found that the first response time was 317 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

flowerwatch.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value5.7 s

50/100

10%

TBT (Total Blocking Time)

Value1,240 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.223

56/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

flowerwatch.com

317 ms

flowerwatch.com

359 ms

www.flowerwatch.com

688 ms

main.css

177 ms

js

98 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 41% of them (20 requests) were addressed to the original Flowerwatch.com, 18% (9 requests) were made to Fonts.gstatic.com and 12% (6 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Flowerwatch.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 345.2 kB (8%)

Content Size

4.2 MB

After Optimization

3.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flowerwatch.com main page is 4.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 17.2 kB

  • Original 24.5 kB
  • After minification 24.1 kB
  • After compression 7.3 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 17.2 kB or 70% of the original size.

Image Optimization

-8%

Potential reduce by 327.9 kB

  • Original 4.1 MB
  • After minification 3.7 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. Flower Watch images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 113 B

  • Original 21.9 kB
  • After minification 21.9 kB
  • After compression 21.8 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 44 B

  • Original 66.1 kB
  • After minification 66.1 kB
  • After compression 66.1 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. Flowerwatch.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (37%)

Requests Now

35

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flowerwatch.com

flowerwatch.com

317 ms

flowerwatch.com

flowerwatch.com

359 ms

www.flowerwatch.com

www.flowerwatch.com

688 ms

main.css

main.css

177 ms

js

js

98 ms

polyfills.js

polyfills.js

732 ms

vue.js

vue.js

276 ms

main.js

main.js

742 ms

api.js

api.js

84 ms

css

css

121 ms

gtm.js

gtm.js

428 ms

analytics.js

analytics.js

430 ms

gb.svg

gb.svg

328 ms

user.svg

user.svg

326 ms

logo.svg

logo.svg

330 ms

rozen.jpg

rozen.jpg

1629 ms

Screenshot-2022-09-09-at-15.40.19.png

Screenshot-2022-09-09-at-15.40.19.png

1981 ms

Screenshot-2022-07-29-at-11.42.27_1.png

Screenshot-2022-07-29-at-11.42.27_1.png

1986 ms

Screenshot-2022-05-16-at-09.22.01.png

Screenshot-2022-05-16-at-09.22.01.png

1633 ms

Logo-FW-approved_eps_00_00.png

Logo-FW-approved_eps_00_00.png

917 ms

shutterstock_1143037052-Groot.jpg

shutterstock_1143037052-Groot.jpg

1593 ms

FlowerWatch-Whitepaper-Cover.jpg

FlowerWatch-Whitepaper-Cover.jpg

1593 ms

KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf

570 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

570 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

996 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsHYl4BO.ttf

KFOjCnqEu92Fr1Mu51S7ACc6CsHYl4BO.ttf

1054 ms

KFOkCnqEu92Fr1Mu51xIIzcXKMny.ttf

KFOkCnqEu92Fr1Mu51xIIzcXKMny.ttf

1053 ms

KFOjCnqEu92Fr1Mu51TjASc6CsHYl4BO.ttf

KFOjCnqEu92Fr1Mu51TjASc6CsHYl4BO.ttf

1149 ms

icons.woff

icons.woff

1288 ms

1281 ms

collect

collect

605 ms

collect

collect

591 ms

collect

collect

442 ms

vendors~jarallax.js

vendors~jarallax.js

837 ms

recaptcha__en.js

recaptcha__en.js

420 ms

insight.min.js

insight.min.js

429 ms

collect

collect

484 ms

anchor

anchor

99 ms

styles__ltr.css

styles__ltr.css

15 ms

recaptcha__en.js

recaptcha__en.js

19 ms

webworker.js

webworker.js

790 ms

logo_48.png

logo_48.png

318 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

46 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

41 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

42 ms

recaptcha__en.js

recaptcha__en.js

401 ms

bframe

bframe

469 ms

recaptcha__en.js

recaptcha__en.js

15 ms

28 ms

Accessibility Review

flowerwatch.com accessibility score

92

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

[aria-hidden="true"] elements contain focusable descendents

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.

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

Links do not have a discernible name

Best Practices

flowerwatch.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

flowerwatch.com SEO score

91

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

flowerwatch.com

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