2 sec in total
140 ms
1.8 sec
65 ms
Welcome to traass.org homepage info - get ready to check Traass best content right away, or after learning these important things about traass.org
At TRAASS International, we provide a full range of Trainings and Monitoring & Evaluation services to organisations seeking to assess their activities to improve both accountability and learning.
Visit traass.orgWe analyzed Traass.org page load time and found that the first response time was 140 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
traass.org performance score
name
value
score
weighting
Value2.1 s
81/100
10%
Value8.2 s
2/100
25%
Value6.0 s
47/100
10%
Value2,740 ms
3/100
30%
Value0.004
100/100
15%
Value20.0 s
2/100
10%
140 ms
68 ms
72 ms
68 ms
61 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Traass.org, 44% (38 requests) were made to Static.wixstatic.com and 24% (21 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 550.8 kB (40%)
1.4 MB
812.9 kB
In fact, the total size of Traass.org main page is 1.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. 60% of websites need less resources to load. HTML takes 553.7 kB which makes up the majority of the site volume.
Potential reduce by 435.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. 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 435.4 kB or 79% of the original size.
Potential reduce by 110.1 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, Traass needs image optimization as it can save up to 110.1 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 5.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. This website has mostly compressed JavaScripts.
Potential reduce by 0 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. Traass.org has all CSS files already compressed.
Number of requests can be reduced by 16 (26%)
62
46
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Traass. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
www.traass.org
140 ms
originTrials.41d7301a.bundle.min.js
68 ms
minified.js
72 ms
focus-within-polyfill.js
68 ms
polyfill.min.js
61 ms
thunderbolt-commons.2113c4aa.bundle.min.js
222 ms
main.6c492079.bundle.min.js
221 ms
lodash.min.js
236 ms
react.production.min.js
54 ms
react-dom.production.min.js
222 ms
siteTags.bundle.min.js
222 ms
wix-perf-measure.umd.min.js
235 ms
08e3e1_466a11a8484c4842a73b520c60bc6fa9~mv2_d_2498_2478_s_4_2.png
581 ms
ZByUrwBVWyE
259 ms
bundle.min.js
171 ms
08e3e1_0a31633686814635b264f5f7e6780e64.png
619 ms
ca2a5a_24b3a8dd6007433780627fd992504700.png
112 ms
ca2a5a_bddff556ee184d6abf8506a8d0503dc7.png
111 ms
ca2a5a_961d0c44bee64552b9b8231158d48596.png
111 ms
course2018_PNG.png
622 ms
logo-full.png
307 ms
oxfam.png
622 ms
OWL-Re-clients-ilo.png
510 ms
chemonics_logo.png
624 ms
austra.png
624 ms
msf-medicines-sans-frontiers-logo-png-tr.png
655 ms
plan%20international.png
655 ms
08e3e1_a7e4113cec4f4661b8b2c46216a2c508~mv2.gif
622 ms
ICRC_logo_Red_Cross.png
654 ms
1200px-World_Vision_Logo_svg.png
654 ms
UNDP_Logo-OutlineWhite-w-TaglineWhite-EN.png
678 ms
charity_roger_federer_foundation.png
679 ms
colour-file-hor.png
925 ms
Corner-Logo.png
795 ms
d92130de1f5e924b5f2cfa0b87b2753f.png
924 ms
iom.png
925 ms
SOS-Childrens-Villages-Logo-.png
925 ms
SOS-Childrens-Villages-Logo-.png
926 ms
WFP-logo-D1D323B823-seeklogo_com.png
1043 ms
wipo.png
1013 ms
wipo.png
1000 ms
bildschirmfoto_2018-09-26_um_16_56_24_pn.png
1116 ms
bildschirmfoto_2019-01-15_um_18_34_59_pn.png
1076 ms
icrcASSESSMENT_PNG.png
1116 ms
logo_edited.png
1268 ms
Deformations-02.png
1216 ms
OSbusinesscard2.png
1253 ms
SEVAL_JPG.jpg
1265 ms
EES_logo_square_200px.jpg
1318 ms
08e3e1_0a31633686814635b264f5f7e6780e64.png
1217 ms
c5749443-93da-4592-b794-42f28d62ef72.woff
29 ms
908c4810-64db-4b46-bb8e-823eb41f68c0.woff
26 ms
bc176270-17fa-4c78-a343-9fe52824e501.woff
15 ms
03805817-4611-4dbc-8c65-0f73031c3973.woff
26 ms
80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff
28 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
29 ms
b56b944e-bbe0-4450-a241-de2125d3e682.woff
53 ms
6f8d1983-4d34-4fa4-9110-988f6c495757.woff
53 ms
file.woff
1222 ms
file.woff
1195 ms
450 ms
454 ms
448 ms
446 ms
448 ms
446 ms
483 ms
480 ms
485 ms
484 ms
476 ms
480 ms
www-player.css
36 ms
www-embed-player.js
78 ms
base.js
112 ms
ad_status.js
174 ms
n80KQ6gtiGJzFTP4vWPPIINPT33fEpzRcKHzGigz3IE.js
120 ms
embed.js
47 ms
id
23 ms
Create
24 ms
GenerateIT
13 ms
qoe
13 ms
log_event
1 ms
deprecation-en.v5.html
6 ms
bolt-performance
24 ms
deprecation-style.v5.css
10 ms
right-arrow.svg
10 ms
traass.org accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
traass.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
traass.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 Traass.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 Traass.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.
traass.org
Open Graph data is detected on the main page of Traass. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: