• Resolved denise8a

    (@denise8a)


    Hi,

    I recently changed hosting to Hostinger and installed LiteSpeed cache per their recommendation.

    However, since then, my site is failing core web vitals due to LCP issues.

    The main issue is the initial server response time.

    I see this header responses:

    HTTP Header
    
    HTTP/1.1 200 OK
    Connection: Keep-Alive
    Keep-Alive: timeout=5, max=100
    x-powered-by: PHP/8.2.13
    x-dns-prefetch-control: on
    expires: Thu, 19 Nov 1981 08:52:00 GMT
    cache-control: no-store, no-cache, must-revalidate
    pragma: no-cache
    content-type: text/html; charset=UTF-8
    x-ua-compatible: IE=edge
    etag: "9079-1703539481;gz"
    vary: Accept-Encoding
    platform: hostinger
    content-security-policy: upgrade-insecure-requests
    x-qc-cache: hit
    content-encoding: gzip
    content-length: 23056
    date: Mon, 25 Dec 2023 22:28:07 GMT
    server: LiteSpeed
    x-qc-pop: NA-US-EWR-HYBRID-133
    alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"

    Not sure if the plugin is caching as indented.

    I’ve been looking into other topics and by looking into the debug log found out that I have this line: [Ctrl]?forced no cache [reason] DONOTCACHEPAGE const.

    I tried to apply the php code to override it, but it didn’t work.

    Then I created a stating site and deactivated all plugins and still see the same line: DONOTCACHEPAGE const and same headers response.

    Then on this stating site I deactivated litespeed and activated wp-rocket and I do not see the initial server response time issue any more and get this other headers:

    HTTP Header
    HTTP/1.1 200 OK
    Date: Mon, 25 Dec 2023 21:59:05 GMT
    Content-Type: text/html; charset=UTF-8
    Transfer-Encoding: chunked
    Connection: keep-alive
    cache-control: public, max-age=0
    expires: Mon, 25 Dec 2023 21:59:05 GMT
    last-modified: Mon, 25 Dec 2023 19:48:44 GMT
    vary: Accept-Encoding,Accept-Encoding
    platform: hostinger
    content-security-policy: upgrade-insecure-requests
    x-turbo-charged-by: LiteSpeed
    CF-Cache-Status: DYNAMIC
    Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=X%2FsXFp%2BE%2FBLgalV4iRsG0W273oUCux%2FbL0BMD8jlRmCGIpoLBiuTRcrnvENx5XnhWuf9C%2B8CViHu%2ByHpQJmsnVBnL9NzqD1HF1lzl%2BTd3Y1VIMUw%2BrGXWiHnCSUjF%2Ba4WR2%2B7PE%3D"}],"group":"cf-nel","max_age":604800}
    NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
    Server: cloudflare
    CF-RAY: 83b45963fbbc198e-EWR
    Content-Encoding: gzip
    alt-svc: h3=":443"; ma=86400

    Would you mind confirming if litespeed is caching properly mi site?

    Report number: BLRQORBK

    Report date: 12/25/2023 22:33:55

    Thanks!

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support qtwrk

    (@qtwrk)

    the cache is working on the link you provided , you can try refresh or re-test it again , the first access may hit cache miss

    Thread Starter denise8a

    (@denise8a)

    Hi @qtwrk!

    thanks for your quick response!

    I do understand that. If I re-test I usually get slightly different numbers. However every time I test a new page get the initial server response time high.

    Comparing the same hosting, same theme, same CDN, same plugins sets between both cache plugins I see a totally different response.

    I have tested multiple posts and on no occasion have I had a high LCP with wp-rocket, nor do I have to redo the test.

    What I’m trying to understand is if I have the optimum configurations for litespeed on my site to prevent failing core web vitals.

    thanks!

    Plugin Support qtwrk

    (@qtwrk)

    there could be some purge happens in the case you don’t want it to

    please check in Cache -> Purge , uncheck all of these “Auto Purge Rules For Publish/Update” , another thing is the crawler could be helpful as well.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Initial server response time, LCP failed’ is closed to new replies.