2.4 sec in total
12 ms
2.2 sec
171 ms
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.orgWe analyzed Healthmap.org page load time and found that the first response time was 12 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
healthmap.org performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value6.5 s
9/100
25%
Value4.1 s
80/100
10%
Value280 ms
81/100
30%
Value0.002
100/100
15%
Value8.2 s
41/100
10%
12 ms
2 ms
35 ms
30 ms
31 ms
Our browser made a total of 164 requests to load all elements on the main page. We found that 69% of them (113 requests) were addressed to the original Healthmap.org, 16% (27 requests) were made to Maps.googleapis.com and 4% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (995 ms) relates to the external source Ssl.google-analytics.com.
Page size can be reduced by 2.4 MB (76%)
3.1 MB
767.0 kB
In fact, the total size of Healthmap.org main page is 3.1 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 92.2 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 92.2 kB or 86% of the original size.
Potential reduce by 66.0 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 66.0 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.0 MB
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 2.0 MB or 79% of the original size.
Potential reduce by 223.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 223.6 kB or 85% of the original size.
Number of requests can be reduced by 88 (58%)
151
63
The browser has sent 151 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 46 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
healthmap.org
12 ms
en
2 ms
35 ms
fonts.css
30 ms
jquery.fancybox.css
31 ms
rating.css
34 ms
jquery.ui.all.css
35 ms
styles.css
38 ms
font-awesome.min.css
35 ms
font-awesome-ie7.min.css
44 ms
jquery.qtip.css
42 ms
jquery.dropdown.css
45 ms
d3.css
45 ms
markerclusterer.js
45 ms
jquery.min.js
48 ms
jquerymigrate.js
45 ms
jquery_ui.js
60 ms
jquery.tools.min.js
45 ms
jquery.cookie.js
45 ms
jquery.qtip.min.js
49 ms
jquery.dropdown.js
46 ms
modernizr.dropdown.js
48 ms
locator.js
48 ms
placeholders.min.js
47 ms
jquery.infieldlabel.min.js
48 ms
hm.js
49 ms
countries.js
48 ms
jquery.fancybox.pack.js
49 ms
jquery.dataTables.js
57 ms
fancybox.js
48 ms
mapvisuals.js
49 ms
mapfunctions.js
48 ms
searchfunctions.js
49 ms
presetfunctions.js
49 ms
kmlfunctions.js
49 ms
displayoptions.js
47 ms
listview.js
48 ms
general.js
47 ms
js
144 ms
jsapi
48 ms
hmspecific.js
41 ms
trendfunctions.js
38 ms
d3.v3.js
44 ms
jquery.ui.base.css
36 ms
jquery.ui.theme.css
38 ms
jquery.geocomplete.min.js
34 ms
infobox.js
32 ms
jquery.ui.core.css
12 ms
jquery.ui.resizable.css
12 ms
jquery.ui.selectable.css
11 ms
jquery.ui.accordion.css
11 ms
jquery.ui.autocomplete.css
12 ms
jquery.ui.button.css
10 ms
jquery.ui.dialog.css
11 ms
jquery.ui.slider.css
12 ms
jquery.ui.tabs.css
12 ms
jquery.ui.datepicker.css
11 ms
jquery.ui.progressbar.css
12 ms
ga.js
108 ms
cl.png
106 ms
diseases_picklist.js
57 ms
locations_picklist.js
62 ms
sources_picklist.js
65 ms
species_picklist.js
68 ms
common.js
64 ms
map.js
67 ms
60.png
29 ms
61.png
30 ms
62.png
30 ms
63.png
32 ms
64.png
31 ms
65.png
32 ms
66.png
32 ms
67.png
31 ms
68.png
50 ms
69.png
50 ms
70.png
49 ms
71.png
49 ms
l1.png
48 ms
l2.png
49 ms
l3.png
52 ms
l4.png
51 ms
l5.png
51 ms
s1.png
52 ms
s2.png
52 ms
s3.png
51 ms
s4.png
52 ms
s5.png
54 ms
mainlogo.png
54 ms
chb.png
54 ms
hms.png
52 ms
desc.png
54 ms
ui-bg_flat_75_ffffff_40x100.png
55 ms
fancybox_overlay.png
55 ms
fancybox_sprite.png
56 ms
fancybox_loading.gif
56 ms
234CA4_E_0.woff
57 ms
fontawesome-webfont.woff
50 ms
234CA4_1_0.woff
40 ms
234CA4_3_0.woff
38 ms
__utm.gif
58 ms
27433633
86 ms
util.js
29 ms
onion.js
44 ms
openhand_8_8.cur
177 ms
ViewportInfoService.GetViewportInfo
29 ms
stats.js
54 ms
controls.js
46 ms
getPreset.php
36 ms
transparent.png
187 ms
player.js
178 ms
player.css
155 ms
ga.js
129 ms
vuid.min.js
170 ms
getAlerts.php
272 ms
vt
73 ms
css
189 ms
vt
32 ms
vt
32 ms
vt
32 ms
vt
46 ms
vt
45 ms
vt
44 ms
vt
44 ms
vt
89 ms
vt
89 ms
vt
89 ms
vt
88 ms
vt
88 ms
vt
87 ms
vt
186 ms
vt
188 ms
vt
174 ms
google4.png
76 ms
mapcnt6.png
76 ms
sv5.png
75 ms
tmapctrl4.png
75 ms
google_white5.png
156 ms
__utm.gif
995 ms
proxy.html
928 ms
288663551.jpg
981 ms
marker.js
756 ms
g.png
34 ms
gt
34 ms
hm.png
34 ms
p.png
34 ms
w.png
33 ms
fao.png
34 ms
r.png
34 ms
fra.png
38 ms
reliefweb.png
38 ms
b.png
37 ms
t.png
36 ms
o.png
38 ms
f.png
38 ms
g2.png
48 ms
e.png
49 ms
AuthenticationService.Authenticate
54 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
126 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
126 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
143 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
152 ms
234CA4_0_0.woff
29 ms
288663551.jpg
55 ms
healthmap.org accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
healthmap.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
healthmap.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
EN
N/A
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.
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: