3.6 sec in total
333 ms
3.1 sec
181 ms
Click here to check amazing Matthys content for Belgium. Otherwise, check out these important facts you probably never knew about matthys.net
Alle gereedschappen en producten voor uw restauraties.
Visit matthys.netWe analyzed Matthys.net page load time and found that the first response time was 333 ms and then it took 3.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.
matthys.net performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value9.8 s
0/100
25%
Value9.8 s
10/100
10%
Value1,610 ms
12/100
30%
Value0.003
100/100
15%
Value17.8 s
4/100
10%
333 ms
1061 ms
597 ms
92 ms
175 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 83% of them (43 requests) were addressed to the original Matthys.net, 4% (2 requests) were made to Seal.thawte.com and 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Matthys.net.
Page size can be reduced by 409.8 kB (54%)
762.3 kB
352.5 kB
In fact, the total size of Matthys.net main page is 762.3 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. 25% of websites need less resources to load. Javascripts take 390.9 kB which makes up the majority of the site volume.
Potential reduce by 41.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. This page needs HTML code to be minified as it can gain 9.7 kB, which is 20% 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 41.0 kB or 84% of the original size.
Potential reduce by 54.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. Obviously, Matthys needs image optimization as it can save up to 54.2 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 275.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 275.5 kB or 70% of the original size.
Potential reduce by 39.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. Matthys.net needs all CSS files to be minified and compressed as it can save up to 39.1 kB or 85% of the original size.
Number of requests can be reduced by 23 (47%)
49
26
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Matthys. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
matthys.net
333 ms
www.matthys.net
1061 ms
matthys-home
597 ms
matthys.css
92 ms
multizoom.css
175 ms
jquery-1.8.3.min.js
496 ms
jquery.numeric.js
326 ms
jquery.validate.min.js
326 ms
jquery.validate.unobtrusive.min.js
244 ms
jquery.unobtrusive-ajax.min.js
244 ms
easySlider1.7v2.js
259 ms
functions.js
333 ms
multizoom.js
421 ms
jquery.tinycarousel.min.js
338 ms
jquery-ui.js
44 ms
getthawteseal
113 ms
body.jpg
91 ms
BAN_Reims2016_NL.jpg
176 ms
8585-TJ-5-QL_01_635683414796289521.jpg
101 ms
12023_635754219795716861.jpg
97 ms
960%20b_635182044607356251.jpg
100 ms
30001_matt_03_635696348387858631.jpg
105 ms
8575-21_NEW_635792161752341882.jpg
176 ms
TM-180b_635193441779235704.jpg
184 ms
7306-00_635185712024274115.jpg
185 ms
G3300_PaintRestoKit_635364386309301344.jpg
190 ms
gtm.js
116 ms
header_nl.jpg
427 ms
key.png
253 ms
topmenu-hover.jpg
254 ms
topmenu-bullet.png
260 ms
languages-bullet.png
260 ms
search.png
270 ms
cart.jpg
337 ms
cart.png
344 ms
category-closed.jpg
341 ms
catalogus.jpg
420 ms
catalogus-field.jpg
352 ms
shoplink_nl.jpg
418 ms
getthawteseal
89 ms
dot_clear.gif
91 ms
product.jpg
415 ms
order-new-right.png
413 ms
order-new-left.png
425 ms
address_nl.jpg
500 ms
footermenu-bullet.png
490 ms
footer_right_nl.jpg
495 ms
ga.js
101 ms
hotjar-31118.js
218 ms
__utm.gif
12 ms
modules-1f5c71aea63f8df71401422ed80fbe5f.js
31 ms
matthys_print.css
83 ms
matthys.net 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
matthys.net 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
matthys.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Matthys.net 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 Matthys.net 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.
matthys.net
Open Graph description is not detected on the main page of Matthys. 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: