Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

harrer.at

Vinzenz Harrer GmbH - der führende Spezialist im Holzbau

Page Load Speed

7.7 sec in total

First Response

403 ms

Resources Loaded

6.4 sec

Page Rendered

844 ms

harrer.at screenshot

About Website

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

Vinzenz Harrer GmbH ist der führende Spezialist für Lösungen im Holzbau. Besuchen Sie unseren Shop und profitieren Sie von der hervorragenden Qualität.

Visit harrer.at

Key Findings

We analyzed Harrer.at page load time and found that the first response time was 403 ms and then it took 7.3 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

harrer.at performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value14.5 s

1/100

10%

TBT (Total Blocking Time)

Value13,300 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.271

45/100

15%

TTI (Time to Interactive)

Value25.8 s

0/100

10%

Network Requests Diagram

harrer.at

403 ms

www.harrer.at

991 ms

www.harrer.at

1652 ms

bundle

704 ms

html5.js

471 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 78% of them (42 requests) were addressed to the original Harrer.at, 6% (3 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Harrer.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 679.2 kB (16%)

Content Size

4.1 MB

After Optimization

3.5 MB

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

HTML Optimization

-82%

Potential reduce by 64.8 kB

  • Original 79.4 kB
  • After minification 71.1 kB
  • After compression 14.6 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 64.8 kB or 82% of the original size.

Image Optimization

-15%

Potential reduce by 607.6 kB

  • Original 4.0 MB
  • After minification 3.4 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, Harrer needs image optimization as it can save up to 607.6 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-8%

Potential reduce by 6.8 kB

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

Requests Breakdown

Number of requests can be reduced by 13 (28%)

Requests Now

46

After Optimization

33

The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Harrer. 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 as a result speed up the page load time.

Accessibility Review

harrer.at accessibility score

81

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

harrer.at SEO score

81

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

    DE

  • Encoding

    UTF-8

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