Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

history.unm.edu

Department of History | The University of New Mexico

Page Load Speed

3.1 sec in total

First Response

324 ms

Resources Loaded

2.4 sec

Page Rendered

364 ms

history.unm.edu screenshot

About Website

Visit history.unm.edu now to see the best up-to-date History Unm content for United States and also check out these interesting facts you probably never knew about history.unm.edu

Visit history.unm.edu

Key Findings

We analyzed History.unm.edu page load time and found that the first response time was 324 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

history.unm.edu performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value890 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

history.unm.edu

324 ms

styles.php

546 ms

site.css

125 ms

jquery.min.js

613 ms

unm_scripts.php

835 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 35% of them (25 requests) were addressed to the original History.unm.edu, 25% (18 requests) were made to Webcore.unm.edu and 18% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (835 ms) relates to the external source Webcore.unm.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 103.3 kB (12%)

Content Size

830.9 kB

After Optimization

727.6 kB

In fact, the total size of History.unm.edu main page is 830.9 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. 35% of websites need less resources to load. Images take 647.9 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 20.8 kB

  • Original 27.9 kB
  • After minification 26.8 kB
  • After compression 7.1 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 20.8 kB or 75% of the original size.

Image Optimization

-6%

Potential reduce by 37.5 kB

  • Original 647.9 kB
  • After minification 610.4 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. History Unm images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 33.3 kB

  • Original 140.4 kB
  • After minification 123.8 kB
  • After compression 107.0 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 33.3 kB or 24% of the original size.

CSS Optimization

-79%

Potential reduce by 11.7 kB

  • Original 14.8 kB
  • After minification 10.1 kB
  • After compression 3.1 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. History.unm.edu needs all CSS files to be minified and compressed as it can save up to 11.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (43%)

Requests Now

68

After Optimization

39

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

Accessibility Review

history.unm.edu accessibility score

94

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

history.unm.edu best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

history.unm.edu SEO score

82

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

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 History.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 History.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

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