2.6 sec in total
327 ms
2.1 sec
169 ms
Visit langzauner.at now to see the best up-to-date Langzauner content and also check out these interesting facts you probably never knew about langzauner.at
Automation, Hydraulikpressen, Metallbearbeitung und Holzbearbeitung – Langzauner setzt seit 1924 auf Perfektion. Jetzt informieren!
Visit langzauner.atWe analyzed Langzauner.at page load time and found that the first response time was 327 ms 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.
langzauner.at performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value8.0 s
2/100
25%
Value11.9 s
4/100
10%
Value820 ms
35/100
30%
Value0.072
96/100
15%
Value8.5 s
37/100
10%
327 ms
738 ms
210 ms
327 ms
230 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 Langzauner.at, 7% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (738 ms) belongs to the original domain Langzauner.at.
Page size can be reduced by 190.6 kB (48%)
400.9 kB
210.3 kB
In fact, the total size of Langzauner.at main page is 400.9 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 187.3 kB which makes up the majority of the site volume.
Potential reduce by 13.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. 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 13.8 kB or 74% of the original size.
Potential reduce by 4.9 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. Langzauner images are well optimized though.
Potential reduce by 139.1 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 139.1 kB or 74% of the original size.
Potential reduce by 32.8 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. Langzauner.at needs all CSS files to be minified and compressed as it can save up to 32.8 kB or 86% of the original size.
Number of requests can be reduced by 9 (32%)
28
19
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Langzauner. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
langzauner.at
327 ms
www.langzauner.at
738 ms
reset.css
210 ms
style_cms_frontend_201311261.css
327 ms
lightbox.css
230 ms
thickbox.css
228 ms
prototype.js
556 ms
jquery-1.10.1.min.js
6 ms
jquery.slides.min.js
229 ms
thickbox2.js
314 ms
lightbox.js
334 ms
js_funktionen.js
334 ms
ga.js
9 ms
bg_full_langzauner.jpg
219 ms
logo.png
215 ms
suche.png
117 ms
menue_trenn.png
116 ms
8_1000_titelbild_1.jpg
372 ms
19_1000_titelbild_2.jpg
537 ms
1_2044910576_dsc08286.jpg
434 ms
1_1311039231_small_eb14_logo_colour_rgb.jpg
329 ms
fb_like.png
324 ms
facebook.png
328 ms
youtube_icon.png
432 ms
__utm.gif
25 ms
bg_menue_klapp.png
414 ms
arrow_white.png
415 ms
loadingAnimation.gif
436 ms
loading.gif
497 ms
close.png
500 ms
langzauner.at 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
Links do not have a discernible name
langzauner.at best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Issues were logged in the Issues panel in Chrome Devtools
langzauner.at 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
Tap targets are not sized appropriately
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Langzauner.at can be misinterpreted by Google and other search engines. Our service has detected that German 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 Langzauner.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.
langzauner.at
Open Graph description is not detected on the main page of Langzauner. 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: