WordPress development: Reddit questions, answered.
Speed fixes, headless vs. classic, page builders vs. custom themes, Core Web Vitals, security, and what it really costs, the honest version, from an agency that's built on WordPress for decades.
What Reddit asks about WordPress
Real questions from r/Wordpress, r/webdev and the wider web, answered by the Atomic Design team without the fluff.
WordPress vs Webflow for a business site, which should I pick?
TL;DRPick WordPress for content-heavy sites, complex functionality, and full ownership; pick Webflow for a fast, design-led marketing site your team can maintain without a developer.
Both are legitimate. WordPress wins when you need deep publishing, custom functionality, e-commerce, membership, or heavy integrations, it's the most flexible and you own everything. Webflow wins for polished, design-driven marketing sites with clean performance and easy in-browser editing, without touching plugins. The trade-offs: WordPress demands more maintenance and can bloat if built carelessly; Webflow is more constrained and a subscription platform. Choose on your actual needs and who'll maintain it, not on which is trendier. For most content-and-conversion business sites, a well-built WordPress or Webflow site both perform; the build quality matters more than the badge.
Is headless WordPress worth it or overkill?
TL;DRHeadless is worth it when you need top-tier performance, a modern front-end stack, or multi-channel content, and overkill for a standard brochure or blog.
Headless keeps WordPress as the content backend while a framework like Next.js renders the front end, unlocking excellent Core Web Vitals, developer-grade flexibility, and content reuse across web and apps. That power comes at a cost: more complexity, higher build and hosting requirements, and you lose the live front-end preview and some plugin conveniences. It's genuinely worth it for high-traffic, performance-critical, or complex sites with a team to maintain it. For a small marketing site or blog, it's usually overkill, a well-optimized classic WordPress build gets you fast enough for far less. Match the architecture to the actual requirement.
Why is my WordPress site so slow and how do I fix it?
TL;DRWordPress is usually slow because of unoptimized images, too many plugins, a heavy theme or page builder, and cheap hosting, all fixable without leaving WordPress.
Slowness rarely comes from WordPress itself; it comes from how it's built and hosted. The usual culprits: large uncompressed images, a bloated theme or page builder loading excess CSS/JS, plugin overload, no caching, and underpowered shared hosting. Fix them in order of impact: compress and properly size images, add a solid caching layer and a CDN, remove or replace heavy plugins, use a lightweight theme, and move to quality managed hosting. Run a speed test to identify the specific offenders before changing anything. A well-optimized WordPress site can absolutely pass Core Web Vitals, most slow ones just haven't been optimized.
Custom theme vs Elementor/Divi, what should I use?
TL;DRUse a page builder like Elementor or Divi for speed and self-editing on a budget; use a custom theme when performance, clean code, and long-term maintainability matter.
Page builders are honestly fine for many small businesses, they let non-developers build and edit pages fast and cheaply. The trade-off is weight: they add CSS and JavaScript that can drag down performance and Core Web Vitals, and they're harder to keep lean over time. A custom theme (or the native block editor with a lightweight theme) gives you clean, fast, purpose-built code and better long-term control, at higher upfront cost. Choose the builder if editing convenience and budget dominate; choose custom if speed, SEO, and scale are priorities. Neither is wrong, it's a trade-off, not a verdict.
Should I move off WordPress, or is it still fine?
TL;DRFor most sites WordPress is still completely fine, don't migrate away from your pain unless a specific need, not frustration, justifies it.
WordPress still powers a huge share of the web because it's flexible, well-supported, and capable when built well. Most "WordPress is bad" experiences trace to a poorly built site, plugin bloat, cheap hosting, a heavy builder, not the platform. Before switching, ask whether a rebuild or optimization on WordPress solves the real problem, because migrations are costly and risk your SEO. Legitimate reasons to move exist: a genuinely better-fit platform for your model, or requirements WordPress serves poorly. But "I'm frustrated" usually means the build needs fixing, not that you need to abandon the platform.
How much should custom WordPress development cost?
TL;DRA genuinely custom WordPress site typically runs $8,000 to $40,000+, depending on design, custom functionality, and integrations, not on the WordPress logo.
Pricing tracks scope, same as any custom build. A custom-themed marketing site with strategy, design, clean code, and SEO foundations usually lands in the low-to-mid five figures; complex functionality, e-commerce, membership, or headless architecture pushes it higher. Templated "custom" sites, a premium theme lightly configured, cost far less and shouldn't be sold as bespoke. Be clear about what "custom" means in your quote: a purpose-built theme and code, or a themed setup. The number reflects the engineering and strategy behind it, and the cheapest quote often means the least custom work.
Are page builders killing my site's performance?
TL;DRThey can be, page builders add extra CSS and JavaScript that often hurt load times and Core Web Vitals, though optimization and lighter builders reduce the damage.
Page builders like Elementor and Divi give you drag-and-drop convenience by injecting significant markup, styles, and scripts, which frequently shows up as slower pages and weaker Core Web Vitals. It's not automatic ruin, you can mitigate with caching, image optimization, disabling unused modules, and choosing lighter-weight builders or the native block editor. But there's a real ceiling: a builder-heavy site is hard to make blazing fast. If performance is genuinely hurting your rankings or conversions and optimization isn't enough, moving critical pages to a custom or block-based build is the durable fix. Measure first, then decide.
Is WordPress still relevant or outdated?
TL;DRWordPress is still very relevant, it powers a large share of the web, keeps evolving with the block editor and headless options, and remains a strong choice when built well.
Reports of WordPress's death are exaggerated. It runs a substantial portion of all websites, has an enormous ecosystem, and has modernized with the block editor, full-site editing, and mature headless capabilities via its REST API. Newer tools like Webflow and Framer are excellent for certain use cases, but they haven't made WordPress obsolete, they've given you more choices. WordPress remains ideal for content-heavy, functionality-rich, ownership-focused sites. The real question is never "is WordPress outdated" but "is WordPress the right fit for this specific project, and will it be built properly?"
What's the real difference between a "custom" and a template WP site?
TL;DRA custom WordPress site is designed and coded around your business; a template site is a pre-made theme configured with your content, and many "custom" quotes are really the latter.
A template WordPress site starts from a purchased theme, so your structure and look are shared with everyone else using it, and you bend your content to fit the theme. A truly custom site is designed for your buyer's path and coded to match, cleaner, faster, more distinctive, and easier to extend. The pricing gap reflects that work. Watch for agencies selling a lightly-skinned theme as "custom." Ask directly: is this a bespoke theme built for us, or a purchased theme configured? Both can look fine; only one is actually custom, and you should pay accordingly.
Headless WP with Next.js, is the complexity worth it?
TL;DRWorth it for high-performance, content-rich, or multi-channel sites with a capable team; not worth it for a simple site that a well-optimized classic build handles fine.
Pairing WordPress with a Next.js front end gives you the best of both: familiar content management for editors and a fast, modern, flexible front end for developers, with strong Core Web Vitals. The complexity is real, two systems to build and maintain, higher hosting demands, more moving parts, and the loss of live front-end preview and some plugins. That complexity pays off when performance is business-critical, when you're serving content to multiple channels, or when you need front-end capabilities WordPress themes can't match. For a standard brochure or blog, it adds cost and overhead you don't need. Decide by requirement and team capacity.
How do I keep WordPress secure without a pile of plugins?
TL;DRSecurity comes mostly from fundamentals, updates, strong access control, quality hosting, and fewer plugins, not from stacking security plugins.
The strongest WordPress security is mostly hygiene, and it doesn't require a plugin pile. Keep core, themes, and plugins updated; use strong passwords with two-factor authentication and limited user roles; run on reputable managed hosting that includes firewalls, malware scanning, and backups; and minimize plugins, since every one is a potential entry point and outdated plugins are the top attack vector. A single well-regarded security plugin can add hardening, but don't stack several, they conflict and slow the site. Fewer, well-maintained components on good hosting beat a wall of security add-ons compensating for a neglected foundation.
How many plugins is too many?
TL;DRThere's no magic number, quality matters more than count, but every plugin adds performance, security, and maintenance cost, so keep only the ones that earn their place.
The "too many plugins" fear is really about quality and overlap, not a hard limit. A site can run fine with twenty lean, well-coded plugins and struggle with five heavy, poorly-built ones. What actually hurts: plugins that load excess scripts, conflict with each other, go unmaintained, or duplicate functionality. Audit periodically, remove anything unused, replace bloated plugins with lighter options or custom code, and prefer plugins that do one thing well and are actively maintained. Judge each plugin on its performance impact and necessity, not the total count. Lean and purposeful beats a big number every time.
WordPress or Shopify for a store that also needs a blog?
TL;DRChoose Shopify if selling is the priority and content is secondary; choose WordPress with WooCommerce if content and flexibility matter as much as the store.
Shopify is purpose-built for selling, the checkout, payments, inventory, and scale are excellent out of the box, and it has a blog, though its content and SEO capabilities are weaker than WordPress. WordPress with WooCommerce flips it: best-in-class content and SEO with a capable, highly flexible store, at the cost of more setup and maintenance. If commerce is the core and you just want basic articles, Shopify is simpler and more reliable. If content marketing drives your acquisition and the store supports it, WordPress plus WooCommerce is the stronger fit. Decide by which side, selling or content, carries your growth.
Who maintains a WordPress site after launch, me or the agency?
TL;DRSomeone has to, WordPress needs ongoing updates, backups, and security, so it's either a care plan with your agency or a clear plan for handling it in-house.
Unlike a static site, WordPress requires continuous upkeep: core, theme, and plugin updates, backups, security monitoring, and occasional fixes when updates conflict. That responsibility is negotiable but not optional. Many agencies offer a maintenance or care plan that handles it for a monthly fee; alternatively you can manage it yourself if you have the time and know-how, or use managed hosting that automates part of it. What you shouldn't do is launch and ignore it, an un-updated WordPress site is a security and performance liability. Settle who owns maintenance before launch, in writing, so nothing falls through the cracks.
Is managed hosting (Kinsta/WP Engine) worth it vs cheap hosting?
TL;DRFor a business site, yes, managed WordPress hosting's speed, security, backups, and support usually pay for themselves versus cheap shared hosting.
Cheap shared hosting is fine for a hobby site, but for a business site the difference is real. Managed hosts like Kinsta and WP Engine deliver faster performance (better for Core Web Vitals and conversions), automatic backups, staging environments, security hardening and malware handling, and expert WordPress support when something breaks. Shared hosting is slower, more crowded, and leaves the technical burden on you. The higher monthly cost buys reliability and time back, which matters when your site earns revenue. If the website is important to your business, treat hosting as infrastructure, not the place to save twenty dollars a month.
How do I migrate off a page builder without breaking the site?
TL;DRRebuild the pages in your new system on a staging site first, preserve URLs and content, then switch over, never migrate live and hope.
Moving off a page builder is delicate because builders wrap content in their own shortcodes and markup that don't carry over cleanly. Do it safely: spin up a staging copy, rebuild the pages in the native block editor or custom theme there, keep the exact same URLs and content so SEO is preserved, and test thoroughly before going live. Watch for content trapped in builder shortcodes that turns to gibberish once the plugin is off, you often re-enter that content. Take a full backup first. Rushed page-builder migrations are a classic way to tank rankings and break layouts, so plan and test before the switch.
My agency built it on WordPress but I can't edit anything, normal?
TL;DRNo, a well-built WordPress site should let you edit content easily, and being locked out is a red flag, not a WordPress limitation.
One of WordPress's core strengths is client-friendly editing, so if you can't update your own content, that's on how it was built, not the platform. Sometimes it's an overcomplicated custom setup with no editing interface; sometimes it's an agency intentionally keeping you dependent so you have to pay for every change. Neither is acceptable for a standard business site. You should get a usable editing experience and training, plus full admin access and ownership. Ask your agency to make content editable and hand over access. If they resist, that tells you something about the relationship, and it may be time to move the site to someone who'll empower you.
WordPress vs custom-coded for performance and SEO?
TL;DRA custom-coded site has a higher performance ceiling, but a well-built WordPress site can absolutely match strong SEO and Core Web Vitals for most business needs.
Pure custom code (or headless) gives you the leanest possible output and the highest performance ceiling, which matters for very high-traffic or performance-critical sites. But the common belief that WordPress is inherently slow or SEO-weak is wrong, that reputation comes from bloated, poorly-built WordPress sites. Built properly, with a lightweight theme, optimized assets, good hosting, and clean structure, WordPress passes Core Web Vitals and ranks excellently, while giving you easy content management custom sites lack. For most businesses, build quality decides performance and SEO far more than platform. Reserve full custom for cases where you genuinely need the extra ceiling.
How do I make a WordPress site pass Core Web Vitals?
TL;DROptimize images, add caching and a CDN, trim plugins and scripts, use a lightweight theme, and host on quality infrastructure, WordPress passes Core Web Vitals when built lean.
Passing Core Web Vitals on WordPress is very achievable and comes down to reducing weight and speeding delivery. The high-impact moves: compress and correctly size images and serve modern formats, implement page caching plus a CDN, eliminate or defer render-blocking CSS and JavaScript, remove unused plugins and heavy page-builder overhead, choose a lightweight theme, and run on fast managed hosting. Lazy-load below-the-fold media and preload critical assets to help LCP, and reserve space for elements to control CLS. Measure with a field-data tool, fix the biggest offenders first, and re-test. Most WordPress sites fail Core Web Vitals from neglect, not because the platform can't pass.
What's the realistic monthly cost of running a WP business site?
TL;DRExpect roughly $50–$500+ a month once you add quality hosting, premium plugins, and maintenance, more if an agency handles upkeep and updates for you.
WordPress itself is free, but running a real business site has ongoing costs. Quality managed hosting typically runs tens to a couple hundred dollars monthly; premium plugins and licenses (forms, SEO, security, backups) add recurring fees; and maintenance, updates, backups, monitoring, small fixes, is either your time or an agency care plan, commonly a few hundred a month. A lean self-managed setup can sit at the low end; a business relying on an agency for hands-off upkeep lands higher. Budget for these from the start, because skipping maintenance to save money usually costs more when something breaks.
Is WooCommerce good enough or should I use Shopify?
TL;DRWooCommerce is good enough, and better on content, SEO, and flexibility, while Shopify is simpler and more hands-off for pure selling.
WooCommerce is a mature, capable e-commerce platform that runs a large share of online stores, and it shines when content, SEO, and customization matter or you want full ownership. The trade-off is that you manage more, hosting, updates, security, and the moving parts of a WordPress store. Shopify handles all that for you with a rock-solid checkout and less maintenance, which is ideal if commerce is your sole focus and you'd rather not touch the plumbing. Neither is "better" universally: pick WooCommerce for flexibility and content-led stores, Shopify for simplicity and pure selling. Match it to how much you want to manage.
Should I let a freelancer build on WP if I'll manage it myself?
TL;DRYes, that can work well, just insist on a clean, well-documented build, full ownership, training, and a maintenance handover so you're not stranded.
A capable freelancer building a WordPress site you'll self-manage is a perfectly reasonable, cost-effective path. Protect yourself by setting the handover terms up front: you get full admin access and ownership of everything, a build that uses a maintainable theme and sensible plugins (not a fragile pile), documentation, and training on how to update content and run backups and updates. Confirm they'll help with a smooth transition rather than disappear at launch. The risk with self-management isn't WordPress, it's inheriting a build only the freelancer understands. Set clear expectations and you get a good site plus the independence you wanted.
Want a fast, secure WordPress site you actually own?
We've built on WordPress for decades, custom themes, headless where it counts, Core Web Vitals passing, no plugin bloat. Let's look at what your site needs.