Tools & Wizards About Us
floraxchange.nl screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

floraxchange.nl

Floriday platform voor kwekers en kopers in de sierteeltsector. - Floriday

Page Load Speed

3.7 sec in total

First Response

1.1 sec

Resources Loaded

2.5 sec

Page Rendered

75 ms

floraxchange.nl screenshot

About Website

Visit floraxchange.nl now to see the best up-to-date Floraxchange content for Turkey and also check out these interesting facts you probably never knew about floraxchange.nl

Floriday is hét platform voor kwekers en kopers in de sierteeltsector. Ervaar het platform nu zelf.

Visit floraxchange.nl

Key Findings

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

Performance Metrics

floraxchange.nl performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value27.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value28.1 s

0/100

25%

SI (Speed Index)

Value55.7 s

0/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value31.0 s

0/100

10%

Network Requests Diagram

floraxchange.nl

1114 ms

jquery.min.js

30 ms

bootstrap.min.js

45 ms

font-awesome.min.css

56 ms

floraxchange-index.min.css

187 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 48% of them (11 requests) were addressed to the original Floraxchange.nl, 13% (3 requests) were made to Maxcdn.bootstrapcdn.com and 13% (3 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Floraxchange.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.3 kB (24%)

Content Size

124.2 kB

After Optimization

93.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Floraxchange.nl main page is 124.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. CSS take 59.7 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 7.8 kB

  • Original 10.9 kB
  • After minification 9.1 kB
  • After compression 3.0 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 1.8 kB, which is 16% 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 7.8 kB or 72% of the original size.

Image Optimization

-17%

Potential reduce by 1.3 kB

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

JavaScript Optimization

-12%

Potential reduce by 5.4 kB

  • Original 46.0 kB
  • After minification 46.0 kB
  • After compression 40.6 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 5.4 kB or 12% of the original size.

CSS Optimization

-26%

Potential reduce by 15.8 kB

  • Original 59.7 kB
  • After minification 59.7 kB
  • After compression 43.9 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. Floraxchange.nl needs all CSS files to be minified and compressed as it can save up to 15.8 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (65%)

Requests Now

17

After Optimization

6

  • Images
  • JavaScript
  • CSS

The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floraxchange. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

floraxchange.nl

floraxchange.nl

1114 ms

jquery.min.js

jquery.min.js

30 ms

bootstrap.min.js

bootstrap.min.js

45 ms

font-awesome.min.css

font-awesome.min.css

56 ms

floraxchange-index.min.css

floraxchange-index.min.css

187 ms

basis

basis

367 ms

jquery.flip.js

jquery.flip.js

329 ms

floraxchange.js

floraxchange.js

339 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

340 ms

jquery.cluetip.js

jquery.cluetip.js

357 ms

js

js

43 ms

jquery.cluetip.css

jquery.cluetip.css

342 ms

tve5qas.css

tve5qas.css

87 ms

p.css

p.css

36 ms

logo-floraxchange-medium.png

logo-floraxchange-medium.png

92 ms

floriday-logo-green-white-horizontal.png

floriday-logo-green-white-horizontal.png

92 ms

loader.gif

loader.gif

571 ms

wait.gif

wait.gif

85 ms

d

d

4 ms

d

d

8 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

14 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

22 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

27 ms

Accessibility Review

floraxchange.nl accessibility score

86

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

floraxchange.nl best practices score

83

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

SEO Factors

floraxchange.nl SEO score

85

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

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

floraxchange.nl

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