kellyteagle

OK the reason is simple. Each plugin you add to a site has the potential to slow it down. Plugins normally come with a bunch of ‘bloat’ that you may or may not need. When they load up on a page, their libraries are imported – often files full of JS or CSS. Each of these requires another HTTP request to the server, and contributes to the page loading time.
This isn’t a problem on computers with good broadband, but on phones or cr*p broadband, it can make a big difference to page loading times.
I like to keep my websites as streamlined as possible – and as a PHP Dev. it should be possible for me to write my own code.

I did in the end, by the way. I found a useful tutorial on the web which helped me work out how to do it ??
I just needed to work out what hooks to use.

• This reply was modified 4 years, 1 month ago by kellyteagle.

I am a PHP dev, and would prefer not to load up my sites sites with too many plugins. Thanks for your replies ??

Thanks for your replies. I had hoped there might be a way to achieve this wihout using a plugin?

Thanks, this has now been resolved elsewhere.

Hi Hannah,
Thanks for allowing my query to remain here for a while. I don’t suppose you or any of the other Automattic experts can suggest how to acheieve this, please?
Thanks,
Kelly

Hi,
Thanks for your replies.
Juan2machado: no I’m not using any custom settings. I’m unsure whether the plugins have their own htaccess files, but I’ll check.

HudsonValleyWebDesign: I migrated the site as I normally do, that is, I backed up the files to a ZIP and downloaded it. I exported the database to an SQL file, and ran a search and replace to correct the URL. I then imported the database to the new server, and extracted the contents of the ZIP file into the root (publichtml in this case).
I’ve done nothing differently to my normal process, the only difference here is that the site has come from a Managed WordPress hosting account with GoDaddy, to a GoDaddy VPS.

Thanks,
Kelly

Hi Benjamin,
Thanks for that, the problem was that the Calendar page was set to the wrong page!
Thanks,
Kelly