Tools & Wizards About Us
prepaidtarife.net screenshot

Report Summary

  • 94

    Performance

    Renders faster than
    93% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

prepaidtarife.net

Prepaid Tarife Vergleich, SONDERAKTIONEN! - prepaidtarife.net

Page Load Speed

3.7 sec in total

First Response

758 ms

Resources Loaded

2.8 sec

Page Rendered

177 ms

prepaidtarife.net screenshot

About Website

Visit prepaidtarife.net now to see the best up-to-date Prepaid Tarife content for Germany and also check out these interesting facts you probably never knew about prepaidtarife.net

Prepaid Tarife Vergleich 2014 ▷ Übersichtlicher Vergleich ✓ keine Grundgebühr ✓ kein Vertrag ✓ Günstigste Minutenpreise ✓ Die Prepaid Tarife Testsieger im Vergleich

Visit prepaidtarife.net

Key Findings

We analyzed Prepaidtarife.net page load time and found that the first response time was 758 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

prepaidtarife.net performance score

94

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

94/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

prepaidtarife.net

758 ms

wp-emoji-release.min.js

136 ms

gdsr.css.php

262 ms

jquery.js

499 ms

jquery-migrate.min.js

426 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that all of those requests were addressed to Prepaidtarife.net and no external sources were called. The less responsive or slowest element that took the longest time to load (758 ms) belongs to the original domain Prepaidtarife.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.4 kB (22%)

Content Size

128.4 kB

After Optimization

100.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prepaidtarife.net main page is 128.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. Javascripts take 45.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 25.7 kB

  • Original 32.4 kB
  • After minification 31.7 kB
  • After compression 6.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 25.7 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 96 B

  • Original 37.8 kB
  • After minification 37.7 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. Prepaid Tarife images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 88 B

  • Original 45.4 kB
  • After minification 45.4 kB
  • After compression 45.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

-19%

Potential reduce by 2.5 kB

  • Original 12.7 kB
  • After minification 12.7 kB
  • After compression 10.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. Prepaidtarife.net needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (42%)

Requests Now

38

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

prepaidtarife.net

prepaidtarife.net

758 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

136 ms

gdsr.css.php

gdsr.css.php

262 ms

jquery.js

jquery.js

499 ms

jquery-migrate.min.js

jquery-migrate.min.js

426 ms

gdsr.js

gdsr.js

441 ms

tablecloth.css

tablecloth.css

455 ms

tablecloth.js

tablecloth.js

736 ms

style.css

style.css

446 ms

layout.css

layout.css

533 ms

ie.css

ie.css

549 ms

custom.css

custom.css

554 ms

plugin.css

plugin.css

617 ms

comment-reply.min.js

comment-reply.min.js

614 ms

wp-embed.min.js

wp-embed.min.js

676 ms

prepaidtarife.jpg

prepaidtarife.jpg

151 ms

prepaid-handy.jpg

prepaid-handy.jpg

243 ms

tr_back.gif

tr_back.gif

110 ms

congstar1.gif

congstar1.gif

133 ms

congstar.gif

congstar.gif

133 ms

d1.gif

d1.gif

134 ms

bestellen.png

bestellen.png

219 ms

klarmobil.gif

klarmobil.gif

240 ms

d2.gif

d2.gif

241 ms

simyo.gif

simyo.gif

240 ms

e+.gif

e+.gif

257 ms

callya.jpg

callya.jpg

326 ms

discotel.gif

discotel.gif

392 ms

o2.gif

o2.gif

366 ms

mcsim.jpg

mcsim.jpg

393 ms

blau.gif

blau.gif

372 ms

maxxim.gif

maxxim.gif

373 ms

hellomobil.gif

hellomobil.gif

433 ms

simply.gif

simply.gif

473 ms

allmobil.gif

allmobil.gif

479 ms

callmobile.gif

callmobile.gif

480 ms

bildmobil.gif

bildmobil.gif

499 ms

xtra.gif

xtra.gif

498 ms

otelo.png

otelo.png

559 ms

stars24.png

stars24.png

598 ms

Accessibility Review

prepaidtarife.net accessibility score

90

Accessibility Issues

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

prepaidtarife.net best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

prepaidtarife.net SEO score

71

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Prepaidtarife.net 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 Prepaidtarife.net 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

prepaidtarife.net

Open Graph description is not detected on the main page of Prepaid Tarife. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: