14.6 sec in total
4.1 sec
9.5 sec
961 ms
Visit lotenal.gob.mx now to see the best up-to-date Lotenal content for Mexico and also check out these interesting facts you probably never knew about lotenal.gob.mx
Visit lotenal.gob.mxWe analyzed Lotenal.gob.mx page load time and found that the first response time was 4.1 sec and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lotenal.gob.mx performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value34.8 s
0/100
25%
Value12.0 s
4/100
10%
Value3,960 ms
1/100
30%
Value0.196
63/100
15%
Value10.1 s
26/100
10%
4081 ms
109 ms
135 ms
142 ms
146 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 88% of them (114 requests) were addressed to the original Lotenal.gob.mx, 8% (10 requests) were made to Google.com and 2% (3 requests) were made to Encuentra.gob.mx. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Lotenal.gob.mx.
Page size can be reduced by 1.1 MB (34%)
3.1 MB
2.1 MB
In fact, the total size of Lotenal.gob.mx main page is 3.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. 60% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 44.0 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 44.0 kB or 78% of the original size.
Potential reduce by 441.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, Lotenal needs image optimization as it can save up to 441.1 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 434.6 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 434.6 kB or 69% of the original size.
Potential reduce by 131.9 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. Lotenal.gob.mx needs all CSS files to be minified and compressed as it can save up to 131.9 kB or 82% of the original size.
Number of requests can be reduced by 79 (64%)
124
45
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lotenal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 37 to 1 for CSS and as a result speed up the page load time.
lotenal.gob.mx
4081 ms
apf.css
109 ms
system.base.css
135 ms
system.menus.css
142 ms
system.messages.css
146 ms
system.theme.css
144 ms
jquery.ui.core.min.css
145 ms
jquery.ui.theme.min.css
145 ms
jquery.ui.button.min.css
195 ms
jquery.ui.resizable.min.css
202 ms
jquery.ui.dialog.min.css
207 ms
jquery.ui.datepicker.min.css
207 ms
date.css
203 ms
field.css
203 ms
node.css
263 ms
search.css
269 ms
user.css
272 ms
views.css
270 ms
ckeditor.css
276 ms
ctools.css
273 ms
menu_icons.css
331 ms
nice_menus.css
338 ms
nice_menus_default.css
339 ms
panels.css
341 ms
views_slideshow.css
343 ms
extlink.css
343 ms
nivo-slider.css
399 ms
default.css
406 ms
views_nivo_slider.css
407 ms
ultimos_permios.css
409 ms
style.css
424 ms
css_injector_1.css
502 ms
css_injector_3.css
471 ms
css_injector_5.css
464 ms
css_injector_6.css
488 ms
css_injector_8.css
490 ms
gobmxWidgetAPI-min.js
130 ms
gobmxWidgetAPI-conf.js
130 ms
css_injector_15.css
449 ms
jquery.min.js
526 ms
jquery.once.js
426 ms
drupal.js
440 ms
jquery.ui.core.min.js
441 ms
jquery.ui.widget.min.js
434 ms
jquery.qtip.js
536 ms
qtip.js
434 ms
jquery.ui.button.min.js
446 ms
jquery.ui.mouse.min.js
443 ms
jquery.ui.draggable.min.js
480 ms
jquery.ui.position.min.js
495 ms
jquery.ui.resizable.min.js
513 ms
jquery.ui.dialog.min.js
458 ms
jquery.ui.dialog.patch.js
449 ms
jquery.ui.datepicker.min.js
463 ms
jquery.cookie.js
481 ms
jquery.form.js
495 ms
ajax.js
518 ms
es_V4DtyJ2A7ow4VNuL972x5os7lCaKYV5ykT8G8vnA6yw.js
459 ms
lightbox.js
462 ms
superfish.js
463 ms
jquery.bgiframe.min.js
480 ms
jquery.hoverIntent.minified.js
494 ms
nice_menus.js
516 ms
panels.js
461 ms
views_slideshow.js
466 ms
extlink.js
466 ms
progress.js
482 ms
jquery.nivo.slider.pack.js
497 ms
views_nivo_slider.js
500 ms
googleanalytics.js
453 ms
ultimos_permios.js
458 ms
buscador_simple.js
447 ms
script.js
462 ms
extlink_extra.js
551 ms
fondo_f2.jpg
545 ms
cuadro.png
114 ms
header5.png
609 ms
19%20Papa%20Francisco%20en%20Me%CC%81xico.jpg
122 ms
21%2050%20Aniversario%20de%20la%20AMIP.jpg
114 ms
banner_convocatoria_0.jpg
121 ms
foraneo_0.jpg
175 ms
bannerOF.jpg
175 ms
buzonoic.jpg
171 ms
I05.jpg
173 ms
sorteos.jpg
537 ms
calendario.jpg
536 ms
billeteros.jpg
536 ms
mayor.jpg
537 ms
cobrar.jpg
537 ms
premios_04.png
538 ms
iso.jpg
539 ms
WLA_SECURITY_WEBlogo_e_RGB.png
539 ms
red_2.jpg
539 ms
red_8.jpg
539 ms
red_4.jpg
556 ms
red_9.jpg
558 ms
red_6.jpg
556 ms
red_7.jpg
557 ms
cse.js
88 ms
nav.png
486 ms
menuitem.png
485 ms
spacer.gif
487 ms
subitem.png
487 ms
tit.png
488 ms
gritona.png
519 ms
liston_rojo.png
487 ms
liston_grande.png
488 ms
buscador.jpg
517 ms
button.png
515 ms
footermenu.png
519 ms
cse.js
425 ms
esferas2.png
700 ms
loading.gif
119 ms
lotenal.gob.mx
4004 ms
bandera.png
110 ms
bullets.png
110 ms
liston_izq_amarillo.png
107 ms
ln.png
150 ms
ui-icons_222222_256x240.png
148 ms
jsapi
60 ms
default+es.css
4 ms
default.css
29 ms
default+es.I.js
35 ms
default.css
112 ms
async-ads.js
210 ms
google_custom_search_watermark.gif
163 ms
small-logo.png
24 ms
search_box_icon.png
25 ms
clear.png
23 ms
nav_logo114.png
7 ms
lotenal.gob.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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Links do not have a discernible name
lotenal.gob.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
lotenal.gob.mx 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 doesn't use legible font sizes
Tap targets are not sized appropriately
N/A
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lotenal.gob.mx can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Spanish. Our system also found out that Lotenal.gob.mx 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.
lotenal.gob.mx
Open Graph description is not detected on the main page of Lotenal. 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: