Tools & Wizards About Us
wheatonfranciscan.org screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

wheatonfranciscan.org

Home • Wheaton Franciscans

Page Load Speed

6 sec in total

First Response

15 ms

Resources Loaded

4 sec

Page Rendered

2 sec

wheatonfranciscan.org screenshot

About Website

Visit wheatonfranciscan.org now to see the best up-to-date Wheaton Franciscan content for United States and also check out these interesting facts you probably never knew about wheatonfranciscan.org

Welcome the Wheaton Franciscan community! We are an organization of Catholic sisters, lay persons, collaborative partners, and friends committed to sharing the Good News of God’s infinite love.

Visit wheatonfranciscan.org

Key Findings

We analyzed Wheatonfranciscan.org page load time and found that the first response time was 15 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

wheatonfranciscan.org performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value10,290 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.282

43/100

15%

TTI (Time to Interactive)

Value22.0 s

1/100

10%

Network Requests Diagram

wheatonfranciscan.org

15 ms

wheatonfranciscan.org

107 ms

wp-emoji-release.min.js

268 ms

ffwd_frontend.css

272 ms

fonts.css

276 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 6% of them (5 requests) were addressed to the original Wheatonfranciscan.org, 89% (72 requests) were made to Secureservercdn.net and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Secureservercdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.7 kB (9%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 110.7 kB

  • Original 131.2 kB
  • After minification 128.9 kB
  • After compression 20.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 110.7 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 6.6 kB

  • Original 892.4 kB
  • After minification 885.8 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. Wheaton Franciscan images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 5.4 kB

  • Original 147.0 kB
  • After minification 147.0 kB
  • After compression 141.6 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.

CSS Optimization

-2%

Potential reduce by 2.9 kB

  • Original 155.9 kB
  • After minification 155.6 kB
  • After compression 153.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. Wheatonfranciscan.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 68 (89%)

Requests Now

76

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wheatonfranciscan.org

wheatonfranciscan.org

15 ms

wheatonfranciscan.org

wheatonfranciscan.org

107 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

268 ms

ffwd_frontend.css

ffwd_frontend.css

272 ms

fonts.css

fonts.css

276 ms

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.css

273 ms

style.css

style.css

285 ms

style.css

style.css

278 ms

c53fe56dbd9628b1cc7b13651e7a4140.min.css

c53fe56dbd9628b1cc7b13651e7a4140.min.css

653 ms

jquery.min.js

jquery.min.js

548 ms

jquery-migrate.min.js

jquery-migrate.min.js

492 ms

ffwd_frontend.js

ffwd_frontend.js

523 ms

jquery.mobile.js

jquery.mobile.js

502 ms

jquery.mCustomScrollbar.concat.min.js

jquery.mCustomScrollbar.concat.min.js

509 ms

jquery.fullscreen-0.4.1.js

jquery.fullscreen-0.4.1.js

863 ms

ffwd_gallery_box.js

ffwd_gallery_box.js

867 ms

js

js

67 ms

style.min.css

style.min.css

994 ms

fusion-vertical-menu-widget.js

fusion-vertical-menu-widget.js

995 ms

cssua.js

cssua.js

995 ms

modernizr.js

modernizr.js

1064 ms

fusion.js

fusion.js

1069 ms

bootstrap.transition.js

bootstrap.transition.js

1070 ms

bootstrap.tooltip.js

bootstrap.tooltip.js

1079 ms

jquery.requestAnimationFrame.js

jquery.requestAnimationFrame.js

1083 ms

jquery.easing.js

jquery.easing.js

1085 ms

jquery.fitvids.js

jquery.fitvids.js

1187 ms

jquery.flexslider.js

jquery.flexslider.js

1189 ms

jquery.ilightbox.js

jquery.ilightbox.js

1295 ms

jquery.mousewheel.js

jquery.mousewheel.js

1289 ms

jquery.placeholder.js

jquery.placeholder.js

1278 ms

jquery.fade.js

jquery.fade.js

1292 ms

fusion-equal-heights.js

fusion-equal-heights.js

1757 ms

fusion-parallax.js

fusion-parallax.js

1759 ms

fusion-video-general.js

fusion-video-general.js

1755 ms

fusion-video-bg.js

fusion-video-bg.js

1755 ms

fusion-lightbox.js

fusion-lightbox.js

1758 ms

fusion-tooltip.js

fusion-tooltip.js

1758 ms

fusion-sharing-box.js

fusion-sharing-box.js

1909 ms

jquery.sticky-kit.js

jquery.sticky-kit.js

1659 ms

fusion-youtube.js

fusion-youtube.js

1653 ms

vimeoPlayer.js

vimeoPlayer.js

1655 ms

avada-general-footer.js

avada-general-footer.js

1661 ms

avada-quantity.js

avada-quantity.js

1653 ms

avada-crossfade-images.js

avada-crossfade-images.js

1923 ms

avada-select.js

avada-select.js

1714 ms

avada-tabs-widget.js

avada-tabs-widget.js

1733 ms

jquery.elasticslider.js

jquery.elasticslider.js

1725 ms

fusion-alert.js

fusion-alert.js

1716 ms

awb-off-canvas.js

awb-off-canvas.js

1692 ms

fusion-flexslider.js

fusion-flexslider.js

1506 ms

fusion-animations.js

fusion-animations.js

1378 ms

fusion-column-legacy.js

fusion-column-legacy.js

1379 ms

jquery.textillate.js

jquery.textillate.js

1408 ms

fusion-title.js

fusion-title.js

1405 ms

fusion-button.js

fusion-button.js

1313 ms

fusion-content-boxes.js

fusion-content-boxes.js

1533 ms

fusion-container.js

fusion-container.js

1525 ms

avada-elastic-slider.js

avada-elastic-slider.js

1527 ms

avada-gravity-forms.js

avada-gravity-forms.js

1516 ms

avada-drop-down.js

avada-drop-down.js

1524 ms

avada-to-top.js

avada-to-top.js

1431 ms

avada-header.js

avada-header.js

1640 ms

avada-menu.js

avada-menu.js

1538 ms

bootstrap.scrollspy.js

bootstrap.scrollspy.js

1537 ms

avada-scrollspy.js

avada-scrollspy.js

1549 ms

fusion-responsive-typography.js

fusion-responsive-typography.js

1541 ms

analytics.js

analytics.js

441 ms

awb-icons.woff

awb-icons.woff

328 ms

fa-solid-900.woff

fa-solid-900.woff

839 ms

fa-regular-400.woff

fa-regular-400.woff

672 ms

fusion-scroll-to-anchor.js

fusion-scroll-to-anchor.js

1490 ms

fusion-general-global.js

fusion-general-global.js

1301 ms

fusion-video.js

fusion-video.js

1291 ms

fusion-column.js

fusion-column.js

1292 ms

be-a-blessing-e1604618531178.png

be-a-blessing-e1604618531178.png

1411 ms

DSCN2168-scaled-e1646160204769.jpg

DSCN2168-scaled-e1646160204769.jpg

1682 ms

home-background-new-1.jpg

home-background-new-1.jpg

1629 ms

collect

collect

13 ms

collect

collect

39 ms

LOGO-INGLESE-JEPG-400x352.jpg

LOGO-INGLESE-JEPG-400x352.jpg

1532 ms

Accessibility Review

wheatonfranciscan.org accessibility score

96

Accessibility Issues

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

Best Practices

wheatonfranciscan.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

wheatonfranciscan.org SEO score

96

Search Engine Optimization Advices

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

wheatonfranciscan.org

Open Graph data is detected on the main page of Wheaton Franciscan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: