Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

drystar.at

DRYSTAR – Leckortung, Schimmelsanierung & Entfeuchtung

Page Load Speed

2.8 sec in total

First Response

341 ms

Resources Loaded

2 sec

Page Rendered

434 ms

drystar.at screenshot

About Website

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

Zuverlässig und professionell – DRYSTAR Österreich bietet Leckortung, Wasserschadensanierung, Trocknung und Schimmelsanierung in Wien, Graz und Linz an. Auch zum Kaufen und Mieten von Luftentfeuchter,...

Visit drystar.at

Key Findings

We analyzed Drystar.at page load time and found that the first response time was 341 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

drystar.at performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

93/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.101

89/100

15%

TTI (Time to Interactive)

Value2.0 s

99/100

10%

Network Requests Diagram

drystar.at

341 ms

www.drystar.at

805 ms

styles.css

219 ms

_require.js

243 ms

csite_modules.js

350 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 113.2 kB (34%)

Content Size

330.5 kB

After Optimization

217.4 kB

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

HTML Optimization

-84%

Potential reduce by 71.2 kB

  • Original 85.1 kB
  • After minification 84.2 kB
  • After compression 13.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 71.2 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 7.6 kB

  • Original 165.3 kB
  • After minification 157.7 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. DRYSTAR images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 34.1 kB

  • Original 52.3 kB
  • After minification 52.3 kB
  • After compression 18.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 34.1 kB or 65% of the original size.

CSS Optimization

-1%

Potential reduce by 299 B

  • Original 27.9 kB
  • After minification 27.9 kB
  • After compression 27.6 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. Drystar.at has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

10

After Optimization

10

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

Accessibility Review

drystar.at accessibility score

83

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

drystar.at best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

drystar.at SEO score

100

Search Engine Optimization Advices

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

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 Drystar.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 Drystar.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 DRYSTAR. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: