10.8 sec in total
3 sec
7.1 sec
710 ms
Visit fruitboomkwekerijmorren.nl now to see the best up-to-date Fruitboomkwekerij Morren content and also check out these interesting facts you probably never knew about fruitboomkwekerijmorren.nl
Welkom op de website van Fruitboomkwekerij Morren in Elburg. Al ruim 30 jaar telen wij kwalitatief hoogwaardige vruchtbomen voor de fruitteeltsector in binnen- en buitenland. Wij zijn de specialist in...
Visit fruitboomkwekerijmorren.nlWe analyzed Fruitboomkwekerijmorren.nl page load time and found that the first response time was 3 sec and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fruitboomkwekerijmorren.nl performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value23.2 s
0/100
25%
Value12.8 s
2/100
10%
Value290 ms
80/100
30%
Value0.031
100/100
15%
Value10.8 s
22/100
10%
3020 ms
65 ms
175 ms
268 ms
272 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 87% of them (78 requests) were addressed to the original Fruitboomkwekerijmorren.nl, 8% (7 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Fruitboomkwekerijmorren.nl.
Page size can be reduced by 467.4 kB (8%)
6.0 MB
5.6 MB
In fact, the total size of Fruitboomkwekerijmorren.nl main page is 6.0 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 5.2 MB which makes up the majority of the site volume.
Potential reduce by 279.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 279.0 kB or 88% of the original size.
Potential reduce by 32.9 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. Fruitboomkwekerij Morren images are well optimized though.
Potential reduce by 140.5 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 140.5 kB or 39% of the original size.
Potential reduce by 14.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. Fruitboomkwekerijmorren.nl has all CSS files already compressed.
Number of requests can be reduced by 40 (58%)
69
29
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fruitboomkwekerij Morren. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
fruitboomkwekerijmorren.nl
3020 ms
js
65 ms
sbi-styles.min.css
175 ms
style.min.css
268 ms
styles.css
272 ms
style.min.css
282 ms
style.min.css
284 ms
cms-navigation-base.css
284 ms
cms-navigation.css
285 ms
theme.css
460 ms
style.css
274 ms
css
48 ms
elementor-icons.min.css
291 ms
custom-frontend-legacy.min.css
294 ms
custom-frontend-lite.min.css
392 ms
swiper.min.css
299 ms
post-7.css
362 ms
post-158.css
390 ms
css
60 ms
fontawesome.min.css
486 ms
solid.min.css
396 ms
jquery.min.js
544 ms
jquery-migrate.min.js
457 ms
language-cookie.js
480 ms
frontend-gtag.min.js
485 ms
animations.min.css
493 ms
jquery.cookie.min.js
647 ms
owl.carousel.min.js
647 ms
imagesloaded.min.js
648 ms
isotope.min.js
648 ms
theme.js
649 ms
slick.min.js
652 ms
jquery.fancybox.min.js
651 ms
content-slider-widget.js
668 ms
webpack.runtime.min.js
684 ms
frontend-modules.min.js
717 ms
waypoints.min.js
717 ms
core.min.js
741 ms
frontend.min.js
742 ms
underscore.min.js
734 ms
wp-util.min.js
698 ms
frontend.min.js
634 ms
Logomorren_boom-M-1.png
228 ms
logoMORREN-web275x90.png
251 ms
appelboomkwekerij-slider1200x700.jpg
605 ms
moerbed-m9.jpg
653 ms
banner-overlay.png
387 ms
kwekerij-appelbomen-topview-bg1920x705.jpg
799 ms
Apple-tree-nursery-scaled.jpeg
798 ms
widget-title-icon.png
339 ms
peren.jpg
607 ms
rootstocks-website.jpg
860 ms
Layer-3-copy.png
693 ms
kwekerij-appelboom-1.png
785 ms
Logomorren-boom-M-vierkant-overlay176x189.png
746 ms
Moerbed-closeup-q9z4p1gow66ojm276nvewagq1lkmstddlc3vs2rsc8.jpg
787 ms
Logomorren-boom-M-trans500x536-1.png
842 ms
kanzi-logo120x80.png
874 ms
gala-dark-ann-logo204x80.png
875 ms
xenia-logo199x80.png
892 ms
kiku-logo201x80.png
893 ms
schnico-logo217x80.png
871 ms
apples-in-box.jpg
989 ms
logoMORREN-web-wit275x90-1.png
898 ms
nl.svg
900 ms
en.svg
919 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFN_C-bw.ttf
24 ms
Manrope-Medium.ttf
925 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FN_C-bw.ttf
36 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFN_C-bw.ttf
58 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59FN_C-bw.ttf
69 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE9_C-bw.ttf
71 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE9_C-bw.ttf
69 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59E9_C-bw.ttf
69 ms
Manrope-Regular.ttf
966 ms
Manrope-Light.ttf
987 ms
embed
320 ms
Manrope-ExtraLight.ttf
983 ms
Manrope-SemiBold.ttf
983 ms
Manrope-Bold.ttf
962 ms
Manrope-ExtraBold.ttf
1000 ms
Herbarium.otf
1067 ms
fa-solid-900.woff
1057 ms
fa-solid-900.woff
1033 ms
fa-regular-400.woff
1080 ms
fa-brands-400.woff
972 ms
fontello.woff
1063 ms
de.svg
1054 ms
icon-wpml-info-white.svg
967 ms
js
54 ms
fruitboomkwekerijmorren.nl accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
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.
fruitboomkwekerijmorren.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
fruitboomkwekerijmorren.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
EN
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fruitboomkwekerijmorren.nl can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Dutch language. Our system also found out that Fruitboomkwekerijmorren.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.
fruitboomkwekerijmorren.nl
Open Graph data is detected on the main page of Fruitboomkwekerij Morren. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: