Excessive or incorrect use of third-party plugins and external scripts (especially with CMS)
Posted: Mon Jan 27, 2025 5:04 am
Not everyone is an expert developer and not everyone is able to work on the source code of a page or theme uploaded to a trusted CMS, so we often resort to using plugins and/or small external scripts to meet a client's requests or to give new features to the project and make it more attractive.
What we need to know is that each resource we add usually increases the amount of code , server-side requests and data that must be downloaded by browsers as they are necessary for the functioning of "each addition", therefore, the general loading times of our site with all the pages it is composed of increase.
For more information, read the post: How to Optimize WordPress for SEO: My List of Plugins and Tools .Obviously, to best manage these parameters you need to know how to work with the .htaccess file, but to the usage of instagram database intervene and access it, simply download it from the Web Server and open it with a NON-VISUAL text editor , such as the classic Notepad (on PC, text-edit for Mac).
Let's see two lines of code, at least for the most used methods.
A) Managing the Caching Process with Cache-Control
We can enable this feature at once on every aspect of our work with just a simple string in the file, like this one below:
Header set Cache-Control "max-age=31536000, public"
But it could be more useful (also based on the structure of the site in question) to check only a specific type of file, so:
It seems difficult, but we can explain every single item we used, so:
filesMatch informs the browser which extensions it should respect the new caching guidelines;
Header set takes care of setting a document header where all the deadlines for requests for content to be kept in cache are expressed.
max-age manages the cache duration, therefore its expiration in time, and is expressed in seconds. In this specific case (if I count correctly), it corresponds to one year.
public specifies that this request is valid for every user's browser and also for a CDN (Content Delivery Network). If it were set to private , it would only be valid for the first part of visitors.
What we need to know is that each resource we add usually increases the amount of code , server-side requests and data that must be downloaded by browsers as they are necessary for the functioning of "each addition", therefore, the general loading times of our site with all the pages it is composed of increase.
For more information, read the post: How to Optimize WordPress for SEO: My List of Plugins and Tools .Obviously, to best manage these parameters you need to know how to work with the .htaccess file, but to the usage of instagram database intervene and access it, simply download it from the Web Server and open it with a NON-VISUAL text editor , such as the classic Notepad (on PC, text-edit for Mac).
Let's see two lines of code, at least for the most used methods.
A) Managing the Caching Process with Cache-Control
We can enable this feature at once on every aspect of our work with just a simple string in the file, like this one below:
Header set Cache-Control "max-age=31536000, public"
But it could be more useful (also based on the structure of the site in question) to check only a specific type of file, so:
It seems difficult, but we can explain every single item we used, so:
filesMatch informs the browser which extensions it should respect the new caching guidelines;
Header set takes care of setting a document header where all the deadlines for requests for content to be kept in cache are expressed.
max-age manages the cache duration, therefore its expiration in time, and is expressed in seconds. In this specific case (if I count correctly), it corresponds to one year.
public specifies that this request is valid for every user's browser and also for a CDN (Content Delivery Network). If it were set to private , it would only be valid for the first part of visitors.