performance-monitor

Àpèjúwe

A ti ti plugin yìí ní Ẹrẹ́nà 5, 2026, kò sì sí fún ìgbàsílẹ̀. Pípa yìí jẹ́ fún ìgbà díẹ̀, ní ndúródé fún àgbéyẹ̀wò kíkún.

Àwọn àgbéyẹ̀wò

Ẹrẹ́nà 10, 2025 1 ìdáhùn
Performance Monitor is a solid concept, but itÌtumọ̀ Yorùbá: ’s not battle-tested. There’s a major issue with how this plugin handles Google PageSpeed API requests. Every time the plugin’s cron job runs, it triggers two blocking requests to the PageSpeed API (mobile and desktop) without any proper caching or time-based checks. The plugin does store the fetched data, but it doesn’t seem to use the cached values on subsequent cron runs,so it keeps hammering the Google API on every cron. Because WP-Cron is synchronous, my site ended up waiting up to 30+ seconds (sometimes much longer) on each cron activation. On busier sites, this makes a bottleneck, and until this is addressed, I’ve had to disable that functionality. If the devs can implement proper caching logic and also let users control how often PageSpeed data is fetched, it would go a long way toward making Performance Monitor a must-have for me. I truly hope the devs can fix this, otherwise the plugin and the dashboard is great
Ka gbogbo àgbéyẹ̀wò 1

Àwọn Olùkópa & Olùgbéejáde

“Performance Monitor” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí.

Àwọn Olùkópa

Túmọ̀ “Performance Monitor” sí èdè rẹ.

Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?

Ṣàwárí koodu, ṣàyẹ̀wò ibi ìpamọ́ SVN, tàbí ṣe àgbékalẹ̀ sí àkọsílẹ̀ ìdàgbàsókè nípasẹ̀ RSS.