6.1 sec in total
416 ms
5.5 sec
145 ms
Click here to check amazing Oeo Unm content for United States. Otherwise, check out these important facts you probably never knew about oeo.unm.edu
Homepage for UNM Office of Equal Opportunity
Visit oeo.unm.eduWe analyzed Oeo.unm.edu page load time and found that the first response time was 416 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
oeo.unm.edu performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value18.0 s
0/100
25%
Value4.0 s
80/100
10%
Value310 ms
77/100
30%
Value0.001
100/100
15%
Value9.5 s
30/100
10%
416 ms
840 ms
135 ms
1131 ms
2140 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 22% of them (16 requests) were addressed to the original Oeo.unm.edu, 29% (21 requests) were made to Webcore.unm.edu and 14% (10 requests) were made to O.twimg.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Webcore.unm.edu.
Page size can be reduced by 62.3 kB (20%)
315.5 kB
253.1 kB
In fact, the total size of Oeo.unm.edu main page is 315.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 134.7 kB which makes up the majority of the site volume.
Potential reduce by 28.8 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 28.8 kB or 74% of the original size.
Potential reduce by 5.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. Oeo Unm images are well optimized though.
Potential reduce by 1.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 27.3 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. Oeo.unm.edu needs all CSS files to be minified and compressed as it can save up to 27.3 kB or 82% of the original size.
Number of requests can be reduced by 26 (38%)
69
43
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oeo Unm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
oeo.unm.edu
416 ms
styles.php
840 ms
site.css
135 ms
jquery.min.js
1131 ms
unm_scripts.php
2140 ms
bootstrap.css
483 ms
jquery.flexslider-min.js
570 ms
flexslider.css
473 ms
ga.js
31 ms
logo-oeo.gif
110 ms
oeo-building.jpg
287 ms
loborespect.jpg
95 ms
ada--forms-slideshow.jpg
685 ms
oeo_lobolouie_lobolucy.jpg
748 ms
protectthepackloborespectpacket.jpg
685 ms
unm_ada_brochure.jpg
598 ms
loborespect_message.jpg
550 ms
lobo_guardian_app.jpg
1320 ms
1502clery.jpg
1264 ms
coercion_is_not_consent.jpg
818 ms
1502smart.jpg
760 ms
cover-posters.jpg
1153 ms
content_back_wide.gif
55 ms
search.gif
56 ms
unm_sprites.gif
55 ms
container_back.gif
56 ms
sdk.js
277 ms
__utm.gif
24 ms
__utm.gif
19 ms
widgets.js
136 ms
collect
53 ms
graybar.gif
54 ms
clear.png
2564 ms
facebook.png
2468 ms
icon_flickr.gif
2464 ms
lastfm.gif
2467 ms
twitter.png
2468 ms
youtube.gif
2466 ms
scvngr.png
2515 ms
unm_tab_close.png
2517 ms
share_back.png
100 ms
bg_direction_nav.png
98 ms
ga-audiences
35 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
131 ms
150 ms
syndication
112 ms
615905939967774720
204 ms
xd_arbiter.php
13 ms
xd_arbiter.php
36 ms
proxy.jpg
67 ms
proxy.jpg
61 ms
proxy.jpg
79 ms
proxy.jpg
68 ms
proxy.jpg
77 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
35 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
74 ms
UndyISuX_normal.png
135 ms
BWright2_normal.JPG
160 ms
UZwDC2Wv_normal.jpg
222 ms
rDXhUgvW_normal.jpg
296 ms
CdEw6lRXIAAuNXT.jpg:small
271 ms
CdCTpljUMAAH-LM.jpg:small
304 ms
CcpEAt8VIAQ_uNA.jpg:small
332 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
34 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
75 ms
proxy.jpg
8 ms
proxy.jpg
7 ms
proxy.jpg
4 ms
proxy.jpg
16 ms
proxy.jpg
5 ms
jot.html
33 ms
styles.php
445 ms
oeo.unm.edu accessibility score
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
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.
oeo.unm.edu 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
oeo.unm.edu SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oeo.unm.edu can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Oeo.unm.edu 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.
oeo.unm.edu
Open Graph description is not detected on the main page of Oeo Unm. 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: