4.1 sec in total
362 ms
3.6 sec
132 ms
Visit keel.es now to see the best up-to-date KEEL content and also check out these interesting facts you probably never knew about keel.es
KEEL contains classical knowledge extraction algorithms, preprocessing techniques, Computational Intelligence based learning algorithms, evolutionary rule learning algorithms, genetic fuzzy systems, e...
Visit keel.esWe analyzed Keel.es page load time and found that the first response time was 362 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
keel.es performance score
362 ms
283 ms
999 ms
102 ms
202 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Keel.es, 92% (61 requests) were made to Sci2s.ugr.es and 2% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Sci2s.ugr.es.
Page size can be reduced by 46.4 kB (19%)
246.9 kB
200.4 kB
In fact, the total size of Keel.es main page is 246.9 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. 25% of websites need less resources to load. Images take 214.8 kB which makes up the majority of the site volume.
Potential reduce by 1.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 1.5 kB or 61% of the original size.
Potential reduce by 24.9 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, KEEL needs image optimization as it can save up to 24.9 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 4.9 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 4.9 kB or 42% of the original size.
Potential reduce by 15.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. Keel.es needs all CSS files to be minified and compressed as it can save up to 15.2 kB or 84% of the original size.
We found no issues to fix!
42
42
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KEEL. According to our analytics all requests are already optimized.
keel.es
362 ms
283 ms
999 ms
style.css
102 ms
functions.js
202 ms
logo_nuevo.jpg
274 ms
cabecera_nueva.jpg
93 ms
cabecera_nueva.jpg
312 ms
bis.jpg
199 ms
menu_nuevo.jpg
93 ms
menu_nuevo.jpg
171 ms
funcMenu.js
165 ms
urchin.js
20 ms
description.gif
93 ms
members.gif
185 ms
publication.gif
468 ms
references.gif
970 ms
keel-dataset.gif
627 ms
keel2.gif
688 ms
software2.gif
1469 ms
links2.gif
276 ms
access.gif
368 ms
description1.gif
459 ms
members1.gif
552 ms
publication1.gif
567 ms
references1.gif
642 ms
keel-dataset1.gif
668 ms
keel3.gif
726 ms
software3.gif
734 ms
links3.gif
768 ms
access1.gif
788 ms
description.gif
103 ms
download.gif
184 ms
manual.gif
184 ms
logoKEEL-dataset-2.png
295 ms
algorithms.gif
233 ms
links.gif
204 ms
private_access.gif
277 ms
ministerio.gif
276 ms
graphs.png
303 ms
fondo_nuevo.jpg
333 ms
keelsoft_snapshot.png
550 ms
doc_icon_tiny.jpg
825 ms
adobe.gif
368 ms
__utm.gif
22 ms
valid-xhtml11-blue
151 ms
vcss-blue
124 ms
description.gif
297 ms
members.gif
222 ms
links2.gif
161 ms
access.gif
96 ms
description1.gif
101 ms
publication.gif
101 ms
members1.gif
92 ms
publication1.gif
101 ms
keel-dataset.gif
101 ms
references1.gif
93 ms
keel-dataset1.gif
101 ms
keel2.gif
92 ms
keel3.gif
92 ms
software3.gif
101 ms
links3.gif
101 ms
access1.gif
92 ms
doc_icon_tiny.jpg
92 ms
references.gif
101 ms
software2.gif
100 ms
keel.es 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
<frame> or <iframe> elements do not have a title
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
keel.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
keel.es SEO score
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
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Keel.es 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 Keel.es 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.
keel.es
Open Graph description is not detected on the main page of KEEL. 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: