Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

geo.arizona.edu

Geosciences |

Page Load Speed

3.5 sec in total

First Response

238 ms

Resources Loaded

3 sec

Page Rendered

200 ms

geo.arizona.edu screenshot

About Website

Visit geo.arizona.edu now to see the best up-to-date Geo Arizona content for United States and also check out these interesting facts you probably never knew about geo.arizona.edu

Visit geo.arizona.edu

Key Findings

We analyzed Geo.arizona.edu page load time and found that the first response time was 238 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

geo.arizona.edu performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.223

56/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

geo.arizona.edu

238 ms

www.geo.arizona.edu

1206 ms

system.base.css

205 ms

system.menus.css

138 ms

system.messages.css

139 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 98% of them (83 requests) were addressed to the original Geo.arizona.edu, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Geo.arizona.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 631.1 kB (23%)

Content Size

2.7 MB

After Optimization

2.1 MB

In fact, the total size of Geo.arizona.edu main page is 2.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. 65% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 70.1 kB

  • Original 84.8 kB
  • After minification 81.1 kB
  • After compression 14.7 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 70.1 kB or 83% of the original size.

Image Optimization

-10%

Potential reduce by 211.5 kB

  • Original 2.2 MB
  • After minification 2.0 MB

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. Geo Arizona images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 250.3 kB

  • Original 330.5 kB
  • After minification 251.7 kB
  • After compression 80.2 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 250.3 kB or 76% of the original size.

CSS Optimization

-84%

Potential reduce by 99.2 kB

  • Original 118.0 kB
  • After minification 82.9 kB
  • After compression 18.8 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. Geo.arizona.edu needs all CSS files to be minified and compressed as it can save up to 99.2 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

83

After Optimization

59

The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geo Arizona. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

geo.arizona.edu accessibility score

71

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

geo.arizona.edu best practices score

83

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

geo.arizona.edu SEO score

70

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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 Geo.arizona.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 Geo.arizona.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 Geo Arizona. 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: