3.4 sec in total
536 ms
2.5 sec
313 ms
Click here to check amazing WFPHA content. Otherwise, check out these important facts you probably never knew about wfpha.org
International, nongovernmental organization composed of multidisciplinary national public health associations. WFPHA is the worldwide professional society that represents and serves the broad field of...
Visit wfpha.orgWe analyzed Wfpha.org page load time and found that the first response time was 536 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
wfpha.org performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value13.8 s
0/100
25%
Value11.8 s
4/100
10%
Value630 ms
47/100
30%
Value0.012
100/100
15%
Value13.8 s
10/100
10%
536 ms
189 ms
196 ms
673 ms
196 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 94% of them (58 requests) were addressed to the original Wfpha.org, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Wfpha.org.
Page size can be reduced by 1.2 MB (74%)
1.6 MB
412.1 kB
In fact, the total size of Wfpha.org main page is 1.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. 45% of websites need less resources to load. CSS take 762.6 kB which makes up the majority of the site volume.
Potential reduce by 94.0 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 94.0 kB or 85% of the original size.
Potential reduce by 18.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, WFPHA needs image optimization as it can save up to 18.0 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 408.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 408.5 kB or 70% of the original size.
Potential reduce by 663.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. Wfpha.org needs all CSS files to be minified and compressed as it can save up to 663.6 kB or 87% of the original size.
Number of requests can be reduced by 47 (80%)
59
12
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WFPHA. 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 21 to 1 for CSS and as a result speed up the page load time.
wfpha.org
536 ms
colorbox5.min.css
189 ms
maximenuckmobile.css
196 ms
template.css
673 ms
moo_maximenuhck.css
196 ms
maximenuhck.php
290 ms
css
68 ms
gantry-navigation.css
196 ms
maximenuresponsiveck.css
284 ms
bootstrap.css
787 ms
fontawesome.css
490 ms
template.css
494 ms
modstyle.css
289 ms
module_default.css
287 ms
modal.css
288 ms
styles.css
377 ms
bootstrap.css
765 ms
bootstrap-responsive.css
478 ms
moo_maximenuhck.css
382 ms
maximenuhck.php
384 ms
maximenuhck.php
474 ms
jquery.min.js
808 ms
jquery-noconflict.js
478 ms
jquery-migrate.min.js
569 ms
bootstrap.min.js
679 ms
jquery.touchSwipe.min.js
574 ms
jquery.colorbox-min.js
678 ms
script.min.js
663 ms
maximenuckmobile.js
742 ms
template.js
758 ms
jquery.ui.core.min.js
757 ms
html5fallback.js
758 ms
calnav.js
838 ms
acymailing_module.js
839 ms
mootools-core.js
1033 ms
mootools-more.js
1320 ms
modal.js
846 ms
jcarousel.js
879 ms
jquery.cj-swipe.js
933 ms
maximenuck.js
935 ms
css
26 ms
fancymenuck.js
885 ms
header-wfpha.png
221 ms
bckgd-top.jpg
200 ms
body_bg.jpg
201 ms
twitter.png
200 ms
fbook.png
200 ms
linkedin.png
199 ms
maxi_arrow0.png
198 ms
maxi_arrow1.png
278 ms
c5de5d469ecd9e0463047035a20a5c6c.jpg
371 ms
thumb_54f573879cc910.78315529.png
368 ms
donate_button.png
278 ms
captcha
638 ms
bg-shodow.png
198 ms
b_90_90_16777215_164_photo_article.png
197 ms
b_90_90_16777215_163_book.jpg
276 ms
read1.png
235 ms
Bz6qCq_T70EQfTlLnC7OLALUuEpTyoUstqEm5AMlJo4.ttf
128 ms
s-BiyweUPV0v-yRb-cjciMDdSZkkecOE1hvV7ZHvhyU.ttf
155 ms
refresh.png
202 ms
fontawesome-webfont.woff
293 ms
wfpha.org accessibility score
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
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
wfpha.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
wfpha.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wfpha.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 Wfpha.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.
wfpha.org
Open Graph description is not detected on the main page of WFPHA. 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: