2.2 sec in total
169 ms
1.5 sec
458 ms
Welcome to meetinghouse.info homepage info - get ready to check Meetinghouse best content right away, or after learning these important things about meetinghouse.info
Germantown Mennonite Historic Trust - preserving the story of the 1683 immigration, 1688 Protest Against Slavery, 1770 Meetinghouse, and continued legacy of Mennonites in Germantown
Visit meetinghouse.infoWe analyzed Meetinghouse.info page load time and found that the first response time was 169 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.
meetinghouse.info performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value7.7 s
3/100
25%
Value6.6 s
37/100
10%
Value1,320 ms
17/100
30%
Value0
100/100
15%
Value11.6 s
18/100
10%
169 ms
262 ms
18 ms
41 ms
58 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 30% of them (19 requests) were addressed to the original Meetinghouse.info, 36% (23 requests) were made to Cdn2.editmysite.com and 14% (9 requests) were made to Calendar.google.com. The less responsive or slowest element that took the longest time to load (811 ms) belongs to the original domain Meetinghouse.info.
Page size can be reduced by 180.0 kB (14%)
1.2 MB
1.1 MB
In fact, the total size of Meetinghouse.info main page is 1.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. 70% of websites need less resources to load. Javascripts take 863.3 kB which makes up the majority of the site volume.
Potential reduce by 84.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 84.3 kB or 80% of the original size.
Potential reduce by 2.0 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. Meetinghouse images are well optimized though.
Potential reduce by 93.3 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 93.3 kB or 11% of the original size.
Potential reduce by 467 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. Meetinghouse.info has all CSS files already compressed.
Number of requests can be reduced by 29 (55%)
53
24
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Meetinghouse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
meetinghouse.info
169 ms
www.meetinghouse.info
262 ms
analytics.js
18 ms
sites.css
41 ms
fancybox.css
58 ms
main_style.css
146 ms
font.css
76 ms
font.css
58 ms
font.css
61 ms
font.css
61 ms
templateArtifacts.js
148 ms
jquery-1.8.3.min.js
75 ms
stl.js
78 ms
main.js
78 ms
commerce-core.js
73 ms
main-commerce-browse.js
76 ms
stl.js
76 ms
collect
63 ms
main-customer-accounts-site.js
36 ms
js
337 ms
ccmtblv2.png
344 ms
email3_trans.gif
394 ms
safe_subscribe_logo.gif
279 ms
body-bg.png
226 ms
wrap-inner-bg-lime.png
224 ms
header-bg-lime.jpg
411 ms
1383784907.png
811 ms
nav-bg-lime.png
431 ms
nav-sep-lime.png
292 ms
nav-active-lime.png
296 ms
main-bot.png
294 ms
main-inner.png
364 ms
banner-bot.png
367 ms
social-lime.png
368 ms
2159637.png
470 ms
392379.jpg
474 ms
footer-wrap-lime.png
439 ms
ga.js
136 ms
snowday262.js
135 ms
466 ms
bold.woff
112 ms
regular.woff
112 ms
regular.woff
111 ms
bold.woff
115 ms
regular.woff
111 ms
light.woff
114 ms
italic.woff
135 ms
lightitalic.woff
134 ms
bolditalic.woff
133 ms
embed
224 ms
embed
366 ms
tp2
129 ms
rs=ABFko3_L7zBdLKvHZ1rVy0blR9lQ0lAAyQ
245 ms
m=embed
22 ms
client.js
29 ms
js
66 ms
cb=gapi.loaded_0
15 ms
logo-plus.png
32 ms
googlelogo_color_46x16dp.png
38 ms
blank.gif
8 ms
menu_arrow_open.gif
10 ms
icon_print.gif
16 ms
btn_menu6.gif
16 ms
combined_v22.png
22 ms
meetinghouse.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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
meetinghouse.info best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
meetinghouse.info SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Meetinghouse.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 Meetinghouse.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.
meetinghouse.info
Open Graph data is detected on the main page of Meetinghouse. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: