My Faaaster site is slow — how do I diagnose it?

Open the site's Monitoring tab: the Latest resource measurements show whether the site is maxing out its memory or CPU, and the graphs show whether the slowness is recent or long-standing. The Performance tab then lets you check the cache.

Contents

• 1. Look at the resources
• 2. Pinpoint when the slowness started
• 3. Check that the cache is working
• 4. Consider more resources
• 5. Bring the site closer to your visitors

1. Look at the resources

Monitoring tab, Latest resource measurements card (Refresh button for a new reading, All metrics for the details):

• Site memory — memory used by your site, relative to the limit allocated to it.
• Site CPU — computing power used by your site, relative to what is allocated to it.
• PHP memory peak — memory consumed by a request, relative to the PHP limit.
• PHP workers — active PHP-FPM processes, relative to the maximum number of workers.
• OPcache memory — memory for precompiled PHP code.

Node load (1 min) and Node CPU pressure (60 s) describe the shared server, not your site alone.

Memory or CPU close to its limit is enough on its own to explain the slowness.

2. Pinpoint when the slowness started

The Monitoring tab also shows the CPU, Memory, Disk, OPcache — free memory and PHP errors graphs over 3 h, 24 h, 7 d or 30 d. A graph that shifts sharply on a specific date points to a change — a newly installed plugin, a traffic spike.

3. Check that the cache is working

Performance tab, Cache section:

• the Server cache avoids calling PHP on every request;
• Cache preloading keeps visitors from waiting while a page is generated;
• the APCu object cache speeds up database queries.

4. Consider more resources

If the site is consistently maxed out, your plan may be undersized: server resources range from ×1 (Dev, Perso) to ×2 (Pro) and ×4 (Business). You can change plans from the Subscription tab.

5. Bring the site closer to your visitors

The CDN Proxy, WAF & Edge caching (Performance tab) serves the site from an edge network. It requires a connected custom domain.

6. Identify the plugin responsible

When resources are healthy and the site is still slow, the code is the cause. WP-CLI is installed on every site, with its profiling extension on sites running PHP 7.4 or later: it points to the culprit instead of leaving you to guess.

Connect via SSH, go to www, then:

wp profile stage --all

This command breaks loading time down by stage — loading the core, plugins, theme, building the page. The heaviest stage tells you where to look.

To drill down to the plugin level:

wp profile hook --all

This is the tool that settles the debate. Rather than deactivating plugins one by one, you see directly which one is taking up the time.

Automatic recommendations

The Server tab, PHP recommendations card, also analyzes your measurements and makes concrete recommendations: raising the number of PHP-FPM workers, increasing the memory limit or the OPcache memory, or moving to a higher plan when the resource can't be adjusted. Each one shows the measured figure and the calculated target; Apply applies the proposed setting.

👉 How do I use WP-CLI? · How do I monitor my site's performance?

Updated on: 10/03/2026