Tools & Wizards About Us
urbanbloom.nl screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

urbanbloom.nl

Visit our store for flowers in Amsterdam - URBANBLOOM

Page Load Speed

8.3 sec in total

First Response

303 ms

Resources Loaded

5.8 sec

Page Rendered

2.1 sec

urbanbloom.nl screenshot

About Website

Click here to check amazing URBANBLOOM content. Otherwise, check out these important facts you probably never knew about urbanbloom.nl

Are you looking for flower shops in Amsterdam? We can help you find your favorite flowers and bouquets in the area. Visit our store or order online.

Visit urbanbloom.nl

Key Findings

We analyzed Urbanbloom.nl page load time and found that the first response time was 303 ms and then it took 8 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

urbanbloom.nl performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value1,040 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value8.9 s

34/100

10%

Network Requests Diagram

urbanbloom.nl

303 ms

1973 ms

index.css

101 ms

style.min.css

205 ms

menu-animation.min.css

281 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 89% of them (76 requests) were addressed to the original Urbanbloom.nl, 4% (3 requests) were made to Stats.wp.com and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Urbanbloom.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 208.7 kB (19%)

Content Size

1.1 MB

After Optimization

889.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Urbanbloom.nl main page is 1.1 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. 60% of websites need less resources to load. Images take 577.8 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 191.1 kB

  • Original 224.6 kB
  • After minification 220.9 kB
  • After compression 33.5 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 191.1 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 4.8 kB

  • Original 577.8 kB
  • After minification 573.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. URBANBLOOM images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 3.2 kB

  • Original 175.7 kB
  • After minification 174.9 kB
  • After compression 172.5 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

-8%

Potential reduce by 9.5 kB

  • Original 120.1 kB
  • After minification 119.9 kB
  • After compression 110.6 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. Urbanbloom.nl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 48 (59%)

Requests Now

81

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

urbanbloom.nl

urbanbloom.nl

303 ms

1973 ms

index.css

index.css

101 ms

style.min.css

style.min.css

205 ms

menu-animation.min.css

menu-animation.min.css

281 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

288 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

290 ms

woocommerce-layout.min.css

woocommerce-layout.min.css

290 ms

woocommerce.min.css

woocommerce.min.css

386 ms

woo-conditional-shipping.css

woo-conditional-shipping.css

301 ms

elementor-icons.min.css

elementor-icons.min.css

382 ms

frontend.min.css

frontend.min.css

485 ms

swiper.min.css

swiper.min.css

395 ms

post-6299.css

post-6299.css

396 ms

frontend.min.css

frontend.min.css

415 ms

global.css

global.css

481 ms

post-1025.css

post-1025.css

483 ms

css

css

41 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

494 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

496 ms

wp-polyfill.min.js

wp-polyfill.min.js

517 ms

hooks.min.js

hooks.min.js

583 ms

w.js

w.js

28 ms

js

js

64 ms

jquery.min.js

jquery.min.js

680 ms

jquery-migrate.min.js

jquery-migrate.min.js

609 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

658 ms

add-to-cart.min.js

add-to-cart.min.js

658 ms

js.cookie.min.js

js.cookie.min.js

659 ms

woocommerce.min.js

woocommerce.min.js

689 ms

s-202411.js

s-202411.js

25 ms

jquery.cookie.min.js

jquery.cookie.min.js

691 ms

woo-conditional-shipping.js

woo-conditional-shipping.js

710 ms

style.min.js

style.min.js

789 ms

sourcebuster.min.js

sourcebuster.min.js

790 ms

order-attribution.min.js

order-attribution.min.js

815 ms

i18n.min.js

i18n.min.js

814 ms

wc-blocks-google-analytics.js

wc-blocks-google-analytics.js

846 ms

actions.js

actions.js

846 ms

e-202411.js

e-202411.js

24 ms

cart-fragments.min.js

cart-fragments.min.js

849 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

849 ms

webpack.runtime.min.js

webpack.runtime.min.js

881 ms

frontend-modules.min.js

frontend-modules.min.js

891 ms

frontend.min.js

frontend.min.js

701 ms

waypoints.min.js

waypoints.min.js

644 ms

core.min.js

core.min.js

663 ms

frontend.min.js

frontend.min.js

663 ms

elements-handlers.min.js

elements-handlers.min.js

704 ms

g.gif

g.gif

74 ms

gtm.js

gtm.js

104 ms

flower-delivery-amsterdam.jpg

flower-delivery-amsterdam.jpg

528 ms

1844 ms

Pluk-boeket-50-005-300x300.jpg

Pluk-boeket-50-005-300x300.jpg

414 ms

Gemengd-boeket-300x300.jpeg

Gemengd-boeket-300x300.jpeg

409 ms

Ecuador-rozen-300x300.jpg

Ecuador-rozen-300x300.jpg

413 ms

bloemen-workshop-300x300.jpg

bloemen-workshop-300x300.jpg

413 ms

Weekboeket-35B-300x300.jpg

Weekboeket-35B-300x300.jpg

415 ms

Vaas-Bombyx-Jiminy-L-300x300.jpeg

Vaas-Bombyx-Jiminy-L-300x300.jpeg

448 ms

Vaas-Bombyx-Tiger-300x300.jpeg

Vaas-Bombyx-Tiger-300x300.jpeg

451 ms

Vaas-Bombyxx-Bambi-300x300.jpeg

Vaas-Bombyxx-Bambi-300x300.jpeg

471 ms

Vaas-Bombyxx-Prince-John-M-300x300.jpeg

Vaas-Bombyxx-Prince-John-M-300x300.jpeg

489 ms

Bolle-vaas-300x300.jpg

Bolle-vaas-300x300.jpg

554 ms

Vaas-Bombyxx-Pegasus-M-300x300.jpeg

Vaas-Bombyxx-Pegasus-M-300x300.jpeg

562 ms

Vaas-Bobyxx-Esmeralda-300x300.jpeg

Vaas-Bobyxx-Esmeralda-300x300.jpeg

579 ms

Vaas-Bombyx-Daisy-M-300x300.jpeg

Vaas-Bombyx-Daisy-M-300x300.jpeg

601 ms

Boeket-rozen-300x300.jpg

Boeket-rozen-300x300.jpg

631 ms

Rouwboeket-300x300.jpg

Rouwboeket-300x300.jpg

667 ms

Zomer-boeket-300x300.jpg

Zomer-boeket-300x300.jpg

667 ms

boeketje-gemengd-300x300.jpg

boeketje-gemengd-300x300.jpg

685 ms

Rood-boeket-300x300.jpg

Rood-boeket-300x300.jpg

719 ms

roze-boeket-1-300x300.jpg

roze-boeket-1-300x300.jpg

702 ms

lente-boeket-300x300.jpg

lente-boeket-300x300.jpg

722 ms

boeket-vaas-favi-300x300.jpg

boeket-vaas-favi-300x300.jpg

702 ms

Veldboeket-300x300.jpg

Veldboeket-300x300.jpg

725 ms

astra.woff

astra.woff

743 ms

g.gif

g.gif

18 ms

ECO-boeket-50-003-300x300.jpg

ECO-boeket-50-003-300x300.jpg

747 ms

Boeketten-categorie-300x300.jpg

Boeketten-categorie-300x300.jpg

780 ms

DutzCilinder-oi23gkzl1ld23q63vuzjq2fe46lak6f4528fhwkou0.jpg

DutzCilinder-oi23gkzl1ld23q63vuzjq2fe46lak6f4528fhwkou0.jpg

772 ms

star.woff

star.woff

792 ms

js

js

51 ms

Planten-categorie-okpts9nbpco4p2xnqst0w0ozmcria6j1v36brc6j7c.jpg

Planten-categorie-okpts9nbpco4p2xnqst0w0ozmcria6j1v36brc6j7c.jpg

781 ms

1391 ms

woocommerce-smallscreen.min.css

woocommerce-smallscreen.min.css

101 ms

Accessibility Review

urbanbloom.nl accessibility score

96

Accessibility Issues

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

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

SEO Factors

urbanbloom.nl SEO score

84

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

Links do not have descriptive text

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

urbanbloom.nl

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