Tools & Wizards About Us
flowerforce.nl screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

flowerforce.nl

FlowerForce | Flowers & Plants online Webshop

Page Load Speed

3.7 sec in total

First Response

428 ms

Resources Loaded

2.9 sec

Page Rendered

325 ms

flowerforce.nl screenshot

About Website

Visit flowerforce.nl now to see the best up-to-date Flower Force content for Russia and also check out these interesting facts you probably never knew about flowerforce.nl

Shop online Flowers & Plants | Daily fresh assortment | Events | Worldwide export | Pre-cooled shipping | FlowerForce - We deliver happiness!

Visit flowerforce.nl

Key Findings

We analyzed Flowerforce.nl page load time and found that the first response time was 428 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

flowerforce.nl performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

flowerforce.nl

428 ms

www.flowerforce.nl

468 ms

main.css

228 ms

modernizr-2.6.2.min.js

231 ms

jquery.js

356 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 73% of them (38 requests) were addressed to the original Flowerforce.nl, 8% (4 requests) were made to F.vimeocdn.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Flowerforce.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 557.3 kB (46%)

Content Size

1.2 MB

After Optimization

658.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flowerforce.nl 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. 50% of websites need less resources to load. Images take 571.2 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 8.1 kB

  • Original 11.4 kB
  • After minification 10.4 kB
  • After compression 3.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. 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 8.1 kB or 71% of the original size.

Image Optimization

-18%

Potential reduce by 105.0 kB

  • Original 571.2 kB
  • After minification 466.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. Obviously, Flower Force needs image optimization as it can save up to 105.0 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 312.0 kB

  • Original 482.0 kB
  • After minification 478.6 kB
  • After compression 170.0 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 312.0 kB or 65% of the original size.

CSS Optimization

-88%

Potential reduce by 132.2 kB

  • Original 151.0 kB
  • After minification 135.8 kB
  • After compression 18.8 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. Flowerforce.nl needs all CSS files to be minified and compressed as it can save up to 132.2 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (40%)

Requests Now

47

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flowerforce.nl

flowerforce.nl

428 ms

www.flowerforce.nl

www.flowerforce.nl

468 ms

main.css

main.css

228 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

231 ms

jquery.js

jquery.js

356 ms

jquery.webticker.js

jquery.webticker.js

239 ms

jquery.cycle.js

jquery.cycle.js

243 ms

main.js

main.js

243 ms

normalize.css

normalize.css

239 ms

base.css

base.css

241 ms

helpers.css

helpers.css

251 ms

form.css

form.css

254 ms

css

css

24 ms

bloemen-04.jpg

bloemen-04.jpg

584 ms

webshop-bg.png

webshop-bg.png

247 ms

icon-support.png

icon-support.png

246 ms

icon-app.png

icon-app.png

249 ms

icon-cart.png

icon-cart.png

247 ms

button-gradient.png

button-gradient.png

399 ms

webshop-label-en.png

webshop-label-en.png

515 ms

flowerforce-logo.png

flowerforce-logo.png

520 ms

dropdown_arrow.png

dropdown_arrow.png

517 ms

lan_en.gif

lan_en.gif

519 ms

nav-home.jpg

nav-home.jpg

559 ms

nav-flowerforce.jpg

nav-flowerforce.jpg

753 ms

nav-partners.jpg

nav-partners.jpg

750 ms

nav-kalender.jpg

nav-kalender.jpg

754 ms

nav-productinfo.jpg

nav-productinfo.jpg

760 ms

nav-socialnews.jpg

nav-socialnews.jpg

783 ms

nav-contact.jpg

nav-contact.jpg

923 ms

1.png

1.png

1211 ms

2.png

2.png

1227 ms

3.png

3.png

1221 ms

4.png

4.png

1106 ms

5.png

5.png

1133 ms

6.png

6.png

1385 ms

7.png

7.png

1489 ms

ga.js

ga.js

7 ms

106787175

106787175

98 ms

ticker-overlay-left.png

ticker-overlay-left.png

1294 ms

ticker-overlay-right.png

ticker-overlay-right.png

1371 ms

9k-RPmcnxYEPm8CNFsH2gg.woff

9k-RPmcnxYEPm8CNFsH2gg.woff

58 ms

wkfQbvfT_02e2IWO3yYueQ.woff

wkfQbvfT_02e2IWO3yYueQ.woff

58 ms

__utm.gif

__utm.gif

25 ms

player.js

player.js

128 ms

player.css

player.css

94 ms

ga.js

ga.js

53 ms

vuid.min.js

vuid.min.js

119 ms

__utm.gif

__utm.gif

22 ms

proxy.html

proxy.html

56 ms

490001623.webp

490001623.webp

156 ms

8381723_60x60.jpg

8381723_60x60.jpg

73 ms

Accessibility Review

flowerforce.nl accessibility score

83

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

flowerforce.nl 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

High

Page has valid source maps

SEO Factors

flowerforce.nl SEO score

83

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

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 Flowerforce.nl 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 Flowerforce.nl 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

flowerforce.nl

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