13.4 sec in total
1.3 sec
11.8 sec
323 ms
Visit frastanzer.at now to see the best up-to-date Frastanzer content and also check out these interesting facts you probably never knew about frastanzer.at
frastanzer - Die regionale BIO-Genossenschaftsbrauerei
Visit frastanzer.atWe analyzed Frastanzer.at page load time and found that the first response time was 1.3 sec and then it took 12.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
frastanzer.at performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value10.1 s
0/100
25%
Value10.7 s
7/100
10%
Value6,960 ms
0/100
30%
Value0.246
50/100
15%
Value14.8 s
8/100
10%
1291 ms
219 ms
334 ms
860 ms
338 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 64% of them (35 requests) were addressed to the original Frastanzer.at, 13% (7 requests) were made to Static.xx.fbcdn.net and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (9 sec) belongs to the original domain Frastanzer.at.
Page size can be reduced by 724.0 kB (27%)
2.7 MB
2.0 MB
In fact, the total size of Frastanzer.at main page is 2.7 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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 19.5 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 6.2 kB, which is 25% 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 19.5 kB or 79% of the original size.
Potential reduce by 29.0 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. Frastanzer images are well optimized though.
Potential reduce by 436.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 436.5 kB or 66% of the original size.
Potential reduce by 239.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. Frastanzer.at needs all CSS files to be minified and compressed as it can save up to 239.1 kB or 83% of the original size.
Number of requests can be reduced by 23 (44%)
52
29
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frastanzer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
frastanzer.at
1291 ms
jcemediabox.css
219 ms
style.css
334 ms
mootools-core.js
860 ms
core.js
338 ms
caption.js
227 ms
jcemediabox.js
781 ms
mootools-more.js
1566 ms
jquery.js
919 ms
cookie.js
442 ms
maxheight.js
449 ms
constant.css
551 ms
template.css
891 ms
ga.js
24 ms
tunzABVar8E
114 ms
uvLJeXSEHG4
165 ms
logo.gif
113 ms
row_banners.jpg
5745 ms
bg.png
4997 ms
peeloverlay.png
136 ms
static_ad_3.jpg
5300 ms
wrapper_img.png
148 ms
img1.jpg
4761 ms
marker_right.gif
4762 ms
img2.jpg
4777 ms
img3.jpg
5089 ms
img4.jpg
5190 ms
list_marker.gif
4944 ms
craft-Truebeer_black.png
5606 ms
craft-badge_black.png
5186 ms
craft-box.png
9019 ms
craft-hoppy.png
5937 ms
craft-dark.png
5622 ms
craft-hornet.png
5842 ms
oeffnungszeiten.jpg
5826 ms
popup.html
5687 ms
tooltip.html
5797 ms
__utm.gif
12 ms
__utm.gif
9 ms
zoom-img.png
5807 ms
likebox.php
81 ms
www-embed-player-vflfNyN_r.css
38 ms
www-embed-player.js
53 ms
base.js
4669 ms
ebiMDO3r-8l.css
4618 ms
TKuNj0xVh4A.js
4628 ms
FJmpeSpHpjS.js
4723 ms
0wM5s1Khldu.js
4645 ms
1bNoFZUdlYZ.js
4644 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
118 ms
ad_status.js
102 ms
I6-MnjEovm5.js
17 ms
pQrUxxo5oQp.js
7 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
53 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
53 ms
frastanzer.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-*] attributes do not match their roles
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
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
Buttons do not have an accessible name
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
frastanzer.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
Missing source maps for large first-party JavaScript
frastanzer.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
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frastanzer.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 Frastanzer.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.
frastanzer.at
Open Graph description is not detected on the main page of Frastanzer. 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: