3.4 sec in total
1.1 sec
2 sec
248 ms
Visit tomassen.com now to see the best up-to-date Tomassen content and also check out these interesting facts you probably never knew about tomassen.com
Tomassen Duck-To B.V. produceert verse bevroren pekingeend en eendendelen. Meer weten over onze kwaliteitseenden? Bezoek dan onze website.
Visit tomassen.comWe analyzed Tomassen.com page load time and found that the first response time was 1.1 sec and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
tomassen.com performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value14.6 s
0/100
25%
Value12.6 s
3/100
10%
Value250 ms
84/100
30%
Value0.016
100/100
15%
Value14.3 s
9/100
10%
1089 ms
262 ms
272 ms
31 ms
463 ms
Our browser made a total of 30 requests to load all elements on the main page. We found that 90% of them (27 requests) were addressed to the original Tomassen.com, 7% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Tomassen.com.
Page size can be reduced by 156.6 kB (18%)
872.7 kB
716.1 kB
In fact, the total size of Tomassen.com main page is 872.7 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. 20% of websites need less resources to load. Images take 649.5 kB which makes up the majority of the site volume.
Potential reduce by 10.8 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. This page needs HTML code to be minified as it can gain 2.6 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 10.8 kB or 72% of the original size.
Potential reduce by 10.1 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. Tomassen images are well optimized though.
Potential reduce by 109.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 109.6 kB or 62% of the original size.
Potential reduce by 26.1 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. Tomassen.com needs all CSS files to be minified and compressed as it can save up to 26.1 kB or 84% of the original size.
Number of requests can be reduced by 15 (52%)
29
14
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tomassen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
tomassen.com
1089 ms
flexslider.css
262 ms
colorbox.css
272 ms
jquery.min.js
31 ms
jquery.colorbox.js
463 ms
jquery.responsivenav.js
186 ms
responsivenav.css
365 ms
jquery.flexslider.js
432 ms
style.css
374 ms
WebResource.axd
392 ms
background.png
94 ms
nl.png
88 ms
en.png
100 ms
de.png
95 ms
es.png
88 ms
zh-CN.png
90 ms
logo.png
275 ms
btn_home.png
172 ms
foto-1.jpg
616 ms
foto-2.jpg
440 ms
crop_duck%20head%20off.jpg
192 ms
crop_BR%2043%20008.jpg
199 ms
crop_Duck%20legs%20in%20sweet%20Chili%20sauce.jpg
263 ms
crop_HQC-logo.jpg
287 ms
bg_button.png
289 ms
ga.js
18 ms
overlay.png
318 ms
border.png
330 ms
controls.png
353 ms
__utm.gif
11 ms
tomassen.com 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.
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.
tomassen.com 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
Page has valid source maps
tomassen.com 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
NL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tomassen.com can be misinterpreted by Google and other search engines. Our service has detected that Dutch 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 Tomassen.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.
tomassen.com
Open Graph description is not detected on the main page of Tomassen. 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: