Website Loading in 30-50 seconds

The first thing I do is run a reputation check on a site, before going to any site on a forum. It doesn’t tell me why, but your site gave a warning. If you are not trying to infect people, then you need to take care of that. It could be from a security issue, from poor conduct of a previous owner, hacking, etc.

Otherwise, I just ran your site through GT, Pingdom, and Google page speed analyzer. I was unable to get any data from Google, and it took several tries on the other two.

There is a waterfall feature on GT that shows where your site is slow (hover on the longest line). In your case it happens to be in server response. On my particular evaluation, it shows your site waiting for a server response for 49s, which points to an issue on your server. If you have a shared hosting plan, you may be sharing the server resources with many other sites, which can vary your site speed throughout the day. You also may have added a plugin that doesn’t play well with others.

I’m not sure what to tell you about the additional user. You should check with Bluehost → it may be something they did to troubleshoot. My first thought, though, was “hacked.”

I have previously tried Bluehost, I did not have a problem with the front end, but the back end was always slow. I recommend SiteGround to all of my clients. Most of my clients sites load in under 3s, if using SiteGround.

• This reply was modified 6 years, 6 months ago by Shanora.

Your issue is definitely server-based, and it appears to be a server-based remote request issue. I suggest that you deactivate Jetpack since it’s known to cause issues like this. If that fixes the problem, great!

If that doesn’t fix the problem, then deactivate the aggregator plugin you’re using. If that fixes the problem, then you’ll need to figure out which one (or ones) of the feeds you’re collecting is causing the problem. It’s possible (actually likely) that each feed is taking a long time to obtain.

Bluehost is a brand name of a hosting conglomerate named EIG, and it does not have a good reputation. One of the things it does with its shared and VPS hosting is throttle incoming bandwidth, which in your case means that collecting your feeds could take a long time. If this is what is happening, the only permanent solution to your problem is to move to better hosting.

Finally, if your feed plugin has an option to cache the feeds, you should consider enabling it. While it’s best to fix the problem, in the meantime, feeds that update once an hour are much better than dynamic feeds that take a minute to load!

Shanora (@shanoranetworks) Thanks for your help. I chose the Domain name myself and bought it. I have run checks and it says the site is 100% ok.I am still even building it slowly. a $96 website for a start performing this way is shocking… I actually thought that some support staff whom I gave access may have done that but it doesn’t make sense… I may as well have been hacked..

I can’t find any data in analytics….I bought 2 domains, 1 from WordPress directly and it loads like in less than 3 seconds while the one I bought from bluehost loads in 30 secs… I will have to move to another hosting…

Dion Designs (@diondesigns) thanks for your advise, I will try those solutions in a few minutes… if it doesn’t work, then, I’ll change hosting

• This reply was modified 6 years, 6 months ago by propheticintercessionafrica.

Here’s what I think is happening…

You are running a RSS aggregation plugin and you are probably triggering that via the built-in WordPress PsuedoCron. WordPress PsuedoCron is triggered when someone visits your website.

I imagine you are also trying to pull feeds in short intervals so you probably have several feeds needing attention at any moment since your site is huge.

My first suggestion is to run cron from the servers cron system itself. Here’s pretty much the way I’ve done it. https://www.wpbeginner.com/plugins/how-to-view-and-control-wordpress-cron-jobs/. This means when a user visits your website that visit doesn’t trigger a cron event so your user doesn’t need to wait for the aggregator plugin to run and share ‘horsepower’ with that.

Now RSS feeds are usually fine with lower update frequencies. My aggregators run at 3 hour intervals for each individual feed. But… there’s a directive sent from many feeds that tells the aggregation system to pull at 60 minutes. My aggregator plugin ignores those requests to speed up so I stay at my desired 3 hours instead.

My aggregator also knows to ignore older posts (set to 60 days) and to pull in a max of 5 posts at any one run from a random list of available posts. And it deletes posts at 61 days just to shrink the post data tables some. In other words I’m running about a 10th the load I’d be running if I left things at import all and at 60 minutes if most feeds are 30 posts or so.

Finally, most of my aggregators run back to back twin WordPress instances with the one instance doing nothing but pulling feeds while the second WordPress pulls from the first and handles the public side of things.

Another thing I do on all my sites is I run my DNS on CloudFlare and let CloudFlare step in and serve my content. CloudFlare is faster and more secure on their DNS then I could ever hope to be and then they reduce my server load by close to 20 percent.

So it takes two hosting packages and CloudFlare to do all that I’ve done but there’s an economy of scale working for me and I own the hosting outlet anyway.