Report Summary

  • 22

    Performance

    Renders faster than
    41% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

aquinas.edu

Home | Aquinas College

Page Load Speed

3.9 sec in total

First Response

1.4 sec

Resources Loaded

2.3 sec

Page Rendered

145 ms

aquinas.edu screenshot

About Website

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

Aquinas College is perfectly situated to provide a comfortable home within the excitement of Grand Rapids. Our campus is more than just a collection of classrooms — it’s both the inspiration and incub...

Visit aquinas.edu

Key Findings

We analyzed Aquinas.edu page load time and found that the first response time was 1.4 sec 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

aquinas.edu performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value19.8 s

0/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value790 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.564

12/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

Network Requests Diagram

aquinas.edu

1426 ms

aquinas.edu

174 ms

css_b6UGREZH6sBPuAn10nUZaZ0Yman7OE0xTUQfpwB6PX4.css

26 ms

css_dSi9hFngtnW40A1nFsnoVBH-WhkxvdS74S9TyUJI6ng.css

51 ms

css_GCSqjtTBSffaUpK005jTzlpor6TdyDWRdZdJO2OZXlk.css

84 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 86% of them (32 requests) were addressed to the original Aquinas.edu, 5% (2 requests) were made to Google-analytics.com and 5% (2 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Aquinas.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 261.2 kB (24%)

Content Size

1.1 MB

After Optimization

824.9 kB

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

HTML Optimization

-80%

Potential reduce by 34.9 kB

  • Original 43.5 kB
  • After minification 41.2 kB
  • After compression 8.6 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 34.9 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 33.6 kB

  • Original 785.8 kB
  • After minification 752.2 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. Aquinas images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 103.2 kB

  • Original 144.4 kB
  • After minification 113.9 kB
  • After compression 41.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 103.2 kB or 71% of the original size.

CSS Optimization

-80%

Potential reduce by 89.5 kB

  • Original 112.5 kB
  • After minification 110.7 kB
  • After compression 23.0 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. Aquinas.edu needs all CSS files to be minified and compressed as it can save up to 89.5 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

35

After Optimization

25

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

Accessibility Review

aquinas.edu accessibility score

91

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 input fields do not have accessible names

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

aquinas.edu SEO score

79

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

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

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 Aquinas.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 Aquinas.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 Aquinas. 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: