Tools & Wizards About Us
agilis.de screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

agilis.de

Start - agilis Verkehrsgesellschaft mbH & Co. KG

Page Load Speed

11.1 sec in total

First Response

741 ms

Resources Loaded

6.5 sec

Page Rendered

3.8 sec

agilis.de screenshot

About Website

Welcome to agilis.de homepage info - get ready to check Agilis best content for Germany right away, or after learning these important things about agilis.de

Ihre Bahn in der Region.

Visit agilis.de

Key Findings

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

Performance Metrics

agilis.de performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

www.agilis.de

741 ms

jquery-3.1.1.min.js

136 ms

isotope.pkgd.min.js

275 ms

styles.css

448 ms

sbi-styles.min.css

445 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 95% of them (62 requests) were addressed to the original Agilis.de, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Agilis.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 280.1 kB (12%)

Content Size

2.3 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 214.8 kB

  • Original 244.3 kB
  • After minification 188.4 kB
  • After compression 29.4 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 55.9 kB, which is 23% 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 214.8 kB or 88% of the original size.

Image Optimization

-3%

Potential reduce by 53.5 kB

  • Original 1.8 MB
  • After minification 1.8 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. Agilis images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 3.0 kB

  • Original 109.6 kB
  • After minification 109.5 kB
  • After compression 106.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. This website has mostly compressed JavaScripts.

CSS Optimization

-6%

Potential reduce by 8.7 kB

  • Original 143.2 kB
  • After minification 143.2 kB
  • After compression 134.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. Agilis.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (67%)

Requests Now

61

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.agilis.de

www.agilis.de

741 ms

jquery-3.1.1.min.js

jquery-3.1.1.min.js

136 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

275 ms

styles.css

styles.css

448 ms

sbi-styles.min.css

sbi-styles.min.css

445 ms

style.min.css

style.min.css

425 ms

styles.css

styles.css

472 ms

video-js.min.css

video-js.min.css

456 ms

style.css

style.css

454 ms

borlabs-cookie_1_de.css

borlabs-cookie_1_de.css

471 ms

default.min.css

default.min.css

474 ms

js_composer.min.css

js_composer.min.css

665 ms

jquery.min.js

jquery.min.js

488 ms

jquery-migrate.min.js

jquery-migrate.min.js

475 ms

rbtools.min.js

rbtools.min.js

578 ms

rs6.min.js

rs6.min.js

890 ms

wpgmza_data.js

wpgmza_data.js

588 ms

borlabs-cookie-prioritize.min.js

borlabs-cookie-prioritize.min.js

594 ms

css

css

203 ms

font-awesome.css

font-awesome.css

592 ms

wp-lightbox-bank.css

wp-lightbox-bank.css

707 ms

js_composer_tta.min.css

js_composer_tta.min.css

688 ms

lightbox.min.css

lightbox.min.css

688 ms

rs6.css

rs6.css

709 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

747 ms

wp-polyfill.min.js

wp-polyfill.min.js

784 ms

index.js

index.js

806 ms

video.min.js

video.min.js

1834 ms

navigation.js

navigation.js

817 ms

agilis.js

agilis.js

848 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

888 ms

wp-lightbox-bank.js

wp-lightbox-bank.js

910 ms

js_composer_front.min.js

js_composer_front.min.js

934 ms

vc-accordion.min.js

vc-accordion.min.js

970 ms

vc-tta-autoplay.min.js

vc-tta-autoplay.min.js

984 ms

lightbox.min.js

lightbox.min.js

1004 ms

borlabs-cookie.min.js

borlabs-cookie.min.js

1026 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

694 ms

font-awesome.min.css

font-awesome.min.css

660 ms

grid24.css

grid24.css

670 ms

main.css

main.css

716 ms

responsive.css

responsive.css

724 ms

print.css

print.css

754 ms

gtm.js

gtm.js

497 ms

agilis-logo-mit-vogel-head.png

agilis-logo-mit-vogel-head.png

894 ms

ag_birds_bgtop.png

ag_birds_bgtop.png

457 ms

ag_consearch_border.png

ag_consearch_border.png

417 ms

dummy.png

dummy.png

418 ms

ag_zuege_netz_mitte.png

ag_zuege_netz_mitte.png

455 ms

warn_magenta.png

warn_magenta.png

455 ms

ag_zuege_netz_nord.png

ag_zuege_netz_nord.png

453 ms

QM-Post_Tag-der-Schiene_22.08.22-1_news.png

QM-Post_Tag-der-Schiene_22.08.22-1_news.png

1299 ms

Grafik_Homepage.png

Grafik_Homepage.png

630 ms

AGILIS2.jpg

AGILIS2.jpg

954 ms

agilis-in-Oberfranken_Beitragsbild_Copyright-Uwe-Miethe.jpg

agilis-in-Oberfranken_Beitragsbild_Copyright-Uwe-Miethe.jpg

815 ms

fb_icon_footer.png

fb_icon_footer.png

520 ms

Instagram_footer.png

Instagram_footer.png

521 ms

EtelkaText.woff

EtelkaText.woff

391 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

392 ms

ag_bird_titletext.png

ag_bird_titletext.png

186 ms

ag_netz_mitte.png

ag_netz_mitte.png

188 ms

ag_netz_nord.png

ag_netz_nord.png

342 ms

ag_birds_bg.png

ag_birds_bg.png

130 ms

ag_birds2_footer.png

ag_birds2_footer.png

116 ms

EtelkaText-Bold.woff

EtelkaText-Bold.woff

272 ms

Accessibility Review

agilis.de accessibility score

84

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

High

Some elements have a [tabindex] value greater than 0

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

agilis.de best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

agilis.de SEO score

93

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

Image elements do not have [alt] attributes

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

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

agilis.de

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