3.2 sec in total
290 ms
2.7 sec
234 ms
Click here to check amazing Taxi content for Germany. Otherwise, check out these important facts you probably never knew about taxi.de
Bestellen oder reservieren Sie Ihr Taxi oder laden Sie die gratis Taxi.de App. Einfach ✓ Zuverlässig ✓ Schnell ✓ ▶ Jetzt Taxi bestellen.
Visit taxi.deWe analyzed Taxi.de page load time and found that the first response time was 290 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
taxi.de performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value22.7 s
0/100
25%
Value10.8 s
6/100
10%
Value340 ms
74/100
30%
Value0
100/100
15%
Value16.8 s
5/100
10%
290 ms
542 ms
459 ms
275 ms
274 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 88% of them (42 requests) were addressed to the original Taxi.de, 4% (2 requests) were made to Googleadservices.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Taxi.de.
Page size can be reduced by 497.7 kB (43%)
1.2 MB
670.1 kB
In fact, the total size of Taxi.de main page is 1.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. 30% of websites need less resources to load. Images take 582.6 kB which makes up the majority of the site volume.
Potential reduce by 18.0 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 18.0 kB or 68% of the original size.
Potential reduce by 89.1 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, Taxi needs image optimization as it can save up to 89.1 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 338.0 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 338.0 kB or 68% of the original size.
Potential reduce by 52.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. Taxi.de needs all CSS files to be minified and compressed as it can save up to 52.7 kB or 82% of the original size.
Number of requests can be reduced by 15 (36%)
42
27
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
taxi.de
290 ms
www.taxi.de
542 ms
application-623c0e55ee1602d852f6a62fe85247cb.js
459 ms
jquery.smartbanner.css
275 ms
jquery.smartbanner.js
274 ms
basic-jquery-slider.css
185 ms
jquery-ui-1.8.21.custom.css
477 ms
style.css
476 ms
custom-form-elements.js
274 ms
jquery-ui-1.10.0.custom.min.js
1040 ms
jquery.validate.js
547 ms
jquery-ui-sliderAccess.js
366 ms
jquery-ui-timepicker-addon.js
731 ms
basic-jquery-slider.js
546 ms
place.js
552 ms
static-86093971c9c628758a68574a16d6e3fc.css
555 ms
order.js
556 ms
conversion.js
22 ms
ga.js
61 ms
logo.png
188 ms
bg-nav.png
93 ms
nav-divider.jpg
187 ms
bg-input-txt.png
93 ms
ubuntu-m-webfont.woff
313 ms
ubuntu-l-webfont.woff
183 ms
passenger.png
176 ms
slider-image2.png
268 ms
slider_order.png
815 ms
phone.png
270 ms
online.png
272 ms
check.png
274 ms
icon-facebook.png
359 ms
icon-twitter.png
363 ms
icon-google.png
364 ms
minitaxi.png
365 ms
back-to-top.jpg
403 ms
bg-slider.jpg
537 ms
bg-main-body-bottom.jpg
814 ms
bg-newsletter.png
444 ms
bg-btn-black.png
442 ms
logo-car.jpg
480 ms
62 ms
ui-bg_highlight-soft_100_eeeeee_1x100.png
502 ms
ui-bg_gloss-wave_35_fece00_500x100.png
505 ms
ui-bg_glass_100_f6f6f6_1x400.png
539 ms
__utm.gif
13 ms
69 ms
49 ms
taxi.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
taxi.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
taxi.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Taxi.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Taxi.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.
taxi.de
Open Graph data is detected on the main page of Taxi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: