Access antilo.de. antilo | Die smarte Telefonie-Cloud

Report Summary

About Website

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

Sichere und unabhängige Telefonanlagen in der Cloud. ☁️ Individuelle und passgenaue Lösungen für Ihre Telefonie! ✔️☎️

Visit antilo.de

name

value

score

weighting

FCP (First Contentful Paint)

Value9.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.8 s

0/100

25%

SI (Speed Index)

Value15.4 s

0/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value26.8 s

0/100

10%

www.antilo.de

1442 ms

style.min.css

400 ms

styles.css

205 ms

cookielay.css

387 ms

all.css

690 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 89% of them (64 requests) were addressed to the original Antilo.de, 4% (3 requests) were made to Gstatic.com and 3% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Antilo.de.

Content Size

5.8 MB

After Optimization

4.2 MB

In fact, the total size of Antilo.de main page is 5.8 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 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 74.4 kB

Original 87.1 kB
After minification 67.8 kB
After compression 12.7 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 19.3 kB, which is 22% 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 74.4 kB or 85% of the original size.

Image Optimization

-11%

Potential reduce by 454.2 kB

Original 4.2 MB
After minification 3.7 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. Obviously, Antilo needs image optimization as it can save up to 454.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-56%

Potential reduce by 536.0 kB

Original 965.4 kB
After minification 965.4 kB
After compression 429.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 536.0 kB or 56% of the original size.

CSS Optimization

-87%

Potential reduce by 489.3 kB

Original 564.9 kB
After minification 469.2 kB
After compression 75.6 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. Antilo.de needs all CSS files to be minified and compressed as it can save up to 489.3 kB or 87% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

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/).

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

antilo.de

Open Graph data is detected on the main page of Antilo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

antilo | Die smarte Telefonie-Cloud | Telefonanlagen hier anfragen

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)