Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

frisbee.nl

app- en webspecialist in Zeeland met 20+ jaar ervaring | FrisBEE BV

Page Load Speed

5.8 sec in total

First Response

353 ms

Resources Loaded

5.1 sec

Page Rendered

352 ms

About Website

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

FrisBEE uit Vlissingen is gespecialiseerd in bedrijfsapps, technisch uitdagende websites en complexe webapplicaties.

Visit frisbee.nl

Key Findings

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

Performance Metrics

frisbee.nl performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value9.0 s

15/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

frisbee.nl

353 ms

www.frisbee.nl

819 ms

main.php

165 ms

cookiewarning.js

247 ms

jquery.tools.min.js

548 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 48% of them (51 requests) were addressed to the original Frisbee.nl, 12% (13 requests) were made to Static.xx.fbcdn.net and 7% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Frisbee.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 798.6 kB (36%)

Content Size

2.2 MB

After Optimization

1.4 MB

In fact, the total size of Frisbee.nl main page is 2.2 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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 70.1 kB

  • Original 94.7 kB
  • After minification 91.3 kB
  • After compression 24.6 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 70.1 kB or 74% of the original size.

Image Optimization

-7%

Potential reduce by 82.2 kB

  • Original 1.2 MB
  • After minification 1.2 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. FrisBEE images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 626.5 kB

  • Original 885.2 kB
  • After minification 795.2 kB
  • After compression 258.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 626.5 kB or 71% of the original size.

CSS Optimization

-82%

Potential reduce by 19.8 kB

  • Original 24.2 kB
  • After minification 18.4 kB
  • After compression 4.4 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. Frisbee.nl needs all CSS files to be minified and compressed as it can save up to 19.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (61%)

Requests Now

104

After Optimization

41

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

Accessibility Review

frisbee.nl accessibility score

64

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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.

Best Practices

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

SEO Factors

frisbee.nl SEO score

98

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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frisbee.nl 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 Frisbee.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 description is not detected on the main page of FrisBEE. 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: