Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

disag.de

DISAG – elektronische Schießanlagen und Auswerteelektronik

Page Load Speed

8.8 sec in total

First Response

1.4 sec

Resources Loaded

7 sec

Page Rendered

423 ms

disag.de screenshot

About Website

Visit disag.de now to see the best up-to-date DISAG content for Germany and also check out these interesting facts you probably never knew about disag.de

Visit disag.de

Key Findings

We analyzed Disag.de page load time and found that the first response time was 1.4 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

disag.de performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

www.disag.de

1352 ms

analytics.js

33 ms

wp-emoji-release.min.js

395 ms

jquery-HoverAlls-2.6.min.css

361 ms

meisterbox.css

337 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 88% of them (74 requests) were addressed to the original Disag.de, 6% (5 requests) were made to Use.typekit.net and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Disag.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (66%)

Content Size

2.2 MB

After Optimization

738.4 kB

In fact, the total size of Disag.de main page is 2.2 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. 50% of websites need less resources to load. CSS take 904.1 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 100.8 kB

  • Original 122.3 kB
  • After minification 120.2 kB
  • After compression 21.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 100.8 kB or 82% of the original size.

Image Optimization

-19%

Potential reduce by 90.8 kB

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

JavaScript Optimization

-72%

Potential reduce by 474.4 kB

  • Original 654.5 kB
  • After minification 617.4 kB
  • After compression 180.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 474.4 kB or 72% of the original size.

CSS Optimization

-84%

Potential reduce by 760.4 kB

  • Original 904.1 kB
  • After minification 761.1 kB
  • After compression 143.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. Disag.de needs all CSS files to be minified and compressed as it can save up to 760.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (69%)

Requests Now

74

After Optimization

23

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

Accessibility Review

disag.de accessibility score

92

Accessibility Issues

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.

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

disag.de SEO score

88

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Disag.de 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 Disag.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 DISAG. 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: