Tools & Wizards About Us
opendatahandbook.org screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

opendatahandbook.org

The Open Data Handbook

Page Load Speed

602 ms in total

First Response

60 ms

Resources Loaded

351 ms

Page Rendered

191 ms

opendatahandbook.org screenshot

About Website

Welcome to opendatahandbook.org homepage info - get ready to check Open Data Handbook best content for Indonesia right away, or after learning these important things about opendatahandbook.org

Guides, case studies and resources for government & civil society on the

Visit opendatahandbook.org

Key Findings

We analyzed Opendatahandbook.org page load time and found that the first response time was 60 ms and then it took 542 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

opendatahandbook.org performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

91/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

61/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

opendatahandbook.org

60 ms

frontend.css

7 ms

main.css

45 ms

css

26 ms

css

38 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 38% of them (13 requests) were addressed to the original Opendatahandbook.org, 26% (9 requests) were made to Fonts.gstatic.com and 9% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (125 ms) relates to the external source Assets.okfn.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 232.0 kB (58%)

Content Size

402.2 kB

After Optimization

170.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Opendatahandbook.org main page is 402.2 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. 60% of websites need less resources to load. CSS take 201.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 13.6 kB

  • Original 17.7 kB
  • After minification 13.2 kB
  • After compression 4.1 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 4.6 kB, which is 26% 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 13.6 kB or 77% of the original size.

Image Optimization

-11%

Potential reduce by 14.2 kB

  • Original 129.7 kB
  • After minification 115.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, Open Data Handbook needs image optimization as it can save up to 14.2 kB or 11% 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 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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 32.0 kB or 60% of the original size.

CSS Optimization

-85%

Potential reduce by 172.2 kB

  • Original 201.9 kB
  • After minification 184.7 kB
  • After compression 29.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. Opendatahandbook.org needs all CSS files to be minified and compressed as it can save up to 172.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (43%)

Requests Now

23

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

opendatahandbook.org

opendatahandbook.org

60 ms

frontend.css

frontend.css

7 ms

main.css

main.css

45 ms

css

css

26 ms

css

css

38 ms

modernizr-2.8.3.min.js

modernizr-2.8.3.min.js

28 ms

jquery.min.js

jquery.min.js

31 ms

plugins.js

plugins.js

16 ms

main.js

main.js

28 ms

frontend.min.js

frontend.min.js

3 ms

okf-panel.html

okf-panel.html

125 ms

ok-ribbon.png

ok-ribbon.png

119 ms

analytics.js

analytics.js

95 ms

home-banner-bg.jpg

home-banner-bg.jpg

53 ms

home-banner.jpg

home-banner.jpg

41 ms

open-knowledge.png

open-knowledge.png

30 ms

shuttleworth-footer.png

shuttleworth-footer.png

73 ms

worldbank-footer.png

worldbank-footer.png

47 ms

od4d-footer.png

od4d-footer.png

52 ms

open-content.svg

open-content.svg

47 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

49 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

71 ms

zJY4gsxBiSo5L7tNutxFNg.ttf

zJY4gsxBiSo5L7tNutxFNg.ttf

72 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

71 ms

4cKlrioa77J2iqTqBgkRWg.ttf

4cKlrioa77J2iqTqBgkRWg.ttf

71 ms

DeoOq1kX9ExfArSHppos_g.ttf

DeoOq1kX9ExfArSHppos_g.ttf

87 ms

_IxjUs2lbQSu0MyFEAfa7aCWcynf_cDxXwCLxiixG1c.ttf

_IxjUs2lbQSu0MyFEAfa7aCWcynf_cDxXwCLxiixG1c.ttf

87 ms

4A-myfZX6oDr9CtSTkTGig.ttf

4A-myfZX6oDr9CtSTkTGig.ttf

86 ms

rapsGf8n-DpRu9kcmAAciA.ttf

rapsGf8n-DpRu9kcmAAciA.ttf

87 ms

icomoon.woff

icomoon.woff

49 ms

bootstrap.min.css

bootstrap.min.css

23 ms

css

css

33 ms

okfn-logo-landscape.png

okfn-logo-landscape.png

31 ms

collect

collect

22 ms

Accessibility Review

opendatahandbook.org accessibility score

91

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.

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

<frame> or <iframe> elements do not have a title

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

Best Practices

opendatahandbook.org best practices score

75

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

opendatahandbook.org SEO score

88

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Opendatahandbook.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 Opendatahandbook.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

opendatahandbook.org

Open Graph description is not detected on the main page of Open Data Handbook. 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: