Tools & Wizards About Us
floridee.de screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

floridee.de

Floridee Blumenversand

Page Load Speed

4 sec in total

First Response

317 ms

Resources Loaded

2.6 sec

Page Rendered

1 sec

floridee.de screenshot

About Website

Visit floridee.de now to see the best up-to-date Floridee content for Germany and also check out these interesting facts you probably never knew about floridee.de

Visit floridee.de

Key Findings

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

Performance Metrics

floridee.de performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value4.4 s

73/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

floridee.de

317 ms

floridee.de

386 ms

www.floridee.de

556 ms

bootstrap.min.css

192 ms

style.css

283 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 87% of them (60 requests) were addressed to the original Floridee.de, 9% (6 requests) were made to Provenexpert.com and 3% (2 requests) were made to Clarity.ms. The less responsive or slowest element that took the longest time to load (837 ms) belongs to the original domain Floridee.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 318.1 kB (11%)

Content Size

2.9 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Floridee.de main page is 2.9 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 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 102.3 kB

  • Original 117.1 kB
  • After minification 104.2 kB
  • After compression 14.9 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. This page needs HTML code to be minified as it can gain 13.0 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 102.3 kB or 87% of the original size.

Image Optimization

-8%

Potential reduce by 208.9 kB

  • Original 2.6 MB
  • After minification 2.4 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. Floridee images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 454 B

  • Original 117.5 kB
  • After minification 117.5 kB
  • After compression 117.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. This website has mostly compressed JavaScripts.

CSS Optimization

-13%

Potential reduce by 6.5 kB

  • Original 48.2 kB
  • After minification 48.2 kB
  • After compression 41.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. Floridee.de needs all CSS files to be minified and compressed as it can save up to 6.5 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (33%)

Requests Now

30

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

floridee.de

floridee.de

317 ms

floridee.de

floridee.de

386 ms

www.floridee.de

www.floridee.de

556 ms

bootstrap.min.css

bootstrap.min.css

192 ms

style.css

style.css

283 ms

Floridee_Logo_Web.webp

Floridee_Logo_Web.webp

325 ms

haken.png

haken.png

326 ms

blumen105152.webp

blumen105152.webp

94 ms

jquery.min.js

jquery.min.js

379 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

377 ms

kontakt.js

kontakt.js

321 ms

config.js

config.js

371 ms

klaro.js

klaro.js

566 ms

bar_floridee-blumenversand-gmbh.js

bar_floridee-blumenversand-gmbh.js

150 ms

blumen105511.png

blumen105511.png

183 ms

blumen105139.png

blumen105139.png

285 ms

blumen105167.png

blumen105167.png

323 ms

blumen103028.png

blumen103028.png

322 ms

blumen103019.png

blumen103019.png

324 ms

blumen103017.png

blumen103017.png

321 ms

blumen102014.png

blumen102014.png

323 ms

blumen105508.png

blumen105508.png

369 ms

blumen107024.png

blumen107024.png

395 ms

blumen102015.png

blumen102015.png

396 ms

blumen102016.png

blumen102016.png

396 ms

blumen105152.webp

blumen105152.webp

471 ms

blumen105511.png

blumen105511.png

380 ms

HG_Spring.jpg

HG_Spring.jpg

273 ms

head_hg.webp

head_hg.webp

186 ms

Versandkostenfrei.png

Versandkostenfrei.png

187 ms

Holz2.jpg

Holz2.jpg

280 ms

blumen105139.png

blumen105139.png

471 ms

blumen103017.png

blumen103017.png

607 ms

blumen103028.png

blumen103028.png

436 ms

blumen105167.png

blumen105167.png

344 ms

blumen102014.png

blumen102014.png

526 ms

blumen103019.png

blumen103019.png

525 ms

raleway-v28-latin-700.woff

raleway-v28-latin-700.woff

438 ms

raleway-v28-latin-800.woff

raleway-v28-latin-800.woff

528 ms

raleway-v28-latin-900.woff

raleway-v28-latin-900.woff

534 ms

raleway-v28-latin-600.woff

raleway-v28-latin-600.woff

537 ms

raleway-v28-latin-500.woff

raleway-v28-latin-500.woff

619 ms

raleway-v28-latin-regular.woff

raleway-v28-latin-regular.woff

624 ms

raleway-v28-latin-300.woff

raleway-v28-latin-300.woff

625 ms

raleway-v28-latin-200.woff

raleway-v28-latin-200.woff

629 ms

raleway-v28-latin-100.woff

raleway-v28-latin-100.woff

630 ms

raleway-v28-latin-italic.woff

raleway-v28-latin-italic.woff

697 ms

raleway-v28-latin-500italic.woff

raleway-v28-latin-500italic.woff

718 ms

raleway-v28-latin-300italic.woff

raleway-v28-latin-300italic.woff

713 ms

raleway-v28-latin-200italic.woff

raleway-v28-latin-200italic.woff

718 ms

raleway-v28-latin-100italic.woff

raleway-v28-latin-100italic.woff

729 ms

raleway-v28-latin-600italic.woff

raleway-v28-latin-600italic.woff

724 ms

raleway-v28-latin-700italic.woff

raleway-v28-latin-700italic.woff

791 ms

raleway-v28-latin-800italic.woff

raleway-v28-latin-800italic.woff

807 ms

raleway-v28-latin-900italic.woff

raleway-v28-latin-900italic.woff

812 ms

blumen105508.png

blumen105508.png

775 ms

bootstrap-icons.css

bootstrap-icons.css

759 ms

blumen107024.png

blumen107024.png

794 ms

blumen102015.png

blumen102015.png

824 ms

blumen102016.png

blumen102016.png

837 ms

izmc5eazy1

izmc5eazy1

50 ms

clarity.js

clarity.js

6 ms

bootstrap-icons.woff

bootstrap-icons.woff

98 ms

provenexpert_logo_black.png

provenexpert_logo_black.png

92 ms

browserbar.css

browserbar.css

27 ms

bubble.png

bubble.png

27 ms

titilliumweb-regular-webfont.woff

titilliumweb-regular-webfont.woff

5 ms

titilliumweb-semibold-webfont.woff

titilliumweb-semibold-webfont.woff

15 ms

c.gif

c.gif

7 ms

Accessibility Review

floridee.de 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

floridee.de 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

floridee.de SEO score

93

Search Engine Optimization Advices

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

floridee.de

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