7.9 sec in total
385 ms
6.9 sec
573 ms
Click here to check amazing Storz content for Germany. Otherwise, check out these important facts you probably never knew about storz.de
Wir helfen Ihnen dabei, Ihre Kunden zu begeistern. Full-Service über alle Disziplinen und Medien hinweg. Willkommen in der Fabrik der Möglichkeiten.
Visit storz.deWe analyzed Storz.de page load time and found that the first response time was 385 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
storz.de performance score
name
value
score
weighting
Value10.7 s
0/100
10%
Value12.0 s
0/100
25%
Value13.1 s
2/100
10%
Value120 ms
97/100
30%
Value0.153
75/100
15%
Value11.1 s
20/100
10%
385 ms
1523 ms
193 ms
592 ms
609 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 94% of them (92 requests) were addressed to the original Storz.de, 4% (4 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Storz.de.
Page size can be reduced by 1.0 MB (39%)
2.6 MB
1.6 MB
In fact, the total size of Storz.de main page is 2.6 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. 55% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 74.3 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 74.3 kB or 81% of the original size.
Potential reduce by 50.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. Storz images are well optimized though.
Potential reduce by 557.0 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 557.0 kB or 71% of the original size.
Potential reduce by 348.6 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. Storz.de needs all CSS files to be minified and compressed as it can save up to 348.6 kB or 84% of the original size.
Number of requests can be reduced by 56 (60%)
94
38
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Storz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
storz.de
385 ms
www.storz.de
1523 ms
s5_tab_show.css
193 ms
module_default.css
592 ms
modal.css
609 ms
jquery.min.js
359 ms
jquery-noconflict.js
209 ms
jquery-migrate.min.js
210 ms
caption.js
290 ms
bootstrap.min.js
313 ms
jquery.ui.core.min.js
314 ms
jquery.ui.sortable.min.js
389 ms
jquery-ui-addons.js
641 ms
s5_tab_show.js
640 ms
acymailing_module.js
589 ms
mootools-core.js
639 ms
core.js
703 ms
mootools-more.js
917 ms
modal.js
701 ms
s5_ls_fade.js
712 ms
bootstrap-default.css
716 ms
bootstrap-responsive.css
727 ms
font-awesome.min.css
801 ms
ionicons.min.css
815 ms
css
27 ms
s5_flex_menu.js
817 ms
s5_flex_menu.css
828 ms
system.css
897 ms
general.css
966 ms
template_default.css
965 ms
template.css
966 ms
com_content.css
998 ms
editor.css
1014 ms
thirdparty.css
1017 ms
css
33 ms
multibox.css
1019 ms
ajax.css
1139 ms
overlay.js
1136 ms
css
44 ms
css
44 ms
custom.css
1046 ms
s5_info_slide.css
962 ms
team.css
947 ms
multibox.js
1031 ms
s5_info_slide.js
962 ms
scrollReveal.min.js
938 ms
scrollfix.js
956 ms
jquery.mousewheel.min.js
912 ms
jquery.simplr.smoothscroll.min.js
984 ms
storz.js
773 ms
index.php
941 ms
system.css
115 ms
startscreen.jpg
118 ms
s5_media_overlay.png
113 ms
s5_logo.png
297 ms
s5_logo_small.png
286 ms
stoerer-leistungen.png
286 ms
stoerer-leistungen-klein.png
117 ms
start_01.jpg
217 ms
start_02.jpg
322 ms
start_04.jpg
326 ms
start_03.jpg
434 ms
beratung.png
387 ms
messe.png
404 ms
industriefilm.png
395 ms
magazine.png
422 ms
web.png
429 ms
print.png
488 ms
storz_video_SPEX-Impulsforum-K%C3%B6lnSS.jpg
1257 ms
lra_es.jpg
1002 ms
Post_Dick_171215.jpg
1119 ms
Post_Silvester.jpg
1375 ms
ksk-es-nt-image-intro.jpg
880 ms
effizienzgipfel-intro.jpg
2164 ms
hajoona.jpg
2127 ms
eep-arena2036-intro.jpg
2027 ms
adac-print-intro.jpg
2217 ms
weber-esslingen-image-intro.jpg
1825 ms
spex-events-intro.jpg
2124 ms
vdi-tectv-intro.jpg
1968 ms
marlok.jpg
2211 ms
dick-print-intro.jpg
2238 ms
stoerer.png
2461 ms
s5_ls.css
2300 ms
ionicons.ttf
2658 ms
startscreen.jpg
2365 ms
s5_ls_preloader.gif
134 ms
maske.jpg
122 ms
s5_media_overlay.png
149 ms
s5_scroll_arrow.png
128 ms
gradient.jpg
140 ms
close.jpg
180 ms
ie.jpg
233 ms
button.jpg
235 ms
ga.js
77 ms
s5_menu_arrow.png
154 ms
maske.jpg
374 ms
__utm.gif
14 ms
storz.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
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
Form elements do not have associated labels
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.
storz.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
Browser errors were logged to the console
storz.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
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Storz.de 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 Storz.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.
storz.de
Open Graph description is not detected on the main page of Storz. 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: