5 sec in total
2 sec
2.7 sec
364 ms
Welcome to fo.am homepage info - get ready to check Fo best content for India right away, or after learning these important things about fo.am
Founded in 2000 in Brussels, FoAM is a cultural laboratory re-imagining possible futures, in the interstices of art, science, nature and the everyday life.
Visit fo.amWe analyzed Fo.am page load time and found that the first response time was 2 sec and then it took 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.
fo.am performance score
name
value
score
weighting
Value1.7 s
92/100
10%
Value3.6 s
62/100
25%
Value3.7 s
85/100
10%
Value20 ms
100/100
30%
Value0.242
51/100
15%
Value5.2 s
74/100
10%
1996 ms
78 ms
156 ms
161 ms
154 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 43% of them (22 requests) were addressed to the original Fo.am, 39% (20 requests) were made to I.vimeocdn.com and 8% (4 requests) were made to B.vimeocdn.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Fo.am.
Page size can be reduced by 66.8 kB (6%)
1.1 MB
1.0 MB
In fact, the total size of Fo.am main page is 1.1 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. 50% of websites need less resources to load. Images take 972.9 kB which makes up the majority of the site volume.
Potential reduce by 27.5 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 5.0 kB, which is 15% 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 27.5 kB or 80% of the original size.
Potential reduce by 3.6 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. Fo images are well optimized though.
Potential reduce by 13.6 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 13.6 kB or 38% of the original size.
Potential reduce by 22.1 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. Fo.am needs all CSS files to be minified and compressed as it can save up to 22.1 kB or 77% of the original size.
Number of requests can be reduced by 12 (24%)
50
38
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fo. 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 JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
fo.am
1996 ms
base.css
78 ms
992.css
156 ms
1382.css
161 ms
okm4bdk.js
154 ms
jquery.min.js
31 ms
foam.js
206 ms
p.gif
137 ms
376457409_640.jpg
45 ms
376457409_640.jpg
86 ms
93 ms
login.png
89 ms
foam-logo.png
92 ms
bubble.png
165 ms
foamplus.png
165 ms
bg_map.png
166 ms
search.png
166 ms
feat_22192965105_a6cc8342bc_o.jpg
242 ms
holder-med.jpg
169 ms
home_16456046155_76e8f99866_o.jpg
388 ms
home_15089333208_88741d2093_o.jpg
312 ms
home_9201721394_c882bccb52_o.jpg
313 ms
play.png
241 ms
icon_tweet.png
243 ms
icon_event.png
314 ms
foamplus1.png
315 ms
393187790_640.jpg
316 ms
407410536_640.jpg
123 ms
425398107_640.jpg
399 ms
474819603_640.jpg
55 ms
387401914_640.jpg
55 ms
395279771_640.jpg
56 ms
307225170_640.jpg
57 ms
477966303_640.jpg
58 ms
376446553_640.jpg
72 ms
175911302_640.jpg
75 ms
275021159_640.jpg
77 ms
417588613_640.jpg
56 ms
385825315_640.jpg
77 ms
289639061_640.jpg
96 ms
395464569_640.jpg
56 ms
384986184_640.jpg
59 ms
395470163_640.jpg
69 ms
385840616_640.jpg
115 ms
393184754_640.jpg
77 ms
188638616_640.jpg
128 ms
436195399_640.jpg
127 ms
203212092_640.jpg
127 ms
ga.js
5 ms
__utm.gif
12 ms
print.css
78 ms
fo.am accessibility score
fo.am best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
fo.am 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 doesn't use legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fo.am 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 Fo.am 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.
fo.am
Open Graph description is not detected on the main page of Fo. 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: