5.8 sec in total
353 ms
5.1 sec
352 ms
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.nlWe 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.
frisbee.nl performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value13.6 s
0/100
25%
Value9.0 s
15/100
10%
Value80 ms
99/100
30%
Value0.017
100/100
15%
Value10.3 s
25/100
10%
353 ms
819 ms
165 ms
247 ms
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 size can be reduced by 769.5 kB (35%)
2.2 MB
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.
Potential reduce by 70.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 70.1 kB or 74% of the original size.
Potential reduce by 82.2 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. FrisBEE images are well optimized though.
Potential reduce by 597.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 597.4 kB or 70% of the original size.
Potential reduce by 19.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. 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.
Number of requests can be reduced by 63 (61%)
104
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.
frisbee.nl
353 ms
www.frisbee.nl
819 ms
main.php
165 ms
cookiewarning.js
247 ms
jquery.tools.min.js
548 ms
prototype.js
747 ms
scriptaculous.js
306 ms
lightview.js
487 ms
algemeen.js
309 ms
lightview.css
327 ms
stylesheet.css
390 ms
jquery.custom_radio_checkbox.js
395 ms
default.css
409 ms
nivo-slider.css
471 ms
jquery.nivo.slider.2.5.1.js
563 ms
widget.js
126 ms
addthis_widget.js
27 ms
1024x1024ss-80.png
251 ms
bg_home.png
402 ms
frisbee_portfolio_2131_0b_icarus_visual_333.jpg
709 ms
frisbee_portfolio_1a5444b3da64ea0672c_0b_vanjole_visual.jpg
511 ms
frisbee_portfolio_9a4f3818a50d46b8cfd_0b_codexgroep-visual.jpg
456 ms
frisbee_portfolio_b97d3bbfa934ac0249d_0b_visual_heemkundigekringwalcheren.jpg
879 ms
frisbee_portfolio_2136_0b_visual_znf2015_2.jpg
1102 ms
snappic_icon.png
541 ms
who_icon.jpg
580 ms
home_twitter.png
583 ms
home_facebook.png
622 ms
footer-wme.png
670 ms
footer-frisbee-grijs.png
672 ms
builder.js
197 ms
effects.js
252 ms
dragdrop.js
255 ms
controls.js
279 ms
slider.js
281 ms
sound.js
339 ms
logo.png
106 ms
sdk.js
474 ms
footer.png
98 ms
ga.js
58 ms
300lo.json
163 ms
all.js&version=v2.0
733 ms
widgets.js
127 ms
plusone.js
155 ms
prev.png
127 ms
topclose.png
125 ms
close_large.png
127 ms
close_small.png
124 ms
loading.gif
152 ms
inner_slideshow_stop.png
172 ms
inner_prev.png
177 ms
inner_next.png
176 ms
controller_prev.png
199 ms
controller_slideshow_stop.png
199 ms
sh.8e5f85691f9aaa082472a194.html
62 ms
linkedin.html
117 ms
__utm.gif
80 ms
share
68 ms
sprite_connect_v12.png
33 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
25 ms
cb=gapi.loaded_0
24 ms
cb=gapi.loaded_1
48 ms
fastbutton
112 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.nl.html
30 ms
controller_next.png
88 ms
postmessageRelay
60 ms
controller_slideshow_play.png
98 ms
controller_close.png
94 ms
cb=gapi.loaded_0
19 ms
cb=gapi.loaded_1
20 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
41 ms
3193398744-postmessagerelay.js
35 ms
rpc:shindig_random.js
44 ms
cb=gapi.loaded_0
3 ms
jot
97 ms
sprite_connect_v12.png
26 ms
169 ms
167 ms
xd_arbiter.php
431 ms
loading.gif
84 ms
ping
98 ms
arrows.png
90 ms
bullets.png
85 ms
page.php
282 ms
share_button.php
172 ms
like.php
173 ms
qeKvIRsJabD.js
490 ms
qeKvIRsJabD.js
692 ms
LVx-xkvaJ0b.png
680 ms
Ezryo55Cca5.css
652 ms
q68gy-v_YMF.js
782 ms
YvxwM8R7ol8.js
800 ms
ihptErjAmMX.js
717 ms
10151338_697331636979460_8342759335071932571_n.jpg
350 ms
1470399_628104853902139_2115275355_n.png
476 ms
12670917_1513193755654352_1760147491270583379_n.jpg
544 ms
1176198_460597744047660_480484141_n.jpg
624 ms
10288710_806764599341491_201642972477177742_n.jpg
753 ms
12650875_901666946616659_8693842728574740919_n.jpg
592 ms
10580202_720367168001001_3178716858881812113_n.jpg
582 ms
11700824_865598303505792_2932156338992378280_n.jpg
579 ms
wL6VQj7Ab77.png
71 ms
s7jcwEQH7Sx.png
70 ms
R9a_DtVRZgv.js
69 ms
cUDgRFxaoIk.js
70 ms
0JBr1QHp8Gi.js
70 ms
kDOzhTr2W91.js
70 ms
frisbee.nl accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
frisbee.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
frisbee.nl SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
NL
NL
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.
frisbee.nl
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: