Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

merton.org

Thomas Merton Center

Page Load Speed

812 ms in total

First Response

111 ms

Resources Loaded

581 ms

Page Rendered

120 ms

merton.org screenshot

About Website

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

The Thomas Merton Center and The International Thomas Merton Society at Bellarmine University

Visit merton.org

Key Findings

We analyzed Merton.org page load time and found that the first response time was 111 ms and then it took 701 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

merton.org performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

62/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value3.0 s

95/100

10%

Network Requests Diagram

merton.org

111 ms

merton.org

149 ms

site.less

43 ms

jquery.min.js

22 ms

jquery.cycle.lite.js

138 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 93% of them (13 requests) were addressed to the original Merton.org, 7% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (265 ms) belongs to the original domain Merton.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 25.6 kB (8%)

Content Size

302.3 kB

After Optimization

276.7 kB

In fact, the total size of Merton.org main page is 302.3 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. 20% of websites need less resources to load. Images take 253.7 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 8.8 kB

  • Original 12.4 kB
  • After minification 11.8 kB
  • After compression 3.5 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 8.8 kB or 71% of the original size.

Image Optimization

-6%

Potential reduce by 16.2 kB

  • Original 253.7 kB
  • After minification 237.5 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. Merton images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 493 B

  • Original 36.2 kB
  • After minification 36.2 kB
  • After compression 35.7 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

We found no issues to fix!

Requests Now

12

After Optimization

12

The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Merton. According to our analytics all requests are already optimized.

Accessibility Review

merton.org accessibility score

73

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

merton.org 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

merton.org SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Merton.org 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 Merton.org 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 Merton. 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: