Tools & Wizards About Us
forgerock.org screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    33% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 70% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    61% of websites

forgerock.org

Digital Identity for Consumers and Workforce | ForgeRock

Page Load Speed

3.3 sec in total

First Response

119 ms

Resources Loaded

2.9 sec

Page Rendered

244 ms

forgerock.org screenshot

About Website

Click here to check amazing Forge Rock content for United States. Otherwise, check out these important facts you probably never knew about forgerock.org

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

Key Findings

We analyzed Forgerock.org page load time and found that the first response time was 119 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

forgerock.org performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value8,790 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.042

99/100

15%

TTI (Time to Interactive)

Value26.1 s

0/100

10%

Network Requests Diagram

forgerock.org

119 ms

forgerock.org

1230 ms

dashicons.min.20160226151100.css

127 ms

jquery-ui-dialog.min.20160226151100.css

52 ms

css

157 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 17% of them (11 requests) were addressed to the original Forgerock.org, 28% (18 requests) were made to Org-static-files-forgerock.netdna-ssl.com and 19% (12 requests) were made to Gravatar.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Gravatar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (78%)

Content Size

2.9 MB

After Optimization

645.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Forgerock.org main page is 2.9 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. 60% of websites need less resources to load. CSS take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 87.9 kB

  • Original 104.9 kB
  • After minification 95.7 kB
  • After compression 17.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 87.9 kB or 84% of the original size.

Image Optimization

-19%

Potential reduce by 21.0 kB

  • Original 113.7 kB
  • After minification 92.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. Obviously, Forge Rock needs image optimization as it can save up to 21.0 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 567.4 kB

  • Original 848.5 kB
  • After minification 848.3 kB
  • After compression 281.1 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 567.4 kB or 67% of the original size.

CSS Optimization

-86%

Potential reduce by 1.6 MB

  • Original 1.9 MB
  • After minification 1.9 MB
  • After compression 254.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. Forgerock.org needs all CSS files to be minified and compressed as it can save up to 1.6 MB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (47%)

Requests Now

57

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 57 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 23 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

forgerock.org

forgerock.org

119 ms

forgerock.org

forgerock.org

1230 ms

dashicons.min.20160226151100.css

dashicons.min.20160226151100.css

127 ms

jquery-ui-dialog.min.20160226151100.css

jquery-ui-dialog.min.20160226151100.css

52 ms

css

css

157 ms

plugins.20160226151100.css

plugins.20160226151100.css

64 ms

combined-theme.min.20160226151100.css

combined-theme.min.20160226151100.css

134 ms

jquery.min.js

jquery.min.js

165 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

148 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

129 ms

core.min.js

core.min.js

143 ms

widget.min.js

widget.min.js

125 ms

mouse.min.js

mouse.min.js

143 ms

resizable.min.js

resizable.min.js

144 ms

draggable.min.js

draggable.min.js

142 ms

button.min.js

button.min.js

143 ms

position.min.js

position.min.js

142 ms

dialog.min.js

dialog.min.js

142 ms

wpdialog.min.20160226151100.js

wpdialog.min.20160226151100.js

143 ms

plugins.20160226151100.js

plugins.20160226151100.js

144 ms

theme.20160226151100.js

theme.20160226151100.js

154 ms

analytics.js

analytics.js

807 ms

ForgeRock_logo.png

ForgeRock_logo.png

180 ms

3e0c5431658cab6c01e63d12962dfb20

3e0c5431658cab6c01e63d12962dfb20

971 ms

FR_plogo_org_FC_openAM.png

FR_plogo_org_FC_openAM.png

146 ms

FR_plogo_org_FC_openDJ.png

FR_plogo_org_FC_openDJ.png

692 ms

FR_plogo_org_FC_openIDM.png

FR_plogo_org_FC_openIDM.png

767 ms

FR_plogo_org_FC_openIG.png

FR_plogo_org_FC_openIG.png

769 ms

ForgeRockFullStack-300x155-480x248.png

ForgeRockFullStack-300x155-480x248.png

770 ms

2143ff8f0e9fa538e5477828e9c85b22-bpthumb.jpg

2143ff8f0e9fa538e5477828e9c85b22-bpthumb.jpg

769 ms

03987e62a081c082da05e7d7cf285829-bpthumb.jpg

03987e62a081c082da05e7d7cf285829-bpthumb.jpg

770 ms

d5b00ad7fcdb5ace96cf01566e6f61ba-bpthumb.jpg

d5b00ad7fcdb5ace96cf01566e6f61ba-bpthumb.jpg

769 ms

b87e2cfea9eae756748203a565c4db07

b87e2cfea9eae756748203a565c4db07

955 ms

489918cf7dc37fc68386383d73979501

489918cf7dc37fc68386383d73979501

1057 ms

e5d785df25986d053d8b2772ef57626c

e5d785df25986d053d8b2772ef57626c

1087 ms

b17c2a866b48a310e512a9a5e1311797

b17c2a866b48a310e512a9a5e1311797

1135 ms

d84c19d550939014175cf3f0f90de029

d84c19d550939014175cf3f0f90de029

1136 ms

4fbb9e0e317d570718d0210b1420401a

4fbb9e0e317d570718d0210b1420401a

1292 ms

71a114225c2e904bacd9de494002a606

71a114225c2e904bacd9de494002a606

1135 ms

c2c30f5b64aa85548601fc1a4ecd7cf6

c2c30f5b64aa85548601fc1a4ecd7cf6

1141 ms

a63d0bff91e589e5d67e22aeee984a61

a63d0bff91e589e5d67e22aeee984a61

1142 ms

ef6568850e297fb8c6530be5b3d92980

ef6568850e297fb8c6530be5b3d92980

1292 ms

f5fa9ba5a2367ae0c0256c90bbadca40

f5fa9ba5a2367ae0c0256c90bbadca40

1184 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

864 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

926 ms

fontello.woff

fontello.woff

594 ms

munchkin.js

munchkin.js

745 ms

urgt0qGO.min.js

urgt0qGO.min.js

741 ms

aXFWQzBvPqw

aXFWQzBvPqw

351 ms

Ru9CGUs_IYM

Ru9CGUs_IYM

359 ms

C5DGTNWhIZY

C5DGTNWhIZY

358 ms

cZ0nNa5Es1o

cZ0nNa5Es1o

439 ms

collect

collect

68 ms

collect

collect

286 ms

ip.json

ip.json

213 ms

pixel

pixel

211 ms

munchkin.js

munchkin.js

25 ms

www-embed-player-vflQrT_sR.css

www-embed-player-vflQrT_sR.css

174 ms

www-embed-player.js

www-embed-player.js

199 ms

pixel

pixel

14 ms

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

43 ms

ad_status.js

ad_status.js

130 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

32 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

33 ms

Accessibility Review

forgerock.org accessibility score

88

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-*] attributes do not have valid values

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

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.org best practices score

67

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

forgerock.org 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.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 Forgerock.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

forgerock.org

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