Tools & Wizards About Us
blog.epidalert.org screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

blog.epidalert.org

Page Load Speed

4.1 sec in total

First Response

299 ms

Resources Loaded

3.4 sec

Page Rendered

456 ms

blog.epidalert.org screenshot

About Website

Welcome to blog.epidalert.org homepage info - get ready to check Blog Epidalert best content right away, or after learning these important things about blog.epidalert.org

Promoting Global Health Security by applying Ebola response experience to prevention, detection and response of infectious disease like Malaria, Lassa fever, Diarrhoeal diseases and Polio

Visit blog.epidalert.org

Key Findings

We analyzed Blog.epidalert.org page load time and found that the first response time was 299 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

blog.epidalert.org performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value1,080 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.276

44/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

blog.epidalert.org

299 ms

wp-emoji-release.min.js

141 ms

style.min.css

249 ms

ctf-styles.min.css

523 ms

genericons.css

252 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 66% of them (37 requests) were addressed to the original Blog.epidalert.org, 9% (5 requests) were made to Fonts.gstatic.com and 7% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Blog.epidalert.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 254.0 kB (36%)

Content Size

708.2 kB

After Optimization

454.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 116.6 kB

  • Original 132.9 kB
  • After minification 121.4 kB
  • After compression 16.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. 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 116.6 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 2.5 kB

  • Original 194.4 kB
  • After minification 191.9 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. Blog Epidalert images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 116.8 kB

  • Original 298.1 kB
  • After minification 293.7 kB
  • After compression 181.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 116.8 kB or 39% of the original size.

CSS Optimization

-22%

Potential reduce by 18.1 kB

  • Original 82.7 kB
  • After minification 82.7 kB
  • After compression 64.6 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. Blog.epidalert.org needs all CSS files to be minified and compressed as it can save up to 18.1 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (69%)

Requests Now

49

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blog.epidalert.org

blog.epidalert.org

299 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

141 ms

style.min.css

style.min.css

249 ms

ctf-styles.min.css

ctf-styles.min.css

523 ms

genericons.css

genericons.css

252 ms

bg-show-hide.css

bg-show-hide.css

181 ms

font-awesome.min.css

font-awesome.min.css

518 ms

bootstrap.css

bootstrap.css

279 ms

animate.css

animate.css

252 ms

owl.carousel.css

owl.carousel.css

319 ms

css

css

75 ms

style.css

style.css

320 ms

jquery.js

jquery.js

470 ms

jquery-migrate.min.js

jquery-migrate.min.js

350 ms

js

js

137 ms

classic-10_7.css

classic-10_7.css

97 ms

mc-validate.js

mc-validate.js

136 ms

embed.js

embed.js

81 ms

widgets.js

widgets.js

165 ms

silicon-counters.css

silicon-counters.css

337 ms

effect.min.js

effect.min.js

337 ms

effect-slide.min.js

effect-slide.min.js

795 ms

effect-highlight.min.js

effect-highlight.min.js

414 ms

effect-fold.min.js

effect-fold.min.js

413 ms

effect-blind.min.js

effect-blind.min.js

790 ms

bg-show-hide.js

bg-show-hide.js

787 ms

silicon-counters.js

silicon-counters.js

789 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

792 ms

bootstrap.js

bootstrap.js

1027 ms

wow.js

wow.js

789 ms

owl.carousel.js

owl.carousel.js

793 ms

jquery.vticker.js

jquery.vticker.js

778 ms

script.js

script.js

781 ms

wp-embed.min.js

wp-embed.min.js

782 ms

ctf-scripts.min.js

ctf-scripts.min.js

1011 ms

analytics.js

analytics.js

157 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQVIT9d4cw.ttf

110 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQVIT9d4cw.ttf

111 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQVIT9d4cw.ttf

194 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQVIT9d4cw.ttf

193 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQVIT9d4cw.ttf

193 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1335 ms

collect

collect

85 ms

2705.svg

2705.svg

522 ms

widget_iframe.7dae38096d06923d683a2a807172322a.html

widget_iframe.7dae38096d06923d683a2a807172322a.html

306 ms

cropped-Add-a-subheading.jpg

cropped-Add-a-subheading.jpg

220 ms

EA_COV-15-717x401.jpg

EA_COV-15-717x401.jpg

277 ms

EA_COV-14-717x401.jpg

EA_COV-14-717x401.jpg

458 ms

AC_BLOG-13-717x401.jpg

AC_BLOG-13-717x401.jpg

364 ms

settings

settings

100 ms

MG_9846-150x100.jpg

MG_9846-150x100.jpg

77 ms

Ebola-WWK-POSTER_EA-01-150x100.png

Ebola-WWK-POSTER_EA-01-150x100.png

164 ms

Ebola-uganda-150x100.jpg

Ebola-uganda-150x100.jpg

163 ms

button.d2f864f87f544dc0c11d7d712a191c1f.js

button.d2f864f87f544dc0c11d7d712a191c1f.js

25 ms

embeds

embeds

61 ms

follow_button.7dae38096d06923d683a2a807172322a.en.html

follow_button.7dae38096d06923d683a2a807172322a.en.html

88 ms

Accessibility Review

blog.epidalert.org accessibility score

92

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

High

Links do not have a discernible name

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

blog.epidalert.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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

blog.epidalert.org SEO score

91

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

    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 Blog.epidalert.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 Blog.epidalert.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

blog.epidalert.org

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