Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

one.org

ONE.org US – Join the fight against extreme poverty and preventable disease

Page Load Speed

1.7 sec in total

First Response

158 ms

Resources Loaded

1.4 sec

Page Rendered

130 ms

one.org screenshot

About Website

Click here to check amazing ONE content for Ethiopia. Otherwise, check out these important facts you probably never knew about one.org

If you believe everyone has the right to a life of opportunity and justice, no matter where they live, and if you believe ordinary people can change the world, then join us at ONE.org.

Visit one.org

Key Findings

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

Performance Metrics

one.org performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value3,800 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.095

91/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

one.org

158 ms

www.one.org

167 ms

us

104 ms

167 ms

412820192.js

118 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 37% of them (21 requests) were addressed to the original One.org, 9% (5 requests) were made to One-org.s3.amazonaws.com and 5% (3 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (381 ms) relates to the external source Act.one.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 660.4 kB (35%)

Content Size

1.9 MB

After Optimization

1.2 MB

In fact, the total size of One.org main page is 1.9 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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 67.0 kB

  • Original 83.0 kB
  • After minification 68.2 kB
  • After compression 16.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 14.8 kB, which is 18% 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 67.0 kB or 81% of the original size.

Image Optimization

-8%

Potential reduce by 83.5 kB

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

JavaScript Optimization

-64%

Potential reduce by 300.7 kB

  • Original 469.7 kB
  • After minification 454.0 kB
  • After compression 169.0 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 300.7 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 209.1 kB

  • Original 251.0 kB
  • After minification 249.1 kB
  • After compression 41.9 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. One.org needs all CSS files to be minified and compressed as it can save up to 209.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (60%)

Requests Now

52

After Optimization

21

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

Accessibility Review

one.org accessibility score

92

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

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

Form elements do not have associated labels

Best Practices

one.org best practices score

75

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

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

one.org SEO score

100

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise One.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 One.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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