Are you not progressing with your WordPress performance? Take a step back • WordPress Help

Do you spend the day on the Internet reading tips and good practices on how to improve the performance of your WordPress and you have the feeling Are you still on the same point?

It's time for to take a step back and make a global and aseptic vision of your project with WordPress it's clear that " the trees do not let you see the forest . "

From time to time, it's time to stop the frenzy of optimizations and changes and perform a quiet perspective exercise of your project with WordPress. Here are a few tips to review or rethink your current performance strategy.

1. Server and hosting

It is likely that you already have your server perfectly optimized, but maybe it is incompatible with your hosting provider, or vice versa, your hosting provider has functions that you do not know and you are not taking advantage of on your server .

Rate your hosting provider and the characteristics of it with respect to others and the current one.

Note : it would be nice to have a tour of your .htaccess too many rules or complex rules even repeated?

2. Topic

Surely the theme that you use for your project is the most suitable by image or weight and needs of your web. Have you tried using another one on your same installation? Have you tried using the same theme that your competition uses?

Note : your plugins may be functionally correct, but maybe they are not optimal . Search and try other plugins that implement the same functionality required.

3. CDN and cache

The use of an CDN external and the correct configuration of the cache of your components guarantees a better performance to your web, but it is likely that is not well optimized, in terms of specific rules of your own project. To review.

Sometimes the optimizations for the use of the browser cache or the CDN are designed for intensive work environments of many users and it may not be your case.

You will get more out of an intermediate CDN in environments of many users and you will get better performance optimizing the browser cache in environments of few users, but with a lot of repeat visits.

Note : in many projects I found cached optimizations, for example in file types and folders, which then did not exist in the project.


The opinion of your users is very important do you take into account all the improvements you are making?
Thinking about optimization, are you thinking also from the user's point of view?

Sometimes they are incompatible terms, we want a fast web, tied to some technical parameters that give us external tools and we are forgetting that it is not functional or we have lost the functionalities that the user / client needed.

Note : test and measure your improvements well, not only in terms of performance, but user satisfaction.

Copy and paste an idea or recommendation on your server is easy, the hard part is to understand, analyze and evaluate the need and the benefit that is obtained.

There are no two identical projects on the Internet so as the good suits have to be made to measure, that is why it is necessary that all the optimizations that you carry out the s try, meditate and values ​​before putting them into operation, maybe they are not necessary or are not very beneficial for your project. But of course, all this look at you taking a step back.

NOTICE : This publication is from two years ago or more. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say that we have not warned you.

Loading …

That may also help you:

HTTP / 2 and WordPress – The future of the Web

The HTTP protocol is the engine that moves the Internet, without which you could not be reading this blog, nor buy online, share content in your networks social and all those things that we are used to.

Now, this protocol, in the HTTP / 1.1 version had not been updated since 1999, but that's it: Welcome HTTP / 2!

What is HTTP / 2?

 HTTP-2 "width =" 480 "height =" 240 "srcset =" 480w, 319w "sizes =" (max-width: 480px) 100vw, 480px "/> </p>
<p> Not a plugin, it's not a bird, it's not an airplane, it's <strong> a new network protocol for the WWW </strong> that comes to improve the current HTTP: the connections between the browser and the web page. </p>
<p> it is about <strong> an improvement of the current HTTP protocol so that the connections to web pages are faster and more efficient </strong>reducing time between calls. </p>
<p> It is <strong> a great improvement </strong>which has been pending since 1999, and that Google started with its <a href= protocol SPDY in 2009, now abandoned when adopting HTTP / 2.

Why is HTTP / 2 better?

 http-vs-http2 "width =" 550 "height =" 538 "srcset =" 550w, -http2-60x60.gif 60w "sizes =" (max-width: 550px) 100vw, 550px "/> </a> </p>
<p> Broadly speaking, and being practical, some of the improvements it incorporates are: </p>
<li><strong> HTTP / 2 requests are much smaller </strong> in size since <strong> uses compression </strong>. </li>
<li><strong> HTTP / 2 uses multiplexing </strong>which allows the sending and receiving of several files at the same time [19659013] HTTP / 2 allows the server to "launch" the content gone </strong>that is, that responds with data to most requests that the client requests. This allows the server to offer data that it knows the browser will need to display a web without having to wait for the browser to receive the first response, and without having to do another cycle of requests. </li>
<li><strong> HTTP / 2 can leave the connection open </strong> for reuse </li>
<li><strong> With HTTP / 2 the browser makes many fewer requests to the server </strong>resulting in a significant reduction in page load time. </li>
<li><strong> HTTP / 2 no longer needs the Most of the HTTP 1.1 syntax </strong>such as methods, status codes, header fields, URIs, etc. The element to be displayed is transported directly between the client and the server. </li>
<li><strong> Fewer headers to transmit </strong> because HTTP / 2 uses compression </li>
<li><strong> HTTP / 2 requires a smaller amount of data </strong>which it translates into less loading time. </li>
<li><strong> HTTP / 2 changes the loading order </strong>which gets a more efficient load of the page when the elements are prioritized. </li>
<p> The first tests show <strong> a improvement of between 20% and 30% in the speed </strong> of downloading the page with this update. </p>
<h2><span id= What do I have to do to use HTTP / 2?

The first thing you should know is that ] the latest versions of the most used browsers are already compatible with HTTP / 2 which is also compatible with previous versions of the protocol, so if you decide to pass to HTTP / 2, you do not lose any users, neither visit nor sale .

The only thing you need to Benefit from this improvement is an SSL certificate and that your hosting provider enables HTTP / 2 on your server if you are already prepared for it. If you are already working with a provider like SiteGround ask to have this functionality enabled, since your servers are ready .

If you have a online store surely you already have an SSL certificate so, what are you waiting for? Speed ​​up your website! Start using HTTP / 2!

HTTP / 2 and WordPress

 WordPress http2

Actually you do not need to do anything in WordPress so you can use the HTTP / 2 protocol apart from having an SSL certificate installed and active and that your hosting provider will activate HTTP / 2.

On the other hand, when using HTTPS, you must make sure that you are serving all your content in https , without mixed content that is, that there is nothing in your site that is still used in http.

Where if you have to do some work, if you did not do it already when going to HTTPS and it is to check that you do not use anything in http, instead of https .

I am referring to images, permanent links, redirects, etc. You should check your WordPress configuration file ( wp-config.php ) to verify that you define your routes with https, and the file .htaccess to review any possible redirection that you still have to an http, for example.

Also, it's not too much to check if there is a plugin that generates absolute http addresses instead of relative ones, whatever that might be.

Of course, you should have in Settings -> General the site address and WordPress in https.

There are plugins like, Really Simple SSL the one that I recommended you the other day talking about SSL which does most of this work, but it does not hurt a review for mixed content. The same browser will inform you if this is happening or not.

But come on, that in principle you do not have to do anything to use HTTP / 2 that you should not already do to have your WordPress with HTTPS but if you were not exhaustive at the time maybe now it is not too much to put yourself to it, for take advantage of all the advantages of both technologies .

HTTP / 2 and developers

 http2 vs http1

Over the years, developers and experts in SEO have developed practices to try to bypass the restrictions and weaknesses of the HTTP / 1.1 protocol, so both plugins and themes have been incorporating a series of tricks that, if active HTTP / 2 is not only necessary but they are counterproductive .

For example, it is very common to use compression, combination and asynchronous loading of CSS files and JavaScript . There are themes that do it by default, and a multitude of SEO plugins, let alone Cache, which also incorporate it.

This, which is a good idea if you're on HTTP / 1.1 is just what you should not do in HTTP / 2 because you do not need it and you will be using resources and processes that harm the performance of your web, being unnecessary.

What is a practice totally discouraged in HTTP / 2 is the fragmentation in several domains known as " sharding ", since it forces more DNS queries.

In short, if you are a developer of WordPress themes or plugins, keep in mind that you do not need to use more sprites or combine unnecessary files or upload assets in your code .


In short, is a good idea to set up HTTP / 2 on your website since you're going to improve the user experience, thanks to the fact that Downloading the page will be faster and more orderly, and is compatible with your current site, and in principle you do not have to implement anything in your code, nor install any plugin or anything similar.

The HTTP improvements / 2 are tremendous and views in a practical way can be summarized in …

  1. Web faster
  2. Web more secure, it forces the adoption of SSL
  3. Web more optimized for mobile
  4. Less consumption of server resources

In case you are not clear enough, I summarize the changes you must do on your website to offer maximum speed and an unbeatable user experience :

  1. Activate a CDN
  2. Offer your secure website through HTTPS with an SSL certificate
  3. Ask your hosting provider to activate HTTP / 2 on the server

Do you already have your website on HTTP / 2? Do you have any doubts? Something that has happened to me?

If you want to ask or share something about it, do not cut yourself, we're all looking forward to your doubts or advice and so we learn more. There you have the comments.

This article would not have been possible without the inestimable help of the great Fernando Puente that to see if at once he registers as a user of the blog and the solito is encouraged 😉

NOTICE : This publication is from two years ago or more. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading …

That may also help you:

What is Photon and how does it work? • WordPress Help

One of the most interesting modules of the plugin JetPack is perhaps also one of the most mysterious or unknown so let's put some light on this little free wonder called Photon .

What is Photon?

 jetpack-photon "width =" 550 "height =" 331 "srcset =" 550w, .jpg 768w, 840w, -photon.jpg 1080w "sizes =" (max-width: 550px) 100vw, 550px "/> </a></p>
<p> Photon is <strong> one of the modules that you can activate in the JetPack plugin </strong>and being one of the most interesting is curiously those that are inactive by default. </p>
<p> According to the pr oppia web of JetPack, Photon is defined as <strong> an image acceleration service for sites hosted on or connected via JetPack </strong>. This means that it will require less loading time in your hosting and <strong> images </strong> will be loaded faster for your visitors. </p>
<p> The same module describes its function: </p>
<p> Improve your site by uploading images from the CDN (Content Delivery Network) of We cached your images and served them from our servers, which reduces the burden on your Web storage provider in a single click. </p>
<p> That is, it comes to be <strong> a kind of content delivery network or CDN </strong> (Content Delivery Network) in the style of Amazon S3 or CloudFlare, but <strong> hosted on servers </strong>and best of all, <strong> at no cost </strong> nor have to configure anything or create new DNS or anything like that. </p>
<h2><span id= How does Photon work?

To use Photon you just have to go to the JetPack page of your WordPress installation and from the configuration menu or main menu, Activate it

Once active there is nothing to configure, it has no settings page, it works automatically from that moment a copy of each one is created of your images on the servers of and the next time someone visits your website you will see your site as always but the images, instead of showing the copy hosted on your server will be displayed on the servers of, adapted to the right size

Apparently nothing will change on your website, except that it will go faster since the images are loaded from much faster and optimized servers.

If you upload an image to illustrate a new publication the process is the same, your site is connected via JetPack with and will also host the image on your servers, so that it is ready by the time you post it and is visible on your website.

The only way to that someone realizes that you are not hosting the images on your server will be reviewing the published URL of each image, as you can see in the following example before and after activating JetPack's Photon:

As you can see the image is no longer on the web server but on the CDN, of type / If you notice it even retains the same relative path of upload and image name.

Some interesting details that you did not know about Photon

  • Photon filters the content but does not make any changes to the WordPress database. ] Photon only acts on the images in the entries and on the highlighted images (image thumbnails)
  • Photon acts on both the old and new entries.
  • Photon only hosts the whole image you upload, without its copies Minor, performing a resize appropriate to the content based on the size values ​​to insert that you define when inserting the image in your entry, the HTML attributes of width and height. In case you do not define any size attribute, it adapts to the maximum container of your input.
  • Photon compresses without loss all the images it hosts using OptiPNG or jpegoptim.
  • Photon is not just a content delivery service but also an image manipulation service. Photon can resize, crop, adjust brightness, contrast and zoom levels and even apply filters to images .
  • If you activate Photon you do not lose anything, your images are still uploading to your server.
  • With Photon you do not save hosting space, because your images keep uploading to your server and creating different sizes.
  • If you deactivate Photon you do not lose anything, the images hosted on your server are loaded.
  • Photon only stores, resizes and serves gif, png and jpg images.
  • Photon can only serve images of servers that serve port 80 (99.99% of the planet's web servers)
  • Photon does not enlarge the images, which would also be horrible and pixelated, it only resizes to smaller sizes, to adapt to the content.
  • If your server takes more than 10 seconds to upload the image to Photon, in the course while uploading the image will appear on the page as if the image is missing, with the resource and broken image.
  • Photon also stores and serves animated gifs but if it requires some resizing then it would be static (this is so even if they are hosted on your server).
  • Photon does not update the cache, it lasts forever. If you want to "update" an image you will have to change the name or upload another one instead.
  • The stacked galleries of JetPack use Photon to work, in fact the images of this type of galleries will be loaded from the CDN even if you do not have active Photon, which means that they activate a "version" of Photon in reality. If you do not want to use Photon you can activate the DEBUG mode of JetPack .
  • Photon also acts on the image thumbnails that are displayed in the JetPack related Entries module.
  • You can use Photon and your cache plugin without problems. In the CDN tab you simply have to indicate that you do not use a CDN, even though you are actually using it.

Does Photon harm my website?

Photon and SEO

In principle might seem that all are advantages when activating Photon because by offering a faster load of your website due to the higher speed of the servers when serving your images, the result is an improvement in many whole navigation experience

And yes, that's true. Activating Photon you get a few load times of your web, which results in better performance and positioning for search engines in the aspect of speed but …

but "is that on the other hand you can lose positioning in the search engines by losing all the traffic to your images which will no longer point to your website but rather to the servers. This is true with any CDN but you must take it into account and weigh what contributes more to the performance and positioning of your website: the speed or visits to the images .

But you must take it into account, as what is clear is that the images hosted on your server will no longer be indexed in Google, that's the case.

Anyway, in my opinion there is no color, it is much better to offer a few load times, taking into account that the traffic coming from images is of very low quality, with some times of permanence in the page ridiculous .

If I have to put in a balance the traffic by the images in front of the of speed and reduction of bounce rate I am clear that Photon wins.

If, in addition, in passing we eliminate the harmful effects of hotlinking on our website because although do it to us no longer consume resources of n Our server, in this sense the advantages win over the inconveniences.

In any case, it is a decision that you must make based on your knowledge and previous statistical analysis, and subsequent checks, as there are situations in which it is better to choose the positioning coming from images. It occurs to me, for example, if you have an infographics site or similar.

Photon ghost URLs

It has been detected that Photon can generate additional URLs on your site even if it is not active, this is because JetPack activates it in part always, for example for the module of related inputs. Fortunately you can disable it completely using the following filter:

Photon and HTTPS

It has been detected that Photon does not get along with SSL certificates because it accepts HTTPS but returns HTTP, but it has an easy solution by applying the following filter: [19659062] add_filter ('jetpack_photon_reject_https', '__return_false');

add_filter ( 'jetpack_photon_reject_https' '__ return_false' )

Rights of transfer of images

Another aspect to take into account would be if there is any right to copy and print the images that you must fulfill, for example if you have assigned rights to an image for your site , but not to house it in a C DN in which case you would have to, or extend the agreement or not activate Photon only for that / s image / s. It's a special case but you have to say it all.

Are there more free CDNs besides Photon?

Of course there are some, but you should bear in mind that none is so easy to activate and use as Photon, here are some how many alternatives to Photon:

So should I use Photon?

If you're not already using another CDN, it's highly recommended. You get the same service but without any cost and without having to configure anything, it works instantly and you get the same as with any of these services, except for the additional features of WAF (Web Application Firewall) that some include.

With Photon you get :

  • Shorter load times.
  • Lower bandwidth consumption of your server.
  • Usability improvements and user experience.
  • Reduction in bounce rate.
  • Less consumption of resources. from the server, which no longer has to display the images.
  • Fewer requests to the database to display the images.
  • You save the cost of a CDN.

In summary, that Photon is one of the reasons why JetPack is a highly recommended plugin, especially for sites hosted on servers with few resources.

JetPack has its stuff and I criticize it a lot, but certainly Photon is a very favorable point, a lot . If you need a CDN and do not want to spend the money it costs or get into cumbersome configurations, or pay an expansion of resources on your server, then Photon is the best option, no doubt.

NOTICE : this publication is two or more years ago. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading …

That may also help you: