Tools & Wizards About Us

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

illig.de

ILLIG Mechanical Engineering – Tradition Forms Future

Page Load Speed

4.3 sec in total

First Response

330 ms

Resources Loaded

3.3 sec

Page Rendered

629 ms

About Website

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

ILLIG provides you with machines and tools for thermoforming as well as packaging production. Satisfied customers in over 80 countries✓

Visit illig.de

Key Findings

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

Performance Metrics

illig.de performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value6.7 s

35/100

10%

TBT (Total Blocking Time)

Value730 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.155

74/100

15%

TTI (Time to Interactive)

Value8.9 s

34/100

10%

Network Requests Diagram

illig.de

330 ms

illig.de

412 ms

www.illig.de

588 ms

en-de

365 ms

uc.js

202 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 90% of them (56 requests) were addressed to the original Illig.de, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Illig.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 251.5 kB (8%)

Content Size

3.0 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Illig.de main page is 3.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. 65% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 129.7 kB

  • Original 142.3 kB
  • After minification 102.3 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 40.0 kB, which is 28% 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 129.7 kB or 91% of the original size.

Image Optimization

-1%

Potential reduce by 22.3 kB

  • Original 2.6 MB
  • After minification 2.5 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. ILLIG images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 94.3 kB

  • Original 223.5 kB
  • After minification 222.8 kB
  • After compression 129.2 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 94.3 kB or 42% of the original size.

CSS Optimization

-10%

Potential reduce by 5.1 kB

  • Original 51.2 kB
  • After minification 51.2 kB
  • After compression 46.1 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. Illig.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (44%)

Requests Now

50

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

illig.de accessibility score

84

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

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

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

illig.de best practices score

83

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

Page has valid source maps

SEO Factors

illig.de SEO score

73

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Document doesn't have a valid hreflang

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 Illig.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 Illig.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 ILLIG. 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: