WP Maximum Execution Time Exceeded vs Fatal Error Notify

Head-to-head on the signals that matter, from the public WordPress.org data.

WP Maximum Execution Time Exceeded

by Johnnie

Health D48

Fatal Error Notify

by Jack Arturo

Health B82

Active-install trajectory

WP Maximum Execution Time Exceeded Fatal Error Notify

Active installs, each indexed to 100 at the start of the window. A line above 100 is growing its install base, below 100 is shrinking.

Metric	WP Maximum Execution Time Exceeded	Fatal Error Notify
Active installs Modeled from the public "N+" band and recent downloads.	20K–30K ✓	6K–7K
Install trend Change in active installs across the charted window.	0%	0%
Overall health	D · 48	B · 82 ✓
Maintenance How recently the plugin was updated.	3/100	85/100 ✓
Rating quality Volume-adjusted review quality.	83/100	87/100 ✓
Support Share of forum threads marked resolved.	70/100	70/100
Rating (adjusted)	4.28★	4.43★ ✓
Reviews	9	18 ✓
Ranking optimization How well the listing is tuned to rank on wp.org.	45/100	93/100 ✓
Removal risk Maintenance signals that precede a wp.org closure. Not an official status.	Elevated	Low ✓
Last updated	5.6y ago	7mo ago ✓
Downloads · 30d	1.2K ✓	800
Category	Uncategorized	Uncategorized

✓ marks the stronger plugin on each row. Rows where they're level show no marker.

Release activity

WP Maximum Execution Time Exceeded Fatal Error Notify

7-day average daily downloads. Downloads spike for about a week after each release as the install base re-downloads, so read this as release cadence, not growth.