WordPress turns on a lot of things by default. Some of them quietly work against your SEO, spawning thin, near-duplicate pages, or loading scripts you never use. You don't need to disable everything, but a handful of defaults are worth switching off on most sites. Here's the shortlist, grouped by why.
Every time you upload an image, WordPress quietly creates a whole separate page for it, a near-empty page with just the image and its caption. Most site owners never notice, but search engines do, and they're rarely a good look. Here's what attachment pages are, why they usually hurt, and how to switch them off cleanly.
WordPress quietly loads an extra JavaScript file called jQuery Migrate on most sites. It's a compatibility crutch for old code: useful while you need it, dead weight once you don't. Here's how to tell which, and how to remove it safely.
WordPress has its own task scheduler, WP-Cron, and most people never think about it until scheduled posts publish late or a busy site's CPU spikes for no obvious reason. The root cause is the same in both cases: WP-Cron isn't a real cron job. It's faked with page loads, and that assumption breaks at both ends of the traffic scale.
Adding FAQ schema takes five minutes. Choosing how to add it, so it doesn't quietly depend on another plugin's internals, takes one decision. This covers both routes, what each one actually outputs, and how to check it.
You change a few lines in a snippet, press Save, and get "Could not update snippet. Request failed with status code 403". Press Save on the unchanged snippet and it works. Your login is fine. Something between you and WordPress is reading the code itself.
Run the test by itself and it passes, every time. Run the whole suite in parallel and it fails, but only some days, and its failure looks exactly like a real bug. In our case the code was fine. The test was waiting on a clock.
You put a "create an account" link on one site of a WordPress multisite. Visitors who click it land on the main site, which either says "Registration has been disabled" or signs them up there instead.
Every feature arrives with its tests. Nobody times the hook. Then one day git push takes 25 minutes for a one-line change, and the suite is still running one test at a time on a 16-core machine.