Tools & Wizards About Us
wkr.at screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

wkr.at

Wiener Korporations Ring - WKR

Page Load Speed

21 sec in total

First Response

379 ms

Resources Loaded

18.9 sec

Page Rendered

1.7 sec

wkr.at screenshot

About Website

Click here to check amazing WKR content. Otherwise, check out these important facts you probably never knew about wkr.at

Wiener Korporations Ring

Visit wkr.at

Key Findings

We analyzed Wkr.at page load time and found that the first response time was 379 ms and then it took 20.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

wkr.at performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value17.6 s

0/100

10%

TBT (Total Blocking Time)

Value820 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value28.9 s

0/100

10%

Network Requests Diagram

wkr.at

379 ms

theme-plugin.css

115 ms

theme.min.css

209 ms

theme-sdn.css

220 ms

jquery.mb.YTPlayer.min.css

216 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 85% of them (53 requests) were addressed to the original Wkr.at, 11% (7 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (18.5 sec) belongs to the original domain Wkr.at.

Page Optimization Overview & Recommendations

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

Content Size

1.0 MB

After Optimization

828.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 66.9 kB

  • Original 78.5 kB
  • After minification 76.7 kB
  • After compression 11.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 66.9 kB or 85% of the original size.

Image Optimization

-10%

Potential reduce by 63.2 kB

  • Original 650.0 kB
  • After minification 586.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. WKR images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 39.0 kB

  • Original 205.2 kB
  • After minification 205.2 kB
  • After compression 166.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 39.0 kB or 19% of the original size.

CSS Optimization

-23%

Potential reduce by 19.6 kB

  • Original 83.6 kB
  • After minification 83.4 kB
  • After compression 64.0 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. Wkr.at needs all CSS files to be minified and compressed as it can save up to 19.6 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (27%)

Requests Now

44

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wkr.at

wkr.at

379 ms

theme-plugin.css

theme-plugin.css

115 ms

theme.min.css

theme.min.css

209 ms

theme-sdn.css

theme-sdn.css

220 ms

jquery.mb.YTPlayer.min.css

jquery.mb.YTPlayer.min.css

216 ms

Geschichte-des-WKR.jpg

Geschichte-des-WKR.jpg

12715 ms

theme-plugin.js

theme-plugin.js

702 ms

theme-script.js

theme-script.js

217 ms

jquery.mb.YTPlayer.min.js

jquery.mb.YTPlayer.min.js

253 ms

jquery.validate.min.js

jquery.validate.min.js

41 ms

Hochschulort-Wien.jpg

Hochschulort-Wien.jpg

13251 ms

Veranstaltungen-des-WKR.jpg

Veranstaltungen-des-WKR.jpg

18515 ms

Mensur.jpg

Mensur.jpg

13527 ms

albia.png

albia.png

13033 ms

aldania.svg

aldania.svg

12928 ms

bruna.svg

bruna.svg

12930 ms

cimbria.svg

cimbria.svg

13038 ms

ooegermanen.svg

ooegermanen.svg

13041 ms

gothia.svg

gothia.svg

13143 ms

hansea.png

hansea.png

13162 ms

kaernten.svg

kaernten.svg

13153 ms

libertas.svg

libertas.svg

13257 ms

moldavia.svg

moldavia.svg

13265 ms

nibelungia.svg

nibelungia.svg

13271 ms

olympia.svg

olympia.svg

13363 ms

saxonia.png

saxonia.png

13396 ms

silesia.png

silesia.png

13403 ms

silvania.svg

silvania.svg

13383 ms

sudetia.svg

sudetia.svg

13475 ms

teutonia.png

teutonia.png

13527 ms

wartburg.svg

wartburg.svg

13511 ms

wiking.svg

wiking.svg

13514 ms

turnverein.svg

turnverein.svg

13588 ms

wkr-logo.svg

wkr-logo.svg

307 ms

confetti.png

confetti.png

319 ms

user.png

user.png

329 ms

calendar.png

calendar.png

324 ms

bootstrap.min.css

bootstrap.min.css

333 ms

animate.css

animate.css

318 ms

line-awesome.min.css

line-awesome.min.css

370 ms

magnific-popup.css

magnific-popup.css

331 ms

spacing.css

spacing.css

344 ms

css

css

33 ms

hero-bg.jpg

hero-bg.jpg

342 ms

middle-banner-bg.jpg

middle-banner-bg.jpg

10766 ms

AlteSchwabacherOSF.woff

AlteSchwabacherOSF.woff

298 ms

AlteSchwabacher-Shadow.woff

AlteSchwabacher-Shadow.woff

371 ms

AlteSchwabacher.woff

AlteSchwabacher.woff

298 ms

AlteSchwabacherOSF-DemiBold.woff

AlteSchwabacherOSF-DemiBold.woff

324 ms

AlteSchwabacher-DemiBold.woff

AlteSchwabacher-DemiBold.woff

359 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

17 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

39 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

60 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

95 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

72 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

72 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

71 ms

la-solid-900.woff

la-solid-900.woff

563 ms

la-regular-400.woff

la-regular-400.woff

412 ms

DanteMTStd-Regular.woff

DanteMTStd-Regular.woff

552 ms

DanteMTStd-Bold.woff

DanteMTStd-Bold.woff

501 ms

la-brands-400.woff

la-brands-400.woff

585 ms

Accessibility Review

wkr.at accessibility score

84

Accessibility Issues

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

wkr.at best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

wkr.at SEO score

77

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

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wkr.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Wkr.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

wkr.at

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