Tools & Wizards About Us
wso2.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wso2.com

Create awesome digital experiences quickly, easily, and securely

Page Load Speed

2 sec in total

First Response

36 ms

Resources Loaded

1.6 sec

Page Rendered

392 ms

wso2.com screenshot

About Website

Visit wso2.com now to see the best up-to-date Wso 2 content for Sri Lanka and also check out these interesting facts you probably never knew about wso2.com

Home page

Visit wso2.com

Key Findings

We analyzed Wso2.com page load time and found that the first response time was 36 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

wso2.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value1,260 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.062

97/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

wso2.com

36 ms

wso2.com

1297 ms

lazysizes.min.js

23 ms

OtAutoBlock.js

58 ms

otSDKStub.js

68 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 7% of them (4 requests) were addressed to the original Wso2.com, 86% (49 requests) were made to Wso2.cachefly.net and 5% (3 requests) were made to Cookie-cdn.cookiepro.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Wso2.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 615.0 kB (46%)

Content Size

1.3 MB

After Optimization

711.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wso2.com main page is 1.3 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. 80% 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. HTML takes 687.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 555.8 kB

  • Original 687.1 kB
  • After minification 621.9 kB
  • After compression 131.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 555.8 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 59.1 kB

  • Original 613.5 kB
  • After minification 554.3 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. Wso 2 images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 89 B

  • Original 25.6 kB
  • After minification 25.6 kB
  • After compression 25.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.

Requests Breakdown

Number of requests can be reduced by 6 (11%)

Requests Now

55

After Optimization

49

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

wso2.com

wso2.com

36 ms

wso2.com

wso2.com

1297 ms

lazysizes.min.js

lazysizes.min.js

23 ms

OtAutoBlock.js

OtAutoBlock.js

58 ms

otSDKStub.js

otSDKStub.js

68 ms

cookie-revoke.js

cookie-revoke.js

33 ms

jquery.validate.js

jquery.validate.js

24 ms

486163bc-a8c5-40d8-b185-c707cc718a23.json

486163bc-a8c5-40d8-b185-c707cc718a23.json

24 ms

location

location

40 ms

wso2-logo.webp

wso2-logo.webp

20 ms

arrow-left.svg

arrow-left.svg

14 ms

white-close.svg

white-close.svg

55 ms

api-manager-logo.webp

api-manager-logo.webp

57 ms

APIMag-menu.svg

APIMag-menu.svg

57 ms

choreo-for-api-management.webp

choreo-for-api-management.webp

154 ms

wso2-api-kubernetes.webp

wso2-api-kubernetes.webp

155 ms

APKMag-menu.svg

APKMag-menu.svg

152 ms

micro-integrator-logo.webp

micro-integrator-logo.webp

150 ms

ballerina-swan-lake-logo-black.webp

ballerina-swan-lake-logo-black.webp

154 ms

Ballerina-menu.svg

Ballerina-menu.svg

159 ms

choreo-for-Integration-logo-black.webp

choreo-for-Integration-logo-black.webp

161 ms

identity-sever-logo.webp

identity-sever-logo.webp

155 ms

is7tag-menu.svg

is7tag-menu.svg

157 ms

asgardeo-logo.webp

asgardeo-logo.webp

155 ms

private-identity-cloud.webp

private-identity-cloud.webp

160 ms

home-choreo-logo.webp

home-choreo-logo.webp

161 ms

EQT-WSO2-menu-Banner-readMore.webp

EQT-WSO2-menu-Banner-readMore.webp

166 ms

world.svg

world.svg

161 ms

wso2-menu-login-icon.svg

wso2-menu-login-icon.svg

163 ms

arrow-menu-orange.png

arrow-menu-orange.png

164 ms

email-decode.min.js

email-decode.min.js

146 ms

EQT_logo.webp

EQT_logo.webp

161 ms

qantas-block.webp

qantas-block.webp

164 ms

quote-icon-ash.webp

quote-icon-ash.webp

163 ms

laposte-block.webp

laposte-block.webp

163 ms

ericsson-block.webp

ericsson-block.webp

170 ms

APItag-body.svg

APItag-body.svg

164 ms

APKtag-body.svg

APKtag-body.svg

168 ms

home-micro-integrator.webp

home-micro-integrator.webp

165 ms

Ballerina-body4.svg

Ballerina-body4.svg

166 ms

home-choreo-for-integration-logo.webp

home-choreo-for-integration-logo.webp

169 ms

home-identity-server.webp

home-identity-server.webp

171 ms

is7tag-body.svg

is7tag-body.svg

170 ms

home-private-ciam-cloud.webp

home-private-ciam-cloud.webp

172 ms

kuppingercole-logo-black.webp

kuppingercole-logo-black.webp

172 ms

forrester-logo-black.webp

forrester-logo-black.webp

173 ms

wso2home-themecon.webp

wso2home-themecon.webp

61 ms

arrow-orange.png

arrow-orange.png

58 ms

arrow-left-orange.png

arrow-left-orange.png

59 ms

arrow-right-orange.png

arrow-right-orange.png

60 ms

home-page-apim-bg.webp

home-page-apim-bg.webp

62 ms

home-page-integration-bg.webp

home-page-integration-bg.webp

67 ms

home-page-iam-bg.webp

home-page-iam-bg.webp

65 ms

home-page-choreo-bg.webp

home-page-choreo-bg.webp

63 ms

g2-spring-background.webp

g2-spring-background.webp

65 ms

kuppingercole2-bg.png

kuppingercole2-bg.png

64 ms

forrester-bg.png

forrester-bg.png

65 ms

Accessibility Review

wso2.com accessibility score

90

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 match their roles

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

wso2.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

SEO Factors

wso2.com SEO score

93

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

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

wso2.com

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