3.7 sec in total
411 ms
2.7 sec
507 ms
Welcome to ffii.org homepage info - get ready to check FFII best content for Russia right away, or after learning these important things about ffii.org
The Foundation for a Free Information Infrastructure (FFII) is a European alliance defending your right to free and competitive software creation since 1999. We are working towards the mitigation of l...
Visit ffii.orgWe analyzed Ffii.org page load time and found that the first response time was 411 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
ffii.org performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value3.2 s
71/100
25%
Value4.8 s
67/100
10%
Value10 ms
100/100
30%
Value0.081
94/100
15%
Value3.3 s
94/100
10%
411 ms
195 ms
198 ms
199 ms
223 ms
Our browser made a total of 25 requests to load all elements on the main page. We found that 96% of them (24 requests) were addressed to the original Ffii.org, 4% (1 request) were made to Old.ffii.org. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ffii.org.
Page size can be reduced by 82.3 kB (21%)
396.2 kB
313.9 kB
In fact, the total size of Ffii.org main page is 396.2 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. 15% of websites need less resources to load. Images take 339.0 kB which makes up the majority of the site volume.
Potential reduce by 17.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 17.0 kB or 75% of the original size.
Potential reduce by 37.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, FFII needs image optimization as it can save up to 37.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 10.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 10.5 kB or 83% of the original size.
Potential reduce by 17.7 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. Ffii.org needs all CSS files to be minified and compressed as it can save up to 17.7 kB or 81% of the original size.
Number of requests can be reduced by 9 (39%)
23
14
The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FFII. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.
ffii.org
411 ms
common.js
195 ms
common.css
198 ms
screen.css
199 ms
ffii-logo-transparent.gif
223 ms
Home
208 ms
Home
1218 ms
Home
2001 ms
Home
1825 ms
Home
204 ms
Home
1233 ms
Home
507 ms
Home
1336 ms
Home
618 ms
moin-edit.png
717 ms
moin-show.png
817 ms
moin-diff.png
917 ms
moin-info.png
1113 ms
moin-subscribe.png
1213 ms
moin-raw.png
1316 ms
moin-print.png
1315 ms
lora.woff
1527 ms
ffii-logo-transparent.gif
211 ms
print.css
103 ms
projection.css
102 ms
ffii.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
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.
ffii.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
Browser errors were logged to the console
ffii.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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ffii.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 Ffii.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.
ffii.org
Open Graph description is not detected on the main page of FFII. 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: