Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

Page Load Speed

9 sec in total

First Response

832 ms

Resources Loaded

7 sec

Page Rendered

1.2 sec

floraa.nl screenshot

About Website

Welcome to floraa.nl homepage info - get ready to check Floraa best content for Netherlands right away, or after learning these important things about floraa.nl

Floraa is een health en food blog. Laat je inspireren over gezond eten & leven, recepten, mindfulness en work-outs. Floor is voedingsdeskundige in Den Bosch

Visit floraa.nl

Key Findings

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

floraa.nl performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value16.5 s

0/100

10%

TBT (Total Blocking Time)

Value10,610 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

www.floraa.nl

832 ms

language-selector.css

166 ms

style-frontend.css

189 ms

font-awesome.min.css

189 ms

sky-forms.css

191 ms

Our browser made a total of 218 requests to load all elements on the main page. We found that 55% of them (120 requests) were addressed to the original Floraa.nl, 9% (20 requests) were made to Static.xx.fbcdn.net and 9% (20 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source S3.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (29%)

Content Size

6.5 MB

After Optimization

4.6 MB

In fact, the total size of Floraa.nl main page is 6.5 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. Only a small number of websites need less resources to load. Images take 4.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 236.8 kB

  • Original 285.8 kB
  • After minification 270.3 kB
  • After compression 49.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. 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 236.8 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 167.7 kB

  • Original 4.3 MB
  • After minification 4.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. Floraa images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 707.1 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 362.3 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 707.1 kB or 66% of the original size.

CSS Optimization

-87%

Potential reduce by 733.4 kB

  • Original 841.2 kB
  • After minification 672.0 kB
  • After compression 107.8 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. Floraa.nl needs all CSS files to be minified and compressed as it can save up to 733.4 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 84 (40%)

Requests Now

208

After Optimization

124

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

Accessibility Review

floraa.nl accessibility score

94

Accessibility Issues

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

Links do not have a discernible name

Best Practices

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

floraa.nl SEO score

99

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floraa.nl can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Dutch. Our system also found out that Floraa.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

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