5.6 sec in total
410 ms
4.9 sec
249 ms
Click here to check amazing Martor content. Otherwise, check out these important facts you probably never knew about martor.de
Hochwertige Sicherheitsmesser, Cuttermesser und Klingen für mehr Arbeitssicherheit. Weitere Schneidwerkzeuge wie Schaber, Entgrater etc. von MARTOR.
Visit martor.deWe analyzed Martor.de page load time and found that the first response time was 410 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
martor.de performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value13.0 s
0/100
25%
Value10.2 s
8/100
10%
Value2,110 ms
7/100
30%
Value0.739
6/100
15%
Value11.0 s
21/100
10%
410 ms
577 ms
1379 ms
115 ms
830 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Martor.de, 95% (74 requests) were made to Martor.com and 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Martor.com.
Page size can be reduced by 210.4 kB (9%)
2.2 MB
2.0 MB
In fact, the total size of Martor.de main page is 2.2 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. 40% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 67.2 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 23.0 kB, which is 29% 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 67.2 kB or 85% of the original size.
Potential reduce by 21.4 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. Martor images are well optimized though.
Potential reduce by 9.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 9.6 kB or 32% of the original size.
Potential reduce by 112.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. Martor.de needs all CSS files to be minified and compressed as it can save up to 112.2 kB or 83% of the original size.
Number of requests can be reduced by 25 (34%)
73
48
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Martor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for CSS and as a result speed up the page load time.
martor.de
410 ms
www.martor.com
577 ms
en.html
1379 ms
merged-cc7a23235c18f02ed5ff520484657744-9f5d4b17e4b73e139710a72aefeb19b5.css
115 ms
merged-d4d2a59b213c9f27f62f44836c3775fd-2eeb2bdd85c830b2e6bc0a2f85886941.js
830 ms
home.css
290 ms
cb_indexedsearch_autocomplete.js
298 ms
cb_indexedsearch_autocomplete.css
298 ms
reset.css
185 ms
default.css
185 ms
grid.css
274 ms
jquery.ntg-infinite-carousel.css
283 ms
threesixty.css
281 ms
jquery.cookiebar.css
283 ms
styles.css
284 ms
cb_indexedsearch_autocomplete.css
370 ms
indexed_search.css
380 ms
mvproducts.css
383 ms
pmkshadowbox.css
381 ms
tt_news.css
383 ms
sr_freecap.css
467 ms
felogin.css
479 ms
fefilelist.css
481 ms
DurotypeFlexoRegular.woff
203 ms
ga.js
111 ms
logo.png
107 ms
slogan.png
107 ms
csm_icon_product-filter_01eae934fe.png
105 ms
csm_icon_new-products_a80e66add1.png
107 ms
nav-specials_icon-leaflet.png
108 ms
nav-specials_icon-compare-list.png
203 ms
magnifying-glass.png
205 ms
middle-shadow.png
204 ms
csm_151103_HP_Teaser_S625_G_1920_85f5f648c5.jpg
1180 ms
csm_151116_Guerteltaschen_v3_01_9816790c77.jpg
787 ms
csm_151106_GDA_1920v4_07_d04fea91ab.jpg
436 ms
csm_Slider1_2014_1280x460_02_c6dd79a8bf.jpg
1060 ms
csm_Slider2_2014_1250x550_02_9e8847155f.jpg
1180 ms
csm_151027_Teaser-SHMK2016_v2_fd95d4be2a.jpg
280 ms
csm_Produktfilter_280x195_0f096e7d2c.jpg
380 ms
csm_MARTOR-NSMHK_336b923bc4.jpg
480 ms
skin.png
518 ms
input-checkbox.png
577 ms
csm_625001_PA2_MARTOR_5ed6eb5945.png
620 ms
csm_625001_PA2_MARTOR_bae05599fa.png
677 ms
csm_380001_PA3_lang_MARTOR_6a6589e5a7.png
722 ms
csm_380001_PA3_lang_MARTOR_ce0486defc.png
775 ms
csm_590001_PA2_MARTOR_67bf2e42cb.png
824 ms
csm_590001_PA2_MARTOR_9640769614.png
863 ms
csm_564001_PA1_MARTOR_097317679d.png
874 ms
csm_564001_PA1_MARTOR_fec54e77e9.png
925 ms
csm_125001_PA2_MARTOR_9c65ac9054.png
962 ms
csm_125001_PA2_MARTOR_f139896f5d.png
973 ms
csm_350001_PA2_MARTOR_eb8568d736.png
1027 ms
csm_350001_PA2_MARTOR_700a019f41.png
1111 ms
csm_122001_PA2_MARTOR_a3a22dce25.png
1112 ms
csm_122001_PA2_MARTOR_ec4792042b.png
1128 ms
csm_116001_PA2_MARTOR_a96042ed7f.png
1133 ms
csm_116001_PA2_MARTOR_b4a1f90abf.png
1161 ms
csm_121001_PA2_MARTOR_3ee2567071.png
1173 ms
skin.css
1152 ms
en.html
1268 ms
csm_121001_PA2_MARTOR_eada6d4d1a.png
1174 ms
csm_437_PA2_MARTOR_c5507bd9c5.png
1174 ms
csm_437_PA2_MARTOR_54da6f0cfc.png
1179 ms
__utm.gif
14 ms
collect
58 ms
csm_123001_PA2_MARTOR_7cfd28a338.png
1098 ms
csm_123001_PA2_MARTOR_35bff11584.png
1160 ms
WA_Teaser_280x190.jpg
1176 ms
a-more.png
1177 ms
to-top.png
1084 ms
footer_nav-marginal_separator.png
995 ms
toggle_sitemap_icon-toggle.png
1028 ms
header_nav-marginal_icon-toggle.png
968 ms
transparent.png
344 ms
skin.png
221 ms
print-c892e9b7a6356cef10c4d44b1d74d9a8.css
104 ms
martor.de 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
[id] attributes on active, focusable elements are not unique
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.
martor.de 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
martor.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Martor.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Martor.de 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.
martor.de
Open Graph description is not detected on the main page of Martor. 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: