Tools & Wizards About Us

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

fst.edu

Franciscan School of Theology | University of San Diego

Page Load Speed

1.7 sec in total

First Response

84 ms

Resources Loaded

868 ms

Page Rendered

787 ms

About Website

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

The Franciscan School of Theology (FST) is an independent, accredited institution dedicated to the Franciscan intellectual tradition.

Visit fst.edu

Key Findings

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

Performance Metrics

fst.edu performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.0 s

33/100

10%

Network Requests Diagram

fst.edu

84 ms

www.fst.edu

49 ms

www.fst.edu

139 ms

jquery.min.js

18 ms

cher-frontend.min.js

27 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 92% of them (79 requests) were addressed to the original Fst.edu, 1% (1 request) were made to Js.hsleadflows.net and 1% (1 request) were made to Js.hs-banner.com. The less responsive or slowest element that took the longest time to load (400 ms) relates to the external source Js.hubspot.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 260.2 kB (11%)

Content Size

2.5 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Fst.edu main page is 2.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 253.5 kB

  • Original 316.3 kB
  • After minification 312.9 kB
  • After compression 62.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 253.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.8 MB
  • After minification 1.8 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. Fst images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 6.7 kB

  • Original 315.7 kB
  • After minification 315.7 kB
  • After compression 309.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 51 (65%)

Requests Now

79

After Optimization

28

  • Images
  • JavaScript

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

Network Requests Diagram

Accessibility Review

fst.edu accessibility score

83

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

[role]s are not contained by their required parent element

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

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

fst.edu best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

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 Fst.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 Fst.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 data is detected on the main page of Fst. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: