3.3 sec in total
238 ms
2.9 sec
143 ms
Welcome to registry.mx homepage info - get ready to check Registry best content for Mexico right away, or after learning these important things about registry.mx
Visit registry.mxWe analyzed Registry.mx page load time and found that the first response time was 238 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
registry.mx performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value9.8 s
0/100
25%
Value10.9 s
6/100
10%
Value1,900 ms
8/100
30%
Value0.079
94/100
15%
Value13.1 s
12/100
10%
238 ms
348 ms
103 ms
196 ms
195 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 96% of them (81 requests) were addressed to the original Registry.mx, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (805 ms) belongs to the original domain Registry.mx.
Page size can be reduced by 195.3 kB (16%)
1.2 MB
1.0 MB
In fact, the total size of Registry.mx main page is 1.2 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. 35% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 28.9 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 5.9 kB, which is 17% 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 28.9 kB or 82% of the original size.
Potential reduce by 66.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. Registry images are well optimized though.
Potential reduce by 62.0 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 62.0 kB or 55% of the original size.
Potential reduce by 37.7 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. Registry.mx needs all CSS files to be minified and compressed as it can save up to 37.7 kB or 86% of the original size.
Number of requests can be reduced by 40 (51%)
79
39
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Registry. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
registry.mx
238 ms
www.registry.mx
348 ms
nicStylesDefault.css
103 ms
dropdown_ie5.css
196 ms
inicio.css
195 ms
mm.js
196 ms
nicscripts.js
198 ms
jquery-1.9.1.min.js
307 ms
jquery.slides.min.js
200 ms
indexNews.js
299 ms
ga.js
40 ms
nic_backfade.jpg
105 ms
nic_lateralizquierdo.jpg
105 ms
nic_esquina01.jpg
105 ms
nic_backheader.jpg
104 ms
nic_header_back_aux.jpg
105 ms
nic_backheader_logo_es.jpg
298 ms
nic_backheader_logo_trns.gif
202 ms
nic_men_06extra.jpg
198 ms
nic_menu_01somos_rty_es.jpg
196 ms
nic_menu_02programa_es.jpg
200 ms
nic_menu_03dominios_es.jpg
199 ms
nic_menu_05oportunidades_es.jpg
293 ms
nic_menu_06sala_es.jpg
293 ms
nic_home_puntos.gif
294 ms
rar_desar1_logo
416 ms
3NfbCfG1AF5eOOqeeHfRsxtHjqN6ZYFAs2G62Ky6_logo
517 ms
rar_desig_logo.gif
717 ms
rar_grupo3_logo.png
805 ms
nic_home_ingresoclientes_es.gif
294 ms
nic_btn_ingresar_es.jpg
296 ms
es_index_online.jpg
484 ms
nic_home_consultar_es.gif
388 ms
nic_btn_buscar_es.jpg
389 ms
nic_home_sitiosinteres_es.gif
391 ms
nic_esquina02.jpg
393 ms
ajs.php
411 ms
__utm.gif
13 ms
collect
60 ms
fileUploadedServlet
226 ms
lg.php
118 ms
ajs.php
124 ms
banner_registry_es.png
580 ms
lg.php
120 ms
ajs.php
125 ms
banner_accredited_es.png
396 ms
lg.php
118 ms
ajs.php
128 ms
banner_reseller_es.png
387 ms
lg.php
119 ms
ajs.php
128 ms
banner_registrant_es.png
490 ms
lg.php
116 ms
nic_home_tit_noticias_es.gif
101 ms
ajs.php
225 ms
fileUploadedServlet
417 ms
lg.php
117 ms
nic_home_tit_important_information_es.gif
99 ms
ajs.php
129 ms
fileUploadedServlet
120 ms
lg.php
117 ms
nic_home_tit_algunosdistribuidores_es.gif
99 ms
nic_home_backlaterales.jpg
101 ms
nic_home_backtextbox.jpg
194 ms
nic_vineta_roja.gif
196 ms
nic_home_lateralshadow.jpg
207 ms
ajs.php
235 ms
fileUploadedServlet
119 ms
lg.php
117 ms
nic_footerbackizq.jpg
100 ms
nic_footerback.jpg
99 ms
nic_footerbackder.jpg
100 ms
nic_lateralderecho.gif
102 ms
nic_esquina03.gif
196 ms
nic_lateralinferior.jpg
196 ms
nic_esquina04.gif
199 ms
ant.png
200 ms
sig.png
212 ms
slide.png
213 ms
selectslide.png
292 ms
nic_btn_iniciarsesion_on_es.gif
100 ms
nic_interior_ayuda_on_es.gif
98 ms
nic_panel_cerrarsesion_on_es.gif
98 ms
nic_panel_regresar_on_es.gif
99 ms
registry.mx 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
[aria-hidden="true"] elements contain focusable descendents
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
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.
registry.mx 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
General
Impact
Issue
Detected JavaScript libraries
registry.mx 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
ES
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Registry.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish 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 Registry.mx 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.
registry.mx
Open Graph description is not detected on the main page of Registry. 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: