Tools & Wizards About Us
prepaid.es screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    86% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

prepaid.es

PREPAID.es seit mehr als 20 Jahren Ihr Spezialist und Dienstleister rund um die preiswerten spanischen Prepaid SIM-Karten

Page Load Speed

4.5 sec in total

First Response

373 ms

Resources Loaded

3.9 sec

Page Rendered

202 ms

prepaid.es screenshot

About Website

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

preiswert im spanien urlaub vom handy telefonieren mit der gsm prepaid karte von airtel vodafone - keine roaming gebühr - geld sparen

Visit prepaid.es

Key Findings

We analyzed Prepaid.es page load time and found that the first response time was 373 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

prepaid.es performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value4.1 s

78/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.138

79/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

prepaid.es

373 ms

reset.css

108 ms

fonts.css

214 ms

jquery-ui-1.8.11.custom.css

222 ms

menu.css

212 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 94% of them (62 requests) were addressed to the original Prepaid.es, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Prepaid.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 504.6 kB (30%)

Content Size

1.7 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prepaid.es main page is 1.7 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 35.7 kB

  • Original 43.6 kB
  • After minification 42.0 kB
  • After compression 7.9 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 35.7 kB or 82% of the original size.

Image Optimization

-11%

Potential reduce by 136.7 kB

  • Original 1.2 MB
  • After minification 1.1 MB

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, Prepaid needs image optimization as it can save up to 136.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 263.8 kB

  • Original 370.4 kB
  • After minification 354.7 kB
  • After compression 106.6 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 263.8 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 68.5 kB

  • Original 82.0 kB
  • After minification 62.5 kB
  • After compression 13.5 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. Prepaid.es needs all CSS files to be minified and compressed as it can save up to 68.5 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

65

After Optimization

51

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

prepaid.es

prepaid.es

373 ms

reset.css

reset.css

108 ms

fonts.css

fonts.css

214 ms

jquery-ui-1.8.11.custom.css

jquery-ui-1.8.11.custom.css

222 ms

menu.css

menu.css

212 ms

font-awesome.css

font-awesome.css

5 ms

screen.css

screen.css

219 ms

style.css

style.css

223 ms

jquery-1.7.min.js

jquery-1.7.min.js

1007 ms

jquery-ui-1.8.11.custom.min.js

jquery-ui-1.8.11.custom.min.js

553 ms

hoverIntent.js

hoverIntent.js

316 ms

jquery.gradient.js

jquery.gradient.js

328 ms

jquery.corner.js

jquery.corner.js

330 ms

jquery.cookie.js

jquery.cookie.js

325 ms

style.css

style.css

422 ms

ga.js

ga.js

47 ms

css

css

94 ms

1.png

1.png

417 ms

banner-all.gif

banner-all.gif

2179 ms

frage-150-www.prepaid.es.png

frage-150-www.prepaid.es.png

803 ms

versand-150-www.prepaid.es.png

versand-150-www.prepaid.es.png

787 ms

standardversand-www.prepaid.es.png

standardversand-www.prepaid.es.png

1960 ms

schnellversand-www.prepaid.es.png

schnellversand-www.prepaid.es.png

1981 ms

sofortversand.png

sofortversand.png

2000 ms

zahlung-150-www.prepaid.es.png

zahlung-150-www.prepaid.es.png

893 ms

barzahlung-www.prepaid.es.png

barzahlung-www.prepaid.es.png

907 ms

postbank-www.prepaid.es.png

postbank-www.prepaid.es.png

998 ms

lacaixa-www.prepaid.es.png

lacaixa-www.prepaid.es.png

1013 ms

visa-www.prepaid.es.png

visa-www.prepaid.es.png

1105 ms

vcard-www.prepaid.es.png

vcard-www.prepaid.es.png

1225 ms

aufladung-aller-spanischen-prepaid-sim-karten.gif

aufladung-aller-spanischen-prepaid-sim-karten.gif

2460 ms

2.png

2.png

639 ms

3.png

3.png

621 ms

4.png

4.png

448 ms

5.png

5.png

522 ms

6.png

6.png

423 ms

7.png

7.png

788 ms

startseite1.png

startseite1.png

529 ms

warenkorb.gif

warenkorb.gif

561 ms

webshop2.png

webshop2.png

627 ms

hitsmobile-farbig.png

hitsmobile-farbig.png

633 ms

handy.png

handy.png

671 ms

smartphone.png

smartphone.png

724 ms

tabs.png

tabs.png

731 ms

mifi.png

mifi.png

738 ms

lebara-holiday.png

lebara-holiday.png

744 ms

www2.gif

www2.gif

781 ms

vodafdone.png

vodafdone.png

828 ms

compare.png

compare.png

835 ms

nachladen.png

nachladen.png

843 ms

download.png

download.png

851 ms

adobe.png

adobe.png

891 ms

netzempfang.png

netzempfang.png

889 ms

hitsmobile-farbig1.png

hitsmobile-farbig1.png

932 ms

lycamobile.png

lycamobile.png

939 ms

abholung.png

abholung.png

947 ms

kontakt.png

kontakt.png

958 ms

agb.png

agb.png

992 ms

newsletter.png

newsletter.png

1001 ms

faq.png

faq.png

1036 ms

versand.png

versand.png

1042 ms

cash.png

cash.png

1051 ms

1027.png

1027.png

1064 ms

bg-display.png

bg-display.png

1096 ms

mainbk.png

mainbk.png

1111 ms

__utm.gif

__utm.gif

15 ms

Accessibility Review

prepaid.es accessibility score

88

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

prepaid.es best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

prepaid.es SEO score

83

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

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

    ISO-8859-1

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

prepaid.es

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