1.8 sec in total
310 ms
800 ms
666 ms
Visit wfafi.org now to see the best up-to-date Wfafi content and also check out these interesting facts you probably never knew about wfafi.org
Visit wfafi.orgWe analyzed Wfafi.org page load time and found that the first response time was 310 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
wfafi.org performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value4.6 s
36/100
25%
Value4.4 s
74/100
10%
Value660 ms
45/100
30%
Value0.167
71/100
15%
Value4.2 s
86/100
10%
310 ms
109 ms
152 ms
283 ms
152 ms
Our browser made a total of 18 requests to load all elements on the main page. We found that 94% of them (17 requests) were addressed to the original Wfafi.org, 6% (1 request) were made to Img.constantcontact.com. The less responsive or slowest element that took the longest time to load (490 ms) belongs to the original domain Wfafi.org.
Page size can be reduced by 109.4 kB (23%)
483.0 kB
373.6 kB
In fact, the total size of Wfafi.org main page is 483.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. 25% of websites need less resources to load. Images take 394.8 kB which makes up the majority of the site volume.
Potential reduce by 74.3 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 9.5 kB, which is 11% 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 74.3 kB or 84% of the original size.
Potential reduce by 35.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. Wfafi images are well optimized though.
We found no issues to fix!
16
16
The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wfafi. According to our analytics all requests are already optimized.
wfafi.org
310 ms
logo2.gif
109 ms
headline.gif
152 ms
none
283 ms
horizontal120.gif
152 ms
pils.gif
149 ms
email2_trans.gif
16 ms
index.1.jpg
102 ms
index.2.jpg
128 ms
Atefeh-16yr-gilr-iran.jpg
276 ms
thestory.jpg
275 ms
khomeini-women.jpg
337 ms
khiabani.jpg
278 ms
poverty-zan2.jpg
337 ms
poverty-zan4.jpg
424 ms
poverty-zan3.jpg
490 ms
poverty-zan.jpg
423 ms
burqa.jpg
368 ms
wfafi.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.
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
<frame> or <iframe> elements do not have a title
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
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.
wfafi.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
wfafi.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 uses legible font sizes
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wfafi.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 Wfafi.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
wfafi.org
Open Graph description is not detected on the main page of Wfafi. 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: