ESI, Headers, and Cache ratios per quic.cloud

  • Resolved RL

    (@lutzryan)


    1 year, 10 months ago

    Looking at analytics in Quic.cloud show a 1 to 25 ratio of cacheable to non cacheable dynamic data. And Im at the tail end of a large international event which I promote, and it would be ideal to get this ironed out for the future.
    –
    I use 2 different feeds on my site that update 2x daily. So 2 differnt pairs of plugins across about 200 pages.

    Below are 2 examples of the 2 pairs.
    https://xzib.com/e/design-miami
    https://xzib.com/news/hypeart
    _____
    ESI
    When I add the php code you advise on other threads and Activate ESI shows X-Qc-Cache:hit, but the x-litespeed header is MISSING.

    Does this mean that the Quic.cloud cdn node is working? Or does the lack of x-litespeed mean that there is NO CACHE?
    _____
    In my quic.cloud analytics on quic.cloud.com
    The static asset ratio to dynamic non cachable assets is 1 to 8.
    And the dynamic non cacheable to cacheable to is 1 to 25
    Does this indicate I should use the ESI feature?

    It just seems like a high amount of data bot being cached. And this is during a time when there is alot of activity on my site due to a specific international event in New york. So id love to get this ironed out for future international events. With hopes Google will continue to prioritize my site in search engines

    The page I need help with: [log in to see the link]

Viewing 12 replies - 16 through 27 (of 27 total)
  • Thread Starter RL

    (@lutzryan)

    The enable esi box was green and has been for about 10 days indicating the on position. The other 2 options on the page are off.

    I just toggled enable ESI off and saved, and then back to on and saved.

    Plugin Support qtwrk

    (@qtwrk)

    if you create a php file put at same dir as wp-config.php , with code 

    <?php
require( './wp-load.php' );
if ( ! apply_filters( 'litespeed_esi_status', false ))
{
echo 'disabled';
}
else {
echo 'enabled';
}

    then access it by browser, what does it return ?

    Thread Starter RL

    (@lutzryan)

    I created a file named “esitest” in public_html and pasted that code

    Not sure what the next step is?

    Plugin Support qtwrk

    (@qtwrk)

    name it like esitest.php , then open it by browser like https://yourdomain.com/esitest.php

    Thread Starter RL

    (@lutzryan)

    it says “enabled”

    Plugin Support qtwrk

    (@qtwrk)

    now this becomes really weird

    please create a ticket by mail to support at litespeedtech.com with reference link to this topic , we will investigate further.

    Thread Starter RL

    (@lutzryan)

    ok.

    I presume I should delete the test files I created?

    Plugin Support qtwrk

    (@qtwrk)

    yes

    Thread Starter RL

    (@lutzryan)

    emailed. thank you.

    I presume you think this can be advantageous for me to deploy this.
    IS there a specific plugin of the 3 you think this will help with (eventon, instagram, rss feed)

    Plugin Support qtwrk

    (@qtwrk)

    I am not sure if there is any advantage or dis-advantage for you , but I am more curious why the ESI was not working

    basically , ESI is useful when you need to make certain part of your page , not to be cached, while keep the page itself it cached , certain section like username , post view counter , mini cart , these are typical usage.

    no , I am not familiar with these things…

    Thread Starter RL

    (@lutzryan)

    My thought process was that it may be helpful to block these shortcode because they often change and the images are hotlinked from a other 3rd party. And I thought it may be idea to keep the balance of the page cached.

    So that it may deliver faster, particularly for mobile users. Thus the reason I thought the ESI can block the elements which I cannot cache from 3rd parties

    Plugin Support qtwrk

    (@qtwrk)

    it depends , but sometimes if too many ESI blocks in there, it could even slow thing down.

Viewing 12 replies - 16 through 27 (of 27 total)
  • The topic ‘ESI, Headers, and Cache ratios per quic.cloud’ is closed to new replies.