Tools & Wizards About Us
developer.db.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

developer.db.com

Open Banking | Beyond PSD2 | Deutsche Bank API Program

Page Load Speed

746 ms in total

First Response

117 ms

Resources Loaded

573 ms

Page Rendered

56 ms

developer.db.com screenshot

About Website

Visit developer.db.com now to see the best up-to-date Developer Db content for Italy and also check out these interesting facts you probably never knew about developer.db.com

Grow your digital business with Deutsche Bank API Products: Instant Payment, Identity Verification, Access to Own Account, +17 more. Join free in seconds.

Visit developer.db.com

Key Findings

We analyzed Developer.db.com page load time and found that the first response time was 117 ms and then it took 629 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

developer.db.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value2,330 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

developer.db.com

117 ms

api.js

28 ms

webtrekk_v4.min.js

108 ms

webtrack_config.js

107 ms

devportal_config.json

104 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 82% of them (9 requests) were addressed to the original Developer.db.com, 9% (1 request) were made to Google.com and 9% (1 request) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (235 ms) belongs to the original domain Developer.db.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 12.1 kB (1%)

Content Size

1.6 MB

After Optimization

1.6 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Developer.db.com main page is 1.6 MB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 10.6 kB

  • Original 13.7 kB
  • After minification 13.6 kB
  • After compression 3.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. 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 10.6 kB or 77% of the original size.

JavaScript Optimization

-0%

Potential reduce by 1.5 kB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 1.6 MB

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

-0%

Potential reduce by 0 B

  • Original 43.3 kB
  • After minification 43.3 kB
  • After compression 43.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. Developer.db.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

10

After Optimization

3

  • AJAX
  • JavaScript
  • CSS

The browser has sent 10 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Developer Db. 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

developer.db.com

developer.db.com

117 ms

api.js

api.js

28 ms

webtrekk_v4.min.js

webtrekk_v4.min.js

108 ms

webtrack_config.js

webtrack_config.js

107 ms

devportal_config.json

devportal_config.json

104 ms

runtime.0b041b57d36e3d80.js

runtime.0b041b57d36e3d80.js

105 ms

polyfills.9fffba75baae0451.js

polyfills.9fffba75baae0451.js

152 ms

scripts.358597538e78e2e0.js

scripts.358597538e78e2e0.js

123 ms

main.32fa5d60b87e91a5.js

main.32fa5d60b87e91a5.js

235 ms

recaptcha__en.js

recaptcha__en.js

20 ms

styles.91b032cd273d9cce.css

styles.91b032cd273d9cce.css

115 ms

Accessibility Review

developer.db.com accessibility score

78

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

Best Practices

developer.db.com 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

Missing source maps for large first-party JavaScript

SEO Factors

developer.db.com SEO score

68

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Developer.db.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Developer.db.com 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

developer.db.com

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