Tools & Wizards About Us
forgerock.de screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% 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

  • 86

    SEO

    Google-friendlier than
    60% of websites

forgerock.de

Digital Identity for Consumers and Workforce | ForgeRock

Page Load Speed

1.6 sec in total

First Response

45 ms

Resources Loaded

1.1 sec

Page Rendered

432 ms

forgerock.de screenshot

About Website

Visit forgerock.de now to see the best up-to-date Forge Rock content and also check out these interesting facts you probably never knew about forgerock.de

Solve any identity use case without breaking legacy systems. Get the ForgeRock identity Platform as-a-Service or push-button deployment to any cloud.

Visit forgerock.de

Key Findings

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

Performance Metrics

forgerock.de performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value1,730 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.413

24/100

15%

TTI (Time to Interactive)

Value17.9 s

3/100

10%

Network Requests Diagram

en.html

45 ms

clientlibs-components-cookie-consent.lc-cd0964ce5e86f6b6f8cb9f90d5f292df-lc.min.js

8 ms

clientlibs-page-all.lc-8d733d5eb47c00668a246733bde7cbb7-lc.min.css

20 ms

clientlibs-cookie.lc-9065d93e33778cff5decc31a91f444ab-lc.min.js

14 ms

clientlibs-page-all.lc-832df8a62ef18c0b9c844bcc8d402e4d-lc.min.js

19 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Forgerock.de, 18% (9 requests) were made to Images.pingidentity.com and 4% (2 requests) were made to Download.pingidentity.com. The less responsive or slowest element that took the longest time to load (778 ms) relates to the external source Download.pingidentity.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 266.1 kB (41%)

Content Size

649.6 kB

After Optimization

383.5 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Forgerock.de main page is 649.6 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. 65% of websites need less resources to load. HTML takes 354.9 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 266.0 kB

  • Original 354.9 kB
  • After minification 353.4 kB
  • After compression 88.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 266.0 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 293.7 kB
  • After minification 293.7 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. Forge Rock images are well optimized though.

CSS Optimization

-12%

Potential reduce by 127 B

  • Original 1.0 kB
  • After minification 1.0 kB
  • After compression 918 B

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. Forgerock.de needs all CSS files to be minified and compressed as it can save up to 127 B or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (60%)

Requests Now

42

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

en.html

en.html

45 ms

clientlibs-components-cookie-consent.lc-cd0964ce5e86f6b6f8cb9f90d5f292df-lc.min.js

clientlibs-components-cookie-consent.lc-cd0964ce5e86f6b6f8cb9f90d5f292df-lc.min.js

8 ms

clientlibs-page-all.lc-8d733d5eb47c00668a246733bde7cbb7-lc.min.css

clientlibs-page-all.lc-8d733d5eb47c00668a246733bde7cbb7-lc.min.css

20 ms

clientlibs-cookie.lc-9065d93e33778cff5decc31a91f444ab-lc.min.js

clientlibs-cookie.lc-9065d93e33778cff5decc31a91f444ab-lc.min.js

14 ms

clientlibs-page-all.lc-832df8a62ef18c0b9c844bcc8d402e4d-lc.min.js

clientlibs-page-all.lc-832df8a62ef18c0b9c844bcc8d402e4d-lc.min.js

19 ms

styles-aaf8010c95.css

styles-aaf8010c95.css

18 ms

clientJs-3a37d6cb0a.js

clientJs-3a37d6cb0a.js

85 ms

clientlibs-components-lightbox.lc-497bd610854dd74491ec84671ba37424-lc.min.css

clientlibs-components-lightbox.lc-497bd610854dd74491ec84671ba37424-lc.min.css

85 ms

clientlibs-components-languageCheck.lc-1fc464ebe3b64628a0656874c940c286-lc.min.css

clientlibs-components-languageCheck.lc-1fc464ebe3b64628a0656874c940c286-lc.min.css

85 ms

clientlibs-components-languageCheck.lc-896209584306a1984137f384964b9bed-lc.min.js

clientlibs-components-languageCheck.lc-896209584306a1984137f384964b9bed-lc.min.js

88 ms

clientlibs-components-container.lc-fe3e849b81f0783af411b2dd4f5373a9-lc.min.css

clientlibs-components-container.lc-fe3e849b81f0783af411b2dd4f5373a9-lc.min.css

85 ms

clientlibs-components-container.lc-e34561ddfcabdf53dddd7f609f492f57-lc.min.js

clientlibs-components-container.lc-e34561ddfcabdf53dddd7f609f492f57-lc.min.js

88 ms

clientlibs-components-rellax.lc-a473aa3c85b1d8fa68a3794f7ee5f397-lc.min.js

clientlibs-components-rellax.lc-a473aa3c85b1d8fa68a3794f7ee5f397-lc.min.js

88 ms

clientlibs-vendors-rellax.lc-c603c319df84051e92f76affd0926d34-lc.min.js

clientlibs-vendors-rellax.lc-c603c319df84051e92f76affd0926d34-lc.min.js

89 ms

clientlibs-components-lobmixed7.lc-33d536f4921db49edf1382f8e59b639f-lc.min.css

clientlibs-components-lobmixed7.lc-33d536f4921db49edf1382f8e59b639f-lc.min.css

90 ms

clientlibs-components-lobText.lc-eee19e39854eaf8054d289bf508f9b21-lc.min.css

clientlibs-components-lobText.lc-eee19e39854eaf8054d289bf508f9b21-lc.min.css

94 ms

clientlibs-components-lobmixed.lc-86296a50b74e74eb91f680acd3287b7b-lc.min.css

clientlibs-components-lobmixed.lc-86296a50b74e74eb91f680acd3287b7b-lc.min.css

101 ms

clientlibs-vendors-lottie.lc-eb0e70a3ac4ff8c241de551483e6d66e-lc.min.js

clientlibs-vendors-lottie.lc-eb0e70a3ac4ff8c241de551483e6d66e-lc.min.js

111 ms

clientlibs-vendors-lottie-interactive.lc-36e904f4f5a4e175d71d585193e9fa02-lc.min.js

clientlibs-vendors-lottie-interactive.lc-36e904f4f5a4e175d71d585193e9fa02-lc.min.js

106 ms

clientlibs-components-lottie.lc-d15017731d843bf70eb26a96dceafca1-lc.min.js

clientlibs-components-lottie.lc-d15017731d843bf70eb26a96dceafca1-lc.min.js

106 ms

clientlibs-components-lobList.lc-90f2ac8d1624d821976d8371338e1ed0-lc.min.css

clientlibs-components-lobList.lc-90f2ac8d1624d821976d8371338e1ed0-lc.min.css

110 ms

clientlibs-components-carousel.lc-77bc3a138efe6e67929cb94f999c790a-lc.min.css

clientlibs-components-carousel.lc-77bc3a138efe6e67929cb94f999c790a-lc.min.css

119 ms

clientlibs-components-carousel.lc-7cd7b02f85da888b8d65e002cd856947-lc.min.js

clientlibs-components-carousel.lc-7cd7b02f85da888b8d65e002cd856947-lc.min.js

126 ms

clientlibs-components-cards.lc-826ad00ebedde3697aa2d9573e7badd1-lc.min.css

clientlibs-components-cards.lc-826ad00ebedde3697aa2d9573e7badd1-lc.min.css

118 ms

clientlibs-components-lobtext11.lc-2464fac0736f9a436836697da7e6694b-lc.min.css

clientlibs-components-lobtext11.lc-2464fac0736f9a436836697da7e6694b-lc.min.css

161 ms

style.css

style.css

220 ms

styles-333680c84b.css

styles-333680c84b.css

197 ms

clientJs-70e0ab76cd.js

clientJs-70e0ab76cd.js

197 ms

Ping-Logo-2.svg

Ping-Logo-2.svg

192 ms

Img-Make-Apps-Delightful-Hero-996x1000.png

Img-Make-Apps-Delightful-Hero-996x1000.png

279 ms

aemFormattingPixelnjs.png

aemFormattingPixelnjs.png

145 ms

Img-DataVis-GartherMagicQuadrant-541x541-Ver2.png

Img-DataVis-GartherMagicQuadrant-541x541-Ver2.png

324 ms

Img-DataVis-ForresterWaveCustomerIAM-541x541-4px.png

Img-DataVis-ForresterWaveCustomerIAM-541x541-4px.png

418 ms

Img-DataVis-KuppColeLeadershipCompassAccessManagement-541x541-Ver2.png

Img-DataVis-KuppColeLeadershipCompassAccessManagement-541x541-Ver2.png

368 ms

Img-DataVis-KuppColeReusableVerifiedIdentity-541x541%20-Ver2.png

Img-DataVis-KuppColeReusableVerifiedIdentity-541x541%20-Ver2.png

330 ms

Img-Homepage-BuildAFoundation-Jan2024-541x541.png

Img-Homepage-BuildAFoundation-Jan2024-541x541.png

329 ms

Img-Homepage-DifferentiateWithInnovation-Jan2024-541x541.png

Img-Homepage-DifferentiateWithInnovation-Jan2024-541x541.png

331 ms

Gotham-Medium_Web.woff

Gotham-Medium_Web.woff

478 ms

Gotham-Medium_Web.woff

Gotham-Medium_Web.woff

121 ms

Gotham-Book_Web.woff

Gotham-Book_Web.woff

778 ms

Gotham-Book_Web.woff

Gotham-Book_Web.woff

122 ms

GothamNarrow-Black_Web.woff

GothamNarrow-Black_Web.woff

143 ms

Img-Homepage-Background-LOB-Card-09-1440x589.png

Img-Homepage-Background-LOB-Card-09-1440x589.png

315 ms

Img-Homepage-Background-LOB-Mixed-08-1440x668.png

Img-Homepage-Background-LOB-Mixed-08-1440x668.png

347 ms

Pattern-HI-Diamond-01-Alignment-Left.svg

Pattern-HI-Diamond-01-Alignment-Left.svg

191 ms

Pattern-HI-Diamond-01-Alignment-Left-2.svg

Pattern-HI-Diamond-01-Alignment-Left-2.svg

186 ms

Pattern-Square-Dot-Grid-Section-01.svg

Pattern-Square-Dot-Grid-Section-01.svg

149 ms

GothamCond-XBlack_Web.woff

GothamCond-XBlack_Web.woff

51 ms

aemFormattingPixelwjs.png

aemFormattingPixelwjs.png

59 ms

Accessibility Review

forgerock.de accessibility score

96

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.

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

forgerock.de 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

forgerock.de SEO score

86

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

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 Forgerock.de 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 Forgerock.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

forgerock.de

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