2.4 sec in total
332 ms
1.9 sec
201 ms
Click here to check amazing I CARE content for Canada. Otherwise, check out these important facts you probably never knew about icare.to
Internet Centre Anti Racism Europe
Visit icare.toWe analyzed Icare.to page load time and found that the first response time was 332 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
icare.to performance score
name
value
score
weighting
Value1.5 s
95/100
10%
Value1.8 s
99/100
25%
Value2.5 s
98/100
10%
Value400 ms
68/100
30%
Value0
100/100
15%
Value2.2 s
99/100
10%
332 ms
385 ms
242 ms
188 ms
190 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 78% of them (46 requests) were addressed to the original Icare.to, 5% (3 requests) were made to Google.com and 5% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (498 ms) belongs to the original domain Icare.to.
Page size can be reduced by 386.0 kB (66%)
585.2 kB
199.2 kB
In fact, the total size of Icare.to main page is 585.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. 60% of websites need less resources to load. CSS take 254.6 kB which makes up the majority of the site volume.
Potential reduce by 15.4 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 15.4 kB or 74% of the original size.
Potential reduce by 4.0 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. I CARE images are well optimized though.
Potential reduce by 155.1 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 155.1 kB or 64% of the original size.
Potential reduce by 211.4 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. Icare.to needs all CSS files to be minified and compressed as it can save up to 211.4 kB or 83% of the original size.
Number of requests can be reduced by 15 (28%)
53
38
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I CARE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
icare.to
332 ms
main.php
385 ms
icare.css
242 ms
search.css
188 ms
mouseover-en.js
190 ms
calNew.js
454 ms
calNew.css
281 ms
AC_RunActiveContent.js
273 ms
brand
15 ms
counter.js
8 ms
brand
20 ms
flashHeader.jpg
82 ms
EN.jpg
87 ms
FR.jpg
88 ms
SP.jpg
89 ms
logo.jpg
160 ms
icare_04.jpg
99 ms
icare_home-over.jpg
187 ms
icare_06.jpg
189 ms
icare_news-over.jpg
189 ms
icare_budhet-over.jpg
188 ms
icare_about-over.jpg
221 ms
icare_crosp-over.jpg
332 ms
icare_countryf-over.jpg
330 ms
icare_travhelp-over.jpg
333 ms
icare_links-over.jpg
335 ms
icare_search-over.jpg
333 ms
icare_archive-over.jpg
336 ms
icare_contact-over.jpg
337 ms
icare_17.jpg
341 ms
maat.gif
380 ms
magenta-newlogo-small.jpg
380 ms
fbgroup.jpg
381 ms
nieuwsjebg2.jpg
380 ms
hcnlogo.jpg
405 ms
MAILINGLIST_ZT.jpg
498 ms
AGENDA_ZT_RI.jpg
443 ms
b6eFWkSKuMw
96 ms
google_custom_search_watermark.gif
32 ms
t.php
57 ms
www-embed-player-vflfNyN_r.css
52 ms
www-embed-player.js
80 ms
base.js
117 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
17 ms
ad_status.js
60 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
55 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
55 ms
icaremenuANIM_02.gif
448 ms
icare_home-over-over.jpg
94 ms
icare_news-over-over.jpg
91 ms
icare_about-over-over.jpg
92 ms
icare_budhet-over-over.jpg
83 ms
icare_crosp-over-over.jpg
97 ms
icare_countryf-over-over.jpg
163 ms
icare_travhelp-over-over.jpg
178 ms
icare_links-over-over.jpg
174 ms
icare_search-over-over.jpg
180 ms
icare_archive-over-over.jpg
187 ms
icare_contact-over-over.jpg
242 ms
icare.to accessibility score
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
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
icare.to 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
icare.to 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
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Icare.to 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 Icare.to 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.
icare.to
Open Graph description is not detected on the main page of I CARE. 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: