Tools & Wizards About Us
open3.at screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

open3.at

Netzwerk zur Förderung von OpenSociety, OpenGov und OpenData in Österreich › open3.at

Page Load Speed

5.6 sec in total

First Response

535 ms

Resources Loaded

3.3 sec

Page Rendered

1.8 sec

open3.at screenshot

About Website

Welcome to open3.at homepage info - get ready to check Open 3 best content right away, or after learning these important things about open3.at

Transparenz und Informationsfreiheit: Warum Gemeinden und Behörden von einem Informationsfreiheitsgesetz profitieren. Open Data und die ...

Visit open3.at

Key Findings

We analyzed Open3.at page load time and found that the first response time was 535 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

open3.at performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

43/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

open3.at

535 ms

www.open3.at

1041 ms

script.js

193 ms

style.css

288 ms

style.min.css

384 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 96% of them (47 requests) were addressed to the original Open3.at, 4% (2 requests) were made to Mapsmarker.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Open3.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 176.1 kB (8%)

Content Size

2.1 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Open3.at main page is 2.1 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. 40% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 86.0 kB

  • Original 108.2 kB
  • After minification 99.2 kB
  • After compression 22.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. 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 86.0 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 86.7 kB

  • Original 1.9 MB
  • After minification 1.8 MB

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. Open 3 images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.0 kB

  • Original 77.2 kB
  • After minification 77.2 kB
  • After compression 76.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-6%

Potential reduce by 2.3 kB

  • Original 40.4 kB
  • After minification 40.4 kB
  • After compression 38.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. Open3.at has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (66%)

Requests Now

47

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Open 3. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

open3.at

open3.at

535 ms

www.open3.at

www.open3.at

1041 ms

script.js

script.js

193 ms

style.css

style.css

288 ms

style.min.css

style.min.css

384 ms

mapsmarkerpro.css

mapsmarkerpro.css

291 ms

style.min.css

style.min.css

294 ms

style.instances-ho-is-po-no-da-co-au-ga-se-is.css

style.instances-ho-is-po-no-da-co-au-ga-se-is.css

296 ms

wp-paginate.css

wp-paginate.css

295 ms

lightbox.js

lightbox.js

393 ms

asp-prereq.js

asp-prereq.js

300 ms

asp-core.js

asp-core.js

306 ms

asp-settings.js

asp-settings.js

307 ms

asp-results-vertical.js

asp-results-vertical.js

307 ms

asp-live.js

asp-live.js

385 ms

asp-autocomplete.js

asp-autocomplete.js

387 ms

asp-load.js

asp-load.js

386 ms

asp-wrapper.js

asp-wrapper.js

387 ms

page_t.jpg

page_t.jpg

192 ms

gluecksspiel-projekt.png

gluecksspiel-projekt.png

192 ms

postdateicon.png

postdateicon.png

179 ms

postauthoricon.png

postauthoricon.png

179 ms

Folge_39_RuP_SoMe_1080x1080_Foto_quer.jpg

Folge_39_RuP_SoMe_1080x1080_Foto_quer.jpg

653 ms

postcategoryicon.png

postcategoryicon.png

183 ms

postcommentsicon.png

postcommentsicon.png

273 ms

datagvat-buddy-logo-full-700x700.png

datagvat-buddy-logo-full-700x700.png

1413 ms

opendata-buddy-beispiel4-250x305.png

opendata-buddy-beispiel4-250x305.png

374 ms

opendata-buddy-beispiel3-250x192.png

opendata-buddy-beispiel3-250x192.png

288 ms

opendata-buddy-beispiel1-250x296.png

opendata-buddy-beispiel1-250x296.png

382 ms

opendata-buddy-beispiel2-250x297.png

opendata-buddy-beispiel2-250x297.png

368 ms

ai-bots-talking-ifg.jpg

ai-bots-talking-ifg.jpg

577 ms

wiener-zeitung-29032023-Transparenz-sorgt-fuer-effiziente-Verwaltung.jpg

wiener-zeitung-29032023-Transparenz-sorgt-fuer-effiziente-Verwaltung.jpg

751 ms

sheet_s.png

sheet_s.png

444 ms

sheet_h.png

sheet_h.png

453 ms

sheet_v.png

sheet_v.png

540 ms

nav.png

nav.png

550 ms

menuitem.png

menuitem.png

637 ms

spacer.gif

spacer.gif

646 ms

subitem.png

subitem.png

647 ms

header980neu.png

header980neu.png

723 ms

post_s.png

post_s.png

733 ms

post_h.png

post_h.png

742 ms

post_v.png

post_v.png

743 ms

postbullets.png

postbullets.png

820 ms

postquote.png

postquote.png

820 ms

sidebar_g.png

sidebar_g.png

828 ms

footer.png

footer.png

837 ms

piwik.js

piwik.js

627 ms

piwik.php

piwik.php

189 ms

Accessibility Review

open3.at accessibility score

93

Accessibility Issues

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

High

Links do not have a discernible name

Best Practices

open3.at best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

open3.at SEO score

79

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Open3.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 Open3.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.

Social Sharing Optimization

open3.at

Open Graph description is not detected on the main page of Open 3. 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: