Tools & Wizards About Us
datajournalismhandbook.org screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

datajournalismhandbook.org

Homepage | DataJournalism.com

Page Load Speed

4 sec in total

First Response

213 ms

Resources Loaded

2.1 sec

Page Rendered

1.7 sec

datajournalismhandbook.org screenshot

About Website

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

The world's largest data journalism learning community. Featuring free video courses, long reads, resources and a discussion platform.

Visit datajournalismhandbook.org

Key Findings

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

Performance Metrics

datajournalismhandbook.org performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value1,460 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.207

60/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

datajournalismhandbook.org

213 ms

datajournalism.com

178 ms

css

37 ms

bundle.css

139 ms

custom.css

113 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Datajournalismhandbook.org, 37% (21 requests) were made to S3.eu-central-1.amazonaws.com and 26% (15 requests) were made to Datajournalism.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source S3.eu-central-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (17%)

Content Size

10.4 MB

After Optimization

8.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-91%

Potential reduce by 331.9 kB

  • Original 363.2 kB
  • After minification 184.0 kB
  • After compression 31.3 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 179.2 kB, which is 49% 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 331.9 kB or 91% of the original size.

Image Optimization

-15%

Potential reduce by 1.4 MB

  • Original 9.7 MB
  • After minification 8.3 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. Obviously, Data Journalism Handbook needs image optimization as it can save up to 1.4 MB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 3.5 kB

  • Original 217.3 kB
  • After minification 217.3 kB
  • After compression 213.8 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

-16%

Potential reduce by 13.0 kB

  • Original 82.1 kB
  • After minification 82.1 kB
  • After compression 69.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. Datajournalismhandbook.org needs all CSS files to be minified and compressed as it can save up to 13.0 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (32%)

Requests Now

44

After Optimization

30

  • Images
  • JavaScript
  • CSS

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Data Journalism 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 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

datajournalismhandbook.org

datajournalismhandbook.org

213 ms

datajournalism.com

datajournalism.com

178 ms

css

css

37 ms

bundle.css

bundle.css

139 ms

custom.css

custom.css

113 ms

animate.css

animate.css

123 ms

element.js

element.js

51 ms

webwhiz-sdk.js

webwhiz-sdk.js

414 ms

jquery-3.1.1.min.js

jquery-3.1.1.min.js

107 ms

hammer.min.js

hammer.min.js

31 ms

polyfill.min.js

polyfill.min.js

333 ms

bundle.js

bundle.js

178 ms

custom.js

custom.js

122 ms

polyfill.min.js

polyfill.min.js

340 ms

boomerang-1.0.0.min.js

boomerang-1.0.0.min.js

144 ms

e76e4cea-702b-4531-ae84-b4b143255aa9.js

e76e4cea-702b-4531-ae84-b4b143255aa9.js

837 ms

VERIFICATION-HANDBOOK-3-frontsmall.png

VERIFICATION-HANDBOOK-3-frontsmall.png

763 ms

read.svg

read.svg

152 ms

watch.svg

watch.svg

122 ms

discuss.svg

discuss.svg

127 ms

ejclogo.png

ejclogo.png

137 ms

google-logo2.svg

google-logo2.svg

138 ms

DATA-HANDBOOK-2-FRONT_small.png

DATA-HANDBOOK-2-FRONT_small.png

831 ms

visualisation.svg

visualisation.svg

679 ms

Story.svg

Story.svg

680 ms

CaseStudy.svg

CaseStudy.svg

677 ms

maximalfocus-HakTxidk36I-unsplash-2.jpg

maximalfocus-HakTxidk36I-unsplash-2.jpg

761 ms

Screenshot-2023-12-04-at-14.00.14.png

Screenshot-2023-12-04-at-14.00.14.png

1297 ms

Screenshot-2023-12-04-at-14.07.55.png

Screenshot-2023-12-04-at-14.07.55.png

1408 ms

ecojustice.jpg

ecojustice.jpg

1314 ms

Screenshot-2023-10-02-at-12.04.47.png

Screenshot-2023-10-02-at-12.04.47.png

1155 ms

womenwood.jpg

womenwood.jpg

938 ms

Screenshot-2023-12-14-at-12.55.42.png

Screenshot-2023-12-14-at-12.55.42.png

1312 ms

book-1-lg.png

book-1-lg.png

1145 ms

VERIFICATION-HANDBOOK-3-FRONT-squashed-squashed.jpg

VERIFICATION-HANDBOOK-3-FRONT-squashed-squashed.jpg

1443 ms

VERIFICATION-HANDBOOK-3-LEFT-homepage.png

VERIFICATION-HANDBOOK-3-LEFT-homepage.png

1274 ms

handbook1-lg.png

handbook1-lg.png

1393 ms

VERIFICATION-HANDBOOK-2-LEFT-homepage.png

VERIFICATION-HANDBOOK-2-LEFT-homepage.png

1443 ms

VERIFICATION-HANDBOOK-1-LEFT-homepage.png

VERIFICATION-HANDBOOK-1-LEFT-homepage.png

1426 ms

Resource.svg

Resource.svg

1437 ms

Cleaning.svg

Cleaning.svg

1503 ms

DataJournalism.svg

DataJournalism.svg

1511 ms

intro.svg

intro.svg

309 ms

stats-shape.svg

stats-shape.svg

368 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e4.woff

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e4.woff

177 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e4.woff

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e4.woff

244 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkQl0k30e4.woff

7Aulp_0qiz-aVz7u3PJLcUMYOFkQl0k30e4.woff

374 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e4.woff

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e4.woff

287 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFlOl0k30e4.woff

7Aulp_0qiz-aVz7u3PJLcUMYOFlOl0k30e4.woff

289 ms

7Aujp_0qiz-afTfcIyoiGtm2P0wG05Fz4eqVxQ.woff

7Aujp_0qiz-afTfcIyoiGtm2P0wG05Fz4eqVxQ.woff

287 ms

7Aujp_0qiz-afTfcIyoiGtm2P0wG00904eqVxQ.woff

7Aujp_0qiz-afTfcIyoiGtm2P0wG00904eqVxQ.woff

288 ms

7Aujp_0qiz-afTfcIyoiGtm2P0wG03Z04eqVxQ.woff

7Aujp_0qiz-afTfcIyoiGtm2P0wG03Z04eqVxQ.woff

287 ms

jizAREVNn1dOx-zrZ2X3pZvkTi2k_iI0q10.woff

jizAREVNn1dOx-zrZ2X3pZvkTi2k_iI0q10.woff

374 ms

jizDREVNn1dOx-zrZ2X3pZvkTiUf2zE.woff

jizDREVNn1dOx-zrZ2X3pZvkTiUf2zE.woff

372 ms

ppms.js

ppms.js

97 ms

ppms.php

ppms.php

376 ms

iubenda.js

iubenda.js

20 ms

Accessibility Review

datajournalismhandbook.org accessibility score

53

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

datajournalismhandbook.org best practices score

67

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

Serves images with low resolution

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

datajournalismhandbook.org SEO score

77

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

High

Image elements do not have [alt] attributes

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

    EN

  • Encoding

    UTF-8

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

datajournalismhandbook.org

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