Access ifac.com.

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.117

85/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

ifac.com

241 ms

ifac.html

137 ms

546195_PosterStore.htm

253 ms

ifac.gif

167 ms

ps_top_left.gif

61 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ifac.com, 77% (50 requests) were made to Imagecache6.allposters.com and 15% (10 requests) were made to Imagecache2.allposters.com. The less responsive or slowest element that took the longest time to load (505 ms) relates to the external source Imagecache6.allposters.com.

Content Size

620 B

After Optimization

260 B

In fact, the total size of Ifac.com main page is 620 B. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. HTML takes 620 B which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 360 B

Original 620 B
After minification 457 B
After compression 260 B

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 163 B, which is 26% 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 360 B or 58% of the original size.

Requests Now

After Optimization

The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ifac. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

<frame> or <iframe> elements do not have a title

Search Engine Optimization Advices

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ifac.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Ifac.com main page’s claimed encoding is . 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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Ifac. 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: