Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

whiz.at

whiz.at is coming soon

Page Load Speed

13.9 sec in total

First Response

3.5 sec

Resources Loaded

10.2 sec

Page Rendered

136 ms

whiz.at screenshot

About Website

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

[EN]: Diese Domain steht zum Verkauf. whiz

Visit whiz.at

Key Findings

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

Performance Metrics

whiz.at performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value170 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

whiz.at

3483 ms

css

23 ms

domain-sale-cart.png

564 ms

domain-buy-hand.png

296 ms

analytics.js

6 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Whiz.at, 44% (4 requests) were made to Google-analytics.com and 11% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Domainname.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 45.8 kB (19%)

Content Size

241.7 kB

After Optimization

196.0 kB

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

HTML Optimization

-72%

Potential reduce by 6.4 kB

  • Original 8.9 kB
  • After minification 8.9 kB
  • After compression 2.5 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 6.4 kB or 72% of the original size.

Image Optimization

-4%

Potential reduce by 7.3 kB

  • Original 162.8 kB
  • After minification 155.4 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. Whiz images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 32.0 kB

  • Original 70.1 kB
  • After minification 70.1 kB
  • After compression 38.1 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 32.0 kB or 46% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

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

Accessibility Review

whiz.at accessibility score

74

Accessibility Issues

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

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.

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

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

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

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whiz.at can be misinterpreted by Google and other search engines. Our service has detected that English 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 Whiz.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 Whiz. 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: