Report Summary

  • 56


    Renders faster than
    72% of other websites

  • 96


    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    86% of websites

  • 97


    Google-friendlier than
    93% of websites

Home - TU Graz

Page Load Speed

30.9 sec in total

First Response

647 ms

Resources Loaded

16.6 sec

Page Rendered

13.6 sec screenshot

About Website

Click here to check amazing TU Graz content for Austria. Otherwise, check out these important facts you probably never knew about

Denken in neuen Dimensionen. Studieren mit Zukunft. Gemeinsam mehr erreichen, mit Wissen, Technik und Leidenschaft - das ist die TU Graz.


Key Findings

We analyzed page load time and found that the first response time was 647 ms and then it took 30.2 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 performance score


Measured Metrics





FCP (First Contentful Paint)

Value4.5 s



LCP (Largest Contentful Paint)

Value12.5 s



SI (Speed Index)

Value7.0 s



TBT (Total Blocking Time)

Value50 ms



CLS (Cumulative Layout Shift)




TTI (Time to Interactive)

Value6.4 s



Network Requests Diagram

647 ms


433 ms


696 ms


244 ms


1120 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 90% of them (37 requests) were addressed to the original, 5% (2 requests) were made to and 5% (2 requests) were made to The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain

Page Optimization Overview & Recommendations

Page size can be reduced by 725.6 kB (10%)

Content Size

7.6 MB

After Optimization

6.8 MB

In fact, the total size of main page is 7.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.5 MB which makes up the majority of the site volume.

HTML Optimization


Potential reduce by 84.9 kB

  • Original 104.0 kB
  • After minification 100.1 kB
  • After compression 19.1 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 84.9 kB or 82% of the original size.

Image Optimization


Potential reduce by 86.2 kB

  • Original 6.5 MB
  • After minification 6.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. TU Graz images are well optimized though.

JavaScript Optimization


Potential reduce by 307.1 kB

  • Original 444.6 kB
  • After minification 405.6 kB
  • After compression 137.5 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 307.1 kB or 69% of the original size.

CSS Optimization


Potential reduce by 247.4 kB

  • Original 526.1 kB
  • After minification 484.5 kB
  • After compression 278.7 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. needs all CSS files to be minified and compressed as it can save up to 247.4 kB or 47% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (42%)

Requests Now


After Optimization


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

Accessibility Review accessibility score


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.




Links do not have a discernible name

Best Practices best practices score


Areas of Improvement

Trust and Safety




Does not use HTTPS


Ensure CSP is effective against XSS attacks





Detected JavaScript libraries

SEO Factors SEO score


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](




Document uses legible font sizes


Tap targets are not sized appropriately

Language and Encoding

  • Language Detected


  • Language Claimed


  • Encoding


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