Report Summary

  • 59

    Performance

    Renders faster than
    75% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

prepaider.com

Prepaid Vergleich - 4 Knaller-Prepaid Tarife aus allen Netzen - Prepaid Tarife Vergleich

Page Load Speed

629 ms in total

First Response

248 ms

Resources Loaded

256 ms

Page Rendered

125 ms

prepaider.com screenshot

About Website

Click here to check amazing Prepaid Er content. Otherwise, check out these important facts you probably never knew about prepaider.com

Visit prepaider.com

Key Findings

We analyzed Prepaider.com page load time and found that the first response time was 248 ms and then it took 381 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

prepaider.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.073

96/100

15%

TTI (Time to Interactive)

Value7.4 s

49/100

10%

Network Requests Diagram

prepaider.com

248 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 205 B (36%)

Content Size

562 B

After Optimization

357 B

In fact, the total size of Prepaider.com main page is 562 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 562 B which makes up the majority of the site volume.

HTML Optimization

-36%

Potential reduce by 205 B

  • Original 562 B
  • After minification 543 B
  • After compression 357 B

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 205 B or 36% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

prepaider.com accessibility score

94

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

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

Links do not have a discernible name

Best Practices

prepaider.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

prepaider.com SEO score

76

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prepaider.com 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 Prepaider.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Prepaid Er. 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: