16.9 sec in total
6.3 sec
10.3 sec
266 ms
Welcome to marzek.at homepage info - get ready to check Marzek best content right away, or after learning these important things about marzek.at
Marzek Etiketten, der Spezialist für Etiketten und Faltschachteln in Mittel- und Osteuropa
Visit marzek.atWe analyzed Marzek.at page load time and found that the first response time was 6.3 sec and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
marzek.at performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value9.3 s
1/100
25%
Value6.4 s
41/100
10%
Value200 ms
90/100
30%
Value0
100/100
15%
Value6.9 s
54/100
10%
6333 ms
144 ms
216 ms
218 ms
218 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 80% of them (73 requests) were addressed to the original Marzek.at, 12% (11 requests) were made to Static.xx.fbcdn.net and 3% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (6.3 sec) belongs to the original domain Marzek.at.
Page size can be reduced by 279.7 kB (9%)
3.3 MB
3.0 MB
In fact, the total size of Marzek.at main page is 3.3 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 3.0 MB which makes up the majority of the site volume.
Potential reduce by 33.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. 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 33.0 kB or 79% of the original size.
Potential reduce by 27.8 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. Marzek images are well optimized though.
Potential reduce by 169.9 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 169.9 kB or 77% of the original size.
Potential reduce by 48.9 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. Marzek.at needs all CSS files to be minified and compressed as it can save up to 48.9 kB or 82% of the original size.
Number of requests can be reduced by 41 (46%)
89
48
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Marzek. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
www.marzek.at
6333 ms
stylesheet_5d370599a3.css
144 ms
reset.css
216 ms
layout.css
218 ms
global.css
218 ms
text-formatting.css
229 ms
nav.css
231 ms
content-elemente.css
250 ms
forms.css
323 ms
module.css
323 ms
browser-fixes.css
326 ms
vendor-prefixes.css
341 ms
relative-width.css
355 ms
jquery-1.4.2.min.js
543 ms
jquery.easyListSplitter.js
430 ms
jquery.opendo-sitemap.js
431 ms
jquery.i18n.js
454 ms
jquery.biggerlink.js
456 ms
locallang.js
459 ms
jquery.jcarousel.js
537 ms
jquery.ui.core.js
538 ms
jquery.ui.widget.js
568 ms
ui.ariaLightbox.js
570 ms
jquery.cj-object-scaler.js
559 ms
master.js
635 ms
jquery.autocomplete.js
637 ms
jquery.autocomplete.css
636 ms
jquery.autocomplete.js
674 ms
body.gif
125 ms
logo_marzek-etiketten.gif
166 ms
icons-sprites.gif
149 ms
arrow-sprites.gif
123 ms
i_d7c58d3d55.jpg
151 ms
i_5738a8a569.jpg
156 ms
i_75c7a69cf1.jpg
222 ms
i_7d0b9534d8.jpg
223 ms
i_f5b8377a3d.jpg
272 ms
S_2cfc8e4659.png
266 ms
S_25e614a546.jpg
271 ms
S_28ddbc0a25.jpg
281 ms
S_04e2e4f443.jpg
350 ms
S_2625d3494c.jpg
348 ms
S_feade228dd.jpg
372 ms
S_79e2ae4e1c.jpg
384 ms
S_a75a10df44.jpg
382 ms
d_7cb67b8b83.jpg
404 ms
S_aacbe0dea3.jpg
440 ms
S_290ce9c43b.jpg
442 ms
S_15e8454ec7.jpg
479 ms
S_ade3395046.jpg
496 ms
S_c5cbaffaa7.jpg
497 ms
2_2dcb886673.jpg
521 ms
S_90ea43e8d8.jpg
555 ms
M_7f52eded0a.jpg
556 ms
w_a020c83309.jpg
1249 ms
logo-clipping-grey.gif
589 ms
S_eb7524b598.png
1116 ms
more-link.gif
623 ms
S_9add5db473.jpg
1084 ms
S_00ea4fdaa6.jpg
1088 ms
S_62820e0e5a.jpg
2059 ms
S_b21159d6a9.jpg
1412 ms
S_2856c4cc16.jpg
1426 ms
S_2069340b3a.jpg
1429 ms
all.js
272 ms
likebox.php
100 ms
S_36b2c5cb98.jpg
2115 ms
d_309a4f5a60.jpg
1761 ms
S_8b91ca98e2.jpg
2334 ms
S_1631544cf8.jpg
1444 ms
S_fd86ea70c6.jpg
1803 ms
S_21b61e1d2a.jpg
1763 ms
JILs2BHKnAI.css
288 ms
hnyz4lqaMhM.css
369 ms
q68gy-v_YMF.js
493 ms
FJmpeSpHpjS.js
626 ms
0wM5s1Khldu.js
516 ms
1bNoFZUdlYZ.js
517 ms
nu-qg3EqU-e.js
518 ms
S_4b53449ca0.jpg
2557 ms
product-link.gif
1817 ms
37 ms
xd_arbiter.php
220 ms
xd_arbiter.php
440 ms
221810_10151385841424530_859028905_n.png
295 ms
wL6VQj7Ab77.png
78 ms
s7jcwEQH7Sx.png
78 ms
I6-MnjEovm5.js
69 ms
pQrUxxo5oQp.js
136 ms
print.css
111 ms
ping
42 ms
marzek.at 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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
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.
marzek.at 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
marzek.at SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Marzek.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Marzek.at 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.
marzek.at
Open Graph description is not detected on the main page of Marzek. 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: