Tools & Wizards About Us
rheintaxi.de screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% 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

  • 93

    SEO

    Google-friendlier than
    83% of websites

rheintaxi.de

RHEIN-TAXI Düsseldorf · ☎ 212121 · Auf die nette Tour...

Page Load Speed

7.5 sec in total

First Response

363 ms

Resources Loaded

7 sec

Page Rendered

169 ms

rheintaxi.de screenshot

About Website

Click here to check amazing RHEIN TAXI content. Otherwise, check out these important facts you probably never knew about rheintaxi.de

Bestellen Sie Ihr Rhein-Taxi Düsseldorf ganz bequem per Telefon (0211)212121, App, Autobooking, Kundenportal oder direkt auf unserer Webseite!

Visit rheintaxi.de

Key Findings

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

Performance Metrics

rheintaxi.de performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value19.8 s

0/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.104

88/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

rheintaxi.de

363 ms

www.rhein-taxi.de

2649 ms

kalender-digital-public.css

220 ms

frontend.min.css

338 ms

flatpickr.min.css

335 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Rheintaxi.de, 99% (93 requests) were made to Rhein-taxi.de. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Rhein-taxi.de.

Page Optimization Overview & Recommendations

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

Content Size

1.1 MB

After Optimization

920.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rheintaxi.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. 50% of websites need less resources to load. Javascripts take 420.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 98.6 kB

  • Original 123.1 kB
  • After minification 120.3 kB
  • After compression 24.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 98.6 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 13.0 kB

  • Original 243.2 kB
  • After minification 230.2 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. RHEIN TAXI images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.2 kB

  • Original 420.6 kB
  • After minification 420.1 kB
  • After compression 419.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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 19.6 kB

  • Original 265.9 kB
  • After minification 250.2 kB
  • After compression 246.2 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. Rheintaxi.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 82 (92%)

Requests Now

89

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rheintaxi.de

rheintaxi.de

363 ms

www.rhein-taxi.de

www.rhein-taxi.de

2649 ms

kalender-digital-public.css

kalender-digital-public.css

220 ms

frontend.min.css

frontend.min.css

338 ms

flatpickr.min.css

flatpickr.min.css

335 ms

select2.min.css

select2.min.css

336 ms

cookieblocker.min.css

cookieblocker.min.css

333 ms

style.css

style.css

335 ms

layout-styles.css

layout-styles.css

336 ms

frontend.css

frontend.css

445 ms

5821887bb01614b9a4addbe7413006c5.min.css

5821887bb01614b9a4addbe7413006c5.min.css

919 ms

jquery.min.js

jquery.min.js

567 ms

jquery-migrate.min.js

jquery-migrate.min.js

445 ms

frontend.js

frontend.js

443 ms

kalender-digital-public.js

kalender-digital-public.js

446 ms

rbtools.min.js

rbtools.min.js

786 ms

rs6.min.js

rs6.min.js

913 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

557 ms

add-to-cart.min.js

add-to-cart.min.js

557 ms

js.cookie.min.js

js.cookie.min.js

670 ms

woocommerce.min.js

woocommerce.min.js

669 ms

flatpickr.min.js

flatpickr.min.js

682 ms

select2.min.js

select2.min.js

788 ms

wc-blocks.css

wc-blocks.css

677 ms

style.min.css

style.min.css

692 ms

rs6.css

rs6.css

907 ms

index.js

index.js

790 ms

index.js

index.js

793 ms

sourcebuster.min.js

sourcebuster.min.js

804 ms

order-attribution.min.js

order-attribution.min.js

907 ms

frontend.min.js

frontend.min.js

908 ms

complianz.min.js

complianz.min.js

927 ms

fusion-column.js

fusion-column.js

926 ms

awb-tabs-widget.js

awb-tabs-widget.js

927 ms

awb-vertical-menu-widget.js

awb-vertical-menu-widget.js

1012 ms

cssua.js

cssua.js

1013 ms

modernizr.js

modernizr.js

1019 ms

fusion.js

fusion.js

1063 ms

swiper.js

swiper.js

955 ms

bootstrap.transition.js

bootstrap.transition.js

840 ms

bootstrap.tooltip.js

bootstrap.tooltip.js

899 ms

jquery.requestAnimationFrame.js

jquery.requestAnimationFrame.js

900 ms

jquery.easing.js

jquery.easing.js

900 ms

jquery.fitvids.js

jquery.fitvids.js

914 ms

jquery.flexslider.js

jquery.flexslider.js

918 ms

jquery.ilightbox.js

jquery.ilightbox.js

840 ms

jquery.mousewheel.js

jquery.mousewheel.js

902 ms

jquery.placeholder.js

jquery.placeholder.js

900 ms

jquery.fade.js

jquery.fade.js

901 ms

fusion-equal-heights.js

fusion-equal-heights.js

802 ms

fusion-parallax.js

fusion-parallax.js

809 ms

fusion-video-general.js

fusion-video-general.js

831 ms

fusion-video-bg.js

fusion-video-bg.js

788 ms

fusion-lightbox.js

fusion-lightbox.js

786 ms

fusion-tooltip.js

fusion-tooltip.js

774 ms

fusion-sharing-box.js

fusion-sharing-box.js

688 ms

jquery.sticky-kit.js

jquery.sticky-kit.js

693 ms

avada-woo-variations.js

avada-woo-variations.js

720 ms

avada-general-footer.js

avada-general-footer.js

769 ms

avada-quantity.js

avada-quantity.js

671 ms

avada-crossfade-images.js

avada-crossfade-images.js

669 ms

avada-select.js

avada-select.js

670 ms

avada-contact-form-7.js

avada-contact-form-7.js

676 ms

avada-privacy.js

avada-privacy.js

608 ms

avada-live-search.js

avada-live-search.js

665 ms

fusion-alert.js

fusion-alert.js

664 ms

awb-off-canvas.js

awb-off-canvas.js

662 ms

fusion-flexslider.js

fusion-flexslider.js

659 ms

fusion-column-legacy.js

fusion-column-legacy.js

666 ms

awb-background-slider.js

awb-background-slider.js

698 ms

jquery.textillate.js

jquery.textillate.js

669 ms

fusion-title.js

fusion-title.js

665 ms

fusion-button.js

fusion-button.js

621 ms

fusion-container.js

fusion-container.js

632 ms

avada-to-top.js

avada-to-top.js

637 ms

avada-header.js

avada-header.js

672 ms

avada-menu.js

avada-menu.js

669 ms

bootstrap.scrollspy.js

bootstrap.scrollspy.js

667 ms

avada-scrollspy.js

avada-scrollspy.js

667 ms

avada-woo-products.js

avada-woo-products.js

666 ms

avada-woocommerce.js

avada-woocommerce.js

669 ms

avada-woo-product-images.js

avada-woo-product-images.js

670 ms

fusion-responsive-typography.js

fusion-responsive-typography.js

667 ms

fusion-scroll-to-anchor.js

fusion-scroll-to-anchor.js

668 ms

fusion-general-global.js

fusion-general-global.js

668 ms

fusion-video.js

fusion-video.js

667 ms

awb-icons.woff

awb-icons.woff

700 ms

fa-solid-900.woff

fa-solid-900.woff

780 ms

fa-regular-400.woff

fa-regular-400.woff

668 ms

RHEIN-TAXI_logo.png

RHEIN-TAXI_logo.png

775 ms

dummy.png

dummy.png

671 ms

RT_BestellWidget.jpg

RT_BestellWidget.jpg

667 ms

RHEIN-TAXI_logo-e1531823907436.png

RHEIN-TAXI_logo-e1531823907436.png

669 ms

bg_flughafenDus.jpg

bg_flughafenDus.jpg

278 ms

Accessibility Review

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

rheintaxi.de best practices score

83

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

High

Browser errors were logged to the console

SEO Factors

rheintaxi.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 Rheintaxi.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 Rheintaxi.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

rheintaxi.de

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