Articles in this section

A WordPress website hosted in Plesk is loading slow: Page cache is detected but the server response time is still slow

Plesk for Windows Plesk for Linux kb: technical

Applicable to:

  • Plesk for Linux
  • Plesk for Windows

Symptoms

  • WordPress website works slowly.
  • WordPress Health Check (WordPress Admin Dashboard > Tools > Site Health) shows the following message:

    PLESK_INFO: Page cache is detected but the server response time is still slow

 

  • Some website pages return 404 error.
  • (Linux) The command below, executed in SSH console, reports high Start transfer time:

    # curl -s -w '\nLookup time:\t\t%{time_namelookup}\nConnect time:\t\t%{time_connect}\nSSL handshake time:\t%{time_appconnect}\nPre-Transfer time:\t%{time_pretransfer}\nRedirect time:\t\t%{time_redirect}\nStart transfer time:\t%{time_starttransfer}\n\nTotal time:\t\t%{time_total}\n' -o /dev/null http://example.com

    Lookup time: 0.308568
    Connect time: 0.588054
    SSL handshake time: 0.881948
    Pre-Transfer time: 0.882106
    Redirect time: 0.000000
    Start transfer time: 6.052138

    Total time: 6.430653

Cause

Active WordPress plugins affect the website performance.

Resolution

  1. Log in to Plesk.
  2. Go to Domains > example.com > WordPress tab > Plugins.
  3. Disable all active plugins and then start enabling them one-by-one to find the faulty ones.

    Note: In some cases, even after disabling affecting WordPress plugins, the message about slow response time may still be shown in WordPress Site Health. In this case, try changing the PHP handler from PHP-FPM by Apache to PHP-FPM by nginx. at Domains > example.com > PHP.

Was this article helpful?

Comments

2 comments
Date Votes
  • I have the same problem, but it loads slowly as soon as I install WordPress, I don't think it's related to the plugins.

    0
  • Is there a way to improve WordPress performance? 

    Writing posts or adding products to WooCommerce take forever. Then the site throws 403 errors forcing a page refresh. Not good UX and Im sure end users will just walk away.

    I've hosted in IIS for 20+ years and don't intend on moving *nix for one site (If that's the only solution).

    0

Please sign in to leave a comment.