714 ms in total
221 ms
375 ms
118 ms
Click here to check amazing Dutchfresh content. Otherwise, check out these important facts you probably never knew about dutchfresh.com
Visit dutchfresh.comWe analyzed Dutchfresh.com page load time and found that the first response time was 221 ms and then it took 493 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.
dutchfresh.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value5.7 s
16/100
25%
Value7.4 s
28/100
10%
Value530 ms
55/100
30%
Value0.031
100/100
15%
Value7.9 s
43/100
10%
221 ms
66 ms
153 ms
8 ms
13 ms
Our browser made a total of 5 requests to load all elements on the main page. We found that 60% of them (3 requests) were addressed to the original Dutchfresh.com, 40% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (221 ms) belongs to the original domain Dutchfresh.com.
Page size can be reduced by 646 B (1%)
65.5 kB
64.9 kB
In fact, the total size of Dutchfresh.com main page is 65.5 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. Only 5% of websites need less resources to load. Images take 47.0 kB which makes up the majority of the site volume.
Potential reduce by 489 B
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 489 B or 43% of the original size.
Potential reduce by 20 B
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. Dutchfresh images are well optimized though.
Potential reduce by 34 B
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.
Potential reduce by 103 B
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. Dutchfresh.com needs all CSS files to be minified and compressed as it can save up to 103 B or 50% of the original size.
We found no issues to fix!
4
4
The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dutchfresh. According to our analytics all requests are already optimized.
dutchfresh.com
221 ms
dutchfresh.css
66 ms
logoDutchFresh.jpg
153 ms
ga.js
8 ms
__utm.gif
13 ms
dutchfresh.com 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
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
dutchfresh.com 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
Browser errors were logged to the console
dutchfresh.com 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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dutchfresh.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Dutchfresh.com 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.
dutchfresh.com
Open Graph description is not detected on the main page of Dutchfresh. 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: