Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

engineeringforchange.org

Engineering For Change – By Engineers, for Everyone

Page Load Speed

9.9 sec in total

First Response

92 ms

Resources Loaded

9.1 sec

Page Rendered

645 ms

engineeringforchange.org screenshot

About Website

Welcome to engineeringforchange.org homepage info - get ready to check Engineering For Change best content for India right away, or after learning these important things about engineeringforchange.org

Engineering for Change provides a forum to connect, collaborate, solve challenges and share knowledge among a growing community of engineers, technologists, social scientists, NGOs, local governments ...

Visit engineeringforchange.org

Key Findings

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

Performance Metrics

engineeringforchange.org performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value2.9 s

94/100

10%

TBT (Total Blocking Time)

Value940 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value2.057

0/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

engineeringforchange.org

92 ms

www.engineeringforchange.org

1962 ms

jquery.min.js

86 ms

colorpicker.css

85 ms

styles.css

85 ms

Our browser made a total of 161 requests to load all elements on the main page. We found that 76% of them (123 requests) were addressed to the original Engineeringforchange.org, 2% (4 requests) were made to Maps.google.com and 2% (4 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (4.9 sec) relates to the external source Reddit.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (34%)

Content Size

5.4 MB

After Optimization

3.5 MB

In fact, the total size of Engineeringforchange.org main page is 5.4 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. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 125.7 kB

  • Original 144.7 kB
  • After minification 112.5 kB
  • After compression 19.0 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 32.1 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 125.7 kB or 87% of the original size.

Image Optimization

-5%

Potential reduce by 145.9 kB

  • Original 3.0 MB
  • After minification 2.9 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. Engineering For Change images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 1.0 MB

  • Original 1.5 MB
  • After minification 1.4 MB
  • After compression 501.2 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 1.0 MB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 553.8 kB

  • Original 656.5 kB
  • After minification 566.1 kB
  • After compression 102.7 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. Engineeringforchange.org needs all CSS files to be minified and compressed as it can save up to 553.8 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

149

After Optimization

79

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

Accessibility Review

engineeringforchange.org accessibility score

78

Accessibility Issues

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Links do not have a discernible name

Best Practices

engineeringforchange.org best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

engineeringforchange.org SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Engineeringforchange.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Engineeringforchange.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 data is detected on the main page of Engineering For Change. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: