Tools & Wizards About Us
bouquet.nl screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

bouquet.nl

Bloemen bestellen & bezorgen | De Roos Bloemist

Page Load Speed

10.7 sec in total

First Response

4.3 sec

Resources Loaded

6.1 sec

Page Rendered

250 ms

bouquet.nl screenshot

About Website

Welcome to bouquet.nl homepage info - get ready to check Bouquet best content right away, or after learning these important things about bouquet.nl

De Roos Bloemist: een begrip in Amsterdam sinds 1927 ✔ De mooiste bloemen & geschenken bestellen en bezorgen in regio Amsterdam ✔ Bestel online

Visit bouquet.nl

Key Findings

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

Performance Metrics

bouquet.nl performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value700 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.121

84/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

bouquet.nl

4305 ms

groupcat.css

505 ms

styles.css

677 ms

widgets.css

511 ms

facebookfree.css

504 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Bouquet.nl, 77% (50 requests) were made to Dev2.florist.nl and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Bouquet.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 646.0 kB (47%)

Content Size

1.4 MB

After Optimization

739.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bouquet.nl main page is 1.4 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. Javascripts take 647.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 46.3 kB

  • Original 58.1 kB
  • After minification 52.1 kB
  • After compression 11.8 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 46.3 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 8.5 kB

  • Original 552.5 kB
  • After minification 543.9 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. Bouquet images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 481.5 kB

  • Original 647.5 kB
  • After minification 519.7 kB
  • After compression 166.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 481.5 kB or 74% of the original size.

CSS Optimization

-86%

Potential reduce by 109.7 kB

  • Original 127.3 kB
  • After minification 96.4 kB
  • After compression 17.7 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. Bouquet.nl needs all CSS files to be minified and compressed as it can save up to 109.7 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

59

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bouquet.nl

bouquet.nl

4305 ms

groupcat.css

groupcat.css

505 ms

styles.css

styles.css

677 ms

widgets.css

widgets.css

511 ms

facebookfree.css

facebookfree.css

504 ms

guestbook.css

guestbook.css

511 ms

prototype.js

prototype.js

773 ms

ccard.js

ccard.js

586 ms

validation.js

validation.js

672 ms

builder.js

builder.js

593 ms

effects.js

effects.js

688 ms

dragdrop.js

dragdrop.js

753 ms

controls.js

controls.js

763 ms

slider.js

slider.js

755 ms

js.js

js.js

758 ms

form.js

form.js

761 ms

menu.js

menu.js

837 ms

translate.js

translate.js

838 ms

cookies.js

cookies.js

842 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

1022 ms

imgpreview.js

imgpreview.js

852 ms

hello.jquery.js

hello.jquery.js

854 ms

less.min.js

less.min.js

1005 ms

cufon-yui.js

cufon-yui.js

922 ms

jquery.cycle.all.js

jquery.cycle.all.js

928 ms

custom.js

custom.js

936 ms

css

css

28 ms

piwik.js

piwik.js

108 ms

bnr_nowAccepting_150x60.gif

bnr_nowAccepting_150x60.gif

83 ms

bk-body.jpg

bk-body.jpg

431 ms

logo.gif

logo.gif

107 ms

fb.gif

fb.gif

107 ms

logo-bloemist.png

logo-bloemist.png

106 ms

Banner_nieuw.jpg

Banner_nieuw.jpg

680 ms

Banner_Bouquet.jpg

Banner_Bouquet.jpg

563 ms

i_asc_arrow.gif

i_asc_arrow.gif

188 ms

kleurrijk_zomers_boeket.jpg

kleurrijk_zomers_boeket.jpg

188 ms

veuve_clicquot_suitcase.jpg

veuve_clicquot_suitcase.jpg

188 ms

phalaenopsis_in_pot.jpg

phalaenopsis_in_pot.jpg

273 ms

boeket_wit_creme.jpg

boeket_wit_creme.jpg

272 ms

boeket_wit.jpg

boeket_wit.jpg

282 ms

creditcards.gif

creditcards.gif

359 ms

ga.js

ga.js

79 ms

topbar.jpg

topbar.jpg

433 ms

dividers_top.gif

dividers_top.gif

355 ms

account_ico.png

account_ico.png

431 ms

cart_ico.png

cart_ico.png

439 ms

login_ico.png

login_ico.png

502 ms

search_bg.png

search_bg.png

516 ms

bkg_btn-small.png

bkg_btn-small.png

515 ms

bkg_toolbar.gif

bkg_toolbar.gif

511 ms

footerbg.jpg

footerbg.jpg

565 ms

all.js

all.js

60 ms

2Q-AW1e_taO6pHwMXcXW5w.ttf

2Q-AW1e_taO6pHwMXcXW5w.ttf

58 ms

OsJ2DjdpjqFRVUSto6IffKCWcynf_cDxXwCLxiixG1c.ttf

OsJ2DjdpjqFRVUSto6IffKCWcynf_cDxXwCLxiixG1c.ttf

57 ms

_aijTyevf54tkVDLy-dlnKCWcynf_cDxXwCLxiixG1c.ttf

_aijTyevf54tkVDLy-dlnKCWcynf_cDxXwCLxiixG1c.ttf

82 ms

0ihfXUL2emPh0ROJezvraKCWcynf_cDxXwCLxiixG1c.ttf

0ihfXUL2emPh0ROJezvraKCWcynf_cDxXwCLxiixG1c.ttf

70 ms

__utm.gif

__utm.gif

38 ms

piwik.php

piwik.php

551 ms

collect

collect

74 ms

125 ms

xd_arbiter.php

xd_arbiter.php

35 ms

xd_arbiter.php

xd_arbiter.php

47 ms

print.css

print.css

85 ms

xd_arbiter.php

xd_arbiter.php

7 ms

Accessibility Review

bouquet.nl accessibility score

79

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-*] attributes do not match their roles

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

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

Best Practices

bouquet.nl best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

bouquet.nl SEO score

92

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bouquet.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Bouquet.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

bouquet.nl

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