Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

wfnen.org

Wadhwani Entrepreneur Network - Wadhwani Foundation

Page Load Speed

57.7 sec in total

First Response

170 ms

Resources Loaded

44.1 sec

Page Rendered

13.5 sec

wfnen.org screenshot

About Website

Click here to check amazing Wfnen content for India. Otherwise, check out these important facts you probably never knew about wfnen.org

Wadhwani Entrepreneur educates and enables startup entrepreneurs with Wadhwani Venture Fastrack [VFT], Wadhwani NEN and Wadhwani Inspire

Visit wfnen.org

Key Findings

We analyzed Wfnen.org page load time and found that the first response time was 170 ms and then it took 57.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 29 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

wfnen.org performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

1/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.045

99/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

wfnen.org

170 ms

www.wfnen.org

1780 ms

twemoji.js

747 ms

wp-emoji.js

730 ms

admin_icon.min.css

764 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 74% of them (98 requests) were addressed to the original Wfnen.org, 14% (18 requests) were made to S3-ap-southeast-1.amazonaws.com and 2% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (26.7 sec) relates to the external source S3-ap-southeast-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (86%)

Content Size

1.6 MB

After Optimization

230.2 kB

In fact, the total size of Wfnen.org main page is 1.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. CSS take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 177.3 kB

  • Original 203.1 kB
  • After minification 153.6 kB
  • After compression 25.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. This page needs HTML code to be minified as it can gain 49.5 kB, which is 24% 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 177.3 kB or 87% of the original size.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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

-87%

Potential reduce by 1.2 MB

  • Original 1.4 MB
  • After minification 1.3 MB
  • After compression 183.4 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. Wfnen.org needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 79 (86%)

Requests Now

92

After Optimization

13

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

Accessibility Review

wfnen.org accessibility score

77

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.

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

wfnen.org SEO score

90

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

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

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