3.2 sec in total
187 ms
2.7 sec
359 ms
Visit fruity-line.nl now to see the best up-to-date Fruity Line content and also check out these interesting facts you probably never knew about fruity-line.nl
Fruity Line is a producer of premium fruit and vegetable juices and smoothies in Europe. Due to the unique cold-press technique remain the fruit and vegetable 'raw'.
Visit fruity-line.nlWe analyzed Fruity-line.nl page load time and found that the first response time was 187 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
fruity-line.nl performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value14.2 s
0/100
25%
Value7.7 s
25/100
10%
Value770 ms
38/100
30%
Value0.012
100/100
15%
Value14.1 s
9/100
10%
187 ms
9 ms
26 ms
85 ms
174 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 32% of them (25 requests) were addressed to the original Fruity-line.nl, 41% (32 requests) were made to Maps.googleapis.com and 9% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (748 ms) belongs to the original domain Fruity-line.nl.
Page size can be reduced by 826.6 kB (51%)
1.6 MB
810.0 kB
In fact, the total size of Fruity-line.nl main page is 1.6 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. 50% of websites need less resources to load. Javascripts take 822.7 kB which makes up the majority of the site volume.
Potential reduce by 31.5 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 31.5 kB or 85% of the original size.
Potential reduce by 26.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. Fruity Line images are well optimized though.
Potential reduce by 542.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 542.3 kB or 66% of the original size.
Potential reduce by 226.2 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. Fruity-line.nl needs all CSS files to be minified and compressed as it can save up to 226.2 kB or 83% of the original size.
Number of requests can be reduced by 34 (49%)
70
36
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fruity Line. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
187 ms
jquery-1.11.3.min.js
9 ms
css
26 ms
js
85 ms
styles.css
174 ms
reset.css
176 ms
global.css
188 ms
style.css
191 ms
conditionizr-4.3.0.min.js
185 ms
modernizr-2.7.1.min.js
185 ms
script.js
344 ms
jquery.js
460 ms
jquery-migrate.min.js
375 ms
jquery.form.min.js
373 ms
scripts.js
366 ms
wp-embed.min.js
369 ms
logo.png
682 ms
arrow_down.svg
538 ms
icon-marker.png
550 ms
icon-phone.png
549 ms
icon-mail.png
545 ms
KT3KS9Aol4WfR6Vas8kNcg.woff
6 ms
wkfQbvfT_02e2IWO3yYueQ.woff
7 ms
BVtM30trf7q_jfqYeHfjtA.woff
9 ms
axgz0-AvTFQ
99 ms
border-bottom-white_header.png
343 ms
search.svg
339 ms
oranges.jpg
748 ms
border-bottom-white.png
336 ms
border-top-white.png
329 ms
fruity_shape.png
388 ms
www-embed-player-vflfNyN_r.css
56 ms
www-embed-player.js
75 ms
base.js
135 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
34 ms
ad_status.js
37 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
27 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
29 ms
common.js
19 ms
map.js
47 ms
util.js
74 ms
marker.js
74 ms
onion.js
15 ms
openhand_8_8.cur
46 ms
ViewportInfoService.GetViewportInfo
43 ms
stats.js
25 ms
controls.js
45 ms
marker.png
175 ms
transparent.png
35 ms
css
59 ms
vt
57 ms
vt
30 ms
vt
32 ms
vt
33 ms
vt
52 ms
vt
64 ms
vt
68 ms
vt
66 ms
vt
64 ms
vt
84 ms
vt
81 ms
vt
77 ms
vt
94 ms
vt
104 ms
vt
108 ms
vt
102 ms
vt
110 ms
vt
111 ms
vt
126 ms
vt
126 ms
vt
124 ms
vt
149 ms
google4.png
14 ms
mapcnt6.png
20 ms
sv5.png
25 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
4 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
8 ms
AuthenticationService.Authenticate
124 ms
fruity-line.nl accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
fruity-line.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
fruity-line.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fruity-line.nl can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fruity-line.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.
fruity-line.nl
Open Graph data is detected on the main page of Fruity Line. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: