Tools & Wizards About Us
saintpatricks.us screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

saintpatricks.us

Saint Patrick's Episcopal Church - Welcome to Saint Patrick's Episcopal Church, Falls Church, Virginia

Page Load Speed

2.2 sec in total

First Response

177 ms

Resources Loaded

1.6 sec

Page Rendered

399 ms

saintpatricks.us screenshot

About Website

Visit saintpatricks.us now to see the best up-to-date Saint Patrick S content and also check out these interesting facts you probably never knew about saintpatricks.us

Saint Patrick's Episcopal Church, an Anglo-Vietnamese Community in Falls Church Virginia is a medium sized parish made up of a diverse community with many different nationalities, interest...

Visit saintpatricks.us

Key Findings

We analyzed Saintpatricks.us page load time and found that the first response time was 177 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

saintpatricks.us performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

saintpatricks.us

177 ms

www.saintpatricks.us

201 ms

www.saintpatricks.us

387 ms

sites.css

25 ms

fancybox.css

35 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 48% of them (11 requests) were addressed to the original Saintpatricks.us, 30% (7 requests) were made to Cdn2.editmysite.com and 4% (1 request) were made to Static.zotabox.com. The less responsive or slowest element that took the longest time to load (387 ms) belongs to the original domain Saintpatricks.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 111.6 kB (17%)

Content Size

654.3 kB

After Optimization

542.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Saintpatricks.us main page is 654.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. Javascripts take 555.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 50.4 kB

  • Original 65.1 kB
  • After minification 64.6 kB
  • After compression 14.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 50.4 kB or 77% of the original size.

Image Optimization

-53%

Potential reduce by 404 B

  • Original 762 B
  • After minification 358 B

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, Saint Patrick S needs image optimization as it can save up to 404 B or 53% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-11%

Potential reduce by 60.7 kB

  • Original 555.1 kB
  • After minification 555.1 kB
  • After compression 494.4 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 60.7 kB or 11% of the original size.

CSS Optimization

-0%

Potential reduce by 158 B

  • Original 33.3 kB
  • After minification 33.3 kB
  • After compression 33.2 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. Saintpatricks.us has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (45%)

Requests Now

20

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

saintpatricks.us

saintpatricks.us

177 ms

www.saintpatricks.us

www.saintpatricks.us

201 ms

www.saintpatricks.us

www.saintpatricks.us

387 ms

sites.css

sites.css

25 ms

fancybox.css

fancybox.css

35 ms

main_style.css

main_style.css

89 ms

templateArtifacts.js

templateArtifacts.js

175 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

37 ms

stl.js

stl.js

40 ms

main.js

main.js

53 ms

main-customer-accounts-site.js

main-customer-accounts-site.js

43 ms

widgets.js

widgets.js

300 ms

footerbg.jpg

footerbg.jpg

204 ms

bodybg.jpg

bodybg.jpg

202 ms

containerbg.jpg

containerbg.jpg

336 ms

social-lightblue.png

social-lightblue.png

296 ms

navigationbg.jpg

navigationbg.jpg

380 ms

powr.js

powr.js

126 ms

ga.js

ga.js

85 ms

snowday262.js

snowday262.js

43 ms

243 ms

generateMap.php

generateMap.php

141 ms

js

js

50 ms

Accessibility Review

saintpatricks.us accessibility score

88

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.

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

<frame> or <iframe> elements do not have a title

Best Practices

saintpatricks.us 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

SEO Factors

saintpatricks.us SEO score

92

Search Engine Optimization Advices

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 Saintpatricks.us 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 Saintpatricks.us 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

saintpatricks.us

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