Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

iapp.de

— Dresden Integrated Center for Applied Physics and Photonic Materials (DC-IAPP) — TU Dresden

Page Load Speed

30.2 sec in total

First Response

4.1 sec

Resources Loaded

25.8 sec

Page Rendered

261 ms

About Website

Click here to check amazing IAPP content for India. Otherwise, check out these important facts you probably never knew about iapp.de

The "Dresden Integrated Center for Applied Physics and Photonic Materials (IAPP)" at the TU Dresden is a world-leading interdisciplinary research center on organic electronics and opotelectronics. …

Visit iapp.de

Key Findings

We analyzed Iapp.de page load time and found that the first response time was 4.1 sec and then it took 26 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

iapp.de performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value23.7 s

0/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value7.3 s

50/100

10%

Network Requests Diagram

iapp

4143 ms

default.css

106 ms

common.css

433 ms

plone-legacy-compiled.css

325 ms

default.js

1127 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Iapp.de, 6% (2 requests) were made to Matomo.tu-dresden.de. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Tu-dresden.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 143.6 kB (13%)

Content Size

1.1 MB

After Optimization

954.4 kB

In fact, the total size of Iapp.de main page is 1.1 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. 30% of websites need less resources to load. Images take 968.2 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 55.0 kB

  • Original 63.9 kB
  • After minification 40.1 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 23.9 kB, which is 37% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 55.0 kB or 86% of the original size.

Image Optimization

-5%

Potential reduce by 44.2 kB

  • Original 968.2 kB
  • After minification 924.0 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. IAPP images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 44.4 kB

  • Original 65.8 kB
  • After minification 65.8 kB
  • After compression 21.4 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 44.4 kB or 67% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

28

After Optimization

28

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

Accessibility Review

iapp.de accessibility score

87

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

iapp.de 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

iapp.de SEO score

91

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

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

    EN

  • Encoding

    UTF-8

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