Tools & Wizards About Us
corticon.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

corticon.com

Corticon BRMS Business Rules Management Engine | Progress

Page Load Speed

2.5 sec in total

First Response

36 ms

Resources Loaded

1.6 sec

Page Rendered

929 ms

corticon.com screenshot

About Website

Visit corticon.com now to see the best up-to-date Corticon content and also check out these interesting facts you probably never knew about corticon.com

Progress Corticon Business Rules Engine helps organizations of all kinds make faster decisions by managing the rules that drive business processes.

Visit corticon.com

Key Findings

We analyzed Corticon.com page load time and found that the first response time was 36 ms and then it took 2.5 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

corticon.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value2,650 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

corticon.com

36 ms

corticon

57 ms

WebResource.axd

51 ms

style.min.css

49 ms

WebResource.axd

77 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Corticon.com, 45% (27 requests) were made to D117h1jjiq768j.cloudfront.net and 10% (6 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (893 ms) relates to the external source D117h1jjiq768j.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 222.8 kB (8%)

Content Size

2.9 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Corticon.com 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. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 119.7 kB

  • Original 158.0 kB
  • After minification 155.5 kB
  • After compression 38.3 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 119.7 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 88.2 kB

  • Original 2.5 MB
  • After minification 2.4 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. Corticon images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 14.9 kB

  • Original 247.6 kB
  • After minification 244.5 kB
  • After compression 232.7 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 90 B

  • Original 59.6 kB
  • After minification 59.6 kB
  • After compression 59.6 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. Corticon.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (40%)

Requests Now

52

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

corticon.com

corticon.com

36 ms

corticon

corticon

57 ms

WebResource.axd

WebResource.axd

51 ms

style.min.css

style.min.css

49 ms

WebResource.axd

WebResource.axd

77 ms

sitefinity-insight-client.min.3.1.13.js

sitefinity-insight-client.min.3.1.13.js

85 ms

index.min.css

index.min.css

29 ms

index.min.js

index.min.js

38 ms

index.min.mjs

index.min.mjs

38 ms

WebResource.axd

WebResource.axd

57 ms

jquery.min.js

jquery.min.js

68 ms

jquery-migrate.min.js

jquery-migrate.min.js

180 ms

otSDKStub.js

otSDKStub.js

179 ms

all.min.js

all.min.js

50 ms

WebResource.axd

WebResource.axd

73 ms

browsersession

browsersession

59 ms

css2

css2

50 ms

background_-_overview.svg

background_-_overview.svg

446 ms

corticon_7_-_overview_illustration.svg

corticon_7_-_overview_illustration.svg

446 ms

arrow-up.svg

arrow-up.svg

452 ms

arrow-down.svg

arrow-down.svg

460 ms

financial-services.png

financial-services.png

459 ms

healthcare.png

healthcare.png

456 ms

insurance.png

insurance.png

458 ms

public-sector.png

public-sector.png

464 ms

any-organization.png

any-organization.png

459 ms

case-study-resourceimage.png

case-study-resourceimage.png

470 ms

insurance-cigna-logo.png

insurance-cigna-logo.png

574 ms

casestudy-resource_image53a4f8ca0307440ea0485c55b5da31a3.png

casestudy-resource_image53a4f8ca0307440ea0485c55b5da31a3.png

639 ms

logo_color24d9986ddcdc4348a728a474a7ab7959.png

logo_color24d9986ddcdc4348a728a474a7ab7959.png

636 ms

ss_adobe.jpg

ss_adobe.jpg

724 ms

adobe-min.png

adobe-min.png

575 ms

casestudy_ebay_650x800.png

casestudy_ebay_650x800.png

721 ms

ebay-min.png

ebay-min.png

634 ms

ss_tokio-marine.jpg

ss_tokio-marine.jpg

881 ms

tokio_marine-min.png

tokio_marine-min.png

701 ms

deep-analysis-vendor-vignette-progress-corticon-thumbnail-2x41e9aceef2fc4368baada5b3238d97c5.jpg

deep-analysis-vendor-vignette-progress-corticon-thumbnail-2x41e9aceef2fc4368baada5b3238d97c5.jpg

880 ms

partnerplus.png

partnerplus.png

892 ms

partnerdirectory.png

partnerdirectory.png

893 ms

thumbnails-300x225_ritm0142884.png

thumbnails-300x225_ritm0142884.png

892 ms

t5oels_errs.jpg

t5oels_errs.jpg

892 ms

get-started-with-corticonjs-rules_270x210.png

get-started-with-corticonjs-rules_270x210.png

891 ms

prefooter-overview0682701dd7d649e38ad92b2081190f84.svg

prefooter-overview0682701dd7d649e38ad92b2081190f84.svg

888 ms

f9397248-1dbe-47fc-9dbf-c50e7dd51096.json

f9397248-1dbe-47fc-9dbf-c50e7dd51096.json

499 ms

render

render

176 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

54 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

155 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

156 ms

KFOkCnqEu92Fr1MmgWxP.ttf

KFOkCnqEu92Fr1MmgWxP.ttf

156 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

157 ms

location

location

89 ms

otBannerSdk.js

otBannerSdk.js

17 ms

en.json

en.json

30 ms

otFlat.json

otFlat.json

26 ms

otCommonStyles.css

otCommonStyles.css

21 ms

gtm.js

gtm.js

202 ms

atcOverride.js

atcOverride.js

181 ms

redirect.js

redirect.js

193 ms

svrGP

svrGP

342 ms

svrGP.aspx

svrGP.aspx

25 ms

Accessibility Review

corticon.com accessibility score

98

Accessibility Issues

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

corticon.com 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

corticon.com SEO score

83

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

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

corticon.com

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