1.1 sec in total
35 ms
899 ms
162 ms
Visit stjames.org now to see the best up-to-date St James content for United States and also check out these interesting facts you probably never knew about stjames.org
Visit stjames.orgWe analyzed Stjames.org page load time and found that the first response time was 35 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
stjames.org performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value13.9 s
0/100
25%
Value73.4 s
0/100
10%
Value2,220 ms
6/100
30%
Value0.008
100/100
15%
Value81.8 s
0/100
10%
35 ms
20 ms
13 ms
8 ms
10 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 85% of them (51 requests) were addressed to the original Stjames.org, 3% (2 requests) were made to Google.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (557 ms) relates to the external source Google.com.
Page size can be reduced by 558.9 kB (11%)
5.2 MB
4.6 MB
In fact, the total size of Stjames.org main page is 5.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.7 MB which makes up the majority of the site volume.
Potential reduce by 24.4 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 24.4 kB or 76% of the original size.
Potential reduce by 207.7 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 James images are well optimized though.
Potential reduce by 295.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 295.1 kB or 72% of the original size.
Potential reduce by 31.7 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. Stjames.org needs all CSS files to be minified and compressed as it can save up to 31.7 kB or 84% of the original size.
Number of requests can be reduced by 24 (41%)
58
34
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of St James. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
www.stjames.org
35 ms
jsapi
20 ms
jquery.min.js
13 ms
jquery.fancybox.css
8 ms
jquery.fancybox.js
10 ms
date.js
9 ms
MOJA.js
13 ms
styles.css
12 ms
flexslider.css
67 ms
jquery.flexslider.js
12 ms
main.js
10 ms
home.js
12 ms
less-1.1.3.min.js
11 ms
maps
94 ms
ga.js
29 ms
bg_visitor_area_wrap.png
12 ms
separator_visitor_area.png
8 ms
10 ms
8 ms
9 ms
6 ms
logo.png
9 ms
icon_magnifyier.png
11 ms
separator_menu.png
10 ms
bg_dropmenu.png
12 ms
bg_marquee_home.jpg
28 ms
overlay_marquee_home.png
12 ms
slide_1.jpg
28 ms
5b327d34731a4453aafa609d7c97198d.png
51 ms
homepage_holyweek.jpg
29 ms
stillman_homepage.png
62 ms
homepage_eastertidegiftsgroups.jpg
42 ms
homepage_momslunch16.jpg
36 ms
stewardship2016_concept_homepage.jpg
53 ms
slide_3.jpg
28 ms
bg_divider_home.png
33 ms
35 ms
40 ms
40 ms
bg_billboard.png
49 ms
separator_billboard.png
44 ms
42 ms
48 ms
button_mystjames_off.png
53 ms
button_giving_off.png
57 ms
button_calendar_off.png
59 ms
separator_footer.png
50 ms
logo_footer.png
53 ms
icon_email_off.png
54 ms
icon_droppin_off.png
58 ms
icon_dclogo_off.png
58 ms
bg_caption_marquee.png
57 ms
slide_indicator_on.png
57 ms
slide_indicator_off.png
58 ms
slide_arrowleft_off.png
56 ms
slide_arrowright_off.png
57 ms
__utm.gif
24 ms
embed
557 ms
js
42 ms
init_embed.js
34 ms
stjames.org 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.
stjames.org 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
Missing source maps for large first-party JavaScript
stjames.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stjames.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Stjames.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.
stjames.org
Open Graph description is not detected on the main page of St James. 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: