Support » Plugin: Add Meta Tags » Efficiency of the new version – not happy!

  • Resolved billichen

    (@billichen)


    I installed the latest (2.6.7) version of the Add Meta Tags plugin yesterday and, after checking with webpagetest.org, noticed that homepage loading time increased by 100-150ms. After re-checking it 5 or 6 times I decided to install P3 (Plugin Performance Profiler) and evaluate AMT plugin effect on page loading speed. The results were quite surprising:
    With minimal configuration (i.e. only basic metadata checked and few global keywords defined) the AMT plugin contributed 19% to page loading total delay caused by 10 installed plugins incl. such heavyweight as Wordfence Security.
    With typical configuration (Opengraph, Dublin Core, and schema.org metadata checked) the plugin was responsible for 23% delay.
    Here are the snapshots for both cases:
    https://www.dropbox.com/s/3xbqnxq8dr0nddk/AddMetaTags%20-%20min%20config.jpg?dl=0
    https://www.dropbox.com/s/uwgxgvvophb6vn5/AddMetaTags%20-%20full%20config.jpg?dl=0

    I am not sure whether this is something wrong with the new version of the plugin or this performance price was always there.

    Considering the importance of page loading speed for SERP I am wondering whether I’ll be better off disabling AMT plugin on my sites..?

    https://wordpress.org/plugins/add-meta-tags/

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author George Notaras

    (@gnotaras)

    Hello,

    Thanks for your feedback.

    As a general conclusion, I’d say that your findings have no real value, unless you provide results with the plugin activated and results with the plugin deactivated.

    homepage loading time increased by 100-150ms.

    Does this mean that you repeatedly measured load time with Add-Meta-Tags deactivated and then with Add-Meta-Tags activated and there had been an increase of 100-150ms in page load time when the plugin was acticvated?

    No matter what, the webpagetest service is not the most accurate tool for the job for this kind of test.

    I am not sure whether this is something wrong with the new version of the plugin or this performance price was always there.

    No recent updates of the plugin can possibly justify an increase in page load time.

    In general, I don;t see anything weird in the provided pie charts, taking into account the type of plugins that are activated.

    What I suggest is deactivate Add-Meta-Tags and re-do the tests. Look for absolute values regarding page load delay. The percentage depends on what kinds of plugins are activated and is always relative.

    George

    Plugin Author George Notaras

    (@gnotaras)

    Also, I am marking this topic as resolved, since there is absolutely nothing I can do.

    Please perform tests with and without Add-Meta-Tags, compare the results and decide whether the overhead justifies disabling the plugin. The decision is up to you.

    Again thanks for your feedback,

    George

    billichen

    (@billichen)

    I am not sure what isn’t clear in my first message… when plugin is disabled I reduce page loading time by 100-150ms, If in addition to basic metadata I check boxes for Opengraph, Dublin Core, and schema.org metadata I loose another 100ms in loading time.
    It is easy to reproduce, anyone can go to webpagetest and check this for your site…
    Anyway, I just wanted to know if this is something that was introduced with the last version, you are saying “no”, so I guess we always paid performance price for the metadata and just didn’t notice it.
    Re: “the webpagetest service is not the most accurate tool for the job for this kind of test“, I don’t know better one… can you suggest an alternative test?

    Plugin Author George Notaras

    (@gnotaras)

    Hi,

    The P3 plugin you mentioned should give a more accurate idea about the overhead when the plugin is activated. webpagetest is affected by many other factors and it’s probably unsuitable for testing the plugin overhead in most cases. Especially, if you test a production web site or a web site hosted on a shared hosting service, then it is a completely inaccurate approach.

    By the way, the by 100-150ms longer page load time you mentioned when the plugin is activated is a huge delay that cannot be justified. Maybe I misunderstood the part of your message explaining that you have actually performed the test with and without the plugin.

    When I have the time, I’ll try to test WP with Add-Meta-Tags as the only activated plugin and see how webpagetest is affected.

    Some preliminary tests using the P3 plugin indicate that the overhead of using Add-Meta-Tags is somewhere between 17-25ms and that’s on a local virtual machine.

    Also, you can always downgrade to an older release (available here) and compare the results.

    If page load time for your public content is such a big problem for your websites, I’d say that you are looking at the wrong direction. I highly recommend searching for caching plugins and/or a CDN service.

    Add-Meta-Tags is as lightweight as possible already and there is nothing more I can do. The ‘lightweightness’ is not only about the overhead in web page load time, but also about the fact that the plugin is not overloaded with tools and seo trackers that would negatively impact user experience.

    Thanks for your feedback.

    George

    Plugin Author George Notaras

    (@gnotaras)

    Also, if possible, I’d be very interested in P3 results with and without Add-Meta-Tags. Also the specifications of your server would also be useful information. On the other hand, if you host your web site on a shared hosting service, the results are not really useful, so please don’t bother.

    Thanks in advance,

    George

    Plugin Author George Notaras

    (@gnotaras)

    Hello,

    Could you tell me which version of the plugin you had installed before upgrading to 2.6.7? I’ll try to investigate this issue in the following week.

    Thanks in advance.

    Plugin Author George Notaras

    (@gnotaras)

    After taking a better look at the images, I notice that the additional runtime due to Add-Meta-Tags is 16-23ms, which is close to my own findings (17-25ms).

    Please let me know a plugin version which has less impact on the load time.

    Hi George,
    I don’t have the information on the old version anymore but I noticed that in the latest version (2.6.11) the part that slows down things is schema.org (approx 50% time increase for this plugin). When I uncheck it I get very reasonable performance – not sure what you changed since 2.6.7 but it is certainly much better now (at least in my tests). Considering the speed improvements, I now have Opengraph and Dublin Core checked and schema.org unchecked.
    Thanks for taking care to address this.

    Plugin Author George Notaras

    (@gnotaras)

    I repeatedly tested the 2.4.3 and 2.6.11 versions of the plugin using P3’s auto test. Below are some results:

    – 2.4.3: http://i.imgur.com/taWxGTZ.jpg
    – 2.6.11: http://i.imgur.com/zVICxor.jpg

    I’d say the average runtime for 2.4.3 is around 14-15ms, while for 2.6.11 is 15-17ms.

    I tested the above in an isolated virtual machine.

    In the following weeks I’ll try to check what can be optimized. My guess is that the gains won’t be bigger than 1-2ms and that’s a very “optimistic” estimate.

    Nevertheless, P3 is a by far better way to get an estimation than webpagetest, because in case of webpagetest, apart from the page generation time on the server, there is the delay of the data delivery over the network plus the time required for the DNS query.

    George

    Plugin Author George Notaras

    (@gnotaras)

    BTW, I stumbled upon a discussion about this issue on the digitalpoint forums. Are you the original poster?

    I’d be very interested in the method you use to measure the page load time using the webpagetest api. The information that is published there about the 0.05-0.1sec delay in page load time as a result of using Add-Meta-Tags is completely false and unrealistic.

    Please provide links to results pages on webpagetest.org with and without the 2.6.7 version of the plugin.

    Thanks in advance for your feedback.

    George

    Plugin Author George Notaras

    (@gnotaras)

    I spent several hours testing and benchmarking. The most reliable results can be achieved by benchmarking a server on the local network with all irrelevant services shut down using the ab tool (with concurrency set to 1). I was able to get a delay of 30-35ms sometimes 40ms (results are not consistent even in this setup) when Add-Meta-Tags was activated. I tried commenting out various features of the plugin in an attempt to determine if there is a specific feature that is more CPU intensive than the others. This was not the case. The delay is a result of all the enhancements of the plugin development during the last months. Also, sanitization functions are used extensively throughout the code in order to make the plugin as secure as possible. This is not going to change.

    As I’ve written on the Digital Point forums, let me know if making the metadata available as plain text or json data on a custom URL like /foobar/POST_ID/ makes your life easier with caching. This is doable, but it will take some weeks before I finally test and implement it. Currently there is absolutely no free time at all.

    Plugin Author George Notaras

    (@gnotaras)

    I’m closing this topic. Feel free to re-open.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Efficiency of the new version – not happy!’ is closed to new replies.