5.8 sec in total
904 ms
3.7 sec
1.1 sec
Visit sct.gob.mx now to see the best up-to-date Sct content for Mexico and also check out these interesting facts you probably never knew about sct.gob.mx
Visit sct.gob.mxWe analyzed Sct.gob.mx page load time and found that the first response time was 904 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
sct.gob.mx performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value12.9 s
0/100
25%
Value28.5 s
0/100
10%
Value18,510 ms
0/100
30%
Value0.021
100/100
15%
Value35.2 s
0/100
10%
904 ms
69 ms
38 ms
55 ms
83 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Sct.gob.mx, 20% (21 requests) were made to Maps.googleapis.com and 10% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (904 ms) relates to the external source Www.gob.mx.
Page size can be reduced by 1.2 MB (23%)
5.1 MB
3.9 MB
In fact, the total size of Sct.gob.mx main page is 5.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 76.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 76.5 kB or 79% of the original size.
Potential reduce by 206.0 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. Sct images are well optimized though.
Potential reduce by 719.8 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 719.8 kB or 68% of the original size.
Potential reduce by 171.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. Sct.gob.mx needs all CSS files to be minified and compressed as it can save up to 171.2 kB or 82% of the original size.
Number of requests can be reduced by 25 (25%)
99
74
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sct. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
sct
904 ms
css
69 ms
application.css
38 ms
application.js
55 ms
mqdefault.jpg
83 ms
gobmxlogo.svg
22 ms
background_Red_Compartida_portal2.jpg
52 ms
logo_SCT_logosombraexterior.png
24 ms
highlight_PORTAL__2_.JPG
27 ms
cover_Portada.jpg
24 ms
cover_Portada.jpg
26 ms
cover_Portada.jpg
23 ms
thumb_GALERIA__2_.JPG
24 ms
thumb_GALERIA__1_.JPG
28 ms
thumb_GALERIA__3_.JPG
48 ms
thumb_GALERIA__4_.JPG
48 ms
thumb_GALERIA__5_.JPG
50 ms
thumb_GALERIA__6_.JPG
47 ms
vlarge_GALERIA__14_.JPG
53 ms
small_FOTO_4.JPG
63 ms
small_foto_2.JPG
60 ms
small_FOTO_4.JPG
65 ms
thumb_Lic._Gerardo_Ruiz_Esparza__14b_.jpg
97 ms
thumb_M_nica_ASpe.jpg
53 ms
thumb_02-Ra_l_Murrieta_Cummings_Subsecretario_de_Infraestructura.jpg
175 ms
thumb_05-Rodrigo_Ram_rez_Reyes_Oficial_Mayor.jpg
69 ms
thumb_04-Yuriria_Mascott_P_rez_Subsecretaria_de_Transportes.JPG
72 ms
thumb_07-Guillermo_Ruiz_de_Teresa_Coordinador_General_Puertos_y_Marina_Mercante.jpg
76 ms
thumb_08-Jos__Antonio_Rodarte_Leal_Coordinador_General_de_Centros_SCT.jpg
73 ms
thumb_25-Adri_n_del_Mazo_Maza_Director_General_de_Autotransporte_Federal.JPG
74 ms
thumb_20-Alejandro_Fern_ndez_Campillo_Director_General_de_Conservaci_n_de_Carreteras.jpg
81 ms
thumb_13-Alexandro_Argud_n_Le_Roy_Director_General_del_AICM.JPG
77 ms
thumb_15-Alfonso_Sarabia_Director_General_de_ASA.JPG
79 ms
thumb_22-Andres_de_la_Cruz_Vielma_Director_General_de_Pol_tica_de_Telecomunicaciones_y_Radiodifusi_n.jpg
91 ms
thumb_35-Jos__A._Ruiz_Massieu_Director_General_de_Programaci_n__Organizaci_n_y_Presupuesto.JPG
82 ms
thumb_33-Clemente_Poon_Hung_Director_Gral_de_Servicios_T_cnicos.jpg
91 ms
thumb_40-Edgar_Olvera_Jim_nez_Coordinador_de_Proyectos_T_cnico_Regulatorios.jpg
92 ms
thumb_11-Elena_Tanus_Meouchi_Directora_General_del_Servicio_Postal_Mexicano.jpg
247 ms
thumb_23-Javier_Valdez_Moreno_Director_General_de_Espectro__Tecnolog_a_y_Cobertura_Social.jpg
170 ms
thumb_27-Guillermo_Nev_rez_Elizondo_Director_General_de_Transporte_Ferroviario_y_Multimodal.jpg
171 ms
mqdefault.jpg
66 ms
mqdefault.jpg
67 ms
js
86 ms
ct.js
473 ms
homepage.js
99 ms
thumb_Jenny_Ochoa.png
233 ms
thumb_10-Jos__A._Juraidini_Rumilla_Diretor_General_de_Telecomm.jpg
155 ms
thumb_17-Jos__San_Mart_n_Romero_Director_General_del_IMT.jpg
161 ms
thumb_34-Mario_de_la_Vega_Grajales_Director_General_de_Vinculaci_n.JPG
156 ms
thumb_Miguel_Pel_ez_Lira.jpg
155 ms
thumb_37-Nidia_Chavez_Rocha_Titular_del__rgano_Interno_de_Control.jpg
157 ms
thumb_41-Omar_Charf_n_Tomassi_Director_del_Sistema_Satelital_MEXSAT.jpg
155 ms
thumb_19-_scar_Ra_l_Callejo_Silva_Director_General_de_Carreteras.jpg
157 ms
thumb_Roberto_Kobeh_Gonz_lez.png
133 ms
thumb_31-Rodolfo_Gonz_lez_Fern_ndez_Director_General_de_Comunicaci_n_Social.jpg
139 ms
thumb_24-Virginia_Col_n_Castro_Directora_General_Adjunta_del_Programa_de_Empleo_Temporal.jpg
139 ms
logo_mexico.svg
135 ms
common.js
26 ms
map.js
80 ms
util.js
85 ms
marker.js
80 ms
overlay.js
79 ms
glyphicons-halflings-regular.woff
35 ms
fontawesome-webfont.woff
67 ms
icogobmx.woff
33 ms
StaticMapService.GetMapImage
439 ms
icons_full.png
54 ms
sdk.js
221 ms
widgets.js
55 ms
onion.js
28 ms
openhand_8_8.cur
35 ms
stats.js
13 ms
controls.js
15 ms
ViewportInfoService.GetViewportInfo
186 ms
transparent.png
55 ms
css
39 ms
google4.png
48 ms
mapcnt6.png
61 ms
sv5.png
62 ms
spotlight-poi.png
67 ms
tmapctrl.png
25 ms
cb_scout5.png
53 ms
tmapctrl4.png
54 ms
imgs8.png
55 ms
63 ms
xd_arbiter.php
126 ms
xd_arbiter.php
264 ms
analytics.js
23 ms
collect
15 ms
collect
57 ms
vt
15 ms
vt
17 ms
vt
27 ms
vt
27 ms
vt
27 ms
vt
27 ms
vt
140 ms
vt
42 ms
vt
64 ms
ga-audiences
40 ms
AuthenticationService.Authenticate
25 ms
nr-852.min.js
15 ms
chartbeat.js
47 ms
4f61afea51
50 ms
ping
10 ms
sct.gob.mx accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
sct.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
User Experience
Impact
Issue
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
sct.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 uses legible font sizes
Tap targets are not sized appropriately
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sct.gob.mx 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 Sct.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.
sct.gob.mx
Open Graph description is not detected on the main page of Sct. 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: