3.1 sec in total
756 ms
2 sec
314 ms
Click here to check amazing DORIS Ooe content for Austria. Otherwise, check out these important facts you probably never knew about doris.ooe.gv.at
Startseite von DORIS interMap. DORIS ist das DigitaleOberösterreichischeRaumInformationssystem - das Geographische Informationssystem des Landes Oö.
Visit doris.ooe.gv.atWe analyzed Doris.ooe.gv.at page load time and found that the first response time was 756 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 45% of websites can load faster.
doris.ooe.gv.at performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value10.0 s
0/100
25%
Value6.4 s
40/100
10%
Value50 ms
100/100
30%
Value0
100/100
15%
Value10.1 s
26/100
10%
756 ms
211 ms
210 ms
418 ms
317 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 98% of them (49 requests) were addressed to the original Doris.ooe.gv.at, 2% (1 request) were made to Pw-p.ooe.gv.at. The less responsive or slowest element that took the longest time to load (928 ms) belongs to the original domain Doris.ooe.gv.at.
Page size can be reduced by 817.6 kB (48%)
1.7 MB
873.5 kB
In fact, the total size of Doris.ooe.gv.at main page is 1.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. 50% of websites need less resources to load. Images take 735.8 kB which makes up the majority of the site volume.
Potential reduce by 54.0 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 14.2 kB, which is 22% 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 54.0 kB or 82% of the original size.
Potential reduce by 75.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. DORIS Ooe images are well optimized though.
Potential reduce by 468.6 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 468.6 kB or 74% of the original size.
Potential reduce by 220.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. Doris.ooe.gv.at needs all CSS files to be minified and compressed as it can save up to 220.1 kB or 85% of the original size.
Number of requests can be reduced by 20 (41%)
49
29
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DORIS Ooe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
doris.ooe.gv.at
756 ms
ooeGui2015.css
211 ms
flexslider.css
210 ms
bootstrap.css
418 ms
ooe.css
317 ms
jquery.fancybox.css
210 ms
jquery-ui.css
430 ms
autocomplete.css
313 ms
landeslogo_mr.png
225 ms
landeslogo.png
312 ms
dorislogo.png
424 ms
icon_marathon.png
323 ms
icon_hinweis.png
323 ms
icon_clairisa.png
311 ms
icon_hofnamen.png
423 ms
GIS_Day_2014.png
700 ms
ortsplan2basemap.png
481 ms
protect_world.png
591 ms
jquery-1.11.2.min.js
325 ms
jquery-migrate-1.2.1.min.js
345 ms
jquery-ui.min.js
528 ms
bootstrap.js
430 ms
jquery.flexslider.js
427 ms
jquery.fancybox.js
519 ms
jquery.mousewheel-3.0.6.pack.js
562 ms
jquery-listnav.js
562 ms
ergaenzung.js
624 ms
tools.js
629 ms
doris_autocomplete.js
630 ms
terraformer-1.0.2.min.js
632 ms
terraformer-wkt-parser.min.js
634 ms
FlaeWiZomm.png
830 ms
unfall.jpg
833 ms
video.png
731 ms
pfarrgrenzen_sz_liedl.jpg
733 ms
DORIS_Web_App.png
733 ms
android_app_on_play_logo_small.png
734 ms
app-download.jpg
834 ms
logo_basemap.png
836 ms
logo_geoland.png
836 ms
logo_doris_transp_footer.png
834 ms
logo_basemap_transp_footer.png
926 ms
logo_geoland_transp_footer.png
928 ms
icon_toplink.png
813 ms
icon_mail.png
815 ms
icon_telefon.png
799 ms
icon_lupe.png
745 ms
icon_hakerl.png
830 ms
piwik.js
611 ms
ooe-druck.css
106 ms
doris.ooe.gv.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
doris.ooe.gv.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
doris.ooe.gv.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 Doris.ooe.gv.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 Doris.ooe.gv.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.
doris.ooe.gv.at
Open Graph description is not detected on the main page of DORIS Ooe. 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: