• Resolved jetxpert

    (@jetxpert)


    Good Day!

    Before we activate Cloudflare (Full Page Caching) using your plugin, can you kindly answer the following questions?

    (1) How does Cloudflare (Full Page Caching) treat dynamic content? (e.g., website pages using Gravity Forms, User Logins, Booking Forms, WooCommerce payments pages, Calendars, etc.). Is the entire page still cached (regardless of each individual plugin’s cache/no-cache settings)?

    (2) If we’re using SGO’s Dynamic Cache and MemCached successfully (as well as Cloudflare caching via Page Rules), do you still recommend activating Cloudflare (Full Page Caching)? If so, why? (beside providing relief to your servers)

    (3) How much faster is Cloudflare (Full Page Caching) vs. Cloudflare (Page Rules)? Data and/or percentages would be appreciated.

    (4) When can we expect SiteGround to update its article about Cloudflare (Full Page Caching) to include some (or all) of the information requested in this forum topic?

    Note: An updated article or expanding your KB on this topic should help cut-down the number of inquiries you’re receiving on this.

    Thank you!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    I will not follow your numeration order but I will address everything ??

    There’s full page caching on SiteGround and full page caching on CloudFlare. Both work in a very similar way using headers. It doesn’t matter if you use our implementation (workers) or Page Rules – it is just the way this cache is handled but it is the same full page caching.

    If you get a CF cached hit it will have exactly the same loading speed no matter if the page was cached because of a page rule or a worker.

    Since both work with headers, our exclude systems work for CF too including default excludes and all the logic behind SGO.

    Now…memcached handles dynamic requests only, it is an object caching so you need the PHP to query the MySQL in order to get improvements. This means it will start working for logged users, excluded pages, etc.

    IF YOU NEED to use a CDN in general, I recommend using full page caching. That’s because if you are only caching the static assets a request goes:

    User -> CF Edge -> SG Server (cached or not) -> CF Edge -> User

    while if you have full page caching it is:

    User -> CF Edge -> User

    which results in much better TTFB. Actually, if your SG is hosted in Europe for example, and your visitors are from Europe, if you enable CF without full page caching, all those people in Europe will load your site slower than without CF ??

    Thread Starter jetxpert

    (@jetxpert)

    @hristo-sg,

    Brilliant. Great reply. It answered our concerns and questions.

    We’ll switch to Full Page Caching this week. If no improvements noticed (from our Global customers), I expect you to buy me a Kamenitza (or two).

    Also, to help you and your customers a bit on this topic, we had expressed concern over losing our Page Rules when we switch to Full Page Caching. Well, we have mitigated our concern (i.e., restoring our Page Rules) by putting together a small procedure (provided below) that will allow customers to print, save, or email their Page Rules prior to switching to Full Page Caching.

    Again, thank you!

    ——————————

    How to Print, Save, or Email Your Cloudflare Page Rules:

    (1) Install the browser extension or add-on, “Print Friendly & PDF”.
    (2) Proceed to your CF Dashboard (Rules).
    (3) Click anywhere inside your Page Rules window.
    (4) Click on the “Print Friendly & PDF” icon (top of browser, a pop-up will appear).
    (5) Click on “Print”, “PDF”, or “Email” to suit your needs.

    Notes:

    (a) The extension or add-on is available for all major browsers.
    (b) Above procedure will grab all Page Rules at once.

    Thread Starter jetxpert

    (@jetxpert)

    Hi @hristo-sg,

    OK, so we finally switched to Cloudflare’s Full Page Caching.

    So far, everything is running great.

    Your patience and insistence that we get rid of WP Rocket and switch to Cloudflare’s Full Page Caching (Workers) is paying off.

    Old dogs are hard to train, but they’re still trainable ??

    Thank you!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Help Appreciated | Cloudflare (Full Page Caching)’ is closed to new replies.