WordPress Page Loading Speeds Where Plugins

This strategy sound in business concept as it allows WordPress users to easily and quickly create some very nice looking websites where they can add website functionality and features even if they do not have very good coding skills, is still however, flawed architecturally as these plugins are enabled through the use of JavaScript callouts which need to pull in the full plug-in code for each 3rd party widget being used on a particular web-page each time that web page is loaded. This causes two things to occur on each page load that significantly reduces the speed of page loading:

First, you are not just loading the native programming logic to the web page that you built and that resides on your server only. You are forced to callout out to potentially dozens of external locations both on your server and on 3rd party servers in order to fully render your web-page which causes lag-time issues and time delays in loading the page.

Second, when you load the plugin, you have to load it as written by the 3rd party which often means that you are loading code that has a number of configurable options that you are note even using for the method in which you are using the plugin. This is a lot of extra programming code being loaded with each page rendering that you don’t need and it tends to make your web-page very “fat”, often putting the page into the 2-4 megabytes of code loading ranges whereas most custom coded pages are loading at under one megabyte of code. The fatness of these pages also impacts negatively on the speed of the web page rendering.
Google and browser manufacturers have already begun to penalize website owners for the use of JavaScript callouts on websites through certain strategies of their own. Browser manufacturers such as Chrome and Firefox for example, are limiting the enabling of some plugins on their platforms, mobile devices in most cases simply won’t run them, and Google penalizes you by not letting your site be found easily through their search engine. I tested the mobile device rejection of plugins with the draft WordPress site I had created by trying to load the page on my cellphone. After waiting over 40 seconds for the page to load, the device just rejected the load entirely, leaving me in limbo looking at a blank screen. This is why it is recommended to limit your use of plugins and eliminate them from your site over time if you can. Move to native coding strategies on you website wherever possible.