3.7 sec in total
335 ms
3.3 sec
109 ms
Welcome to orf-gis.at homepage info - get ready to check Orf GIS best content right away, or after learning these important things about orf-gis.at
Möglichst schnell. Möglichst unbürokratisch. Möglichst ohne Reibungsverluste soll das Gebührengeld kosteneffizient bei ORF, Bund und Ländern einlangen. Sollen die Gebührenzahler informiert werden und ...
Visit orf-gis.atWe analyzed Orf-gis.at page load time and found that the first response time was 335 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
orf-gis.at performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value6.6 s
8/100
25%
Value8.8 s
16/100
10%
Value670 ms
45/100
30%
Value0.176
68/100
15%
Value10.8 s
22/100
10%
335 ms
881 ms
43 ms
126 ms
369 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Orf-gis.at, 94% (32 requests) were made to Orf.beitrag.at and 3% (1 request) were made to Cdn.priv.center. The less responsive or slowest element that took the longest time to load (956 ms) relates to the external source Orf.beitrag.at.
Page size can be reduced by 31.7 kB (14%)
223.2 kB
191.5 kB
In fact, the total size of Orf-gis.at main page is 223.2 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. Images take 183.9 kB which makes up the majority of the site volume.
Potential reduce by 24.1 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 12.8 kB, which is 45% 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 24.1 kB or 85% of the original size.
Potential reduce by 7.5 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. Orf GIS images are well optimized though.
Potential reduce by 20 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 17 (57%)
30
13
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Orf GIS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
orf-gis.at
335 ms
orf.beitrag.at
881 ms
truendo_cmp.pid.js
43 ms
23e8d02434493289e0ddc7eb4133aed2-fbbd1198a53efcc0981d2625b6eb75ba.css
126 ms
merged-87054609421cd8b2888bc7fa8173cb8d-5ce4c609e6d18f57778c61f2999ecb6b.css
369 ms
jquery-2.1.1.min.js
466 ms
bootstrap.min.js
346 ms
bootstrap-datepicker.js
478 ms
jquery.mask.min.js
356 ms
bootstrapValidator.min.js
481 ms
gisforms.js
480 ms
jquery.fancybox.2.1.4.min.js
486 ms
jquery.dataTables.min.js
493 ms
dataTables.bootstrap.js
581 ms
jquery.autocomplete.js
584 ms
alpine-3.11.1.min.js
582 ms
html2pdf.bundle.js
956 ms
29bfe8318ce2ad6a25bd6e7fbac8a211.js
597 ms
obs.css
618 ms
jpFaq.js
696 ms
main.js
698 ms
giscore.js
698 ms
jquery.dependency.js
718 ms
obs_logo.png
123 ms
csm_Bild7_6e542b2b9d.jpg
232 ms
csm_Bild1_070da9fa39.jpg
241 ms
csm_Bild2_9984ff0f05.jpg
233 ms
csm_Bild3_ec2e3dd3c1.jpg
231 ms
csm_Bild4_1b6a1ed210.jpg
125 ms
csm_Bild5_ed067190ca.jpg
245 ms
csm_Bild6_1a2f846736.jpg
248 ms
FAQ64x64px.png
353 ms
glyphicons-halflings-regular.woff
309 ms
Raleway.woff
312 ms
orf-gis.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
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.
orf-gis.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
orf-gis.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 Orf-gis.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 Orf-gis.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.
orf-gis.at
Open Graph description is not detected on the main page of Orf GIS. 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: