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

  • 93

    SEO

    Google-friendlier than
    83% of websites

flinndal.fr

Flinndal, dé Webshop voor Vitaminen

Page Load Speed

2.5 sec in total

First Response

121 ms

Resources Loaded

1.3 sec

Page Rendered

1.1 sec

flinndal.fr screenshot

About Website

Visit flinndal.fr now to see the best up-to-date Flinndal content and also check out these interesting facts you probably never knew about flinndal.fr

De beste vitaminen, multivitaminen en omega 3 vetzuren bestel je bij Flinndal. Voor 23:00 besteld? De volgende werkdag geleverd in je brievenbus.

Visit flinndal.fr

Key Findings

We analyzed Flinndal.fr page load time and found that the first response time was 121 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

flinndal.fr performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value6,490 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.14

79/100

15%

TTI (Time to Interactive)

Value33.2 s

0/100

10%

Network Requests Diagram

www.flinndal.nl

121 ms

loader.js

61 ms

webfont.js

60 ms

gtm.js

151 ms

clerk.js

744 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Flinndal.fr, 10% (3 requests) were made to Cdnjs.cloudflare.com and 7% (2 requests) were made to App.usercentrics.eu. The less responsive or slowest element that took the longest time to load (744 ms) relates to the external source Cdn.clerk.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 247.5 kB (35%)

Content Size

712.0 kB

After Optimization

464.6 kB

In fact, the total size of Flinndal.fr main page is 712.0 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. 45% of websites need less resources to load. Javascripts take 413.0 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 209.0 kB

  • Original 256.2 kB
  • After minification 255.0 kB
  • After compression 47.1 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 209.0 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 4.5 kB
  • After minification 4.5 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. Flinndal images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 26.8 kB

  • Original 413.0 kB
  • After minification 413.0 kB
  • After compression 386.2 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

-30%

Potential reduce by 11.6 kB

  • Original 38.4 kB
  • After minification 38.4 kB
  • After compression 26.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. Flinndal.fr needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 30% of the original size.

Requests Breakdown

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

Requests Now

25

After Optimization

15

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

Accessibility Review

flinndal.fr accessibility score

86

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

flinndal.fr 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

flinndal.fr SEO score

93

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

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

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