5.1 sec in total
425 ms
3.8 sec
862 ms
Welcome to iris.ai homepage info - get ready to check Iris best content for India right away, or after learning these important things about iris.ai
AI for scientific text understanding - literature reviews, research data extraction, post-market surveillance, and other tedious tasks.
Visit iris.aiWe analyzed Iris.ai page load time and found that the first response time was 425 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
iris.ai performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value6.4 s
9/100
25%
Value49.8 s
0/100
10%
Value60,270 ms
0/100
30%
Value0.041
99/100
15%
Value76.4 s
0/100
10%
425 ms
312 ms
173 ms
481 ms
171 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 66% of them (53 requests) were addressed to the original Iris.ai, 5% (4 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Iris.ai.
Page size can be reduced by 706.1 kB (18%)
3.9 MB
3.2 MB
In fact, the total size of Iris.ai main page is 3.9 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 186.8 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 186.8 kB or 85% of the original size.
Potential reduce by 446.4 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, Iris needs image optimization as it can save up to 446.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 23.2 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 23.2 kB or 17% of the original size.
Potential reduce by 49.7 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. Iris.ai needs all CSS files to be minified and compressed as it can save up to 49.7 kB or 36% of the original size.
Number of requests can be reduced by 45 (58%)
78
33
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iris. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
iris.ai
425 ms
dnyuo.css
312 ms
js
173 ms
dnylo.css
481 ms
css
171 ms
dnylo.css
398 ms
dnylo.css
420 ms
dnylo.js
520 ms
dnylo.js
570 ms
dnylo.js
456 ms
dnylo.js
455 ms
jquery.sticky.min.js
172 ms
css
171 ms
css
171 ms
shell.js
354 ms
magnific-popup.css
167 ms
jquery.magnific-popup.min.js
352 ms
fallback.js
381 ms
core.min.js
442 ms
datepicker.min.js
442 ms
jquery.typewatch.js
452 ms
featherlight.js
452 ms
select2.full.min.js
673 ms
tooltip.js
667 ms
lity.min.js
671 ms
colorbrightness.min.js
668 ms
owl.carousel.min.js
670 ms
main.js
667 ms
2048671.js
339 ms
slick.min.js
764 ms
mouse.min.js
762 ms
draggable.min.js
767 ms
droppable.min.js
762 ms
slider.min.js
767 ms
ctf-scripts.min.js
761 ms
css
96 ms
js
182 ms
analytics.js
290 ms
yB7I2FU1_normal.jpg
245 ms
3aqMV0lA_normal.jpg
246 ms
Iris.AI_logo_black_small.png
252 ms
user.svg
249 ms
RW.png
749 ms
nature_logo.png
252 ms
red-bull_logo.png
249 ms
fast-company_logo.png
250 ms
theengineer_logo.png
408 ms
tech_crunch_logo.png
418 ms
world-economic-forum_logo.png
409 ms
wired_logo-1.png
405 ms
business_insider_nordic_logo.png
407 ms
Singularity-University_logo.png
410 ms
youtube_anita_tedx_logo.png
1240 ms
huffpost_logo.jpg
524 ms
science_logo.png
409 ms
VentureBeat_logo.png
523 ms
slush_logo.png
524 ms
Iris.AI_logo_scaled.png
546 ms
39-1.gif
419 ms
HeroShot-Today-1.svg
420 ms
jwmNRnwk92-.png
419 ms
arrow-down.svg
458 ms
collect
134 ms
collect
210 ms
uwt.js
151 ms
leadflows.js
512 ms
2048671.js
458 ms
2048671.js
509 ms
fb.js
479 ms
json
306 ms
ajax-loader.gif
162 ms
slick.woff
160 ms
adsct
283 ms
adsct
277 ms
json
143 ms
dnylo.css
89 ms
enterprise.js
309 ms
menu.js
271 ms
themify.sidemenu.js
152 ms
recaptcha__en.js
33 ms
iris.ai 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
Form elements do not have associated labels
Links do not have a discernible name
iris.ai best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
iris.ai SEO score
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 Iris.ai 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 Iris.ai 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.
iris.ai
Open Graph data is detected on the main page of Iris. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: