Performance
What a forms plugin costs a page in CSS, JavaScript and requests, and how to keep that cost near zero.
8 articles
-
Core Forms 4.8
Every Core Forms stylesheet and script is served minified, cutting the front-end CSS and JavaScript payload by about 23 percent, with readable sources still in the package. Page-level form detection now covers reusable blocks, widgets and template parts. Released August 29, 2026.
Read → -
Core Forms 4.5
Standalone form pages at /collect/form-slug/, front-end assets loaded per feature instead of all at once, a native no-JavaScript submission path, and explicit analytics and partial-entry controls. Released July 22, 2026.
Read → -
Lean WordPress forms for course creators
Course landing pages live or die on funnel speed. Here's the form stack I use on course sites where every kilobyte counts.
Read → -
Mailchimp WordPress Integration: Subscribe From Your Own Form
Connect a WordPress form to Mailchimp with an API key and an audience ID, including double opt-in. The older Mailchimp for WordPress action still works if you already use it.
Read → -
Stop the forms-plugin stylesheet bloat
Audit form styles by page and feature, disable optional presentation CSS when appropriate, and keep styles needed for working forms.
Read → -
The honest case for AJAX form submission
AJAX submission is the default in every modern forms plugin. But should it be? When it helps, when it hurts, and how to switch modes.
Read → -
Load WordPress forms without unnecessary JavaScript
A breakdown of what's in a typical forms plugin's frontend bundle, and how to cut it without losing anything important.
Read → -
Your contact form doesn't need a builder
Build a simple contact form in HTML, use visual controls when they help, and check what actually loads for visitors.
Read →
Stop reading. Ship a form.
All these notes are from running Core Forms on real client sites.
Use code HALLOWEEN for 35% off either plan. Ends November 2 (IST).