12.2 sec in total
2.5 sec
9.4 sec
328 ms
Visit stjohnsucc.info now to see the best up-to-date St Johns UCC content and also check out these interesting facts you probably never knew about stjohnsucc.info
Welcome to St. John's United Church of Christ, Boalsburg. No matter who you are, you have a place here, where ALL are loved.
Visit stjohnsucc.infoWe analyzed Stjohnsucc.info page load time and found that the first response time was 2.5 sec and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
stjohnsucc.info performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value43.1 s
0/100
25%
Value4.2 s
78/100
10%
Value180 ms
92/100
30%
Value0.005
100/100
15%
Value5.0 s
77/100
10%
2483 ms
188 ms
164 ms
491 ms
184 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 32% of them (23 requests) were addressed to the original Stjohnsucc.info, 68% (48 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Stjohnsucc.info.
Page size can be reduced by 642.9 kB (4%)
15.3 MB
14.7 MB
In fact, the total size of Stjohnsucc.info main page is 15.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. 70% of websites need less resources to load. Images take 15.0 MB which makes up the majority of the site volume.
Potential reduce by 153.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. 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 153.3 kB or 84% of the original size.
Potential reduce by 489.1 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. St Johns UCC images are well optimized though.
Potential reduce by 456 B
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.
Potential reduce by 43 B
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. Stjohnsucc.info has all CSS files already compressed.
Number of requests can be reduced by 5 (23%)
22
17
The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of St Johns UCC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
stjohnsucc.info
2483 ms
jquery.min.js
188 ms
jquery-migrate.min.js
164 ms
scripts.min.js
491 ms
jquery.fitvids.js
184 ms
jquery.mobile.js
185 ms
common.js
199 ms
Picture1.jpg
121 ms
PastorTom.jpg
2272 ms
DurnerKeyboard-300x223.jpg
464 ms
Churchfront.jpg
1177 ms
freely-6069.jpg
1091 ms
churchrainbow.jpg
1475 ms
churchpic5-scaled.jpg
730 ms
a-charlie-brown-christmas1-300x225.jpg
587 ms
20231005_094411-1024x577.jpg
1015 ms
St.-Johns-2018-150x150.jpg
1014 ms
AJustWorldLogo_small.png
1753 ms
New-Comma-Rainbow.jpg
1740 ms
Hearing-Loop-logo.jpg
1493 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
18 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
22 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
31 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
35 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
36 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
34 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
34 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
35 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
35 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
43 ms
font
8 ms
5aUu9_-1phKLFgshYDvh6Vwt5eFIqER2jg.ttf
6 ms
5aUu9_-1phKLFgshYDvh6Vwt5f1LqER2jQ.woff
9 ms
5aUu9_-1phKLFgshYDvh6Vwt5f1LqER2jg.ttf
9 ms
5aUu9_-1phKLFgshYDvh6Vwt5dlKqER2jQ.woff
8 ms
5aUu9_-1phKLFgshYDvh6Vwt5dlKqER2jg.ttf
7 ms
font
31 ms
5aUu9_-1phKLFgshYDvh6Vwt5alOqER2jg.ttf
20 ms
5aUz9_-1phKLFgshYDvh6Vwt7VRtuw.woff
22 ms
5aUz9_-1phKLFgshYDvh6Vwt7VRtuA.ttf
20 ms
5aUu9_-1phKLFgshYDvh6Vwt5fFPqER2jQ.woff
20 ms
5aUu9_-1phKLFgshYDvh6Vwt5fFPqER2jg.ttf
21 ms
5aUt9_-1phKLFgshYDvh6Vwt5TldsW1V.woff
22 ms
5aUt9_-1phKLFgshYDvh6Vwt5TldsW1W.ttf
24 ms
modules.woff
1436 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff
23 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf
23 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff
22 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf
24 ms
font
27 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf
24 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff
28 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf
28 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exg.woff
27 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf
28 ms
5aUo9_-1phKLFgshYDvh6Vwt7V9VBEhGh09A.woff
14 ms
5aUo9_-1phKLFgshYDvh6Vwt7V9VBEhGh09D.ttf
40 ms
5aUo9_-1phKLFgshYDvh6Vwt7V9VGEtGh09A.woff
32 ms
5aUo9_-1phKLFgshYDvh6Vwt7V9VGEtGh09D.ttf
44 ms
5aUo9_-1phKLFgshYDvh6Vwt7V9VPEpGh09A.woff
44 ms
5aUo9_-1phKLFgshYDvh6Vwt7V9VPEpGh09D.ttf
35 ms
5aUo9_-1phKLFgshYDvh6Vwt7V9VTE5Gh09A.woff
14 ms
5aUo9_-1phKLFgshYDvh6Vwt7V9VTE5Gh09D.ttf
15 ms
5aUt9_-1phKLFgshYDvh6Vwt7V9dsW1V.woff
51 ms
5aUt9_-1phKLFgshYDvh6Vwt7V9dsW1W.ttf
38 ms
5aUo9_-1phKLFgshYDvh6Vwt7V9VFE9Gh09A.woff
64 ms
5aUo9_-1phKLFgshYDvh6Vwt7V9VFE9Gh09D.ttf
44 ms
5aUv9_-1phKLFgshYDvh6Vwt7V9V3F1frmw.woff
96 ms
5aUv9_-1phKLFgshYDvh6Vwt7V9V3F1frm8.ttf
71 ms
style.min.css
140 ms
style.min.css
57 ms
stjohnsucc.info accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
stjohnsucc.info best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
stjohnsucc.info SEO score
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stjohnsucc.info 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 Stjohnsucc.info 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.
stjohnsucc.info
Open Graph description is not detected on the main page of St Johns UCC. 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: