Tools & Wizards About Us
search.unm.edu screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    74% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

search.unm.edu

Search Home :: Search UNM | The University of New Mexico

Page Load Speed

2.6 sec in total

First Response

107 ms

Resources Loaded

2.4 sec

Page Rendered

123 ms

search.unm.edu screenshot

About Website

Welcome to search.unm.edu homepage info - get ready to check Search UNM best content for United States right away, or after learning these important things about search.unm.edu

Visit search.unm.edu

Key Findings

We analyzed Search.unm.edu page load time and found that the first response time was 107 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

search.unm.edu performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value850 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

107 ms

styles.php

450 ms

site.css

101 ms

jquery.min.js

588 ms

unm_scripts.php

912 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 15% of them (6 requests) were addressed to the original Search.unm.edu, 44% (17 requests) were made to Webcore.unm.edu and 23% (9 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (925 ms) relates to the external source Webcore.unm.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 29.2 kB (13%)

Content Size

219.7 kB

After Optimization

190.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Search.unm.edu main page is 219.7 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. 25% of websites need less resources to load. Javascripts take 155.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 17.1 kB

  • Original 23.1 kB
  • After minification 22.4 kB
  • After compression 5.9 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 17.1 kB or 74% of the original size.

Image Optimization

-14%

Potential reduce by 4.7 kB

  • Original 33.7 kB
  • After minification 29.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. Obviously, Search UNM needs image optimization as it can save up to 4.7 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 1.6 kB

  • Original 155.7 kB
  • After minification 155.7 kB
  • After compression 154.1 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.

CSS Optimization

-80%

Potential reduce by 5.7 kB

  • Original 7.1 kB
  • After minification 5.4 kB
  • After compression 1.4 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. Search.unm.edu needs all CSS files to be minified and compressed as it can save up to 5.7 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (62%)

Requests Now

34

After Optimization

13

  • Images
  • JavaScript
  • CSS

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Search 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

107 ms

styles.php

styles.php

450 ms

site.css

site.css

101 ms

jquery.min.js

jquery.min.js

588 ms

unm_scripts.php

unm_scripts.php

912 ms

search-styles.css,custom-search-styles.css,responsive.css,custom-search-responsive.css

search-styles.css,custom-search-styles.css,responsive.css,custom-search-responsive.css

114 ms

tinynav.min.js

tinynav.min.js

132 ms

ga.js

ga.js

29 ms

unm_logo.gif

unm_logo.gif

65 ms

search-UNM.png

search-UNM.png

109 ms

content_back_wide.gif

content_back_wide.gif

61 ms

search.gif

search.gif

53 ms

cse.js

cse.js

15 ms

graybar.gif

graybar.gif

51 ms

clear.png

clear.png

876 ms

facebook.png

facebook.png

778 ms

icon_flickr.gif

icon_flickr.gif

924 ms

lastfm.gif

lastfm.gif

925 ms

twitter.png

twitter.png

778 ms

youtube.gif

youtube.gif

925 ms

scvngr.png

scvngr.png

828 ms

unm_tab_close.png

unm_tab_close.png

828 ms

unm_sprites.gif

unm_sprites.gif

89 ms

share_back.png

share_back.png

161 ms

cse.js

cse.js

62 ms

__utm.gif

__utm.gif

28 ms

__utm.gif

__utm.gif

40 ms

collect

collect

59 ms

jsapi

jsapi

37 ms

ga-audiences

ga-audiences

20 ms

default+en.css

default+en.css

9 ms

default.css

default.css

26 ms

default+en.I.js

default+en.I.js

21 ms

default.css

default.css

28 ms

async-ads.js

async-ads.js

59 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

33 ms

small-logo.png

small-logo.png

16 ms

clear.gif

clear.gif

13 ms

styles.php

styles.php

165 ms

Accessibility Review

search.unm.edu accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

search.unm.edu best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

search.unm.edu SEO score

91

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Search.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 Search.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.

Social Sharing Optimization

search.unm.edu

Open Graph description is not detected on the main page of Search 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: