Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

sapdb.org

SAP MaxDB | SAP Community

Page Load Speed

2.5 sec in total

First Response

226 ms

Resources Loaded

2 sec

Page Rendered

291 ms

sapdb.org screenshot

About Website

Welcome to sapdb.org homepage info - get ready to check SAP Db best content right away, or after learning these important things about sapdb.org

Find the latest user blogs, questions and answers, and resources along with featured community content. Join the conversation with other SAP MaxDB users today.

Visit sapdb.org

Key Findings

We analyzed Sapdb.org page load time and found that the first response time was 226 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

sapdb.org performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value2,350 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.84

4/100

15%

TTI (Time to Interactive)

Value15.8 s

6/100

10%

Network Requests Diagram

sapdb.org

226 ms

maxdb

201 ms

maxdb

420 ms

launch-e004d02e792c.min.js

31 ms

b520154aed287048.css

336 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Sapdb.org, 90% (27 requests) were made to Pages.community.sap.com and 3% (1 request) were made to Community.sap.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Pages.community.sap.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 301.2 kB (57%)

Content Size

523.9 kB

After Optimization

222.7 kB

In fact, the total size of Sapdb.org main page is 523.9 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. 35% of websites need less resources to load. Javascripts take 306.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 82.9 kB

  • Original 102.0 kB
  • After minification 102.0 kB
  • After compression 19.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 82.9 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 115.8 kB
  • After minification 115.8 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. SAP Db images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 218.3 kB

  • Original 306.1 kB
  • After minification 306.1 kB
  • After compression 87.8 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 218.3 kB or 71% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (63%)

Requests Now

27

After Optimization

10

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SAP 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 18 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

sapdb.org accessibility score

96

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 input fields do not have accessible names

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.

Best Practices

sapdb.org best practices score

83

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

sapdb.org SEO score

88

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

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 Sapdb.org 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 Sapdb.org 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

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