Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

kontext.at

KONTEXT Wien | Corporate Design und Werbung, die bewegt.

Page Load Speed

3.4 sec in total

First Response

318 ms

Resources Loaded

2.7 sec

Page Rendered

436 ms

kontext.at screenshot

About Website

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

Corporate Design, Logo, Printprodukte, Website, Branding – wir sind eine Wiener Design- und Werbeagentur und gestalten mit größter Leidenschaft.

Visit kontext.at

Key Findings

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

Performance Metrics

kontext.at performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

8/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

kontext.at

318 ms

kontext.at

649 ms

gtm.js

85 ms

KON_LO_2010_280px_RGB.png

106 ms

matomo.js

665 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 88% of them (23 requests) were addressed to the original Kontext.at, 8% (2 requests) were made to Ma.kontext.at and 4% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (978 ms) relates to the external source Ma.kontext.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 421.8 kB (59%)

Content Size

714.6 kB

After Optimization

292.8 kB

In fact, the total size of Kontext.at main page is 714.6 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. 35% of websites need less resources to load. HTML takes 485.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 405.6 kB

  • Original 485.9 kB
  • After minification 485.4 kB
  • After compression 80.3 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 405.6 kB or 83% of the original size.

Image Optimization

-23%

Potential reduce by 16.2 kB

  • Original 70.8 kB
  • After minification 54.6 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. Obviously, KONTEXT needs image optimization as it can save up to 16.2 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 64 B

  • Original 157.9 kB
  • After minification 157.9 kB
  • After compression 157.9 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 10 (48%)

Requests Now

21

After Optimization

11

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

Accessibility Review

kontext.at accessibility score

98

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

Links do not have a discernible name

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

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