Tools & Wizards About Us
community.pega.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 0

    SEO

community.pega.com

Pega Community | Training & Resources for Pega Developers

Page Load Speed

3.7 sec in total

First Response

406 ms

Resources Loaded

1.7 sec

Page Rendered

1.5 sec

community.pega.com screenshot

About Website

Visit community.pega.com now to see the best up-to-date Community Pega content for India and also check out these interesting facts you probably never knew about community.pega.com

Discover Pega Community, your source for training, documentation, and career-building as a Pega Developer.

Visit community.pega.com

Key Findings

We analyzed Community.pega.com page load time and found that the first response time was 406 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 55% of websites can load faster.

Performance Metrics

community.pega.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value27.6 s

0/100

10%

TBT (Total Blocking Time)

Value35,500 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value46.8 s

0/100

10%

Network Requests Diagram

community.pega.com

406 ms

notice

235 ms

answers.css

205 ms

answerstemplates.compiled.min.js

278 ms

answers.min.js

292 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 74% of them (25 requests) were addressed to the original Community.pega.com, 9% (3 requests) were made to Assets.sitescdn.net and 9% (3 requests) were made to Consent.trustarc.com. The less responsive or slowest element that took the longest time to load (864 ms) relates to the external source Consent.trustarc.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 332.9 kB (9%)

Content Size

3.6 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Community.pega.com main page is 3.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 303.9 kB

  • Original 349.5 kB
  • After minification 274.2 kB
  • After compression 45.5 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 75.2 kB, which is 22% 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 303.9 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 27.8 kB

  • Original 3.1 MB
  • After minification 3.1 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. Community Pega images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 1.2 kB

  • Original 24.7 kB
  • After minification 24.7 kB
  • After compression 23.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 67 B

  • Original 101.1 kB
  • After minification 101.1 kB
  • After compression 101.0 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. Community.pega.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

33

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

community.pega.com

community.pega.com

406 ms

notice

notice

235 ms

answers.css

answers.css

205 ms

answerstemplates.compiled.min.js

answerstemplates.compiled.min.js

278 ms

answers.min.js

answers.min.js

292 ms

google_tag.script.js

google_tag.script.js

108 ms

css_xyfDXN3QwgBDoyn5G9IqXXDbhKAp6xkEgWMCE3_btA4.css

css_xyfDXN3QwgBDoyn5G9IqXXDbhKAp6xkEgWMCE3_btA4.css

201 ms

css_bZkdDvUYkDNHa3d30UHiEggxEgW2z5AfAGVadX9OPuQ.css

css_bZkdDvUYkDNHa3d30UHiEggxEgW2z5AfAGVadX9OPuQ.css

180 ms

js_By7WUCZFCfXxTUiL84B0vrm1tsUp_fhWstxyihAcBZ0.js

js_By7WUCZFCfXxTUiL84B0vrm1tsUp_fhWstxyihAcBZ0.js

106 ms

index.min.js

index.min.js

237 ms

js_V65K0x_2ft8soshxIahFYZYcUXuWQnU0WPA5qzAsE9w.js

js_V65K0x_2ft8soshxIahFYZYcUXuWQnU0WPA5qzAsE9w.js

78 ms

log

log

864 ms

v1.7-9931

v1.7-9931

864 ms

pega-logo.svg

pega-logo.svg

628 ms

Navigation_Tile_GetStarted.png

Navigation_Tile_GetStarted.png

400 ms

Role_Menu_Tile_0.png

Role_Menu_Tile_0.png

398 ms

FeaturedApp_0.png

FeaturedApp_0.png

398 ms

CFP_Background_0.png

CFP_Background_0.png

342 ms

pwi23-hp-band3-right-imgv2.png

pwi23-hp-band3-right-imgv2.png

380 ms

Comm_Hero_Background_v3.jpg

Comm_Hero_Background_v3.jpg

415 ms

Yellow_Background.jpg

Yellow_Background.jpg

400 ms

Comm_Hero.png

Comm_Hero.png

416 ms

Orange_Rectangle.png

Orange_Rectangle.png

413 ms

Latest%20News%20Background_0.png

Latest%20News%20Background_0.png

413 ms

Training_Background_2.png

Training_Background_2.png

413 ms

Training_v2.png

Training_v2.png

415 ms

video_Background.png

video_Background.png

478 ms

image_2924.jpg

image_2924.jpg

431 ms

image_2903.jpg

image_2903.jpg

428 ms

image_2902.jpg

image_2902.jpg

479 ms

Forum_Background_3.png

Forum_Background_3.png

433 ms

Forums_Person.png

Forums_Person.png

427 ms

gtm.js

gtm.js

242 ms

notice

notice

88 ms

Accessibility Review

community.pega.com accessibility score

94

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

Image elements do not have [alt] attributes

Best Practices

community.pega.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

SEO Factors

community.pega.com SEO score

0

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 Community.pega.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 Community.pega.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

community.pega.com

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