3.7 sec in total
587 ms
2.9 sec
208 ms
Click here to check amazing INVEX content for Mexico. Otherwise, check out these important facts you probably never knew about invex.com
- (root)INVEX
Visit invex.comWe analyzed Invex.com page load time and found that the first response time was 587 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
invex.com performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value14.0 s
0/100
25%
Value8.3 s
19/100
10%
Value1,070 ms
25/100
30%
Value0.627
9/100
15%
Value15.0 s
7/100
10%
587 ms
151 ms
145 ms
293 ms
215 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 95% of them (58 requests) were addressed to the original Invex.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Invex.com.
Page size can be reduced by 1.1 MB (52%)
2.1 MB
1.0 MB
In fact, the total size of Invex.com main page is 2.1 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. 50% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 12.7 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. This page needs HTML code to be minified as it can gain 2.3 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 12.7 kB or 69% of the original size.
Potential reduce by 560.8 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, INVEX needs image optimization as it can save up to 560.8 kB or 39% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 363.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 363.2 kB or 72% of the original size.
Potential reduce by 170.3 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. Invex.com needs all CSS files to be minified and compressed as it can save up to 170.3 kB or 88% of the original size.
Number of requests can be reduced by 22 (37%)
59
37
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of INVEX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
invex.com
587 ms
invex.css
151 ms
menu.css
145 ms
invex_rojo.css
293 ms
Dialogs.css
215 ms
ECommerce.css
145 ms
jquery.bxslider.css
140 ms
WebResource.axd
281 ms
jquery-1.9.1.min.js
429 ms
jquery-migrate-1.1.1.min.js
211 ms
GoogleAnalytics.js
219 ms
mootools.js
332 ms
ScriptResource.axd
400 ms
ScriptResource.axd
251 ms
ScriptResource.axd
297 ms
ScriptResource.axd
303 ms
ScriptResource.axd
308 ms
jquery.li-scroller.1.0.js
366 ms
functions.js
409 ms
functions2.js
408 ms
jquery.tools.min.js
410 ms
resoluciones.js
441 ms
jquery.bxslider.js
448 ms
bg.gif
202 ms
busqueda_lupa.png
202 ms
001_invex-fiduciario.aspx
496 ms
002_perfil_inversor-diversifica.aspx
942 ms
008.aspx
1552 ms
009.aspx
2094 ms
ic_alza.png
405 ms
ic_baja.png
346 ms
ga.js
36 ms
busqueda_back.png
248 ms
account_icon.png
304 ms
mail_icon.png
320 ms
fondoGeneralMenu.png
375 ms
logo.png
393 ms
fondoMenuInicial.png
393 ms
fondoMenu.png
445 ms
ind_start.png
462 ms
el_bg.png
463 ms
indicadores_icon.png
514 ms
ind_sep.png
533 ms
twitter_icon.png
533 ms
ind_end.png
583 ms
video.png
603 ms
booket1.png
882 ms
booket2.png
654 ms
booket3.png
1232 ms
Barrainvex4.jpg
725 ms
piePagina.aspx
800 ms
__utm.gif
37 ms
bx_loader.gif
782 ms
controls.png
817 ms
collect
63 ms
PiePagina.css
102 ms
footer_back.jpg
74 ms
buro1.jpg
72 ms
codusef-135x60.png
73 ms
IPAB-109X60px.png
141 ms
logo_footer.png
140 ms
invex.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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
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
invex.com SEO score
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Invex.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 Invex.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.
invex.com
Open Graph description is not detected on the main page of INVEX. 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: