That is a great response (above my own), but I think you should first tackle this from the perspective of “Define the problem; then figure out how to fix it”.
I checked the main page, then the two pages to which harmck linked, and then two more subpages (in the Ministries sections). Sometimes it is hard to tell this, but try checking each page after clearing your browser cache (mentioned above, a good suggestion to ensure this is how new visitors are seeing the page) and using a blank tab. Reason being, it appears that…once the host responded to my requests, the load time was less than 2 seconds. All I seem to notice is that it takes awhile before loading/rendering even begins, which might be that to which you are referring.
This wiki article (apparently pertaining to a particular hosting service) should apply to your situation and be highly relevant: https://neowiki.neoseeker.com/wiki/Troubleshooting_Slow_Pages_on_Neoseeker
Where it says “[ server id: venture ··· elapsed: 0.4924869537 ]”, this is definitely a bit that is generated by some custom troubleshooting code they use on their pages.
In reference to creating that output, a quick Google search turned up this link to what appears to be the most important snippet of code needed to generate this sort of data. I suggest putting a variation of that code at the bottom of some pages you feel are loading slowest to more easily compare the load duration (described in 1. of the first link as “if you count that it takes 10 seconds for a page to load and the elapsed time of the page is 10.35seconds it means…”) versus the connection reaction time (described in 2.). When added together, these two durations are the actual time it takes from click to full display. But without one or the other being defined through server output…you get the idea!
From what I am seeing, it appears that 2. is more likely to be occurring (and hence the fault would lie with your internet connection, not your host), but I cannot definitively answer either way without actually getting a residual message from the page reflecting this.
Best of luck to you in defining the actual problem, and hopefully its only your personal connection at fault.