4.9 sec in total
740 ms
3.8 sec
400 ms
Visit gaceta.unam.mx now to see the best up-to-date Gaceta UNAM content for Mexico and also check out these interesting facts you probably never knew about gaceta.unam.mx
Órgano informativo de la Universidad Nacional Autónoma de México
Visit gaceta.unam.mxWe analyzed Gaceta.unam.mx page load time and found that the first response time was 740 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
gaceta.unam.mx performance score
name
value
score
weighting
Value17.4 s
0/100
10%
Value17.8 s
0/100
25%
Value17.5 s
0/100
10%
Value1,470 ms
14/100
30%
Value0
100/100
15%
Value27.1 s
0/100
10%
740 ms
159 ms
455 ms
30 ms
361 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 63% of them (66 requests) were addressed to the original Gaceta.unam.mx, 5% (5 requests) were made to Sync-iad.e-planning.net and 4% (4 requests) were made to Ads.us.e-planning.net. The less responsive or slowest element that took the longest time to load (830 ms) relates to the external source Backslash.gr.
Page size can be reduced by 613.1 kB (37%)
1.7 MB
1.1 MB
In fact, the total size of Gaceta.unam.mx main page is 1.7 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 871.2 kB which makes up the majority of the site volume.
Potential reduce by 55.4 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 7.9 kB, which is 11% 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 55.4 kB or 78% of the original size.
Potential reduce by 53.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. Gaceta UNAM images are well optimized though.
Potential reduce by 426.9 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 426.9 kB or 68% of the original size.
Potential reduce by 77.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. Gaceta.unam.mx needs all CSS files to be minified and compressed as it can save up to 77.0 kB or 81% of the original size.
Number of requests can be reduced by 54 (55%)
98
44
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gaceta UNAM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.gaceta.unam.mx
740 ms
gaceta_sup.css
159 ms
magnific-popup.css
455 ms
jquery.min.js
30 ms
jquery.magnific-popup.js
361 ms
jplayer.blue.monday.css
171 ms
jquery.jplayer.js
580 ms
jplayer.playlist.js
317 ms
colorbox.css
87 ms
jquery.colorbox.js
259 ms
photoswipe.css
257 ms
default-skin.css
259 ms
photoswipe.min.js
430 ms
photoswipe-ui-default.min.js
349 ms
jquery.contenthover.min.js
830 ms
css
24 ms
style.css
473 ms
grid.css
430 ms
theme.css
439 ms
flexslider.css
513 ms
jquery.js
679 ms
jquery-migrate.min.js
530 ms
bootstrap.min.css
657 ms
style.css
392 ms
small-menu.js
764 ms
jquery.flexslider.js
546 ms
superfish.js
468 ms
custom.js
502 ms
wp-embed.min.js
543 ms
bootstrap-typeahead.js
588 ms
autocomplete_solr.js
609 ms
ct.js
214 ms
wp-emoji-release.min.js
89 ms
medium-rectangle1.jpg
267 ms
Leader-board.jpg
267 ms
bt_twit_top.png
88 ms
banner.jpg
264 ms
bt_leermas.jpg
90 ms
portada.jpg
265 ms
gal_cen00.jpg
333 ms
camara.jpg
263 ms
gal_ilust00.jpg
553 ms
sec_comunidad.jpg
266 ms
sec_academia.jpg
305 ms
sec_cultura.jpg
315 ms
sec_gobierno.jpg
331 ms
sec_deportes.jpg
416 ms
anteriores.jpg
463 ms
slide.png
400 ms
suple_ant.png
415 ms
llamado_suplemento.jpg
415 ms
descargar_pdf.png
485 ms
ver_pdf.png
498 ms
slide.png
498 ms
suple_ant.png
499 ms
llamado1.jpg
534 ms
llamado2.jpg
571 ms
llamado3.jpg
579 ms
llamado4.jpg
579 ms
contraportada00.jpg
657 ms
agenda.jpg
687 ms
agen_dig.png
635 ms
sdk.js
271 ms
analytics.js
21 ms
t3m.js
256 ms
profiles.js
10 ms
profile
18 ms
collect
16 ms
plek.jpg
614 ms
impresa.jpg
621 ms
enc_fotoprin.jpg
610 ms
pleka.jpg
667 ms
epl-41.js
241 ms
e403
14 ms
g.jpg
199 ms
impresa_convo.jpg
670 ms
jplayer.blue.monday.video.play.png
672 ms
jplayer.blue.monday.jpg
672 ms
piwik.js
352 ms
overlay.png
83 ms
139 ms
xd_arbiter.php
210 ms
xd_arbiter.php
418 ms
Home
5 ms
Home
185 ms
Home
166 ms
pm_match
7 ms
multi-sync.js
14 ms
um
7 ms
um
5 ms
emily.html
10 ms
pm_match
5 ms
um
4 ms
um
4 ms
conversion.js
18 ms
base.js
6 ms
trk
17 ms
b
17 ms
b
17 ms
like.php
85 ms
ca
19 ms
TDz_0Zz7Dzz.js
487 ms
LVx-xkvaJ0b.png
547 ms
__tt.gif
10 ms
um
3 ms
gaceta.unam.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-*] attributes do not match their roles
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.
[aria-*] attributes do not have valid values
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
[id] attributes on active, focusable elements are not unique
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
gaceta.unam.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
gaceta.unam.mx 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gaceta.unam.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Gaceta.unam.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.
gaceta.unam.mx
Open Graph description is not detected on the main page of Gaceta UNAM. 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: