Unam.mx UNAM | Portal UNAM
Con centros de estudio en varios Estados del país, pero mayormente en el Distrito Federal, la UNAM es la universidad pública más grande en el país.

unam.mx Desktop Performance
46/100
These metrics represent real-world Chrome users experience viewing unam.mx web page. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
First Input Delay
First Contentful Paint
Cumulative Layout Shift
Largest Contentful Paint
Metrics
Cumulative Layout Shift9/100 0.657
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Time to Interactive22/100 6.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Speed Index24/100 3.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Largest Contentful Paint38/100 2.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Total Blocking Time63/100 280 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
First Contentful Paint89/100 1.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Should Fix (21)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Properly size images
Potential savings of 609 KiB
1,360 ms
Remove unused JavaScript
Potential savings of 862 KiB
790 ms
Defer offscreen images
Potential savings of 409 KiB
760 ms
Serve images in next-gen formats
Potential savings of 514 KiB
680 ms
Eliminate render-blocking resources
Potential savings of 630 ms
634 ms
Efficiently encode images
Potential savings of 267 KiB
400 ms
Remove unused CSS
Potential savings of 135 KiB
80 ms
Reduce initial server response time
Root document took 650 ms
48 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Does not use passive listeners to improve scrolling performance
Reduce the impact of third-party code
Third-party code blocked the main thread for 720 ms
Ensure text remains visible during webfont load
Serve static assets with an efficient cache policy
62 resources found
Avoid enormous network payloads
Total size was 5,644 KiB
Minimize main-thread work
4.3 s
Reduce JavaScript execution time
2.1 s
Largest Contentful Paint element
1 element found
User Timing marks and measures
3 user timings
Avoid long main-thread tasks
8 long tasks found
Avoid large layout shifts
5 elements found
Avoid chaining critical requests
13 chains found
Keep request counts low and transfer sizes small
257 requests • 5,644 KiB
Passed Audits (9)
Minify CSS
Potential savings of 3 KiB
Preconnect to required origins
Avoid multiple page redirects
Potential savings of 190 ms
Preload key requests
Use video formats for animated content
Enable text compression
Avoids `document.write()`
Minify JavaScript
Avoids an excessive DOM size
548 elements

unam.mx Desktop SEO
92/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (1)
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Passed Audits (11)
robots.txt is valid
Page has successful HTTP status code
Image elements have `[alt]` attributes
Document has a meta description
Page isn’t blocked from indexing
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Document has a valid `hreflang`
Document has a valid `rel=canonical`
Document has a `<title>` element
Links have descriptive text
Document avoids plugins

unam.mx Desktop Best Practices
69/100
These checks highlight opportunities to improve the overall code health of unam.mx page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (4)
General
Browser errors were logged to the console
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
7 vulnerabilities detected
Does not use HTTPS
1 insecure request found
Links to cross-origin destinations are unsafe
Passed Audits (10)
Page has the HTML doctype
Detected JavaScript libraries
Avoids deprecated APIs
Properly defines charset
Avoids requesting the geolocation permission on page load
Allows users to paste into password fields
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Avoids Application Cache
Serves images with appropriate resolution

unam.mx Desktop Progressive Web App
22/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (9)
Fast and reliable
Current page does not respond with a 200 when offline
`start_url` does not respond with a 200 when offline
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 29.0 s
PWA Optimized
Manifest doesn't have a maskable icon
Does not set a theme color for the address bar.
Is not configured for a custom splash screen
Installable
Does not register a service worker that controls page and `start_url`
Does not use HTTPS
1 insecure request found
Web app manifest does not meet the installability requirements
Passed Audits (4)
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Contains some content when JavaScript is not available
Redirects HTTP traffic to HTTPS
Provides a valid `apple-touch-icon`

unam.mx Desktop Accessibility
97/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (2)
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
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.
`<frame>` or `<iframe>` elements do not have a title
Passed Audits (26)
`[role]` values are valid
No element has a `[tabindex]` value greater than 0
ARIA IDs are unique
`[aria-*]` attributes match their roles
Image elements have `[alt]` attributes
Buttons have an accessible name
`[aria-hidden="true"]` elements do not contain focusable descendents
`[role]`s are contained by their required parent element
Form elements have associated labels
`[aria-*]` attributes have valid values
`<html>` element has a `[lang]` attribute
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
`[id]` attributes on active, focusable elements are unique
Heading elements appear in a sequentially-descending order
`<html>` element has a valid value for its `[lang]` attribute
`[aria-hidden="true"]` is not present on the document `<body>`
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Links have a discernible name
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
The page contains a heading, skip link, or landmark region
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[aria-*]` attributes are valid and not misspelled
Document has a `<title>` element
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`[role]`s have all required `[aria-*]` attributes
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

Desktop Speed
38/100
These checks analyze the performance of unam.mx on desktop devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (6)
Optimize images
Leverage browser caching
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Avoid landing page redirects
Minify JavaScript
Minify CSS
Passed Audits (4)
Enable compression
Reduce server response time
Minify HTML
Prioritize visible content
www.unam.com
www.unam.net
www.unam.org
www.unam.info
www.unam.biz
www.unam.us
www.unam.mobi
www.nam.mx
www.unam.mx
www.ynam.mx
www.uynam.mx
www.yunam.mx
www.hnam.mx
www.uhnam.mx
www.hunam.mx
www.jnam.mx
www.ujnam.mx
www.junam.mx
www.inam.mx
www.uinam.mx
www.iunam.mx
www.uam.mx
www.ubam.mx
www.unbam.mx
www.ubnam.mx
www.uham.mx
www.unham.mx
www.ujam.mx
www.unjam.mx
www.umam.mx
www.unmam.mx
www.umnam.mx
www.unm.mx
www.unqm.mx
www.unaqm.mx
www.unqam.mx
www.unwm.mx
www.unawm.mx
www.unwam.mx
www.unsm.mx
www.unasm.mx
www.unsam.mx
www.unzm.mx
www.unazm.mx
www.unzam.mx
www.una.mx
www.unan.mx
www.unamn.mx
www.unanm.mx
www.unaj.mx
www.unamj.mx
www.unajm.mx
www.unak.mx
www.unamk.mx
www.unakm.mx
www.unam.net
www.unam.org
www.unam.info
www.unam.biz
www.unam.us
www.unam.mobi
www.nam.mx
www.unam.mx
www.ynam.mx
www.uynam.mx
www.yunam.mx
www.hnam.mx
www.uhnam.mx
www.hunam.mx
www.jnam.mx
www.ujnam.mx
www.junam.mx
www.inam.mx
www.uinam.mx
www.iunam.mx
www.uam.mx
www.ubam.mx
www.unbam.mx
www.ubnam.mx
www.uham.mx
www.unham.mx
www.ujam.mx
www.unjam.mx
www.umam.mx
www.unmam.mx
www.umnam.mx
www.unm.mx
www.unqm.mx
www.unaqm.mx
www.unqam.mx
www.unwm.mx
www.unawm.mx
www.unwam.mx
www.unsm.mx
www.unasm.mx
www.unsam.mx
www.unzm.mx
www.unazm.mx
www.unzam.mx
www.una.mx
www.unan.mx
www.unamn.mx
www.unanm.mx
www.unaj.mx
www.unamj.mx
www.unajm.mx
www.unak.mx
www.unamk.mx
www.unakm.mx