3.7 sec in total
247 ms
2.9 sec
554 ms
Visit tsetse.org now to see the best up-to-date Tsetse content and also check out these interesting facts you probably never knew about tsetse.org
Visit tsetse.orgWe analyzed Tsetse.org page load time and found that the first response time was 247 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
tsetse.org performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value8.5 s
1/100
25%
Value8.9 s
15/100
10%
Value690 ms
43/100
30%
Value0.397
25/100
15%
Value13.1 s
12/100
10%
247 ms
539 ms
87 ms
173 ms
240 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 73% of them (66 requests) were addressed to the original Tsetse.org, 12% (11 requests) were made to Platform.twitter.com and 8% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (838 ms) belongs to the original domain Tsetse.org.
Page size can be reduced by 121.3 kB (3%)
4.6 MB
4.4 MB
In fact, the total size of Tsetse.org main page is 4.6 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. 70% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.
Potential reduce by 96.6 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 96.6 kB or 86% of the original size.
Potential reduce by 0 B
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. Tsetse images are well optimized though.
Potential reduce by 24.5 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 24.5 kB or 12% of the original size.
Potential reduce by 126 B
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. Tsetse.org has all CSS files already compressed.
Number of requests can be reduced by 23 (28%)
81
58
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tsetse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
tsetse.org
247 ms
www.tsetse.org
539 ms
css_ywqYrtSodM0qVMzAkOSnqZ_iBnAVpkSeD_yPtUN9tBk.css
87 ms
css_fglpEG36znORq62tLFx_xLFCApQtKj0euNRNM6mIzvY.css
173 ms
css_XhJSeKZD-VAZ0naopRVL8qQb6AD6DKqlP8sCI93p1iM.css
240 ms
css_gmiVfO0PbMEVwt9rGqS8aYUNPI_EX5qfxcyn3Krw0d4.css
556 ms
js_i9NufjfDOspjOmJjciXsp4UAk0UDk-hHgik712q8s30.js
397 ms
js_hrZlh1KdgifEAT4KvIXU8HYGliJG5TUV2spfipZLT2s.js
332 ms
js_l-TSRX_ZU-j1L7FB8AQXkGM1sTZmFpYn8IiHt4YelwY.js
250 ms
js_luge8_9Ka4x5XhkiOHeeHmN-s0HUizyvrCWIAODIgcE.js
258 ms
js
60 ms
js_TFRT0iPIX0AK3Sqd2gK-6QdV_xFDoszYfGIl70hYOZI.js
476 ms
js_4QY69l_m6F-2gDkMgTgJ7hUatxkIn8T0E9OF5_gpKpk.js
415 ms
widgets.js
97 ms
js_U_LuyhNdryFynEkAsPV5DCOD7jDu9CAqBPJ-rU4058g.js
342 ms
css
34 ms
js
338 ms
analytics.js
336 ms
survey%20trap%20in%20Chad%20%28photo%20by%20Inaki%20Tirados%29.JPG
498 ms
iStock-996051328.jpg
494 ms
18172400146_5c6bc93725_o.jpg
405 ms
Greenshot%202018-05-09%2017.41.58.png
508 ms
Checking%20trap%20contents.jpg
575 ms
node803-steve_head_250x332.jpg
405 ms
g_vale_full.jpg
644 ms
Andrew%20Hope%20LR.JPG
508 ms
Clement-Mangwiro.jpg
581 ms
Img_4024a.jpg
653 ms
male%20placeholder.jpg
578 ms
john%20morton.jpg
574 ms
female%20placeholder.jpg
654 ms
Johnhargrove.jpg
658 ms
WHO%20Stakeholders%20Meeting_2.JPG
661 ms
journal.pntd_.0007737.g001.PNG
667 ms
image%20for%20Josh%20news%20story_0.png
722 ms
Bandundu%20Team%20Monitoring%20in%20Pandemic.jpg
730 ms
screening%20news%20story_2_1.jpg
731 ms
iStock-139703045.jpg
823 ms
Bandundu-DRC_J.Ndungu_2.jpg
826 ms
HAT%20Picture%201%20crop.jpg
838 ms
tiny%20tsarget.jpg
801 ms
node%20506%20-%20trypanosomiasis.jpg
809 ms
lstm-400_300.jpg
811 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
353 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYA.ttf
440 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUZiYA.ttf
454 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf
457 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf
456 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTQ3ig.ttf
455 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTQ3ig.ttf
455 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
256 ms
survey%20trap%20in%20Chad%20%28photo%20by%20Inaki%20Tirados%29.JPG
666 ms
iStock-996051328.jpg
674 ms
18172400146_5c6bc93725_o.jpg
596 ms
Greenshot%202018-05-09%2017.41.58.png
777 ms
Checking%20trap%20contents.jpg
780 ms
node803-steve_head_250x332.jpg
630 ms
g_vale_full.jpg
674 ms
Andrew%20Hope%20LR.JPG
802 ms
Clement-Mangwiro.jpg
744 ms
Img_4024a.jpg
752 ms
male%20placeholder.jpg
754 ms
slick.woff
715 ms
john%20morton.jpg
726 ms
collect
66 ms
female%20placeholder.jpg
640 ms
Johnhargrove.jpg
663 ms
WHO%20Stakeholders%20Meeting_2.JPG
651 ms
journal.pntd_.0007737.g001.PNG
676 ms
settings
73 ms
image%20for%20Josh%20news%20story_0.png
625 ms
Bandundu%20Team%20Monitoring%20in%20Pandemic.jpg
633 ms
screening%20news%20story_2_1.jpg
630 ms
iStock-139703045.jpg
660 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
22 ms
Bandundu-DRC_J.Ndungu_2.jpg
600 ms
tsetse_org
74 ms
HAT%20Picture%201%20crop.jpg
618 ms
tiny%20tsarget.jpg
624 ms
node%20506%20-%20trypanosomiasis.jpg
629 ms
lstm-400_300.jpg
626 ms
extlink_s.png
656 ms
ajax-loader.gif
603 ms
polyfills-3b821eda8863adcc4a4b.js
23 ms
runtime-a697c5a1ae32bd7e4d42.js
43 ms
modules.20f98d7498a59035a762.js
83 ms
main-fd9ef5eb169057cda26d.js
87 ms
_app-88bf420a57d49e33be53.js
98 ms
%5BscreenName%5D-c33f0b02841cffc3e9b4.js
102 ms
_buildManifest.js
104 ms
_ssgManifest.js
103 ms
tsetse.org accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
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
Links do not have a discernible name
tsetse.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
tsetse.org SEO score
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 uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tsetse.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 Tsetse.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.
tsetse.org
Open Graph description is not detected on the main page of Tsetse. 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: