Tools & Wizards About Us
tanken.de screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 94

    SEO

    Google-friendlier than
    90% of websites

tanken.de

Tanken sie günstig mit den aktuellen Benzinpreisen auf tanken.de

Page Load Speed

2.6 sec in total

First Response

230 ms

Resources Loaded

1.9 sec

Page Rendered

505 ms

tanken.de screenshot

About Website

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

Finden sie auf tanken.de die günstigsten und billigsten Spritpreise für Super E5, Super E10 und Diesel an Tankstellen in der Umgebung

Visit tanken.de

Key Findings

We analyzed Tanken.de page load time and found that the first response time was 230 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

tanken.de performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value5,150 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

tanken.de

230 ms

tanken.de

527 ms

80gnh.css

110 ms

80gnh.css

218 ms

80gnh.css

290 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 71% of them (20 requests) were addressed to the original Tanken.de, 7% (2 requests) were made to Gravatar.com and 7% (2 requests) were made to . The less responsive or slowest element that took the longest time to load (527 ms) belongs to the original domain Tanken.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 182.3 kB (34%)

Content Size

533.4 kB

After Optimization

351.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tanken.de main page is 533.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. HTML takes 216.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 178.4 kB

  • Original 216.0 kB
  • After minification 211.7 kB
  • After compression 37.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. 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 178.4 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 2.3 kB

  • Original 39.1 kB
  • After minification 36.8 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. Tanken images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 78 B

  • Original 187.5 kB
  • After minification 187.5 kB
  • After compression 187.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

-2%

Potential reduce by 1.5 kB

  • Original 90.8 kB
  • After minification 90.8 kB
  • After compression 89.3 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. Tanken.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (58%)

Requests Now

24

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tanken. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tanken.de

tanken.de

230 ms

tanken.de

tanken.de

527 ms

80gnh.css

80gnh.css

110 ms

80gnh.css

80gnh.css

218 ms

80gnh.css

80gnh.css

290 ms

80gnh.css

80gnh.css

393 ms

80gnh.js

80gnh.js

400 ms

jscripts.php

jscripts.php

307 ms

adsbygoogle.js

adsbygoogle.js

46 ms

js

js

71 ms

hoverintent-js.min.js

hoverintent-js.min.js

309 ms

admin-bar.min.js

admin-bar.min.js

318 ms

navigation.min.js

navigation.min.js

387 ms

skip-link-focus-fix.min.js

skip-link-focus-fix.min.js

464 ms

comment-reply.min.js

comment-reply.min.js

465 ms

catchbase-scrollup.min.js

catchbase-scrollup.min.js

465 ms

jscripts-ftr-min.js

jscripts-ftr-min.js

527 ms

2764dcf3b3e1e0cb26cd2869ec77cc02

2764dcf3b3e1e0cb26cd2869ec77cc02

89 ms

b2f8f841b663c5b718f6b9def984572d

b2f8f841b663c5b718f6b9def984572d

88 ms

tanken-300x200.jpg

tanken-300x200.jpg

109 ms

wann-tankt-man-am-g%C3%BCnstigsten-300x195.jpg

wann-tankt-man-am-g%C3%BCnstigsten-300x195.jpg

108 ms

6b573c216cda30b6e4570508c3746c3e

6b573c216cda30b6e4570508c3746c3e

89 ms

Genericons.svg

Genericons.svg

210 ms

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

41 ms

wARDj0u

wARDj0u

41 ms

tank2.htm

tank2.htm

132 ms

js

js

89 ms

gps.JPG

gps.JPG

473 ms

Accessibility Review

tanken.de accessibility score

92

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

High

Page has valid source maps

SEO Factors

tanken.de SEO score

94

Search Engine Optimization Advices

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tanken.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 Tanken.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

tanken.de

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