Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

zauner.at

Cafe Konditorei Zauner Bad Ischl - Onlineshop Versand weltweit

Page Load Speed

7.3 sec in total

First Response

403 ms

Resources Loaded

6.6 sec

Page Rendered

320 ms

zauner.at screenshot

About Website

Visit zauner.at now to see the best up-to-date Zauner content and also check out these interesting facts you probably never knew about zauner.at

Hier finden Sie die Webseite des ehemaligen k.u.k. Hofzuckerbäckers und Hoflieferanten. Für unsere Köstlichkeiten bieten wir weltweiten Versand.

Visit zauner.at

Key Findings

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

Performance Metrics

zauner.at performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value16.9 s

0/100

25%

SI (Speed Index)

Value13.6 s

2/100

10%

TBT (Total Blocking Time)

Value1,340 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

zauner.at

403 ms

www.zauner.at

773 ms

messages.min.css

112 ms

shop.css

222 ms

integrations.css

314 ms

Our browser made a total of 150 requests to load all elements on the main page. We found that 99% of them (148 requests) were addressed to the original Zauner.at, 1% (1 request) were made to Googletagmanager.com and 1% (1 request) were made to . The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Zauner.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (78%)

Content Size

2.4 MB

After Optimization

540.0 kB

In fact, the total size of Zauner.at main page is 2.4 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. 65% of websites need less resources to load. CSS take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 197.7 kB

  • Original 237.5 kB
  • After minification 234.9 kB
  • After compression 39.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 197.7 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 535 B

  • Original 55.8 kB
  • After minification 55.3 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. Zauner images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 709.0 kB

  • Original 952.2 kB
  • After minification 831.3 kB
  • After compression 243.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 709.0 kB or 74% of the original size.

CSS Optimization

-83%

Potential reduce by 1.0 MB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 201.8 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. Zauner.at needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 127 (90%)

Requests Now

141

After Optimization

14

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

Accessibility Review

zauner.at accessibility score

95

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

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.

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

zauner.at SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zauner.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 Zauner.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 data is detected on the main page of Zauner. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: