Tools & Wizards About Us
floragard.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

floragard.com

Floragard ▷ 100% Premium Blumenerden & Substrate

Page Load Speed

4.5 sec in total

First Response

495 ms

Resources Loaded

3 sec

Page Rendered

924 ms

floragard.com screenshot

About Website

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

Floragard für anspruchsvolle Pflanzarbeiten im Garten oder das passende Substrat für die Pflanzenproduktion ➤ Jetzt entdecken!

Visit floragard.com

Key Findings

We analyzed Floragard.com page load time and found that the first response time was 495 ms and then it took 4 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

floragard.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value1,240 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.517

15/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

www.floragard.de

495 ms

www.floragard.de

401 ms

de-de

327 ms

js

476 ms

css

777 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that all of those requests were addressed to Floragard.com and no external sources were called. The less responsive or slowest element that took the longest time to load (777 ms) relates to the external source Floragard.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 253.3 kB (18%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Floragard.com 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. 45% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 98.5 kB

  • Original 121.0 kB
  • After minification 121.0 kB
  • After compression 22.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 98.5 kB or 81% of the original size.

Image Optimization

-11%

Potential reduce by 143.0 kB

  • Original 1.3 MB
  • After minification 1.1 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. Obviously, Floragard needs image optimization as it can save up to 143.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-45%

Potential reduce by 11.8 kB

  • Original 26.3 kB
  • After minification 26.3 kB
  • After compression 14.4 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 11.8 kB or 45% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (21%)

Requests Now

24

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.floragard.de

www.floragard.de

495 ms

www.floragard.de

www.floragard.de

401 ms

de-de

de-de

327 ms

js

js

476 ms

css

css

777 ms

CookieBanner.js

CookieBanner.js

404 ms

gs.analytics2.js

gs.analytics2.js

406 ms

bottom

bottom

605 ms

jquery.signalR-2.2.0.js

jquery.signalR-2.2.0.js

483 ms

hubs

hubs

407 ms

de-DE.png

de-DE.png

108 ms

it-IT.png

it-IT.png

109 ms

en-GB.png

en-GB.png

111 ms

fr-FR.png

fr-FR.png

109 ms

es-ES.png

es-ES.png

108 ms

zh-CN.png

zh-CN.png

109 ms

1903x800px-Blumenerde-rechts-r1-1903x800-proportionalsmallest.webp

1903x800px-Blumenerde-rechts-r1-1903x800-proportionalsmallest.webp

198 ms

1903x800px-Basissubstrat-fuer-Chilipflanzen-r1-1903x800-proportionalsmallest.webp

1903x800px-Basissubstrat-fuer-Chilipflanzen-r1-1903x800-proportionalsmallest.webp

288 ms

1903x800px-Kompost-r1-1903x800-proportionalsmallest.webp

1903x800px-Kompost-r1-1903x800-proportionalsmallest.webp

380 ms

l002-Button-IVG-Mitgliedschaft-3-210505-r1-192x128-proportionalexact.webp

l002-Button-IVG-Mitgliedschaft-3-210505-r1-192x128-proportionalexact.webp

195 ms

rpp_logo_cirkels_lc_supporter_def-r2-192x128-proportionalexact.webp

rpp_logo_cirkels_lc_supporter_def-r2-192x128-proportionalexact.webp

197 ms

ErdenundSubstrate-r1-192x128-proportionalexact.webp

ErdenundSubstrate-r1-192x128-proportionalexact.webp

198 ms

New-logo-GME-r1-192x128-proportionalexact.webp

New-logo-GME-r1-192x128-proportionalexact.webp

295 ms

Hintergrund_Erde_1920px_neu.jpg

Hintergrund_Erde_1920px_neu.jpg

285 ms

Hintergrund_Holz_1920px.jpg

Hintergrund_Holz_1920px.jpg

669 ms

video-icon-small.png

video-icon-small.png

285 ms

MuliBold.ttf

MuliBold.ttf

368 ms

MuliRegular.ttf

MuliRegular.ttf

389 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

391 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

390 ms

Hintergrund_Erde_1920px_angeschnitten.jpg

Hintergrund_Erde_1920px_angeschnitten.jpg

621 ms

Kalam-Regular.ttf

Kalam-Regular.ttf

436 ms

Accessibility Review

floragard.com accessibility score

73

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

Buttons do not have an accessible name

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.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

floragard.com SEO score

90

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floragard.com 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 Floragard.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

floragard.com

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