Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

Page Load Speed

4.1 sec in total

First Response

404 ms

Resources Loaded

3.3 sec

Page Rendered

362 ms

eligio.org screenshot

About Website

Click here to check amazing Eligio content. Otherwise, check out these important facts you probably never knew about eligio.org

Visit eligio.org

Key Findings

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

Performance Metrics

eligio.org performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value0.6 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

www.eligio.org

404 ms

wp-emoji-release.min.js

64 ms

output.css

125 ms

style.css

91 ms

jquery.js

125 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 28% of them (16 requests) were addressed to the original Eligio.org, 14% (8 requests) were made to Image2.pubmatic.com and 9% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Synad3.nuffnang.com.ph.

Page Optimization Overview & Recommendations

Page size can be reduced by 697.5 kB (40%)

Content Size

1.7 MB

After Optimization

1.0 MB

In fact, the total size of Eligio.org main page is 1.7 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. 70% of websites need less resources to load. Javascripts take 918.0 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 56.2 kB

  • Original 76.8 kB
  • After minification 71.3 kB
  • After compression 20.6 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 56.2 kB or 73% of the original size.

Image Optimization

-4%

Potential reduce by 26.3 kB

  • Original 670.5 kB
  • After minification 644.1 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. Eligio images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 550.8 kB

  • Original 918.0 kB
  • After minification 915.9 kB
  • After compression 367.3 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 550.8 kB or 60% of the original size.

CSS Optimization

-81%

Potential reduce by 64.2 kB

  • Original 79.0 kB
  • After minification 63.8 kB
  • After compression 14.8 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. Eligio.org needs all CSS files to be minified and compressed as it can save up to 64.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (56%)

Requests Now

48

After Optimization

21

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

Accessibility Review

eligio.org accessibility score

71

Accessibility Issues

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

Document doesn't have a <title> element

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

Best Practices

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

SEO Factors

eligio.org SEO score

55

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

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eligio.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Eligio.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 Eligio. 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: