Report Summary

  • 85

    Performance

    Renders faster than
    89% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

enketo.org

Enketo

Page Load Speed

2.6 sec in total

First Response

190 ms

Resources Loaded

2.1 sec

Page Rendered

315 ms

About Website

Visit enketo.org now to see the best up-to-date Enketo content for Yemen and also check out these interesting facts you probably never knew about enketo.org

Enketo Open-Source Project for the ODK ecosystem.

Visit enketo.org

Key Findings

We analyzed Enketo.org page load time and found that the first response time was 190 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

enketo.org performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

81/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.233

53/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

enketo.org

190 ms

enketo.org

418 ms

front.css

191 ms

front-combined.min.js

457 ms

ga.js

40 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 95% of them (35 requests) were addressed to the original Enketo.org, 5% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (949 ms) belongs to the original domain Enketo.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 331.3 kB (41%)

Content Size

805.1 kB

After Optimization

473.8 kB

In fact, the total size of Enketo.org main page is 805.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 491.6 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 9.4 kB

  • Original 13.2 kB
  • After minification 11.7 kB
  • After compression 3.7 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 1.5 kB, which is 11% 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 9.4 kB or 72% of the original size.

Image Optimization

-21%

Potential reduce by 104.2 kB

  • Original 491.6 kB
  • After minification 387.5 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. Obviously, Enketo needs image optimization as it can save up to 104.2 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 94.6 kB

  • Original 157.2 kB
  • After minification 157.2 kB
  • After compression 62.6 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 94.6 kB or 60% of the original size.

CSS Optimization

-86%

Potential reduce by 123.0 kB

  • Original 143.1 kB
  • After minification 113.8 kB
  • After compression 20.1 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. Enketo.org needs all CSS files to be minified and compressed as it can save up to 123.0 kB or 86% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

32

After Optimization

32

The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Enketo. According to our analytics all requests are already optimized.

Accessibility Review

enketo.org accessibility score

98

Accessibility Issues

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

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

enketo.org SEO score

98

Search Engine Optimization Advices

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 Enketo.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 Enketo.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 Enketo. 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: