9 sec in total
1.4 sec
7.1 sec
478 ms
Visit imoncology.com now to see the best up-to-date Imoncology content for Spain and also check out these interesting facts you probably never knew about imoncology.com
Descubre por qué somos expertos en oncología. Busca información sobre los tipos de cáncer, sus tratamientos y cómo y dónde te ayudamos a tratarlos.
Visit imoncology.comWe analyzed Imoncology.com page load time and found that the first response time was 1.4 sec and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
imoncology.com performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value9.8 s
0/100
25%
Value11.8 s
4/100
10%
Value4,120 ms
1/100
30%
Value0.163
72/100
15%
Value18.5 s
3/100
10%
1378 ms
27 ms
400 ms
277 ms
282 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 72% of them (63 requests) were addressed to the original Imoncology.com, 7% (6 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Partner.shareaholic.com.
Page size can be reduced by 2.1 MB (59%)
3.5 MB
1.4 MB
In fact, the total size of Imoncology.com main page is 3.5 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. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 241.5 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 241.5 kB or 90% of the original size.
Potential reduce by 30.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. Imoncology images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 74% of the original size.
Potential reduce by 685.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. Imoncology.com needs all CSS files to be minified and compressed as it can save up to 685.4 kB or 85% of the original size.
Number of requests can be reduced by 50 (63%)
80
30
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imoncology. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.imoncology.com
1378 ms
shareaholic.js
27 ms
bbpress.css
400 ms
styles.css
277 ms
cff-style.css
282 ms
font-awesome.min.css
21 ms
swpm.common.css
281 ms
validationEngine.jquery.css
284 ms
tribe-events-full.min.css
556 ms
style.css
1272 ms
style.css
560 ms
jquery-jvectormap-2.0.2.css
421 ms
css
24 ms
style.css
535 ms
shortcodes.css
836 ms
shortcodes_responsive.css
564 ms
animate.min.css
840 ms
jquery.js
986 ms
jquery-migrate.min.js
690 ms
bsk_pdf_manager.js
693 ms
jquery.validationEngine-en.js
839 ms
jquery.validationEngine.js
961 ms
jquery-jvectormap-2.0.2.min.js
1255 ms
jquery-jvectormap-es-merc-en-c.js
1100 ms
jquery-jvectormap-es-merc-en.js
1404 ms
fdcc7076237f06abafd8b0aaaab58c5a.json
46 ms
css
15 ms
editor.js
676 ms
jquery.form.min.js
698 ms
scripts.js
818 ms
eu-cookie-law.js
816 ms
cff-scripts.js
834 ms
custom.js
1099 ms
general.js
951 ms
comment-reply.min.js
968 ms
jquery.fitvids.js
970 ms
waypoints.min.js
973 ms
jquery.magnific-popup.js
1218 ms
public.min.js
1115 ms
imagesloaded.js
1105 ms
masonry.js
1121 ms
extra.css
1015 ms
iconos.css
1124 ms
analytics.js
129 ms
logo-imo-oncology.jpg
174 ms
Cyberknife21.jpg
171 ms
empty.png
172 ms
portada-21.jpg
422 ms
portada-3.jpg
1011 ms
slider_4.jpg
173 ms
slide-fundacionb.jpg
483 ms
logo-fundacion-blanco.png
323 ms
blurbs1.jpg
323 ms
tomoterapia-espec.jpg
323 ms
espec2.jpg
481 ms
dr-ignacio-azinovic.jpg
482 ms
gonzalez-larriba-r.jpg
481 ms
concha-alonso-2.jpg
485 ms
FONDO-NI%C3%91O-faldon1-e1458295471809-400x250.jpg
607 ms
linfedema2-400x250.jpg
606 ms
0unnamed-400x250.jpg
607 ms
eventos.jpg
607 ms
shrMain.min.js
59 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
95 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
176 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
101 ms
EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf
102 ms
ETmodules_v2.ttf
691 ms
icomoon.ttf
707 ms
close.png
627 ms
admin-ajax.php
1552 ms
_KgyLYKzdyg
140 ms
collect
55 ms
jquery.min.js
56 ms
www-embed-player-vflfNyN_r.css
176 ms
www-embed-player.js
220 ms
base.js
242 ms
analytics.js
133 ms
pageview.gif
65 ms
partners.js
3148 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
23 ms
ad_status.js
61 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
59 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
62 ms
imoncology-banner-inicio.jpg
554 ms
close.png
132 ms
tribe-events-full-mobile.min.css
138 ms
imoncology.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
imoncology.com 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
imoncology.com 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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imoncology.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Imoncology.com 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.
imoncology.com
Open Graph description is not detected on the main page of Imoncology. 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: