Tools & Wizards About Us
edify.org screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

edify.org

Every Child Deserves to Learn and Flourish | Edify.org

Page Load Speed

2.9 sec in total

First Response

79 ms

Resources Loaded

2.2 sec

Page Rendered

590 ms

edify.org screenshot

About Website

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

We are a global nonprofit improving and expanding sustainable Christ-centered education in the developing world through training, loan capital, and education technology.

Visit edify.org

Key Findings

We analyzed Edify.org page load time and found that the first response time was 79 ms and then it took 2.8 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

edify.org performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value1,300 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value1.056

2/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

edify.org

79 ms

edify.org

92 ms

js

78 ms

prettyPhoto.css

29 ms

wp-video-lightbox.css

34 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 55% of them (45 requests) were addressed to the original Edify.org, 33% (27 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Edify.org.

Page Optimization Overview & Recommendations

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

Content Size

2.0 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Edify.org main page is 2.0 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. Only a small number of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 134.7 kB

  • Original 162.7 kB
  • After minification 162.6 kB
  • After compression 28.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. 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 134.7 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.1 MB
  • After minification 1.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. Edify images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 26.0 kB

  • Original 564.4 kB
  • After minification 564.4 kB
  • After compression 538.4 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

-10%

Potential reduce by 14.2 kB

  • Original 140.9 kB
  • After minification 140.9 kB
  • After compression 126.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. Edify.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 42 (88%)

Requests Now

48

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

edify.org

edify.org

79 ms

edify.org

edify.org

92 ms

js

js

78 ms

prettyPhoto.css

prettyPhoto.css

29 ms

wp-video-lightbox.css

wp-video-lightbox.css

34 ms

style.min.css

style.min.css

38 ms

icons.css

icons.css

35 ms

style.css

style.css

40 ms

style.css

style.css

40 ms

wp_head.css

wp_head.css

42 ms

normalize.css

normalize.css

44 ms

style.css

style.css

60 ms

custom.css

custom.css

1020 ms

job-listings.css

job-listings.css

48 ms

app.css

app.css

43 ms

style.css

style.css

91 ms

themify-icons.min.css

themify-icons.min.css

51 ms

dflip.min.css

dflip.min.css

60 ms

style.min.css

style.min.css

64 ms

css

css

48 ms

jquery.min.js

jquery.min.js

89 ms

jquery-migrate.min.js

jquery-migrate.min.js

118 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

119 ms

video-lightbox.js

video-lightbox.js

120 ms

frontend-gtag.min.js

frontend-gtag.min.js

120 ms

snap.svg-min.js

snap.svg-min.js

121 ms

modernizr.custom.js

modernizr.custom.js

120 ms

jquery.exitintent.min.js

jquery.exitintent.min.js

122 ms

custom.js

custom.js

120 ms

css

css

66 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

120 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

120 ms

app.js

app.js

121 ms

custom.unified.js

custom.unified.js

124 ms

es6-promise.auto.min.js

es6-promise.auto.min.js

120 ms

api.js

api.js

47 ms

recaptcha.js

recaptcha.js

121 ms

dflip.min.js

dflip.min.js

122 ms

frontend-bundle.min.js

frontend-bundle.min.js

120 ms

common.js

common.js

122 ms

wp_footer.js

wp_footer.js

122 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

106 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

103 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

101 ms

mic0ilr.js

mic0ilr.js

578 ms

fbevents.js

fbevents.js

138 ms

edify_logo_RGB300.png

edify_logo_RGB300.png

110 ms

preloader.gif

preloader.gif

111 ms

subscribe-loader.gif

subscribe-loader.gif

111 ms

pxiByp8kv8JHgFVrLGT9V1s.ttf

pxiByp8kv8JHgFVrLGT9V1s.ttf

203 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

468 ms

pxiByp8kv8JHgFVrLDz8V1s.ttf

pxiByp8kv8JHgFVrLDz8V1s.ttf

610 ms

pxiByp8kv8JHgFVrLFj_V1s.ttf

pxiByp8kv8JHgFVrLFj_V1s.ttf

613 ms

pxiGyp8kv8JHgFVrLPTedw.ttf

pxiGyp8kv8JHgFVrLPTedw.ttf

613 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

613 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

613 ms

pxiByp8kv8JHgFVrLDD4V1s.ttf

pxiByp8kv8JHgFVrLDD4V1s.ttf

613 ms

pxiByp8kv8JHgFVrLBT5V1s.ttf

pxiByp8kv8JHgFVrLBT5V1s.ttf

613 ms

modules.ttf

modules.ttf

466 ms

recaptcha__en.js

recaptcha__en.js

499 ms

IMG_3451-scaled.jpg

IMG_3451-scaled.jpg

312 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

205 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

205 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

205 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

204 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

202 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

204 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

212 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

212 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

213 ms

-nFvOHYr-vcC7h8MklGBkrvmUG9rbpkisrTrN2zR3A.ttf

-nFvOHYr-vcC7h8MklGBkrvmUG9rbpkisrTrN2zR3A.ttf

383 ms

-nFvOHYr-vcC7h8MklGBkrvmUG9rbpkisrTrU23R3A.ttf

-nFvOHYr-vcC7h8MklGBkrvmUG9rbpkisrTrU23R3A.ttf

381 ms

-nFvOHYr-vcC7h8MklGBkrvmUG9rbpkisrTrT27R3A.ttf

-nFvOHYr-vcC7h8MklGBkrvmUG9rbpkisrTrT27R3A.ttf

380 ms

-nFvOHYr-vcC7h8MklGBkrvmUG9rbpkisrTra2_R3A.ttf

-nFvOHYr-vcC7h8MklGBkrvmUG9rbpkisrTra2_R3A.ttf

383 ms

-nFvOHYr-vcC7h8MklGBkrvmUG9rbpkisrTrG2vR3A.ttf

-nFvOHYr-vcC7h8MklGBkrvmUG9rbpkisrTrG2vR3A.ttf

380 ms

-nFiOHYr-vcC7h8MklGBkrvmUG9rbpkisrTT7w.ttf

-nFiOHYr-vcC7h8MklGBkrvmUG9rbpkisrTT7w.ttf

213 ms

-nFvOHYr-vcC7h8MklGBkrvmUG9rbpkisrTrQ2rR3A.ttf

-nFvOHYr-vcC7h8MklGBkrvmUG9rbpkisrTrQ2rR3A.ttf

379 ms

-nFvOHYr-vcC7h8MklGBkrvmUG9rbpkisrTrJ2nR3A.ttf

-nFvOHYr-vcC7h8MklGBkrvmUG9rbpkisrTrJ2nR3A.ttf

384 ms

-nFsOHYr-vcC7h8MklGBkrvmUG9rbpkisrTri0jx.ttf

-nFsOHYr-vcC7h8MklGBkrvmUG9rbpkisrTri0jx.ttf

383 ms

d

d

205 ms

d

d

208 ms

d

d

208 ms

Accessibility Review

edify.org accessibility score

90

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

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

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

Missing source maps for large first-party JavaScript

SEO Factors

edify.org SEO score

89

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

edify.org

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