9.1 sec in total
380 ms
8 sec
683 ms
Visit cartesio.com now to see the best up-to-date Cartesio content for Spain and also check out these interesting facts you probably never knew about cartesio.com
Gestora independiente de fondos de inversión donde los gestores están realmente alineados con el inversor y los resultados son excelentes
Visit cartesio.comWe analyzed Cartesio.com page load time and found that the first response time was 380 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
cartesio.com performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value15.0 s
0/100
25%
Value8.6 s
17/100
10%
Value550 ms
54/100
30%
Value0.357
30/100
15%
Value15.6 s
6/100
10%
380 ms
1174 ms
396 ms
966 ms
558 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 77% of them (73 requests) were addressed to the original Cartesio.com, 8% (8 requests) were made to Apis.google.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Cartesio.com.
Page size can be reduced by 928.6 kB (41%)
2.3 MB
1.4 MB
In fact, the total size of Cartesio.com main page is 2.3 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. 55% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 47.3 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 47.3 kB or 80% of the original size.
Potential reduce by 733.1 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, Cartesio needs image optimization as it can save up to 733.1 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 63.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 63.2 kB or 47% of the original size.
Potential reduce by 85.0 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. Cartesio.com needs all CSS files to be minified and compressed as it can save up to 85.0 kB or 88% of the original size.
Number of requests can be reduced by 33 (38%)
87
54
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cartesio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
cartesio.com
380 ms
www.cartesio.com
1174 ms
colorbox.css
396 ms
styles.css
966 ms
slider_styles.css
558 ms
css
85 ms
css
116 ms
css
128 ms
css
126 ms
jquery.min.js
114 ms
jquery-ui.min.js
147 ms
layout.css
334 ms
jquery-1.6.1.min.js
328 ms
funciones.js
341 ms
jquery.cookie.js
464 ms
challenge
45 ms
jquery.colorbox.js
644 ms
jquery.scrollTo.js
487 ms
jquery.nivo.slider.js
389 ms
analytics.js
87 ms
cartesio-logo.png
238 ms
slider01.jpg
4436 ms
slider02.jpg
1740 ms
slider03.jpg
673 ms
slider04.jpg
5588 ms
slider05.jpg
5602 ms
cartesio_y_blanco_slider.svg
407 ms
boton_rentabilidad.png
528 ms
boton_informacion.png
670 ms
cartesio_x_blanco_slider.svg
797 ms
cartesio_equity_blanco_slider.svg
829 ms
cartesio_income_blanco_slider.svg
940 ms
flecha01.png
952 ms
cartesio_x_white.png
1197 ms
flecha03.png
1082 ms
cartesio_y_med.png
1219 ms
cartesio_x_med.png
1310 ms
cartesio_equity_vert.png
1492 ms
cartesio_income_vert.png
1436 ms
logo_pdf.png
1566 ms
10_aniversario_peque.png
1608 ms
flecha04.png
1694 ms
cartesio_y.png
1745 ms
cartesio_y_peq.png
1818 ms
cartesio_y.svg
1859 ms
premio_cartesio_y.jpg
1887 ms
cartesio_equity_asterisco.png
1944 ms
cartesio_equity.svg
1977 ms
premio_cartesio_equity.jpg
2045 ms
cartesio_x.png
2077 ms
cartesio_x_peq.png
2125 ms
cartesio_x.svg
2165 ms
premio_cartesio_x.jpg
2226 ms
cartesio_income_asterisco.png
2259 ms
cartesio_income.svg
2291 ms
premio_cartesio_income.jpg
2368 ms
dazS1PrQQuCxC3iOAJFEJbfB31yxOzP-czbf6AAKCVo.ttf
162 ms
y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf
193 ms
dazS1PrQQuCxC3iOAJFEJZ_TkvowlIOtbR7ePgFOpF4.ttf
200 ms
collect
138 ms
platform.js
265 ms
flecha02.png
2168 ms
cb=gapi.loaded_0
10 ms
cb=gapi.loaded_1
38 ms
fastbutton
110 ms
one.png
2007 ms
postmessageRelay
70 ms
cb=gapi.loaded_0
35 ms
cb=gapi.loaded_1
35 ms
3193398744-postmessagerelay.js
62 ms
rpc:shindig_random.js
58 ms
two.png
1976 ms
cb=gapi.loaded_0
22 ms
three.png
1845 ms
four.png
1856 ms
five.png
1823 ms
cartesio_equity_med.png
1955 ms
cartesio_income_med.png
1764 ms
localizador.png
1793 ms
contacta.png
1751 ms
telefono.png
1709 ms
fax.png
1683 ms
cartesio_grey.png
1644 ms
logo_fb.png
1601 ms
logo_gplus.png
1526 ms
logo_in.png
1509 ms
logo_tw.png
1529 ms
close.png
1495 ms
overlay.png
1460 ms
cayetano.jpg
1657 ms
alvaro.jpg
1669 ms
juan.jpg
1672 ms
foto_grupo.jpg
2021 ms
cartesio_y_white.png
942 ms
cartesio_equity_white.png
160 ms
cartesio.com 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
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
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.
cartesio.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
cartesio.com 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
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cartesio.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 Cartesio.com main page’s claimed encoding is windows-1252. 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.
cartesio.com
Open Graph description is not detected on the main page of Cartesio. 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: