3.3 sec in total
76 ms
2.3 sec
936 ms
Click here to check amazing Iaffe content. Otherwise, check out these important facts you probably never knew about iaffe.org
IAFFE
Visit iaffe.orgWe analyzed Iaffe.org page load time and found that the first response time was 76 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
iaffe.org performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value5.1 s
25/100
25%
Value6.3 s
42/100
10%
Value480 ms
60/100
30%
Value0.169
70/100
15%
Value11.8 s
17/100
10%
76 ms
59 ms
676 ms
65 ms
62 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 73% of them (56 requests) were addressed to the original Iaffe.org, 14% (11 requests) were made to Platform.twitter.com and 8% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (676 ms) belongs to the original domain Iaffe.org.
Page size can be reduced by 584.8 kB (5%)
11.4 MB
10.9 MB
In fact, the total size of Iaffe.org main page is 11.4 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. Only a small number of websites need less resources to load. Images take 11.0 MB which makes up the majority of the site volume.
Potential reduce by 73.9 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 73.9 kB or 70% of the original size.
Potential reduce by 400.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. Iaffe images are well optimized though.
Potential reduce by 99.9 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 99.9 kB or 33% of the original size.
Potential reduce by 10.5 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. Iaffe.org needs all CSS files to be minified and compressed as it can save up to 10.5 kB or 33% of the original size.
Number of requests can be reduced by 47 (71%)
66
19
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iaffe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
iaffe.org
76 ms
www.iaffe.org
59 ms
www.iaffe.org
676 ms
css
65 ms
new-jevents.css
62 ms
jquery.min.js
102 ms
jquery-migrate.min.js
98 ms
jquery-ui-custom-elvn-fr.min.js
85 ms
jQueryUIDialogInclude.js
84 ms
jquery.dataTables.js
79 ms
jquery.tablednd-0.5.js
100 ms
json2.js
172 ms
underscore.js
193 ms
ui.all.css
197 ms
jqueryui.css
174 ms
system-messages.css
196 ms
mootools.js
196 ms
joomla.javascript.js
191 ms
caption.js
197 ms
ajax_1.3.js
268 ms
modal.css
213 ms
modal.js
216 ms
css2
96 ms
general.css
575 ms
nivo-slider.css
213 ms
mc01.css
231 ms
mc02.css
251 ms
editor.css
266 ms
hoverIntent.js
265 ms
jquery.nivo.slider.pack.js
272 ms
crawler.js
278 ms
crawler.js
293 ms
widgets.js
187 ms
mc-respond-v2.1.js
304 ms
ui.base.css
109 ms
ui.theme.css
118 ms
ui.core.css
65 ms
ui.resizable.css
42 ms
ui.accordion.css
46 ms
ui.dialog.css
64 ms
ui.slider.css
57 ms
ui.tabs.css
80 ms
ui.datepicker.css
80 ms
ui.progressbar.css
91 ms
logo.png
143 ms
alt-logo.png
140 ms
CONFERENCE%20HEADER.png
309 ms
Clear%20banner%20updated.jpg
284 ms
Clear%20banner%20updated%201.png
326 ms
2%20%281%29.png
311 ms
IAFFE%20Website%20landing%20page%20images%201.png
329 ms
Landing%20page%20image%201.png
149 ms
Rome%20Conference.png
332 ms
IAFFE%20Logo%205x5.png
304 ms
loading.gif
318 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsWUBw.ttf
125 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhHMWUBw.ttf
126 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhh8KUBw.ttf
127 ms
jizMREVItHgc8qDIbSTKq4XkRiUawTk7f45UM9y05oZ8RNDM.ttf
150 ms
jizMREVItHgc8qDIbSTKq4XkRiUawTk7f45UM9y05oZORNDM.ttf
150 ms
jizMREVItHgc8qDIbSTKq4XkRiUawTk7f45UM9y05obVQ9DM.ttf
151 ms
fc-2.jpg
216 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
131 ms
sn-twitter.svg
67 ms
sn-linkedin.svg
66 ms
www.iaffe.org
622 ms
settings
100 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
22 ms
IAFFE
83 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
23 ms
runtime-b1c52fd0a13ead5fcf6b.js
98 ms
modules-96ebc7ac3ad66d681a3d.js
102 ms
main-babd9234dc048fb47339.js
124 ms
_app-a9c9f1a99e4414675fb1.js
197 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
205 ms
_buildManifest.js
228 ms
_ssgManifest.js
229 ms
iaffe.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
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
iaffe.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
iaffe.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
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iaffe.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 Iaffe.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.
iaffe.org
Open Graph description is not detected on the main page of Iaffe. 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: