Access holyname.org. Holy Name

name

value

score

weighting

FCP (First Contentful Paint)

Value10.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value24.0 s

0/100

25%

SI (Speed Index)

Value25.0 s

0/100

10%

TBT (Total Blocking Time)

Value1,530 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.051

99/100

15%

TTI (Time to Interactive)

Value30.9 s

0/100

10%

holyname.org

150 ms

main-011116.css

174 ms

accordion-menu.css

97 ms

roboto-font.css

72 ms

fugu-font.css

66 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 93% of them (67 requests) were addressed to the original Holyname.org, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (524 ms) belongs to the original domain Holyname.org.

Content Size

3.5 MB

After Optimization

2.7 MB

In fact, the total size of Holyname.org main page is 3.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. 40% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 60.5 kB

Original 71.8 kB
After minification 59.3 kB
After compression 11.3 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. This page needs HTML code to be minified as it can gain 12.5 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 60.5 kB or 84% of the original size.

Image Optimization

-11%

Potential reduce by 306.2 kB

Original 2.8 MB
After minification 2.5 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. Obviously, Holy Name needs image optimization as it can save up to 306.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 389.0 kB

Original 552.2 kB
After minification 344.1 kB
After compression 163.1 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 389.0 kB or 70% of the original size.

CSS Optimization

-84%

Potential reduce by 75.5 kB

Original 90.3 kB
After minification 70.3 kB
After compression 14.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. Holyname.org needs all CSS files to be minified and compressed as it can save up to 75.5 kB or 84% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA IDs are not unique

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.

High

Buttons do not have an accessible name

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

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

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links do not have descriptive text

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

High

Links are not crawlable

High

robots.txt is not valid

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/).

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

holyname.org

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Holy Name

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

holyname.org

main-011116.css

accordion-menu.css

roboto-font.css

fugu-font.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

holyname.org

main-011116.css

accordion-menu.css

roboto-font.css

fugu-font.css

css

js

jquery.js

jquery-1.9.1.js

back-to-top.js

font-awesome.min.css

thickbox.css

thickbox.js

jssor.js

jssor.slider.js

error.aspx

google-plus.png

youtube.png

twitter.png

facebook.png

hnmc-header-logo.png

search-32-blue.png

find-phys-2.png

divide.png

x-mark-48.png

doctor-suitecase-32.png

search-32-gray.png

patient-32.png

hospital-32.png

arrow-16-white.png

OMNIA-020116.jpg

HeartMonth-0216.jpg

ER-0216.jpg

CSONJ-0216.jpg

haiti-101515-2.jpg

hnhfitness-0216.jpg

HNPN-0216.jpg

CPR-0216.jpg

ER-0216-b.jpg

haiti-101515-4.jpg

KMP-0915.jpg

Mulkay.jpg

Safety-Score-1115-A.jpg