6.3 sec in total
1.3 sec
4.6 sec
484 ms
Visit g19.at now to see the best up-to-date G 19 content for Austria and also check out these interesting facts you probably never knew about g19.at
Website des Döblinger Gymnasiums
Visit g19.atWe analyzed G19.at page load time and found that the first response time was 1.3 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
g19.at performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value4.8 s
31/100
25%
Value6.6 s
37/100
10%
Value0 ms
100/100
30%
Value0.049
99/100
15%
Value4.8 s
79/100
10%
1257 ms
489 ms
293 ms
198 ms
202 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 98% of them (47 requests) were addressed to the original G19.at, 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain G19.at.
Page size can be reduced by 1.5 MB (24%)
6.2 MB
4.7 MB
In fact, the total size of G19.at main page is 6.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. 30% of websites need less resources to load. Images take 5.4 MB which makes up the majority of the site volume.
Potential reduce by 24.4 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 24.4 kB or 76% of the original size.
Potential reduce by 852.1 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. Obviously, G 19 needs image optimization as it can save up to 852.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 360.7 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 360.7 kB or 70% of the original size.
Potential reduce by 222.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. G19.at needs all CSS files to be minified and compressed as it can save up to 222.8 kB or 84% of the original size.
Number of requests can be reduced by 28 (60%)
47
19
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of G 19. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
g19.at
1257 ms
bootstrap.min.css
489 ms
bootstrap-responsive.min.css
293 ms
bootstrap-extended.css
198 ms
system.css
202 ms
general.css
202 ms
template.css
302 ms
template_pro.css
497 ms
red.css
400 ms
business.css
403 ms
jsn_css3.css
582 ms
custom.css
496 ms
modstyle.css
598 ms
jfontsize.css
599 ms
finder.css
683 ms
jquery.min.js
991 ms
jquery-noconflict.js
692 ms
jquery-migrate.min.js
780 ms
caption.js
792 ms
mootools-core.js
1094 ms
core.js
875 ms
mootools-more.js
1389 ms
bootstrap.min.js
1077 ms
noconflict.js
984 ms
utils.js
1165 ms
jsn_template.js
1180 ms
jquery.jfontsize-1.0.min.js
1183 ms
autocompleter.js
1376 ms
system.css
1097 ms
css
69 ms
ProgrammNawiTagSpezial.jpg
684 ms
logo_name.jpg
201 ms
g19_header_13.jpg
495 ms
mqdefault.jpg
197 ms
Mauthausen20166.JPG
1501 ms
image.jpeg
1785 ms
g19_unesco.jpg
294 ms
g19_fdz.jpg
397 ms
polyhymnia_logo.jpg
600 ms
Unternehmerfhrerschein.png
491 ms
bg-module-richbox-1.png
575 ms
bg-promo.png
672 ms
dot.png
676 ms
glyphicons-halflings.png
769 ms
liste.png
783 ms
h3.jpg
872 ms
menu_row.jpg
871 ms
print.css
102 ms
g19.at accessibility score
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
Links do not have a discernible 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.
g19.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
g19.at 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 G19.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 G19.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.
g19.at
Open Graph description is not detected on the main page of G 19. 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: