Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

leibnitz.at

Newsroom der Stadt Leibnitz - Die offizielle News-Seite der Stadtgemeinde Leibnitz

Page Load Speed

2.8 sec in total

First Response

311 ms

Resources Loaded

2.1 sec

Page Rendered

411 ms

leibnitz.at screenshot

About Website

Welcome to leibnitz.at homepage info - get ready to check Leibnitz best content for Austria right away, or after learning these important things about leibnitz.at

Allgemeine Informationen zur Stadtgemeinde Leibnitz, zur Stadtverwaltung inkl. Mitarbeiterverzeichnis; Informationen zu politischen Mandataren, Gremien und Wahlen sowie die wichtigsten Termine in Leib...

Visit leibnitz.at

Key Findings

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

Performance Metrics

leibnitz.at performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

55/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.7 s

69/100

10%

Network Requests Diagram

leibnitz.at

311 ms

www.leibnitz.at

331 ms

www.leibnitz.at

562 ms

news-basic.css

12 ms

theme-d451ea9f93050a3fcec4b948de28ad06b5e1d4e0a142348379b0d8e384f15087-2e95a51074974f623d3e6c6122a080c0.css

33 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that all of those requests were addressed to Leibnitz.at and no external sources were called. The less responsive or slowest element that took the longest time to load (562 ms) belongs to the original domain Leibnitz.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 471.0 kB (23%)

Content Size

2.0 MB

After Optimization

1.5 MB

In fact, the total size of Leibnitz.at main page is 2.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 79.6 kB

  • Original 91.4 kB
  • After minification 91.4 kB
  • After compression 11.9 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 79.6 kB or 87% of the original size.

Image Optimization

-20%

Potential reduce by 391.5 kB

  • Original 1.9 MB
  • After minification 1.5 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. Obviously, Leibnitz needs image optimization as it can save up to 391.5 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 17 B

  • Original 655 B
  • After minification 655 B
  • After compression 638 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.

Requests Breakdown

Number of requests can be reduced by 32 (52%)

Requests Now

61

After Optimization

29

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

Accessibility Review

leibnitz.at accessibility score

78

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

leibnitz.at best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

leibnitz.at SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leibnitz.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Leibnitz.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

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