Tools & Wizards About Us
healthmap.org screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

healthmap.org

Flu & Ebola Map | Virus & Contagious Disease Surveillance

Page Load Speed

650 ms in total

First Response

8 ms

Resources Loaded

559 ms

Page Rendered

83 ms

healthmap.org screenshot

About Website

Click here to check amazing Health Map content for United States. Otherwise, check out these important facts you probably never knew about healthmap.org

HealthMap brings together disparate data sources to achieve a unified and comprehensive view of the current global state of infectious diseases.

Visit healthmap.org

Key Findings

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

Performance Metrics

healthmap.org performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value4.3 s

75/100

10%

TBT (Total Blocking Time)

Value420 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

healthmap.org

8 ms

en

2 ms

167 ms

fonts.css

11 ms

jquery.fancybox.css

12 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 96% of them (85 requests) were addressed to the original Healthmap.org, 1% (1 request) were made to Maps.googleapis.com and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (294 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

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

Content Size

719.0 kB

After Optimization

426.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 28.1 kB

  • Original 35.5 kB
  • After minification 29.0 kB
  • After compression 7.4 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 6.5 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 28.1 kB or 79% of the original size.

Image Optimization

-97%

Potential reduce by 120.0 kB

  • Original 123.3 kB
  • After minification 3.3 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, Health Map needs image optimization as it can save up to 120.0 kB or 97% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-26%

Potential reduce by 138.4 kB

  • Original 529.8 kB
  • After minification 529.8 kB
  • After compression 391.4 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 138.4 kB or 26% of the original size.

CSS Optimization

-19%

Potential reduce by 5.7 kB

  • Original 30.4 kB
  • After minification 29.9 kB
  • After compression 24.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. Healthmap.org needs all CSS files to be minified and compressed as it can save up to 5.7 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (65%)

Requests Now

81

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

healthmap.org

healthmap.org

8 ms

en

en

2 ms

167 ms

fonts.css

fonts.css

11 ms

jquery.fancybox.css

jquery.fancybox.css

12 ms

rating.css

rating.css

15 ms

jquery.ui.all.css

jquery.ui.all.css

15 ms

styles.css

styles.css

31 ms

font-awesome.min.css

font-awesome.min.css

29 ms

font-awesome-ie7.min.css

font-awesome-ie7.min.css

27 ms

jquery.qtip.css

jquery.qtip.css

35 ms

jquery.dropdown.css

jquery.dropdown.css

34 ms

d3.css

d3.css

34 ms

markerclusterer.js

markerclusterer.js

37 ms

jquery.min.js

jquery.min.js

39 ms

jquerymigrate.js

jquerymigrate.js

39 ms

jquery_ui.js

jquery_ui.js

52 ms

jquery.tools.min.js

jquery.tools.min.js

51 ms

jquery.cookie.js

jquery.cookie.js

51 ms

jquery.qtip.min.js

jquery.qtip.min.js

51 ms

jquery.dropdown.js

jquery.dropdown.js

52 ms

modernizr.dropdown.js

modernizr.dropdown.js

52 ms

locator.js

locator.js

52 ms

jquery.infieldlabel.min.js

jquery.infieldlabel.min.js

51 ms

hm.js

hm.js

52 ms

countries.js

countries.js

52 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

53 ms

jquery.dataTables.js

jquery.dataTables.js

64 ms

fancybox.js

fancybox.js

63 ms

mapvisuals.js

mapvisuals.js

64 ms

mapfunctions.js

mapfunctions.js

65 ms

searchfunctions.js

searchfunctions.js

64 ms

presetfunctions.js

presetfunctions.js

64 ms

kmlfunctions.js

kmlfunctions.js

65 ms

displayoptions.js

displayoptions.js

66 ms

listview.js

listview.js

65 ms

general.js

general.js

66 ms

hmspecific.js

hmspecific.js

66 ms

js

js

197 ms

jsapi

jsapi

37 ms

js

js

294 ms

trendfunctions.js

trendfunctions.js

63 ms

d3.v3.js

d3.v3.js

68 ms

jquery.geocomplete.min.js

jquery.geocomplete.min.js

68 ms

infobox.js

infobox.js

67 ms

jquery.ui.base.css

jquery.ui.base.css

66 ms

jquery.ui.theme.css

jquery.ui.theme.css

50 ms

loader.js

loader.js

25 ms

jquery.ui.core.css

jquery.ui.core.css

4 ms

jquery.ui.resizable.css

jquery.ui.resizable.css

6 ms

jquery.ui.selectable.css

jquery.ui.selectable.css

6 ms

jquery.ui.accordion.css

jquery.ui.accordion.css

6 ms

jquery.ui.autocomplete.css

jquery.ui.autocomplete.css

6 ms

jquery.ui.button.css

jquery.ui.button.css

7 ms

jquery.ui.dialog.css

jquery.ui.dialog.css

8 ms

jquery.ui.slider.css

jquery.ui.slider.css

9 ms

jquery.ui.tabs.css

jquery.ui.tabs.css

10 ms

jquery.ui.datepicker.css

jquery.ui.datepicker.css

11 ms

jquery.ui.progressbar.css

jquery.ui.progressbar.css

11 ms

cl.png

cl.png

83 ms

60.png

60.png

19 ms

61.png

61.png

19 ms

62.png

62.png

20 ms

63.png

63.png

20 ms

64.png

64.png

21 ms

65.png

65.png

21 ms

66.png

66.png

21 ms

67.png

67.png

22 ms

68.png

68.png

23 ms

69.png

69.png

24 ms

70.png

70.png

24 ms

71.png

71.png

24 ms

l1.png

l1.png

25 ms

l2.png

l2.png

25 ms

l3.png

l3.png

26 ms

l4.png

l4.png

26 ms

l5.png

l5.png

27 ms

s1.png

s1.png

27 ms

s2.png

s2.png

27 ms

s3.png

s3.png

28 ms

s4.png

s4.png

28 ms

s5.png

s5.png

29 ms

mainlogo.png

mainlogo.png

29 ms

chb.png

chb.png

30 ms

hms.png

hms.png

30 ms

234CA4_E_0.woff

234CA4_E_0.woff

31 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

30 ms

234CA4_1_0.woff

234CA4_1_0.woff

31 ms

234CA4_3_0.woff

234CA4_3_0.woff

32 ms

Accessibility Review

healthmap.org accessibility score

98

Accessibility Issues

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

healthmap.org best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

healthmap.org SEO score

81

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 doesn't use 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 Healthmap.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 Healthmap.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

healthmap.org

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