Tools & Wizards About Us
giropay.de screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

giropay.de

Online bezahlen mit giropay - direkt vom Girokonto

Page Load Speed

3.8 sec in total

First Response

586 ms

Resources Loaded

2.7 sec

Page Rendered

570 ms

giropay.de screenshot

About Website

Click here to check amazing Giropay content for Germany. Otherwise, check out these important facts you probably never knew about giropay.de

giropay ist das Online-Zahlverfahren der deutschen Banken und Sparkassen. Vertraue den Sicherheits- und Datenschutzstandards des Online-Bankings.

Visit giropay.de

Key Findings

We analyzed Giropay.de page load time and found that the first response time was 586 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

giropay.de performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value6.2 s

63/100

10%

Network Requests Diagram

www.giropay.de

586 ms

config.js

121 ms

klaro.js

447 ms

webtrekk_config.js

452 ms

cookie.js

463 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 215.9 kB (14%)

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Giropay.de main page is 1.6 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. 35% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 31.7 kB

  • Original 37.8 kB
  • After minification 30.6 kB
  • After compression 6.1 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. This page needs HTML code to be minified as it can gain 7.1 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 31.7 kB or 84% of the original size.

Image Optimization

-11%

Potential reduce by 150.8 kB

  • Original 1.4 MB
  • After minification 1.2 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, Giropay needs image optimization as it can save up to 150.8 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

-15%

Potential reduce by 17.8 kB

  • Original 118.7 kB
  • After minification 118.7 kB
  • After compression 101.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 17.8 kB or 15% of the original size.

CSS Optimization

-30%

Potential reduce by 15.8 kB

  • Original 52.0 kB
  • After minification 52.0 kB
  • After compression 36.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. Giropay.de needs all CSS files to be minified and compressed as it can save up to 15.8 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (19%)

Requests Now

37

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.giropay.de

www.giropay.de

586 ms

config.js

config.js

121 ms

klaro.js

klaro.js

447 ms

webtrekk_config.js

webtrekk_config.js

452 ms

cookie.js

cookie.js

463 ms

fontawesome-5.15.3.min.css

fontawesome-5.15.3.min.css

451 ms

slick.dotsass

slick.dotsass

477 ms

styles.dotsass

styles.dotsass

574 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

670 ms

slick.min.js

slick.min.js

549 ms

myfunction.js

myfunction.js

548 ms

slider.js

slider.js

547 ms

giropay_miniPad_quer_RGB_60px.svg

giropay_miniPad_quer_RGB_60px.svg

211 ms

brezel-story.jpg

brezel-story.jpg

777 ms

brezel-hd2.jpg

brezel-hd2.jpg

676 ms

bezahlen-wie-du-moechtest-screen.jpg

bezahlen-wie-du-moechtest-screen.jpg

387 ms

bwbank.png

bwbank.png

366 ms

comdirect.png

comdirect.png

364 ms

commerzbank.png

commerzbank.png

366 ms

deutsche-bank.png

deutsche-bank.png

368 ms

mlp.png

mlp.png

367 ms

norisbank.png

norisbank.png

392 ms

postbank.png

postbank.png

463 ms

psdbank.png

psdbank.png

463 ms

sparda-bank.png

sparda-bank.png

483 ms

sparkasse.png

sparkasse.png

489 ms

volksbanken-raiffeisenbanken.png

volksbanken-raiffeisenbanken.png

561 ms

1822-direkt.png

1822-direkt.png

562 ms

bbbank.png

bbbank.png

585 ms

helaba.png

helaba.png

586 ms

pressebild-esso-giropay.jpg

pressebild-esso-giropay.jpg

1177 ms

a-ries.jpg

a-ries.jpg

1059 ms

signets-banken.png

signets-banken.png

683 ms

facebook.svg

facebook.svg

684 ms

xing.svg

xing.svg

771 ms

linkedin.svg

linkedin.svg

780 ms

giropay_miniPad_quer_transparent_RGB_60px.svg

giropay_miniPad_quer_transparent_RGB_60px.svg

783 ms

GiroSansPro-Light.woff

GiroSansPro-Light.woff

941 ms

GiroSansPro-ExtraLight.woff

GiroSansPro-ExtraLight.woff

746 ms

GiroSansPro-Regular.woff

GiroSansPro-Regular.woff

755 ms

GiroSansPro-Semibold.woff

GiroSansPro-Semibold.woff

849 ms

GiroSansPro-Bold.woff

GiroSansPro-Bold.woff

1052 ms

GiroSansPro-Black.woff

GiroSansPro-Black.woff

1091 ms

cookieicon.svg

cookieicon.svg

823 ms

Accessibility Review

giropay.de accessibility score

69

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

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

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

Image elements do not have [alt] attributes

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

giropay.de best practices score

75

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

Browser errors were logged to the console

SEO Factors

giropay.de SEO score

82

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Giropay.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Giropay.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

giropay.de

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