2.5 sec in total
211 ms
2.2 sec
129 ms
Visit if.ly now to see the best up-to-date If content and also check out these interesting facts you probably never knew about if.ly
The International Foundation for Science and Technology | المؤسسة الدولية للعلوم و التكنولوجيا
Visit if.lyWe analyzed If.ly page load time and found that the first response time was 211 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
if.ly performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value2.1 s
95/100
25%
Value2.1 s
99/100
10%
Value0 ms
100/100
30%
Value0.441
21/100
15%
Value0.8 s
100/100
10%
211 ms
176 ms
236 ms
321 ms
233 ms
Our browser made a total of 26 requests to load all elements on the main page. We found that all of those requests were addressed to If.ly and no external sources were called. The less responsive or slowest element that took the longest time to load (804 ms) belongs to the original domain If.ly.
Page size can be reduced by 433.0 kB (58%)
743.5 kB
310.5 kB
In fact, the total size of If.ly main page is 743.5 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. 20% of websites need less resources to load. Javascripts take 479.3 kB which makes up the majority of the site volume.
Potential reduce by 6.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. This page needs HTML code to be minified as it can gain 1.5 kB, which is 16% 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 6.9 kB or 72% of the original size.
Potential reduce by 50.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. Obviously, If needs image optimization as it can save up to 50.0 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 334.8 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 334.8 kB or 70% of the original size.
Potential reduce by 41.2 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. If.ly needs all CSS files to be minified and compressed as it can save up to 41.2 kB or 80% of the original size.
Number of requests can be reduced by 18 (72%)
25
7
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of If. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
211 ms
system.css
176 ms
position.css
236 ms
layout.css
321 ms
general.css
233 ms
personal.css
236 ms
template.css
301 ms
jquery.min.js
647 ms
jquery-noconflict.js
375 ms
jquery-migrate.min.js
371 ms
caption.js
377 ms
mootools-core.js
583 ms
core.js
424 ms
mootools-more.js
804 ms
bootstrap.min.js
575 ms
md_stylechanger.js
497 ms
hide.js
513 ms
respond.src.js
595 ms
template.js
602 ms
system.css
489 ms
personal2.png
475 ms
if.ly-logo.png
260 ms
fr_fr.gif
88 ms
ar_aa.gif
91 ms
en.gif
89 ms
print.css
90 ms
if.ly accessibility score
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
Links do not have a discernible name
if.ly 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
if.ly SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
AR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise If.ly can be misinterpreted by Google and other search engines. Our service has detected that Arabic is used on the page, and it does not match the claimed English language. Our system also found out that If.ly 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.
if.ly
Open Graph description is not detected on the main page of If. 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: