16.1 sec in total
3.5 sec
12 sec
708 ms
Visit aeal.es now to see the best up-to-date AEAL content for Peru and also check out these interesting facts you probably never knew about aeal.es
AEAL - Asociación de pacientes de Linfoma, Mieloma, Leucemia y Síndromes Mieloproliferativos, el sitio de información del cáncer oncohematológico para los pacientes.
Visit aeal.esWe analyzed Aeal.es page load time and found that the first response time was 3.5 sec and then it took 12.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
aeal.es performance score
name
value
score
weighting
Value8.8 s
0/100
10%
Value43.0 s
0/100
25%
Value24.8 s
0/100
10%
Value500 ms
58/100
30%
Value0.062
97/100
15%
Value30.1 s
0/100
10%
3467 ms
34 ms
516 ms
259 ms
828 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 41% of them (63 requests) were addressed to the original Aeal.es, 11% (16 requests) were made to Maps.googleapis.com and 11% (16 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source External.xx.fbcdn.net.
Page size can be reduced by 1.7 MB (48%)
3.5 MB
1.8 MB
In fact, the total size of Aeal.es 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. 60% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 126.6 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 126.6 kB or 78% of the original size.
Potential reduce by 61.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. AEAL images are well optimized though.
Potential reduce by 979.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 979.2 kB or 67% of the original size.
Potential reduce by 535.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. Aeal.es needs all CSS files to be minified and compressed as it can save up to 535.2 kB or 86% of the original size.
Number of requests can be reduced by 82 (56%)
146
64
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AEAL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
aeal.es
3467 ms
analytics.js
34 ms
wp-emoji-release.min.js
516 ms
styles.css
259 ms
settings.css
828 ms
font-awesome.css
592 ms
collect
26 ms
jquery_datetimepicker.css
368 ms
bootstrap.css
1127 ms
responsive.css
868 ms
style.css
1483 ms
widget.css
948 ms
flexslider.css
790 ms
mediaelementplayer.min.css
1259 ms
prettyphoto.css
1274 ms
cs_woocommerce.css
1857 ms
jquery.js
1899 ms
jquery-migrate.min.js
1511 ms
jquery.themepunch.tools.min.js
2172 ms
jquery.themepunch.revolution.min.js
2603 ms
cs-connect.js
1736 ms
css
44 ms
js
86 ms
comment-reply.min.js
1379 ms
jquery.form.min.js
1838 ms
scripts.js
1754 ms
counter.js
1833 ms
cause_functions.js
1874 ms
bootstrap_min.js
2408 ms
jquery_datetimepicker.js
2581 ms
mediaelement-and-player.min.js
2684 ms
wp-mediaelement.js
2122 ms
underscore.min.js
2407 ms
wp-util.min.js
2369 ms
backbone.min.js
2696 ms
wp-playlist.js
2668 ms
functions.js
2803 ms
addthis_widget.js
9 ms
css
14 ms
css
25 ms
logo_aeal_web_aeal.png
441 ms
banner-aeal-alopecia2.jpg
1240 ms
banner-LNH.jpg
1092 ms
BANER_WEB_AEAL_APOYA_2016.jpg
1183 ms
banner-aeal-apadrina.jpg
1227 ms
BANER_WEB_AEAL_SENSIBILIZACION_2016.jpg
1230 ms
ROCHE.png
836 ms
JANSSEN.png
834 ms
logo_aeal_web_aeal.png
833 ms
INVITACI%C3%93N_SOCIOS_DMCC2016-370x208.jpg
1216 ms
HEADER_WEB_AEAL_DM_LMC_LMA_2015-370x208.png
1757 ms
HEADER_FACEBOOK_AEAL_DM_MIELOMA_MULTIPLE_AEAL_2015-370x208.png
1706 ms
asamblea-370x208.jpg
1725 ms
image0012-370x208.jpg
1631 ms
Alopecia-noticias-aeal.jpg
1813 ms
logo_facebook_web_aeal.png
1514 ms
logo_twitter_web_aeal.png
1780 ms
logo_vimeo_web_aeal.png
2040 ms
logo_you_tube_web_aeal.png
2040 ms
Untitled-1.png
2263 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
55 ms
fontawesome-webfont.woff
2580 ms
fontawesome-webfont.woff
2519 ms
y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf
26 ms
K6ngFdK5haaaRGBV8waDwA.ttf
92 ms
barra_actualidad_web_aeal.png
2352 ms
sdk.js
269 ms
bg-blockot.png
1974 ms
widgets.js
88 ms
barra_lienzo_web_aeal.png
2460 ms
footer-web-aeal.jpg
2674 ms
440 ms
xd_arbiter.php
361 ms
xd_arbiter.php
716 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
206 ms
300lo.json
76 ms
loader.gif
1752 ms
coloredbg.png
1913 ms
large_left.png
1967 ms
large_right.png
1985 ms
sh.8e5f85691f9aaa082472a194.html
58 ms
pixel
24 ms
pixel
19 ms
match-result
4 ms
page.php
343 ms
syndication
102 ms
623397260634791936
172 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
39 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
63 ms
LUdypCgtRlc.css
297 ms
46icGyCHNkx.css
367 ms
7UFpPvIym7D.css
439 ms
q68gy-v_YMF.js
631 ms
YvxwM8R7ol8.js
654 ms
ihptErjAmMX.js
567 ms
3So47A9WcrL.js
509 ms
cUsKAwzqrQw.js
678 ms
f6902542ca0992883873d549dd5df8bf_normal.jpeg
172 ms
5UGcvdEx_normal.jpg
196 ms
n5EmdbGt_normal.jpeg
230 ms
y_OHMlYG_normal.jpg
261 ms
CdmknTjWIAICXXb.jpg
308 ms
CdmrVrOW8AQp3CZ.jpg
285 ms
Cdk8kdYXEAAV9j3.jpg
356 ms
CdQe2XEW0AAMwmO.jpg
398 ms
CdGSdP2XEAAl2QP.jpg
330 ms
Cc9BgYLW4AAa-FT.jpg
317 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
73 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
97 ms
link_v1_e64f66f5650df987d97cc5f00c4cb5987f367028.svg
7 ms
jot.html
27 ms
12832391_1132780026732308_7101518939687779423_n.jpg
384 ms
safe_image.php
1828 ms
safe_image.php
3775 ms
399782_592601614083488_1077117309_n.jpg
439 ms
10492302_1135387976471513_180936098920787471_n.jpg
634 ms
8681_1135387589804885_6629842473290671402_n.jpg
724 ms
wL6VQj7Ab77.png
128 ms
s7jcwEQH7Sx.png
128 ms
GtIpNnEyqq_.png
128 ms
lRyN50VcaFW.js
68 ms
common.js
22 ms
util.js
47 ms
stats.js
67 ms
AuthenticationService.Authenticate
265 ms
R9a_DtVRZgv.js
91 ms
cUDgRFxaoIk.js
90 ms
0JBr1QHp8Gi.js
89 ms
kDOzhTr2W91.js
88 ms
map.js
12 ms
marker.js
48 ms
onion.js
20 ms
openhand_8_8.cur
115 ms
ViewportInfoService.GetViewportInfo
105 ms
controls.js
23 ms
css
181 ms
transparent.png
85 ms
infowindow.js
122 ms
spotlight-poi.png
84 ms
google4.png
107 ms
mapcnt6.png
145 ms
sv5.png
145 ms
tmapctrl.png
102 ms
cb_scout5.png
104 ms
tmapctrl4.png
113 ms
imgs8.png
114 ms
google_white5.png
113 ms
vt
68 ms
vt
67 ms
vt
68 ms
vt
99 ms
vt
95 ms
aeal.es 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
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
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
aeal.es 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
aeal.es 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
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 Aeal.es 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 Aeal.es 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.
aeal.es
Open Graph description is not detected on the main page of AEAL. 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: