Tools & Wizards About Us
floriangeier.at screenshot

Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

floriangeier.at

floriangeier.at

Page Load Speed

1.4 sec in total

First Response

445 ms

Resources Loaded

805 ms

Page Rendered

121 ms

floriangeier.at screenshot

About Website

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

Visit floriangeier.at

Key Findings

We analyzed Floriangeier.at page load time and found that the first response time was 445 ms and then it took 926 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

floriangeier.at performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

92/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value1.3 s

100/100

10%

Network Requests Diagram

floriangeier.at

445 ms

geier.css

115 ms

valid-xhtml10

33 ms

vcss

222 ms

eh.jpg

224 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 83% of them (10 requests) were addressed to the original Floriangeier.at, 8% (1 request) were made to W3.org and 8% (1 request) were made to Jigsaw.w3.org. The less responsive or slowest element that took the longest time to load (445 ms) belongs to the original domain Floriangeier.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.5 kB (36%)

Content Size

94.7 kB

After Optimization

60.2 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Floriangeier.at main page is 94.7 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. Only 5% of websites need less resources to load. Images take 85.3 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 4.0 kB

  • Original 5.9 kB
  • After minification 5.6 kB
  • After compression 1.8 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 4.0 kB or 69% of the original size.

Image Optimization

-32%

Potential reduce by 27.5 kB

  • Original 85.3 kB
  • After minification 57.8 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, Floriangeier needs image optimization as it can save up to 27.5 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-83%

Potential reduce by 2.9 kB

  • Original 3.6 kB
  • After minification 3.0 kB
  • After compression 617 B

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. Floriangeier.at needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

11

After Optimization

11

  • Images
  • CSS

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floriangeier. According to our analytics all requests are already optimized.

Network Requests Diagram

floriangeier.at

floriangeier.at

445 ms

geier.css

geier.css

115 ms

valid-xhtml10

valid-xhtml10

33 ms

vcss

vcss

222 ms

eh.jpg

eh.jpg

224 ms

gz.jpg

gz.jpg

224 ms

inf.jpg

inf.jpg

333 ms

schule.jpg

schule.jpg

336 ms

priv.jpg

priv.jpg

356 ms

mail.gif

mail.gif

257 ms

titel17.jpg

titel17.jpg

235 ms

geier_balken.png

geier_balken.png

216 ms

Accessibility Review

floriangeier.at accessibility score

84

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

floriangeier.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

SEO Factors

floriangeier.at SEO score

67

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floriangeier.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Floriangeier.at main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

floriangeier.at

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