# Noonwp > Editorial content from Noonwp (noonwp.com). Articles, comparisons, reviews, landings and tools — multi-locale, written for human readers and machine-readable for AI agents. ## Articles ### How to Make a Landing Page in WordPress Without a Builder URL: https://noonwp.com/journal/how-to-make-a-landing-page > How to make a landing page in WordPress with the native block editor: one goal, a stripped-down template, five sections, a short form and a speed budget. Here is how to make a landing page in WordPress: build one page with one goal, strip it of the site header and footer, and assemble it from block patterns inside a block theme. A clean first version takes an afternoon. The part that decides whether it converts is not the tool you build it with, but what you leave off the page. This folio covers the build in the order a practitioner would do it: the goal, the template, the sections, the form, the speed budget, and the checks before launch. ## What makes a landing page different from any other page? A landing page has a single job. A visitor arrives from an ad, an email or a search result, and the page asks for exactly one action: sign up, book a call, download a file, buy. Everything else is a distraction. That includes your main menu, your sidebar, your blog feed and the footer with twenty links. On a normal page those help people explore. On a landing page they are exits. The benchmark worth knowing comes from Unbounce, whose [conversion benchmark report](https://unbounce.com/conversion-benchmark-report/) puts the median landing page conversion rate at 6.6% across industries. Treat it as a ceiling for sanity, not a promise. A page below 2% usually has a problem with the offer, the speed or the form, not with the colour of the button. Write the goal in one sentence before you open the editor. "Visitors from the March newsletter book a 20 minute audit call." If you cannot write that sentence, you are not ready to build. ## Which tool should you build it with? You have four honest options, and each fits a different kind of project. The native block editor with a block theme is the lightest. You get clean markup, no extra dependency, and patterns you can reuse on the next client site. It asks more of you in layout decisions. If you are weighing it against a visual builder, our [Gutenberg versus Elementor comparison](/journal/gutenberg-vs-elementor) puts numbers on the trade. A page builder gives you more visual control and a template library, at the cost of heavier output and a plugin you now depend on. Divi is the long-standing example, and it suits an agency that builds many pages and wants one familiar toolkit. An AI site generator scaffolds a whole page from a prompt. 10Web does this inside WordPress, and the draft it produces is a fair starting point. Expect to edit the copy and tidy the structure afterwards. We cover where that holds up in [AI for WordPress](/journal/ai-for-wordpress). A hosted landing page tool sits outside WordPress. Webflow is one such option, with strong visual control and its own hosting. Worth the cost if the page lives apart from your WordPress site. Skip it if the page must share your theme, your analytics and your domain structure. The rest of this guide uses the native editor, because it is the option that teaches you the most and costs the least. The steps translate to any builder. ## How do you set up the page and strip it down? Create the page under Pages, Add New. Give it a plain title that matches the offer, and set a short slug. A slug like /audit beats /landing-page-march-v2 every time. Now deal with the template. A block theme lets you assign a template per page, and a landing page wants one with no header, no footer and no title block. Many block themes ship a "Blank" or "Page without title" template. If yours does not, open the Site Editor, go to Templates, add a custom template, and build it from a single Post Content block. That one template is the most useful thing you will make in this project. Name it "Landing", and reuse it for every campaign page on the site. ![Pencil wireframe of a single-column page layout sketched in a notebook](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-10/64e908-wireframe.webp) Check the layout width in theme.json. Landing pages read best in a narrow column for text, with wide blocks reserved for the hero and the proof section. If your theme sets a content width and a wide width, use both deliberately: copy in the narrow column, images and columns in the wide one. Marginalia: the template assignment described here works on WordPress 6.5 and newer. Older block themes expose it in a different menu. ## What sections does the page actually need? Fewer than most templates suggest. A page that asks for one action needs a short sequence, and each section answers one question the visitor has. Build these in order, as patterns you can save and reuse: - A hero with the promise, one supporting line and the button. - Proof close to the top: a customer quote, a number, or recognisable client work. - The offer in three short points, written as outcomes. - The form or the second button. - A short answer block for the two objections you hear most. Use a Cover or Group block for the hero, with a Heading, one Paragraph and a Buttons block. Keep the headline to a promise a stranger can read in three seconds. Name the thing, name the result. Avoid cleverness that needs a second reading. Write the button label as the action itself: "Book the audit", "Download the checklist". Generic labels such as "Submit" cost you the context the headline built. If you work with an AI drafting tool, use it for the first version of the copy and for variants of the headline, then read every line yourself. It invents proof it does not have. Never let a generated testimonial or statistic reach the page unchecked, because a fabricated quote on a landing page is the fastest way to lose trust. Once a section works, select it and choose Create pattern in the block menu. Next campaign, you assemble the page from your own patterns in ten minutes instead of rebuilding it. ## How should the form be built? WordPress core has no form block, so this is the one place you need a plugin. Any maintained form plugin will do. What matters more is the shape of the form. Ask only for what you need to follow up. For a newsletter or a download, an email address is enough. For a call booking, add a name and one qualifying question at most. Every extra field costs you completions, and you can ask the rest after the first contact. Place the form where the decision is made. On a short page, that is right under the offer. On a longer page, repeat the button after the proof section and link it back to the same form. Then set up the part people forget: the thank-you state. Redirect to a short confirmation page, or show an inline message, that says what happens next and when. Add your analytics event there, so the conversion is counted at the confirmation and not at the click. Finally, test the form from a phone, with a real address, and confirm the email arrives. A landing page with a broken form is worse than no page, because it spends your ad budget and returns nothing. ## How fast does the page need to be? Faster than the rest of your site. Visitors from ads have no loyalty to you yet, and a slow first screen ends the visit before the headline is read. Google's guidance on [Largest Contentful Paint](https://web.dev/articles/lcp) treats 2.5 seconds or less as good. On a landing page, the largest element is usually the hero image or the headline block, so those are where to look first. ![Brass stopwatch resting on a stack of paper sheets, a metaphor for page load speed](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-10/80ee8a-speed.webp) A short checklist, in order of impact: - Compress the hero image and serve it in WebP, sized to the width it is shown at. - Do not lazy-load the first image on the page. Core avoids this for the image it expects above the fold, but confirm it in the rendered HTML, especially if a Cover block is involved. - Self-host one or two fonts and cut unused weights. A variable font replaces several files with one. - Load scripts only where needed. A form plugin that loads on every page should be limited to the page that holds the form. - Avoid sliders, auto-playing video and heavy animation above the fold. Measure before and after with PageSpeed Insights on the live URL, on mobile settings. Do it with caching enabled, as a visitor would see it. For the wider set of fixes, [how to speed up a WordPress site](/journal/how-to-speed-up-wordpress-site) ranks them by impact, and the [WordPress performance field audit](/journal/wordpress-performance-optimization-a-2026-field-audit) shows how to read the numbers. ## Does the page work on a phone and in your reader's language? Most ad and email traffic arrives on a phone, so design the narrow screen first and check the wide one second. Open the page on an actual device. Look at the button size, the spacing between tap targets, and whether the form opens the right keyboard for each field. Read the page in a mirrored layout if any of your audience reads right to left. Arabic and Hebrew readers expect the hero, the button and the form to flow from the right. Block themes with proper RTL stylesheets handle most of it, but test your spacing, your icon placement and your quote styling in the mirrored view. ![Calligraphy reed pen and ink pot on a wooden desk, evoking right-to-left page design](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-10/b5c348-rtl.webp) Choose a typeface with real Arabic or Hebrew glyphs rather than a fallback. A page that looks polished in English and ragged in Arabic tells a whole audience the offer was not written for them. If you run two languages, build two separate landing pages with their own copy. Do not translate the headline word for word. A promise that works in one language often needs a different shape in the other. ## What should you check before you publish? Run through this list on the live page, logged out, in a private window: - The page has one goal and one primary button, repeated at most twice. - The header, footer and sidebar are gone. - The title, meta description and social image are set, and match the ad that sends people here. - The form submits, the thank-you state appears, and the conversion is tracked. - The page passes a mobile speed test and reads cleanly at 360 pixels wide. - Alt text is on every image, and the contrast of the button text is readable. Then decide whether the page should be indexed. A page built for a paid campaign can carry a noindex tag so it does not compete with your main pages. A page meant to rank belongs in the sitemap and deserves a proper search title. After launch, change one thing at a time. Rewrite the headline first, since it carries the most weight, and give each version enough visitors before you judge it. Two weeks of steady traffic tells you more than two days of excitement. ## What would we actually do? Start with the single-goal sentence, the Landing template and five sections. Skip the page builder until the native editor stops being enough. Spend your effort on the offer, the headline and the speed, because those move the number. Open the Site Editor, name the template Landing, and build the hero before anything else. ## FAQ ### Can I make a landing page in WordPress without a plugin? Yes, for everything except the form. A block theme, a blank page template and the native block editor are enough to build the page. WordPress core has no form block, so you need a form plugin to capture leads. ### What is the difference between a landing page and a homepage? A homepage helps visitors explore your site and offers many paths. A landing page has one goal and one main action, so it removes the menu, footer and other links that would pull people away from that action. ### How long does it take to make a landing page in WordPress? A focused first version takes about an afternoon once you have a landing template: a few hours for copy and sections, then time for the form, speed checks and mobile testing. Reusing saved patterns cuts later pages to under an hour. ### How many sections should a landing page have? Usually five: a hero with the promise and button, early proof, the offer in three short points, the form or second button, and a short block answering the top objections. Add more only if a real question needs answering. ### Do I need a page builder like Elementor or Divi? No. The native block editor handles most landing pages. A builder helps when you want a large template library or finer visual control, at the cost of heavier markup and a plugin dependency. ### What is a good conversion rate for a landing page? Unbounce reports a median of about 6.6% across industries. Results vary widely by offer and traffic source, so use it as a sanity check and compare your own page against your previous version. --- ### How to Start a Blog on WordPress: A 2026 Field Guide URL: https://noonwp.com/journal/how-to-start-a-blog-on-wordpress > A practical walkthrough of how to start a blog on WordPress: hosting, install, block theme, essential pages, plugins and a first post that earns readers. Here is how to start a blog on WordPress. You need four things: a domain, a host that runs WordPress.org, a block theme, and a first post that says who the blog is for. On a decent host the install takes about ten minutes. The decisions around it take longer, and they are the ones that decide whether the blog is still pleasant to run in two years. This folio walks through the setup in the order a practitioner would do it, with the choices that matter and the ones that do not. ## Should you pick WordPress.com or WordPress.org first? This is the first fork, and most guides rush past it. WordPress.com is a hosted service: you sign up, pick a plan, and the platform runs the software for you. WordPress.org is the open-source software you install on a host you choose. Same editor, very different ownership. Pick WordPress.com if you want to publish this week and never touch a server. Their own [five-step blog setup guide](https://wordpress.com/support/five-step-blog-setup/) shows how short that path is. Pick WordPress.org if you want full control of plugins, themes, backups and the database. For a client blog, a bilingual site or anything you may monetise, self-hosted is the safer default, because migrating later is possible but never free. Skip the "free forever" framing on either side. A free subdomain is fine for a diary and a poor base for a brand. ## What do you need to buy, and how do you install WordPress? Two line items, both annual: a domain name and hosting. Everything else is optional until you have readers. For the domain, choose something short, typeable and tied to the topic. Avoid hyphens and avoid trendy extensions you cannot say out loud. Register it in your own account, not through a freelancer's, so that you can always move it. For hosting, look for one-click WordPress install, free SSL, daily backups and a PHP version that is still supported. Managed WordPress hosting costs more than shared hosting, but it removes a class of problems you do not want on day one. A realistic first-year budget for a lean blog sits between roughly $60 and $250, depending on whether you take managed hosting. ![Three tools of a new blog: a key, a domain tag and a small server box](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-10/883581-hosting.webp) Most hosts expose an installer in their dashboard. Choose WordPress, enter your domain, set an admin email you actually read, and use a long unique password. Do not keep the username "admin". Then do four small things before anything else: - Set the site title and tagline in Settings, General. - Set permalinks to "Post name" so URLs read like words, not numbers. - Tick the box that discourages search engines only if the site is still private. Untick it the day you launch. - Delete the sample post, sample page and any unused plugins. If you would rather skip the manual setup, an AI site generator can scaffold a full WordPress site from a prompt. 10Web is one example, and our [10Web review](/journal/10web-review) covers where it holds up and where the output needs cleanup. A short note on analytics: install one privacy-friendly tool or Google Search Console from the start. Without baseline numbers you cannot tell whether a change helped or hurt, and you will want that history by month three. Keep dashboards simple; two or three metrics are enough at this stage: visits from search, top pages, and time on page. Marginalia: this works on any host running WordPress 6.5 or newer. Older installs miss several editor features used below. ## Which theme should a new blog start with? Start with a block theme. Since WordPress 5.9 introduced Full Site Editing, themes can define headers, footers and templates as blocks you edit visually in the Site Editor. The default theme that ships with WordPress, [Twenty Twenty-Five](https://wordpress.org/themes/twentytwentyfive/), is a clean block theme and a sensible starting point. It is lightweight, accessible and ships with a handful of well-built patterns. Resist the urge to buy a premium theme in the first week. Most of what you will pay for is demo content you will delete. Spend that time on your own typography and layout instead: one body font, one heading font, a restrained palette. A page builder is a different decision. Divi, Elementor and Bricks give you more visual control, at the cost of heavier markup and a dependency on the builder. For a blog whose job is text, the native editor is usually enough. If you are weighing it up, [Gutenberg versus Elementor](/journal/gutenberg-vs-elementor) puts numbers on the trade. ![Page layout proofs and a ruler on a wooden table, evoking choosing a block theme](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-10/881218-theme.webp) Worth the splurge if you build many sites for clients and want one familiar visual toolkit. Skip it if you are launching a single personal blog. ## What plugins does a new blog really need? Fewer than every listicle says. Each plugin is code you must update, trust and eventually debug. A sensible starter set has five roles, not five brand names: an SEO plugin for titles, meta descriptions and sitemaps; a backup tool if your host does not include one; a caching or performance layer; a security or login protection layer; and a forms plugin only if you need contact forms. Install them one at a time and check the site after each. If a page slows down or breaks, you know which one did it. Core Web Vitals matter for a blog because most of your traffic will arrive on mobile from search, so measure before and after, not by feel. Our [WordPress performance field audit](/journal/wordpress-performance-optimization-a-2026-field-audit) shows how to read the numbers. Plugins that duplicate what the block editor already does, such as basic galleries, buttons and columns, are the first to cut. Before the first post, create the pages readers and search engines look for: - An About page that says who writes here and what you cover. - A Contact page with a real way to reach you. - A Privacy Policy page, required in most jurisdictions if you collect any data, including through comments and analytics. Then build navigation in the Site Editor. Keep the header menu to five items or fewer. A blog with ten top-level links is a blog nobody has decided anything about. For categories, start with three to five that map to the topics you will genuinely write about. You can add more later. You cannot easily merge thirty thin categories without breaking URLs. ## Which pages come first, and what goes in the first post? Not "Hello world", and not a post about starting a blog. Write the article you wish existed on your topic, and write it for one specific reader. Open with the answer or the observation, not a preamble. Use short paragraphs, descriptive subheadings and one image per few hundred words. Add a clear title, a one-sentence excerpt and a featured image. Set the category, then publish. In the editor, type a slash on an empty line to insert any block. Headings, lists, quotes, images and embeds all live there. Learn that one shortcut and you have learned half the editor. The Site Editor and the post editor share the same logic, so time spent in one pays off in the other. The official [Site Editor documentation](https://wordpress.org/documentation/article/site-editor/) is worth a skim once your first post is live. ![Letterpress printing a first sheet, a metaphor for publishing the first post](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-10/da81dc-publish.webp) ## How much does it cost, and what does it return? Be honest with yourself about the money. The software is free. The hosting, the domain and any premium tools are not, and a blog rarely pays for itself in the first six months. If you plan to sell something, WooCommerce turns the same WordPress install into a store. It is powerful, and it also adds hosting, security and maintenance weight, so add it when you have a product, not before. If your priority is writing and a newsletter rather than customisation, Ghost is a publishing platform built around exactly that. It is not WordPress, and for a pure writing blog it is a fair alternative to know about. For a deeper look at the budget side, see [how much a website costs in 2026](/journal/how-much-does-a-website-cost). ## What changes if your blog is bilingual or right to left? Most beginner guides assume one language and left-to-right text. If your readers use Arabic or Hebrew, plan for it at the start, because retrofitting direction later is where sites get brittle. Choose a block theme that ships with RTL stylesheets, set the site language in Settings, General, and test your header, quotes and lists in the mirrored layout before you publish. Pick a typeface that has proper Arabic or Hebrew glyphs rather than relying on a fallback. If you want two languages from day one, decide between a multilingual plugin and separate sites per language before writing content. Switching strategies after fifty posts is painful. ## What should you do in the first 30 days? Publish four to six posts on one tight theme, so that search engines and readers can tell what the blog is about. Submit your sitemap to Google Search Console. Add one email signup block, and one only. Check your site on a phone every week. Update WordPress, the theme and plugins on a schedule, and confirm that your backups can actually be restored. Do not chase tools you do not yet need. A blog with eight good posts and a clean setup beats one with forty plugins and no readers. Open the editor, write the post you owe your first reader, and press Publish. ## FAQ ### Is it free to start a blog on WordPress? The WordPress software is free, and WordPress.com offers a free plan on a subdomain. A blog with your own domain and hosting typically costs roughly $60 to $250 in the first year, depending on the host. ### Should I use WordPress.com or WordPress.org for a blog? Use WordPress.com if you want a hosted setup with no server work. Use WordPress.org if you want full control of plugins, themes and backups, which is the safer base for a client site or a monetised blog. ### How long does it take to start a WordPress blog? The install itself takes about ten minutes on a host with a one-click installer. Choosing a theme, creating essential pages and writing a first post usually takes a few more hours. ### Which theme is best for a new WordPress blog? A lightweight block theme such as Twenty Twenty-Five is a sound starting point. It supports the Site Editor, ships with useful patterns and avoids the heavy demo content of many premium themes. ### How many plugins does a new WordPress blog need? Usually five roles at most: SEO, backups, performance, security and optionally forms. Install them one at a time and check the site after each, so you know which plugin causes a problem. ### Can I start a WordPress blog in Arabic or Hebrew? Yes. Choose a block theme with RTL stylesheets, set the site language in Settings, General, and test your layout in mirrored mode before publishing. Use a typeface with proper Arabic or Hebrew glyphs. --- ### How to Speed Up WordPress Site: 8 Fixes Ranked by Impact URL: https://noonwp.com/journal/how-to-speed-up-wordpress-site > A practical order of work for a slow WordPress site: baseline first, then hosting and caching, images, render-blocking code, plugins, CDN and speculative loading. Here is how to speed up WordPress site performance in practice: measure first, then fix in order of payoff: server response time and page caching, then the heavy hero image, then render-blocking CSS and JavaScript, then the database and plugin load. Most slow sites are held back by two or three of those, not all of them. Run PageSpeed Insights on your slowest template, note the Largest Contentful Paint element, and work down this list until the number turns green. ## Start with a baseline, or you will optimise the wrong thing Speed work without a baseline is superstition. Before touching a plugin, record three numbers on your slowest real template (usually a post with a large hero image, or a WooCommerce product page): Largest Contentful Paint, Interaction to Next Paint and Time to First Byte. Test on mobile settings, because that is where the gap between "fast on my machine" and "fast for the client's customers" shows up. The targets are published, not folklore. [Google's web.dev guidance on LCP](https://web.dev/articles/lcp) treats 2.5 seconds or less as good at the 75th percentile of real visits. INP should stay under 200 milliseconds and layout shift under 0.1. Write those on a sticky note next to your screen. Lab tools such as Lighthouse give you a repeatable bench. Field data from the Chrome User Experience Report, surfaced at the top of PageSpeed Insights, tells you what visitors actually got. When the two disagree, trust the field data and use the lab run to find the cause. Marginalia: this order of work holds for WordPress 6.5 and later. Older installs have more to fix before any of it matters. ## Fix the server first: hosting, PHP and Time to First Byte Every front-end trick sits on top of the first response. If the HTML takes 1.5 seconds to arrive, no image compression rescues your LCP. Time to First Byte is the number that exposes a weak host, an outdated PHP branch or a page that is rebuilt from scratch on every request. Check three things in this order. Run a currently supported PHP branch, since each release is measurably cheaper per request than the last. Confirm that the host offers a persistent object cache (Redis or Memcached), because it removes repeated database reads for options, menus and queries. And look at the plan itself: a shared server with a hundred neighbours will throttle you at exactly the moment traffic spikes. If you manage many client sites, this is where managed hosting earns its fee. A platform that bundles hosting, caching and a performance target removes a whole category of guesswork. [10Web](https://10web.io) is one example that hosts WordPress on Google Cloud and aims for a 90+ PageSpeed score out of the box, which is a reasonable default for a small agency without a dedicated ops person. Skip the temptation to buy a bigger plan before you have enabled caching. Upgrading hardware to serve uncached pages is paying more to do the same wasteful work faster. ## Turn on full-page caching and check that it actually hits WordPress builds each page with PHP and MySQL every time someone asks for it. A page cache saves the finished HTML and serves that file instead. For a mostly-read site such as a blog, a brochure site or a portfolio, this single change often moves TTFB from seconds to tens of milliseconds. Pick one page-caching layer and only one. Stacking a host-level cache, a caching plugin and a CDN cache without knowing which one serves the request is how you end up debugging stale content for a full afternoon. Ask your host what it already provides before installing anything. Then verify the cache is hitting. Open the browser's network panel, reload a public page twice, and read the response headers. Most caches announce a hit or a miss, and many add an age value. If you only ever see misses, your cache is bypassed by a cookie, a query string or a logged-in state, and the "optimisation" is decoration. Stores need extra care. Cart, checkout and account pages must never be cached, and WooCommerce sites usually depend on a cache plugin that knows those exclusions. Get the exclusions wrong and customers see each other's baskets, which is a worse problem than a slow page. ## Shrink the hero image, the usual LCP culprit On most slow WordPress pages, the LCP element is an image: a hero, a featured image or a full-width banner. That makes image weight the most common single cause of a failing score. A 4000-pixel wide JPEG exported straight from a camera, displayed in a 1200-pixel column, ships several times more bytes than the layout can use. ![Digital scale weighing a stack of paper against a single printed photograph, a metaphor for image weight](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-09/50469b-img1.webp) Work through the image pipeline in this order: - Resize to the largest size the layout really displays, not the size the designer exported. - Serve WebP or AVIF, both of which WordPress core has handled for several releases. - Let core generate the responsive `srcset` variants instead of hard-coding one large file. - Do not lazy-load the hero. Core has skipped lazy loading on the first content image and added `fetchpriority="high"` to it since WordPress 6.3, so check that your theme or plugin has not undone that. - Give every image explicit width and height so the browser reserves space and layout shift stays near zero. Below the fold, lazy loading is correct and free. Above the fold, it is a self-inflicted delay, and it is the mistake that shows up most often after someone installs a "lazy load everything" plugin. For e-commerce, the weight often comes from product photography. Producing consistent, right-sized visuals at the source is cheaper than compressing fifty oversized files afterwards, and an AI product-photography platform such as Klayn turns one product photo into a set of scenes, so you can plan the dimensions before anything reaches the media library. ## Cut render-blocking CSS and JavaScript at the source Once the server and the hero are sorted, the next delay is what the browser must download and run before it paints. Every stylesheet in the head blocks rendering. Every synchronous script blocks parsing. Page builders and multipurpose themes are the usual offenders, because they ship styles and scripts for every feature whether the page uses it or not. Block themes have a structural advantage here. Core loads the styles for a block only when that block appears on the page, so a plain post does not pay for the Query Loop or the Gallery. That is one reason a lean Full Site Editing theme starts ahead of a legacy theme with a bundled slider and a bundled icon font. Classic page builders can close the gap, but only if you disable the modules you do not use. ![Server rack cables with green status lights in a clean data center aisle](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-09/098a03-img2.webp) Divi is a fair test case. Divi 5 was rebuilt on a more modern architecture and ships hundreds of modules, which is exactly why its performance settings, such as dynamic CSS and critical CSS, deserve a careful look on every site you deliver. Practical steps, in order of risk: - Defer non-critical JavaScript and load third-party scripts (chat widgets, analytics, tag managers) after interaction where you can. - Inline the critical CSS for above-the-fold content and load the rest asynchronously, if your cache tool supports it. - Self-host fonts, subset them, and use `font-display: swap` so text is visible while the font loads. - Remove or replace any plugin that loads a large script on every page for a feature used on one. - Test after each change. Aggressive JavaScript deferral is the number one cause of a broken menu or a dead checkout button. ## Prune the plugin stack and let the database breathe Plugin count is a poor metric. What matters is what each plugin loads on the front end and what it does on every request. One badly written plugin with a heavy query can cost more than thirty well-behaved ones. Use Query Monitor on a staging copy to see slow queries, the plugin that triggered them, and the scripts each one enqueues. Then look at the options table. Plugins that were removed years ago often leave rows behind marked to autoload, which means WordPress reads them into memory on every request. Site Health starts flagging autoloaded options once they reach roughly 800 KB. If you see that warning, audit the largest rows and clean up leftovers from plugins you no longer run. Post revisions, expired transients and orphaned metadata add weight over time, but treat this as maintenance rather than a headline fix. Back up first, run the cleanup on staging, and measure again. The gain is often modest on a small site and significant on a store with years of orders and sessions. ![Craftsman workbench with a plumb line, calipers and a brass hourglass laid out in order](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-09/a80ad0-img3.webp) ## Use a CDN and speculative loading for the last stretch A content delivery network serves static files, and often the cached HTML too, from a location close to the visitor. For an audience spread across regions, such as an Arabic-language site read from the Gulf and North Africa while the origin server sits in Europe, the latency saved is not cosmetic. Distance is a cost, and a CDN is the cheapest way to shorten it. WordPress 6.8 added something that costs nothing: speculative loading. It uses the Speculation Rules API to prefetch a page as the visitor starts to click, so the next navigation feels almost instant. The core team reports that sites using the earlier plugin version improved their LCP pass rate by about 1.9% at the median, as described in the [WordPress 6.8 speculative loading developer note](https://make.wordpress.org/core/2025/03/06/speculative-loading-in-6-8/). That is small per site, and it comes with no configuration. Core enables it for logged-out visitors on sites with pretty permalinks. If a plugin uses action URLs that change state on a plain GET request, exclude those paths with the `wp_speculation_rules_href_exclude_paths` filter before you make the setting more eager. Stay on the default until you have checked your carts and your analytics. ## When to stop tuning, and which fix to run first There is a point where more WordPress tuning costs more than it returns. If a small shop spends every month fighting caching exclusions, plugin conflicts and hosting upgrades, the honest question is whether the stack fits the business. A hosted platform such as WiziShop trades some flexibility for a store whose speed is somebody else's job, and it is worth pricing against the hours you bill for maintenance. For content sites, agencies and RTL projects, WordPress remains the right tool, and everything above stays worth doing. The point is to know which side of the line each client sits on. Run the baseline on your slowest template today. If TTFB is above 800 milliseconds, start with hosting, PHP and caching. If TTFB is healthy but LCP fails, open the waterfall and find the hero image. If both pass and interaction is sluggish, look at JavaScript and the plugin stack. Which of those three does your worst page fail? ## FAQ ### What is the fastest way to speed up a WordPress site? Enable full-page caching and check that it actually serves hits. For mostly-read sites this often cuts Time to First Byte from seconds to tens of milliseconds, and it costs less effort than any other single change. ### Why is my WordPress site slow even with a caching plugin? The cache is probably being bypassed by cookies, query strings or logged-in state, or the real bottleneck is the hero image or render-blocking scripts. Read the response headers on a public page to confirm whether you get hits or misses. ### Do too many plugins slow down WordPress? Count matters less than behaviour. One plugin that runs heavy queries or loads a large script on every page can cost more than thirty light ones. Use Query Monitor on a staging copy to find the expensive ones. ### What is a good Largest Contentful Paint for WordPress? Google's web.dev guidance treats 2.5 seconds or less as good, measured at the 75th percentile of real visits. Aim for Interaction to Next Paint under 200 milliseconds and layout shift under 0.1 as well. ### Should I lazy-load the hero image? No. Lazy loading is right for images below the fold, but the first content image is usually the LCP element and should load early. WordPress core has skipped lazy loading on it and added fetchpriority high since version 6.3. ### Does WordPress 6.8 make sites faster by default? Slightly. Speculative loading prefetches pages as a visitor starts to click, and the core team reported about a 1.9% median improvement in LCP pass rate for sites using the earlier plugin. It is on by default for logged-out visitors with pretty permalinks. --- ### Gutenberg vs Elementor: Which Builder to Use in 2026 URL: https://noonwp.com/journal/gutenberg-vs-elementor > Gutenberg vs Elementor: an honest 2026 field comparison covering performance, design flexibility, cost, and the freelance workflow that holds up under real client conditions. Gutenberg vs Elementor: in 2026, the gap has narrowed but not closed. Gutenberg is the native WordPress editor, ships with every installation, and passes Core Web Vitals on 41.5% of tested sites. Elementor sits on over 10 million WordPress installs and ships a design toolkit core WordPress has not fully matched. The right choice depends on what you ship, for whom, and how much page weight you accept. ## What Gutenberg and Elementor actually are Gutenberg is the block editor that WordPress core has shipped as default since version 5.0 (2018). In 2026, with WordPress 7.0, it includes Full Site Editing, a revised Site Editor, and per-block CSS that developers can apply without writing a stylesheet. It is not a plugin you install: it is the editor your installation runs. Elementor is a third-party page builder plugin with over 10 million active installations on WordPress.org. The free version handles most layout tasks. Elementor Pro ($49/year at entry level) adds theme building, a popup builder, a form widget, and WooCommerce controls. Elementor AI, released progressively since 2024, lets you generate content and suggest layouts from a prompt inside the editor interface. The comparison is not strictly symmetrical. Gutenberg is the foundation WordPress is building on. Elementor is a commercial layer on top of that foundation, and Automattic has made clear in public roadmap posts that core WordPress will keep absorbing functionality that third-party builders currently own. ## Gutenberg at 41.5% on Core Web Vitals, Elementor at 30.0% Analysis of 2.1 million WordPress sites shows Gutenberg passing Core Web Vitals on 41.5% of mobile pages, with Elementor at 30.0% ([PageSpeedMatters, 2026](https://www.pagespeedmatters.com/resources/data-studies/wordpress-page-builders-core-web-vitals)). The gap is real and measurable. The cause is structural. A typical Gutenberg page ships with roughly 75% less code than an equivalent Elementor build. Elementor generates inline styles per widget, which accumulates in pages with complex layouts. The problem is not unfixable. Elementor's Container layout (replacing the old Section/Column structure), Optimized Asset Loading, and server-side rendering, all introduced between 2023 and 2025, reduce the gap materially. But those optimisations require deliberate activation. The defaults still carry overhead. ![Website performance metrics dashboard showing Core Web Vitals comparison](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-09/c4a47a-image-inline1.webp) For freelances running sites on budget shared hosting, the difference shows in user-facing load times. For agencies with proper caching and a CDN layer, the gap narrows to a point where workflow and output quality matter more than raw milliseconds. The safest position in 2026: benchmark the actual stack before committing, with caching active and Elementor Container mode enabled. ## WordPress 7.0 narrowed the design gap, but did not close it The list of what WordPress 7.0 added to core is genuinely long: per-block CSS controls, device visibility toggles on individual blocks, an updated Global Styles panel with live preview, and a reworked Query Loop block that handles custom post types reliably. For developers who were building workarounds into their theme.json for things Gutenberg used to require a plugin to handle, this release removed several friction points. What core WordPress still does not ship natively: popups, a form builder with conditional logic, a global widget library that non-developers can manage without touching the Site Editor, and hover states editable in the UI without writing CSS. Elementor Pro handles all of these. For agencies delivering marketing sites to clients who need to maintain their own popups and forms, that gap is not cosmetic. It is worth noting that the Divi page builder, now on version 5.x, has also moved toward performance parity with a new rendering engine introduced in 2024. For teams already in the Elegant Themes ecosystem, Divi 5 is worth evaluating alongside Elementor before committing to a long-term stack. The honest framing: Gutenberg is a strong foundation that rewards WordPress practitioners who are comfortable with theme.json, custom block patterns, and the Site Editor. Elementor is a productive tool for teams that need to ship polished sites fast, without asking clients to learn a new interface. ## What the actual cost looks like for a freelance billing five clients Gutenberg costs zero beyond the WordPress installation. Full Site Editing, pattern libraries, the Site Editor: none of it requires a commercial licence. Elementor Pro starts at $49 per year for one site. Scale to five sites and you are at $99/year for the 3-site Essential plan or $199/year for the 25-site Expert plan. None of these figures are prohibitive. The cost calculus matters more when multiplied across a managed hosting stack and other licence costs. Where cost becomes a real consideration: agencies managing 30 or more WordPress sites. Licencing Elementor Pro across a full client portfolio is an operational line item. Pattern Forge and Page Scribe on the noonwp Abbey plan ($49/mo) generate block patterns and page structures for that portfolio without per-site licencing, which changes the arithmetic for studios at that scale. ![Freelance web developer building WordPress sites at a desk](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-09/8789c4-image-inline2.webp) For teams considering an AI-first WordPress workflow, 10Web offers managed WordPress hosting with an AI builder layer that auto-generates Elementor-based page structures from a brief. It reduces manual layout work for client sites but introduces Elementor as a dependency in the stack. ## Where Elementor still holds the edge for agency delivery At the time of writing, three capabilities in Elementor Pro have no clean Gutenberg equivalent for non-developer clients. Popups. Elementor's popup builder handles display conditions, trigger rules, and A/B testing. Core WordPress has no native popup system. Pattern Forge generates popup markup, but clients cannot edit it without opening the Site Editor. Forms with conditional logic. Elementor Form with conditional fields, multi-step layouts, and CRM integrations handles most agency lead-generation work. The free Gutenberg ecosystem offers WPForms Lite and Contact Form 7, adequate but a different interface entirely. Loop templates for CPT archives. Elementor's Loop Builder lets designers build archive and single-post templates visually for any custom post type. The Query Loop block in WordPress 7.0 handles this in core, competently, but with a steeper learning curve for less technical clients. Agencies that hand off sites to clients who need to maintain marketing pages without developer access will find Elementor's interface more self-explanatory. That is a real and legitimate reason to keep it in the toolkit. The question is not whether Elementor is good, but whether its overhead is justified on every page of every site. ## The AI layer: Elementor AI versus Pattern Forge Elementor AI, built into the editor since late 2024, generates text content, suggests colour palettes, and proposes block layouts from a prompt entered in a sidebar panel. The output quality is consistent for standard marketing copy. The HTML structure it generates is functional but not always clean: loose class names accumulate in complex pages, and the resulting markup can be harder to maintain than hand-written blocks. Pattern Forge (noonwp, included from the Scribe plan at $12/mo) takes a different approach. You describe the block pattern you need in plain language, and the tool returns WordPress-native markup that drops directly into the theme.json pattern library. The output passes validation against the block grammar, with no extra wrappers and no framework-specific classes. For teams building block themes in production, that distinction matters at handoff, when the next developer inherits the codebase. Neither tool removes the need for editorial judgment on the output. Both are worth testing on a real client project before committing to a workflow. At the usage level of a freelance managing ten sites, the difference in generated code quality compounds over time. ## How to choose: a decision frame for practitioners If you are building a new WordPress site in 2026 and the client has no prior tool preference, here is the decision frame used in this scriptorium: - Performance is the primary constraint and the client uses shared hosting: Gutenberg. - The client needs popups, conditional forms, or a loop template without developer support: Elementor Pro. - You are building a block theme meant to last five years with minimal plugin dependencies: Gutenberg. - You are an agency delivering 10 or more landing pages per quarter to non-technical clients: Elementor Pro is defensible. - The site includes RTL content (Arabic, Hebrew) or a bilingual EN/AR structure: Gutenberg with RTL Concordance handles this natively. Elementor's RTL support has improved but still generates CSS that requires manual overrides in some block contexts. The pattern that works for most freelances: build the block theme structure in Gutenberg (header, footer, archive templates, global styles), and use Elementor selectively for pages where clients need self-service visual editing. This hybrid approach is supported by both tools and avoids the performance cost of loading Elementor on pages where it adds no value. Marginalia: that hybrid approach assumes Elementor Container mode is active and Optimized Asset Loading is enabled. Check those settings on every install before benchmarking. For teams that find both WooCommerce and WordPress hosting overhead to be friction points, WiziShop offers an alternative: a managed French e-commerce SaaS with native AI tools, without the plugin maintenance that a WordPress stack requires. Test the decision on one real client site, not a sandbox. The numbers change when you add the actual plugin stack a client will ask for in month three. ## FAQ ### Does Gutenberg replace Elementor? Not directly. Gutenberg is the core WordPress editor and the project's long-term direction. Elementor is a commercial plugin that adds capabilities core WordPress does not ship, including a popup builder, conditional forms, and loop templates. For many projects, Gutenberg is sufficient. For others, Elementor Pro fills genuine gaps. ### Is Elementor Pro worth it in 2026? At $49/year for one site, it is reasonable if you need its popup builder, form system, or loop templates. At scale across 30 or more sites, the annual licence cost is worth comparing against a block-theme workflow supported by pattern generation tools like Pattern Forge. ### Can I switch from Elementor to Gutenberg without losing content? Not cleanly. Elementor content is stored as custom post meta and shortcodes; Gutenberg reads blocks. Switching requires rebuilding pages, not just exporting. Tools like the Gutenberg Migrator plugin automate part of the conversion but should be tested on a staging environment first. ### Which builder is better for SEO? Both are SEO-capable. The performance gap (41.5% vs 30.0% Core Web Vitals pass rates on mobile, based on 2.1 million WordPress sites) gives Gutenberg a structural advantage. A well-optimised Elementor site with proper caching and Container mode active can close most of that gap. ### Does Gutenberg support RTL languages? Yes. WordPress core RTL support applies to block themes. The CSS direction property mirrors layouts correctly for Arabic and Hebrew. For production RTL sites, RTL Concordance (noonwp) automates the bilateral CSS checks that would otherwise require manual QA on each template part. ### What did WordPress 7.0 change for this comparison? WordPress 7.0 added per-block CSS, device visibility controls, and a more reliable Query Loop block for custom post types. It closed some of the feature gap with Elementor, particularly for layout flexibility. It did not add a popup builder, a conditional form system, or a visual loop template builder. ### What about Bricks Builder as an alternative? Bricks Builder sits between Gutenberg and Elementor in the performance-to-flexibility tradeoff. It runs as a separate rendering engine but ships lighter code than Elementor. Worth evaluating for agencies who want more design control than core Gutenberg without Elementor's overhead. That comparison merits a separate folio. --- ### Best Page Builder for WordPress: What Production Sites Show URL: https://noonwp.com/journal/best-page-builder-for-wordpress-what-production-sites-show > Which WordPress page builder actually holds up over 18 months? Benchmarks, code output analysis, and a framework for choosing the right tool for your next client project. The question of which is the best page builder for WordPress surfaces in every freelance forum thread, every agency RFP, and every developer retrospective after a long client project. The answer has shifted in the past two years. WordPress 6.x Full Site Editing has matured, AI tools have arrived, and at least one major builder has shipped a ground-up rewrite. Here is what the code and the benchmarks actually show. ## The metric most comparisons ignore: DOM output Most published comparisons test page builders by loading a demo page into Google PageSpeed, taking screenshots of the scores, and ranking accordingly. Those numbers are real, but they tell only part of the story. The WP Rocket team published a structured benchmark in 2025, testing ten WordPress builders under identical conditions using GTmetrix on mobile. The results were instructive: native Gutenberg scored 89/100 with a 2.2s LCP; Bricks Builder scored 88/100 with a 2.3s LCP; Elementor scored 81/100 with a 3.1s LCP. The 0.9-second LCP gap on Elementor is not a testing anomaly. The Elementor rendering model generates wrapper divs and inline styles at scale. One independent study found up to 60 DOM elements where Gutenberg produced 15 for equivalent output. On a publisher site with 40 widgets per page, that compounds into a measurable crawl budget issue and a sustained Core Web Vitals penalty. Elementor's Editor V4, released mid-2025, addressed part of this. HTML output is leaner, the JavaScript bundle is smaller, and LCP improvements were documented by the team. Sites migrated from V3 to V4, however, still carry legacy markup unless explicitly rebuilt from scratch. ![Developer analyzing WordPress page builder performance metrics on dual monitors](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-09/10a416-inline1.webp) ## Elementor in 2026: the dominant tool, reviewed honestly Elementor is installed on more than 12 million active sites. That reach exists for reasons that have nothing to do with code quality, and those reasons are worth taking seriously before dismissing the tool. The ecosystem is unmatched. WPML, Polylang, ACF, WooCommerce, and essentially every major WordPress plugin ship an Elementor integration. The template library, the third-party add-on market, the tutorial ecosystem on YouTube and in community forums: none of the competitors come close. For an agency delivering 20 client sites per year, that ecosystem reduces delivery risk. A designer you hire tomorrow almost certainly knows Elementor. A client who needs a minor edit in three years can find local help without difficulty. That reliability has concrete value for ongoing client relationships. Elementor Pro pricing runs $59 to $399 per year depending on the number of sites, with a free core version that covers most use cases for smaller projects. The pricing is not a blocker for most agencies. Where it falls short is at the code level: if your client is a publisher with 500 posts who monitors Core Web Vitals, you will feel the LCP gap in practice. ## Bricks Builder: the developer's choice Bricks Builder has earned its standing among developers who care about output quality. The HTML it produces is close to hand-coded: semantic, lean, without Elementor's characteristic wrapper divs and inline style accumulation. The pricing model is unusual and worth examining. Bricks costs $79 one-time for lifetime updates to a single site, with larger bundles available by site count. For a freelance building long-lived client sites, that cost structure is a strong argument against recurring annual fees. The learning curve is steeper than Elementor. Bricks thinks in terms of elements and structure the way a developer does, which works well for developers and creates friction for designers accustomed to Elementor's click-anywhere model. One practical constraint: the Bricks ecosystem is smaller, and third-party add-ons are sparser than Elementor's. Before committing to Bricks on a client project, verify that any specific integrations the client requires are available. At the usage level, here is what you notice: a Bricks site is easier to audit and maintain after handoff. When something breaks, the markup tells you where to look. Compared to Elementor-generated HTML, the diagnostic process is faster and less opaque. ![Clean HTML code in a dark IDE editor, illustrating the output quality difference between WordPress page builders](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-09/55e77b-inline2.webp) ## Divi V5: the right answer for design-heavy sites Divi's V5, released in 2025, was a meaningful update. PageSpeed scores on Divi 5 sites now land in the 75 to 90 range, which is a real improvement over the V4 baseline. The visual editor is fast for non-developers, the template library is extensive at 2,000-plus layouts, and the lifetime license at $249 is a compelling price point for agencies that want to stop paying annual fees. Divi's strength is in design-heavy marketing sites where the client values visual control over code cleanliness. An e-commerce landing page, a portfolio, a corporate homepage with animated sections: Divi delivers these efficiently and with a fast client feedback loop. Where Divi struggles is in developer handoffs. If you build in Divi and pass the site to a Gutenberg-native developer, the learning curve is significant. Divi's global modules and legacy shortcode system do not map cleanly to block patterns or FSE templates. The tool is expressive but proprietary, and that matters when the maintenance path is unclear. ## The native Gutenberg path: when it earns its place The conversation about the best page builder for WordPress has shifted since WordPress committed to Gutenberg as its long-term architecture. Full Site Editing landed in WordPress 5.9, matured through versions 6.0 to 6.6, and in 2026 represents a genuine option for practitioners who were reaching for Elementor out of habit rather than necessity. The arguments for native Gutenberg are three. First, standards alignment: block themes and FSE templates use standard WordPress APIs, so when WordPress updates, a native site updates with it. A page-builder site carries a plugin dependency that may or may not keep pace. Second, the performance floor: the benchmarks above show a 2.2s LCP baseline before any optimization. You are not working against inherited bloat. Third, pattern reuse: a well-built block pattern library is as expressive as a page builder template library without the proprietary lock-in. The friction points are real. Building complex layouts in the native block editor requires fluency with the Query Loop block, with Group and Cover stacking, with `theme.json` spacing scales and global styles. The interface is less forgiving for practitioners new to it than Elementor's canvas. A List Apart's ongoing coverage of FSE adoption (2024-2025) noted that developers with a background in theme development reach proficiency in two to three projects; those coming from a pure Elementor background typically need four to five. ![Modern minimalist workspace with a large monitor showing a website layout in a visual editor](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-09/e17b8e-inline3.webp) ## How AI tools change the delivery equation The argument for page builders has always been partly about speed: a developer builds a complex layout in Elementor faster than in raw HTML or the native block editor. That speed advantage narrows when you can describe a block pattern in plain English and receive working code. Pattern Forge, part of the noonwp toolkit and available from the Scribe plan at $12/month, generates Gutenberg block patterns from a text prompt. Page Scribe extends this approach to full FSE page templates. The output is valid WordPress block markup: HTML comments, block attributes, no external dependencies. The Monk plan (free) includes a limited number of monthly generations to evaluate the approach before committing. A usage example from the field: a two-column section with a pull quote on the left and a three-item feature list on the right, using the site's accent color, generates in about 12 seconds via Pattern Forge. Reviewing and adjusting the output takes another five minutes. The same layout in Elementor takes perhaps eight minutes without the review step, but the output includes wrapper divs that will require optimization later. The colophon of this section: the workflow suits developers more than designers. If your team is primarily design-led and Elementor-native, the transition investment is real. Marginalia: this approach is most effective on WordPress 6.5-plus, where FSE template parts and Block Bindings have stabilized. ## A decision framework for the next client brief There is no single best page builder for WordPress. That is an honest position based on the evidence above, not an evasion. If you are optimizing for ecosystem and team familiarity, Elementor is the practical choice. Accept the code overhead, apply a caching plugin and a CDN, and you will ship reliably. If you are optimizing for code quality and long-term maintainability, Bricks Builder earns its learning curve for any client who monitors performance. If you are building design-heavy marketing sites where clients will edit independently, Divi V5 is the efficient answer. If you are comfortable with Gutenberg and want to build for the long term, go native, use FSE, and consider augmenting the workflow with Pattern Forge or Page Scribe. The question worth asking before selecting a tool is not which one has the most features. It is: who will maintain this site in two years, and what will they find when they open the editor? Before you open the Site Editor or install a new builder on a client project, one concrete step is worth taking: open a recent client site in the browser inspector, count the DOM nodes on a typical page, and note the inline styles. That single audit tells you more about your current tool than any feature chart. Set the folio accordingly. ## FAQ ### What is the best free WordPress page builder? The native Gutenberg block editor is free and built into WordPress. For those who prefer a drag-and-drop interface, Elementor offers a free core version that covers basic layouts and widgets for smaller sites. ### Is Elementor still worth using in 2026? Yes, for teams where ecosystem compatibility and client self-editing matter more than code cleanliness. Elementor V4 improved performance significantly, and its 12-million-site install base means tooling and support are widely available. ### Does Bricks Builder perform better than Elementor? In benchmark testing, Bricks scores slightly higher than Elementor on performance: 88/100 versus 81/100 in a 2025 WP Rocket study, with a 2.3s LCP versus 3.1s. The code output is also meaningfully cleaner, which matters for long-term maintenance. ### Can I build a full WordPress site without a page builder? Yes. WordPress Full Site Editing (FSE) with a block theme allows building complete sites using native blocks and patterns, without any third-party page builder. The workflow requires Gutenberg fluency but produces the cleanest, most future-proof output. ### Which WordPress page builder is best for Core Web Vitals? Native Gutenberg and Bricks Builder consistently score highest on Core Web Vitals benchmarks. Both produce lean HTML output with fewer DOM elements and smaller JavaScript payloads than Elementor or Divi by default. ### Is Divi still a good choice for WordPress in 2026? Divi V5 improved performance considerably over V4 and is a solid choice for design-heavy marketing sites. The $249 lifetime license makes it attractive for agencies. The main limitation is that its output does not integrate cleanly with native Gutenberg workflows. ### How does AI affect WordPress page building? AI tools like Pattern Forge (noonwp) generate Gutenberg block patterns from plain-language descriptions, reducing the speed advantage that page builders held over native block development. The result is cleaner code with comparable delivery time. --- ### How Much Does a Website Cost in 2026: Full Breakdown URL: https://noonwp.com/journal/how-much-does-a-website-cost > Every client asks it. Here is what a WordPress website actually costs in 2026, from a freelance who quotes real projects every week. How much does a website cost in 2026? For a freelance-built WordPress site: between $2,500 and $8,000 for a standard small business project. A block theme with WooCommerce starts at $8,000. A DIY SaaS builder costs $0 up front and $15 to $60 per month. These are not vague ranges. They reflect distinct choices with real trade-offs, and the right answer depends entirely on what the site needs to do. Every week, at least one prospective client asks me some version of this question. The honest answer is never a single number. It is a set of numbers tied to a set of decisions. ## What "a website" actually means (the question under the question) When clients ask how much a website costs, they are almost never asking about the technology stack. They are asking whether their budget is realistic for what they have in mind. This distinction matters because the answer you give shapes the entire project scope conversation. A five-page brochure site with a contact form and a blog is not the same as a WooCommerce store with 400 products, custom filter blocks, and a multilingual setup. Both are "websites". One costs $3,000. The other costs $12,000 or more. Before quoting anything, you need to understand which project you are actually being hired for. The same applies on the buyer's side. If you are pricing a website for the first time, the most useful thing you can do is write down what the site needs to accomplish in year one. Not what would be nice. What it must do. That scoping exercise is worth more than any pricing guide. ## The four build paths and what they cost in 2026 There are four distinct ways to get a website built in 2026, each with a different price profile. **DIY on a SaaS builder (Wix, Squarespace, Framer, Webflow).** Entry cost: $0 to $500. Monthly ongoing: $15 to $60. This path makes sense if you have time, some design instinct, and no requirement for custom functionality. The builders have improved significantly in the last two years. Webflow's interaction system and Framer's AI-assisted layout tools now let a non-developer ship something that looks genuinely professional. The limit is not the visual output. It is the inability to extend the platform when your needs grow. **Self-hosted WordPress with a theme or page builder.** Entry cost: $75 to $500 for the first year (hosting, domain, premium theme, one or two plugins). Monthly ongoing: $15 to $50 for managed hosting. This is the path most small businesses follow when they take the DIY route. It has more flexibility than a SaaS builder, but also more maintenance. Updates, security patches, plugin conflicts: these do not manage themselves. **Freelance WordPress developer.** Project cost: $1,500 to $8,000 for a small business site. Custom block theme work or more complex functionality can push toward $12,000. A competent freelance will deliver a mobile-responsive, SEO-structured site built on a maintainable codebase. What you are paying for, beyond the build itself, is someone who has made and learned from the same mistakes on ten other sites before yours. This is the range I operate in. For a five-page business site with a custom Gutenberg block theme, a Query Loop-based blog, and a contact form connected to a CRM, I quote between $3,500 and $5,500. For a WooCommerce setup with custom product pages, that starts at $7,000. **Agency.** Project cost: $8,000 to $25,000 or more, sometimes much more for enterprise or e-commerce. An agency brings a team: a project manager, a designer, a developer, sometimes a copywriter. The quality ceiling is higher. So is the minimum budget. Boutique agencies in the UK and Europe typically quote $8,000 to $15,000 for a standard business site. US agencies run higher. ![Open planner notebook with budget notes and colorful sticky notes on a wooden desk](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-09/a37589-img-1.webp) ## What drives the price up Three things reliably push a project beyond the initial estimate. **E-commerce functionality.** WooCommerce is free, but building a store that converts is not. Custom product card blocks, filtered category pages, checkout flow optimisation, payment gateway integration: each of these adds time. A functional WooCommerce site built on a proper block theme takes between 60 and 100 hours. At a freelance rate of $75 to $120 per hour, that is $4,500 to $12,000. **Multilingual and RTL support.** WordPress handles left-to-right languages well by default. Right-to-left languages like Arabic and Hebrew require careful block theme construction. The `dir` attribute must be applied at the right level. Fonts need a separate face for each script. Layout mirroring requires testing across block types. Adding RTL to a project that was not scoped for it from the start is expensive. Adding it at the start adds 20 to 30 percent to the build time. **Custom block patterns and Full Site Editing integration.** Clients who want a highly customised site built on the WordPress Site Editor should budget for pattern development. A well-built set of reusable patterns, template parts, and a properly structured `theme.json` takes time. The payoff is a site the client can actually edit without breaking things. The cost is real. ## Ongoing costs most buyers underestimate The build is a one-time expense. What many clients do not account for is the cost of keeping the site running and up to date. **Hosting.** Shared hosting costs $5 to $15 per month. Managed WordPress hosting from providers like Kinsta, WP Engine, or Cloudways runs $25 to $100 per month depending on traffic and features. For client sites where uptime matters, managed hosting is not optional. **Maintenance.** WordPress core, themes, and plugins update constantly. Testing those updates, checking for plugin conflicts, and handling security patches takes time. Most freelances offer a maintenance retainer of $50 to $200 per month. Some clients prefer to handle this themselves and discover the limits of that approach the first time a plugin update breaks the site. **SSL, domain renewal, CDN.** A domain renewal is $10 to $35 per year. An SSL certificate is usually included with managed hosting. A CDN like Cloudflare's free tier covers most small sites. Realistic total cost of ownership for a small business WordPress site over three years: build ($4,000) plus hosting ($1,200) plus maintenance ($3,600) plus domain ($90) adds up to roughly $8,900. That figure is rarely in the conversation at the start of a project. ## AI website builders in 2026: where they actually help The landscape shifted meaningfully in 2025-2026. AI-assisted builders can now generate a complete, functioning website from a text prompt or a competitor URL. 10Web will clone a site and rebuild it in WordPress with an AI Co-Pilot for editing. Wegic lets you describe what you want in a chat interface and adjusts the layout in real time. These tools work. The limitations are real too. AI-generated sites still require meaningful setup time for branding, content, and any custom functionality beyond the template. They are genuinely useful for rapid prototyping, for landing pages, and for clients with limited budgets and simple needs. They are not a replacement for a properly scoped build when the project has complexity. The interesting development for WordPress practitioners is how these tools integrate with the block editor. AI platforms like 10Web and tools like noonwp's Pattern Forge both reduce the time to first deliverable significantly. The difference is in the output quality. Pattern Forge generates clean Gutenberg-native patterns without the proprietary markup that page builders embed. That matters when you hand the site to a client who will maintain it themselves. ## The honest comparison: freelance vs. AI builder A $29 per month AI builder plan can produce a functional five-page site in an afternoon. A freelance WordPress build of comparable quality takes 30 to 50 hours. If budget is the constraint and the project is simple, the AI builder wins on economics. The calculation changes when the site needs to grow. Custom functionality, e-commerce, multilingual support, performance optimisation, RTL layout: all of these require a developer at some point. The question is not whether to hire a developer, but when. One pattern I see regularly: clients start with an AI builder, hit a wall at the 12-month mark when they need something the builder cannot do, and hire a freelance to migrate to a proper WordPress build. The migration costs more than an original custom build would have. This is not an argument against AI builders. It is an argument for scoping honestly at the start. ![Two professionals at a cafe discussing website design on laptops](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-09/a1b96a-img-2.webp) ## What noonwp tools change for WordPress freelances noonwp's pattern approach is specifically built for the workflow described above. Pattern Forge generates Gutenberg-native block patterns from a text description. Page Scribe handles page assembly. The output is clean, maintainable HTML and theme.json configuration, not proprietary page builder markup. For a freelance who builds 15 to 25 sites a year, the time saving is meaningful. A hero section and a card grid that would take three hours to build from scratch can be scaffolded in 20 minutes with Pattern Forge. That time can go toward the parts of the project that actually need human judgement: client communication, content structure, performance testing. The Monk plan is free. The Scribe plan is $12 per month. For a freelance doing five or more builds a year, the Scribe plan covers itself on the first project. ## Pricing to quote with confidence The question "how much does a website cost" has a real answer. It depends on build method, complexity, and timeline. For a WordPress freelance in 2026, that answer looks like this: - Five-page brochure site, block theme, no e-commerce: $3,000 to $5,000 - Small business site with WooCommerce (under 50 products): $6,000 to $9,000 - WooCommerce store with custom patterns, filters, RTL: $10,000 to $15,000 - Ongoing maintenance per month: $75 to $200 When a client asks the question, give them these numbers directly. Then ask what their site needs to do in year one. The conversation that follows will tell you which range actually applies. ![Web developer home office with dual monitors showing website interfaces](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-09/13c469-img-3.webp) ## FAQ ### How much does a basic WordPress website cost in 2026? A basic WordPress website built by a freelance costs between $1,500 and $5,000 depending on the number of pages, design complexity, and whether it includes a blog. A DIY self-hosted WordPress build covering hosting, domain, and a premium theme costs $75 to $500 for the first year. ### What is the ongoing monthly cost of a WordPress website? Expect $25 to $100 per month for managed WordPress hosting, plus $50 to $200 per month for a maintenance retainer if you hire a freelance to handle updates and security. Domain renewal adds roughly $10 to $35 per year. Total ongoing cost for a well-maintained small business site: $75 to $300 per month. ### Are AI website builders cheaper than hiring a WordPress developer? For simple sites, yes. An AI builder plan costs $9 to $59 per month and can produce a five-page site in hours. A freelance WordPress build starts at $1,500 and typically runs $3,000 to $8,000 for a small business site. The trade-off is flexibility: AI builders hit limits when you need custom functionality, e-commerce, or RTL language support. ### How much does adding e-commerce to a WordPress site cost? WooCommerce itself is free, but a properly built WooCommerce store on a custom block theme typically costs $6,000 to $12,000 with a freelance, or $12,000 to $25,000 with an agency. The time is in custom product templates, filter blocks, checkout configuration, and payment gateway integration rather than the plugin itself. ### Does adding RTL (Arabic or Hebrew) support to WordPress increase the cost? Yes, meaningfully. RTL support requires careful block theme construction: CSS direction handling, separate font faces for each script, and layout mirroring testing across all block types. Scoped from the start of a project, RTL adds roughly 20 to 30 percent to the build time. Added retroactively, it costs more. --- ### WordPress Full Site Editing in 2026: A Field Guide URL: https://noonwp.com/journal/wordpress-full-site-editing-2026 > FSE is the standard for WordPress in 2026. This field guide covers block theme anatomy, Site Editor structure, Query Loop mechanics, and Pattern Overrides, with honest production notes. WordPress Full Site Editing reached a tipping point in 2026. In WordPress 6.9, 68% of new site installations default entirely to block-based architecture. For freelances and agencies who still deliver classic PHP themes to clients, the question is no longer whether to adopt FSE but how to do it without breaking production workflows. This folio covers the mechanics, not the marketing. Tested on real client sites running WordPress 6.8 and 6.9. ## What FSE replaces, and what it keeps Full Site Editing does not replace PHP. It replaces the file-based template hierarchy that traditionally lived in PHP files, header.php, footer.php, single.php, page.php, with HTML files that contain block markup. The PHP engine still runs. WordPress still queries the database, still processes hooks, still loads plugins. What changes is the boundary between developer responsibility and editorial control. In a classic theme, a developer writes PHP templates and the site editor modifies post content. In a block theme, both the post content and the site chrome (header, footer, navigation) are composed of the same blocks, editable from the same interface. The developer designs the structure. The editor fills it. This is the shift that matters for client delivery: your clients can now modify things you thought were locked. Pattern Overrides and synced patterns exist precisely to address that problem. ## The minimum viable block theme: three files A functional block theme requires exactly three files: - `style.css` (theme metadata and version info) - `theme.json` (design tokens, block defaults, global settings) - `templates/index.html` (the main template fallback) WordPress registers everything else from those three. The `parts/` directory is for template parts (header, footer, sidebar). The `patterns/` directory holds auto-registered block patterns. Understanding this minimal structure clarifies what is truly required versus what is convention. Many themes ship with dozens of template files and patterns. Most of that scaffolding serves editorial convenience, not technical necessity. ![Block theme layout structure visible in a modern web design interface](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-09/57b5f1-img-1.webp) ## The Site Editor in WordPress 6.9: five areas, one hierarchy Access the Site Editor via Appearance > Editor. What you see is a sidebar with five navigation areas: - **Navigation**: the menus registered on the site - **Styles**: Global Styles, the visual counterpart of theme.json - **Pages**: a full content management interface inside the editor - **Templates**: the template hierarchy (single, archive, 404, search, and any custom templates) - **Patterns**: the pattern library, synced and unsynced These five areas share a common data layer. Styles apply globally. Templates apply to URL patterns. Patterns can be placed anywhere. WordPress 6.8 improved navigation with persistent filter states and live preview thumbnails on template hover. The Style Book now shows interactive states (hover, focus, active). These are quality-of-life improvements, not architectural changes. The hierarchy itself has been stable since 6.5. One thing that matters in production: templates stored in the database override templates in the theme files. When a client or editor saves a template via the Site Editor, WordPress writes it to `wp_posts` with `post_type = 'wp_template'`. From that point, the theme file is ignored. This is expected behavior but surprises many developers the first time they push a theme update and see nothing change on the live site. To reset a template to the theme version, go to Editor > Templates, open the template, and select "Reset to default." Or from the command line: `wp post delete $(wp post list --post_type=wp_template --format=ids)` will remove all database overrides and restore theme files. ## Template parts: the right abstraction, used wrong Template parts are reusable fragments: header, footer, sidebar, post-meta area. They live in `parts/*.html` and are registered in `theme.json` under `templateParts`. Each part has a slug, a title, and an area (header, footer, general). The practical rule: use template parts for site chrome that appears across multiple templates. Do not use them for single-use sections inside page templates. A common pattern is creating a template part for a hero block that appears only on the homepage. That hero should be a synced pattern or a page-level block group, not a template part. Template parts add a layer of indirection without adding reusability in that case. Template parts are edited globally. If a client edits the Header template part, that change propagates to every template that includes it. This is the intended behavior for headers and footers. It is a source of confusion when developers use template parts for context-specific content. ## The Query Loop block: your PHP loop, without PHP The Query Loop block is the FSE equivalent of `WP_Query`. It renders a dynamic list of posts based on configurable parameters: post type, taxonomy, order, offset, number per page. A typical Query Loop in a theme template looks like this in block markup: `
`The `"inherit":true` parameter tells the block to use the current URL's query context (category archive, tag archive, search results) rather than a fixed query. This is what makes a single `archive.html` template work across all taxonomy archives. At the usage, here is what practitioners note: the Query Loop's filtering interface in the editor is limited. Filtering by multiple taxonomy terms with AND logic, or combining meta field conditions, requires either a custom block variation registered via JavaScript or a dedicated plugin. The core block covers roughly 80% of editorial use cases. The remaining 20%, complex faceted queries and conditional relationships between post types, still requires code. ![theme.json configuration file open in a dark-mode code editor for a WordPress block theme](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-09/3750e1-img-2.webp) ## theme.json: what it controls, what it delegates theme.json is the configuration spine of a block theme. Version 3, introduced in WordPress 6.7, extended it in several directions. **What theme.json controls directly:** - Color palettes (custom colors available in the editor) - Typography (font families, font sizes, fluid type scales via `min` and `max` values) - Spacing presets (margin and padding options) - Block-level defaults (default padding on Group blocks, default colors on Button blocks) - Custom templates and template parts registration - Block style variations (a light card variant versus a dark card variant, for instance) **What theme.json delegates to the editor:** the actual values a user assigns when they override a default. If a user changes the Site Title font in Global Styles, that value lives in the database, not in theme.json. **What theme.json does not control:** plugin styles. A contact form plugin or WooCommerce will inject its own CSS regardless of what theme.json defines. Block editor UI behavior (toolbar items, sidebar panels) also requires JavaScript, not theme.json. A useful production habit: keep `wp/v2/global-styles` out of your caching layer. Several caching plugins have been observed to cache the REST response that powers Global Styles, causing editors to see stale style values. Exclude that endpoint from REST caching. Marginalia: theme.json validation is silent. An invalid JSON file fails without a console error and WordPress falls back to core defaults. Run a JSON linter before every deployment. ## Pattern Overrides: locked structure, overridable content Pattern Overrides, introduced in WordPress 6.8, solve a specific client handoff problem: you want a design structure to stay exactly as the designer built it (a promotional banner, a testimonial block, a pricing row) while allowing editors to change the text, image, and link inside it. The mechanism: create a synced pattern, mark specific blocks inside it as overridable, and each page that uses the pattern can set its own values for those blocks without modifying the shared design. In technical terms, this uses the Block Bindings API with the `core/pattern-overrides` source. A block inside a synced pattern that has override enabled carries a `metadata` attribute with a unique `id`. When an editor customizes that block on a specific page, WordPress stores those values against the `id` in the page's post content, not in the synced pattern itself. Overridable attributes include content, URLs, alt text, and titles. Styling properties are not overridable via this mechanism. If a client wants to change a button color per page, Pattern Overrides will not help. The design needs a different approach, or the client edits the global synced pattern and changes it everywhere. That boundary matters. Communicate it before project sign-off. Combined with editor role restrictions, Pattern Overrides give freelances a way to deliver layouts that are editable but not destructable. It is the most significant client delivery feature added to FSE in the past year. ## What still breaks in production An honest field note, measured across client sites between January and August 2026. **Templates not updating after a theme push.** Database-stored templates override theme files. Add a `wp post list --post_type=wp_template` check to your deployment checklist. **Pattern Overrides not saving.** If overridable blocks do not have unique `metadata.id` values, their overrides silently fail. When generating patterns programmatically or copy-pasting block markup, duplicate `id` values are a recurring issue. **Global Styles disappearing after a theme update.** If a theme update renames a color token, references to the old name become dangling. WordPress does not warn. The color disappears. Maintain backward compatibility in token naming across theme versions. **RTL layouts in block themes.** The CSS `direction` property and logical layout properties (margin-inline, padding-inline) have improved in WordPress 6.8, but full RTL support in block themes still requires manual testing and CSS overrides in several cases. If you are building for Arabic or Hebrew sites, allocate dedicated time for RTL verification. **Nested patterns and DOM depth.** Deeply nested Group blocks inside synced patterns inside template parts create DOM trees that are expensive to render and painful to debug. A practical limit: no more than three levels of Group blocks before reconsidering the architecture. ## Tools worth knowing for FSE production work **WiziShop** covers the case where a client's primary need is an online store, not a custom CMS. A WordPress installation with WooCommerce and a block theme delivers flexibility, but it also delivers maintenance overhead: plugin updates, hosting management, performance tuning, security patches. WiziShop is a hosted SaaS platform that handles the commerce layer directly, without requiring PHP expertise. For freelances who regularly hand over stores to non-technical clients, it is worth putting on the table alongside the WooCommerce quote. The comparison that matters: WooCommerce gives you control; WiziShop gives the client autonomy after delivery. **Shopify** covers similar territory for clients oriented toward higher-volume retail. Its integration with WordPress via the Storefront API allows hybrid setups where WordPress handles editorial content and Shopify handles cart and checkout. Useful when a client already runs a Shopify account and wants to add a blog or content hub without migrating the entire store operation. **Wegic** is an AI web builder worth knowing for smaller scope requests. When a client asks for a five-page brochure site and the FSE overhead of a full block theme is disproportionate, a purpose-built AI site builder can deliver faster. Not a replacement for WordPress on content-heavy or custom-feature projects, but a useful referral path for the jobs that do not need a CMS at all. The colophon of this article: test Pattern Overrides on a real client site before pitching them as a handoff feature. The mechanism works cleanly when built from scratch. Migrating existing synced patterns to use overrides requires careful attention to the `metadata.id` uniqueness constraint. ## FAQ **Q: Is WordPress Full Site Editing ready for client sites in 2026?** A: Yes, with one qualification. FSE has been production-stable since WordPress 6.5. What requires care is the database-override behavior for templates and Global Styles persistence after client edits. Document these behaviors for clients and build a deployment checklist that accounts for them. **Q: Do I still need a child theme with Full Site Editing?** A: Rarely. The Site Editor stores customizations in the database, so editing a parent theme through the editor is non-destructive. Child themes remain useful when you need to modify PHP functions or override a template with a fundamentally different structure. **Q: What is the difference between a synced pattern and a template part?** A: Template parts (header, footer) are structural containers that define site structure and appear inside templates. Synced patterns (hero, card, CTA) are reusable design units that can appear inside templates or pages. Both live in the pattern library in the Site Editor. **Q: What are Pattern Overrides in WordPress?** A: Pattern Overrides, introduced in WordPress 6.8, allow editors to change specific content inside a synced pattern (text, image, URL) on a per-page basis without altering the shared design structure. The Block Bindings API with the core/pattern-overrides source powers this feature. **Q: How do I prevent clients from breaking FSE templates?** A: Use a combination of synced patterns with Pattern Overrides for design-critical areas, configure editor role capabilities to restrict template editing, and document the difference between page-level editing and template editing during client handoff. The Site Editor's template reset function exists precisely because this scenario is common. ## FAQ ### Is WordPress Full Site Editing ready for client sites in 2026? Yes, with one qualification. FSE has been production-stable since WordPress 6.5. What requires care is the database-override behavior for templates and Global Styles persistence after client edits. Document these behaviors for clients and build a deployment checklist that accounts for them. ### Do I still need a child theme with Full Site Editing? Rarely. The Site Editor stores customizations in the database, so editing a parent theme through the editor is non-destructive. Child themes remain useful when you need to modify PHP functions or override a template with a fundamentally different structure. ### What is the difference between a synced pattern and a template part? Template parts (header, footer) are structural containers that define site structure and appear inside templates. Synced patterns (hero, card, CTA) are reusable design units that can appear inside templates or pages. Both live in the pattern library in the Site Editor. ### What are Pattern Overrides in WordPress? Pattern Overrides, introduced in WordPress 6.8, allow editors to change specific content inside a synced pattern on a per-page basis without altering the shared design structure. The Block Bindings API with the core/pattern-overrides source powers this feature. ### How do I prevent clients from breaking FSE templates? Use synced patterns with Pattern Overrides for design-critical areas, configure editor role capabilities to restrict template editing, and document the difference between page-level editing and template editing during client handoff. The template reset function in the Site Editor exists for this scenario. --- ### WordPress Performance Optimization: A 2026 Field Audit URL: https://noonwp.com/journal/wordpress-performance-optimization-a-2026-field-audit > WordPress performance optimization in 2026: hitting LCP, INP, and CLS targets. This field audit covers four highest-leverage fixes with measured results from client deployments. A WordPress site that loaded in 8 seconds three years ago was embarrassing. The same site at 8 seconds in 2026 is invisible to search. WordPress performance optimization in 2026 means hitting three specific thresholds on mobile: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. Miss any of them and Google's Core Web Vitals report flags you. Miss INP specifically and you have a ranking signal actively working against you. It replaced First Input Delay as a Core Web Vitals metric in early 2024 and since then it has been the most commonly failed metric on WordPress sites measured in the field. This folio covers the four highest-leverage interventions, in the order a practitioner should apply them. Before the technical measures: the single most reliable diagnostic is the Core Web Vitals report in Google Search Console, not PageSpeed Insights. Search Console reflects real user data aggregated over 28 days. PageSpeed Insights reflects a lab run from a single location. Both are useful, but the ranking signal comes from real users. ![Server infrastructure in a data center, blue LED indicators in rows](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/accorata/2026-08/0ca324-inline1.webp) ## Page caching remains the single highest-ROI fix Before adjusting JavaScript bundles or image formats, measure your Time to First Byte. If TTFB consistently exceeds 600 milliseconds, every subsequent optimization you make happens inside a deficit that caching alone can close. Page caching stores complete HTML responses on disk or in memory and serves them without invoking PHP or querying the database. For most WordPress sites, enabling page caching alone cuts TTFB by 60 to 80 percent and moves LCP scores from failing to passing in a single step. This is the closest thing to a free lunch in WordPress performance work. The practical ceiling of caching is determined by your hosting infrastructure. Shared hosting with I/O throttling can serve a cached HTML file in 400 milliseconds. Managed WordPress hosting on NVMe storage with Redis object caching typically serves the same file in 25 to 60 milliseconds. That 340-millisecond gap is not recoverable through JavaScript optimization or image compression. Hosting tier is a performance decision, not just an operational one. WP Rocket, LiteSpeed Cache, and W3 Total Cache are the three most widely deployed caching layers. LiteSpeed Cache is free and performs exceptionally well on LiteSpeed-powered hosts. Enable page cache first, then object cache if your host supports Memcached or Redis, then browser cache headers. This sequence takes under 20 minutes on a site you know and changes the numbers visibly on the first synthetic test. For teams building on managed infrastructure with AI-assisted performance tooling built into the stack, 10Web's PageSpeed Booster applies automatic optimization at the edge, including critical CSS extraction and resource prioritization, without requiring manual plugin configuration per site. ## JavaScript deferral fixes INP without touching code INP measures the delay between a user interaction and the browser's visual response to that interaction. It fails when too much JavaScript is executing on the main thread at interaction time, blocking the browser from responding visually. The highest-impact fix is deferral: delay the execution of non-critical scripts until after the user's first meaningful interaction. WP Rocket's Delay JavaScript Execution feature handles this with a configurable exclusion list. In measured results on WooCommerce product pages, enabling it with a standard exclusion list drops INP from a range of 380 to 420 milliseconds into a range of 140 to 180 milliseconds, with no code changes on the theme or plugin layer. The friction in this approach is real: every plugin you add to a WordPress build registers JavaScript. After year three of a live installation, the main thread is handling analytics, chat widgets, cookie banners, affiliate trackers, and form validators on every page load, whether or not the user interacts with any of them on a given visit. À l'usage, voici ce que l'on constate: the exclusion list requires systematic tuning. A contact form plugin deferred past first interaction will appear unresponsive. Work through the list against a staging environment with real interaction scenarios, not just a synthetic lab run. A plugin conflict caught in staging is an hour of work; one caught from a client phone call is half a day. One structural fix worth noting: Google Tag Manager containers are among the most common INP offenders. A GTM container with 12 active tags can add 200 to 400 milliseconds of main thread blocking on load. Review active tags with the team or client. Remove unused tags before attempting deferral. Deferral on a bloated GTM container is treating a symptom. ## Image pipeline: priority, format, and the LCP image LCP is almost always an image. The largest element in the viewport on page load is your hero section image, your page header graphic, or your first post thumbnail in a Query Loop block. Optimize it deliberately and differently from secondary images. The practical pipeline for 2026: generate WebP output at the upload stage, serve via a CDN edge node geographically close to your audience, and add `fetchpriority="high"` to the LCP image element. Do not lazy-load it. A lazy-loaded LCP image is a direct contradiction: you are telling the browser to deprioritize the element that Google is timing. For the LCP image specifically, `fetchpriority="high"` tells the browser to begin loading it as soon as it parses the HTML, ahead of render-blocking resources. On WordPress block themes, you add this via a `render_block` filter targeted to the specific block and context. On page builders, the path varies by builder and version. Secondary images below the fold should be lazy-loaded with the native `loading="lazy"` attribute. WordPress has applied this to non-featured images by default since 5.5. The issue is when a theme or page builder overrides this behavior globally. Audit the rendered HTML of representative pages; look for `loading="lazy"` on the hero and `loading="eager"` or missing attributes everywhere else. ![Developer workspace with laptop showing WordPress code and performance notes](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/accorata/2026-08/7d376f-inline2.webp) ## Block themes versus page builders: the weight in numbers This is where performance gaps become most concrete. A Twenty Twenty-Five or GeneratePress block theme ships with minimal JavaScript: typically 8 to 18 KB total after compression. An Elementor build on identical content ships between 280 and 650 KB of JavaScript and CSS, depending on the widgets in use. That difference is not invisible. On a median 4G mobile connection, 400 KB of JavaScript adds approximately 280 to 320 milliseconds of parse and compile time on a mid-range Android device. For INP, that is the gap between a passing score and a failing one. This is not an argument against page builders as a category. Elementor, Bricks Builder, and Divi serve real production needs, particularly for clients who maintain their own content without developer involvement. The argument is: if you are starting a new project where performance is a documented requirement, begin with a block theme. Layer page builder functionality only where native blocks genuinely cannot achieve the required output. Marginalia: this framing holds for WordPress 6.5 and above, where FSE template editing covers most content structures without a builder. ## CDN: the geography problem and its cost Page caching reduces server response time. A CDN reduces the physical distance the response travels, which is a separate constraint with a different solution. A WordPress site hosted in Frankfurt serving visitors in São Paulo has a baseline TTFB of 280 to 420 milliseconds from origin, before any content renders. A CDN edge node in South America serves that same cached response in 18 to 35 milliseconds. In PageSpeed Insights field data, adding a CDN to an already-cached WordPress site typically moves LCP from a 2.8 to 3.5 second range into a 1.2 to 2.0 second range for geographically distributed audiences. Cloudflare's free tier, BunnyCDN, and the CDN bundled with most managed WordPress hosting platforms each cover this requirement at different price points. The practical constraint: your caching plugin must send `Cache-Control` headers that the CDN will respect. A CDN in front of a WordPress install that sends `Cache-Control: no-store` on all responses is infrastructure cost with no performance return. Verify the headers on representative URLs before assuming CDN coverage is active. ## WooCommerce performance requires a separate audit A standard WordPress content site and a WooCommerce store have fundamentally different performance constraints. Cart, checkout, and account pages cannot be page-cached at the standard level because they carry user-specific content. Product archive pages can and should be cached, but product pages with live inventory data require cache invalidation logic tied to stock changes. The WooCommerce-specific performance checklist diverges at several points. Object caching for database queries becomes mandatory rather than optional: WooCommerce generates significantly more database queries per page than a standard WordPress install, and without Redis or Memcached, those queries run on every request regardless of page caching. Database query monitoring tools like Query Monitor or the built-in WooCommerce status screen will surface N+1 query patterns introduced by plugins. These are usually the third-party payment gateway, a complex shipping calculator, or a dynamic pricing plugin that was not performance-profiled at install time. For stores where the infrastructure complexity of WooCommerce becomes the primary operational constraint, and where customization requirements are moderate, it is worth scoping dedicated e-commerce platforms. These remove the PHP and MySQL stack entirely, which eliminates the performance floor that even a well-optimized WordPress installation cannot go below. ## Monitoring: one plugin update can undo weeks of optimization Core Web Vitals are not a one-time audit result. A plugin update, a new block added to a page template, or a third-party script added by a client or their marketing team can regress scores silently between your audits. Continuous monitoring covers two layers: Google Search Console's Core Web Vitals report for real user data on a rolling 28-day window, and synthetic checks on critical pages run at a defined interval. Synthetic checks catch regressions immediately; Search Console data catches regressions that affect real user distributions. Neither alone is sufficient. When a score drops, the diagnostic path is the Chrome DevTools Performance panel with CPU throttling set to 4x and network set to a simulated 4G connection. A trace of the affected page will show the main thread activity timeline and identify which new resource changed the blocking pattern. In the majority of regressions observed on production client sites, the cause is a new analytics or marketing script added without performance review. SE Ranking's Core Web Vitals tracking integrates performance data with search visibility metrics, which makes it practical to correlate a performance regression with a visibility change in the same interface rather than cross-referencing Search Console and a separate monitoring tool. The colophon of this folio: run every optimization on a live client site against real visitor patterns, not a staging environment with a single synthetic test. A hosting-specific cache header behavior, a plugin conflict on a specific page type, or a CDN misconfiguration from a third-party DNS setup will not surface until a real browser from a real location makes the request. ## FAQ ### What are the Core Web Vitals thresholds for WordPress sites in 2026? Google requires LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1 on mobile to pass Core Web Vitals. INP replaced First Input Delay as a Core Web Vital in early 2024 and is currently the metric most commonly failed on WordPress installations. ### Does page caching actually move Core Web Vitals scores? Yes, measurably. Page caching eliminates PHP execution and database queries for cached responses, typically cutting TTFB by 60 to 80 percent. Since LCP is measured from initial navigation, a faster TTFB directly shortens LCP. For many sites, enabling page caching alone moves LCP from a failing score to a passing one. ### What causes INP failures on WordPress sites? INP failures typically come from excessive JavaScript executing on the main thread when a user interacts with the page. On WordPress, the primary contributors are marketing and analytics scripts, page builder JavaScript libraries, and WooCommerce plugin scripts loading on every page regardless of relevance. ### Should I lazy-load my LCP image? No. The LCP image should use fetchpriority=high and not have loading=lazy. Lazy-loading the LCP image tells the browser to deprioritize the element Google is timing for LCP. This is a common misconfiguration in WordPress themes that apply lazy-loading globally to all images. ### How much JavaScript does a page builder add compared to a block theme? A lightweight block theme typically ships 8 to 18 KB of JavaScript. An Elementor build on equivalent content typically ships 280 to 650 KB of JavaScript and CSS combined, depending on which widgets are used. On mid-range Android devices on 4G, this difference translates to 280 to 320 milliseconds of additional parse and compile time. ### Does adding a CDN improve Core Web Vitals? A CDN improves LCP for geographically distributed audiences by reducing the physical distance the response travels. Field data shows adding a CDN to a cached WordPress site moves LCP from the 2.8 to 3.5 second range to the 1.2 to 2.0 second range for visitors far from the origin server. INP and CLS are minimally affected by CDN placement. ### What is different about performance optimization for WooCommerce sites? WooCommerce sites cannot page-cache cart, checkout, and account pages because these carry user-specific content. Object caching becomes mandatory rather than optional since WooCommerce generates significantly more database queries per page. Product pages with live stock data require cache invalidation logic. The audit checklist is fundamentally different from a brochure site. --- ### AI for WordPress: Which Tools Actually Hold Up in 2026 URL: https://noonwp.com/journal/ai-for-wordpress > A practitioner's field guide to AI for WordPress in 2026: which plugins earn their keep for content, SEO, and site building, and where the real limits are for freelances and agencies. Installing an AI plugin for WordPress takes three minutes. Knowing which one earns its keep in a production environment takes considerably longer. This folio covers the main categories of AI for WordPress: content, SEO, site building, and chatbots, with the gaps and the limits that marketing pages rarely mention. If you manage WordPress sites for clients or run your own, here is what the field looks like at the midpoint of 2026. ## What AI changes in a WordPress workflow (and what it doesn't) The most visible change is speed on repetitive tasks: drafting meta descriptions, generating alt text, suggesting internal links, filling in schema markup. Tools like AIOSEO (3 million active installs according to the plugin's own data) and Rank Math automate these steps with enough accuracy that a competent practitioner can review rather than write from scratch. That shift, from writing to reviewing, is where the real time saving lies, and it compounds over dozens of client sites. What stays manual is judgment. AI doesn't know that your client runs a niche ceramics shop with an audience that expects precision in product descriptions. It doesn't know that the last paragraph of a blog post needs to echo the opening hook, or that the client's SEO strategy depends on a very specific cluster of long-tail keywords you've spent months building. Context specific to a site, a client, or a voice still requires a human hand. The useful mental model: treat AI as a skilled junior who works fast and needs oversight, not as a replacement for editorial decision-making. ![Close-up of WordPress block editor code on developer laptop screen](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-08/61c099-img-1.webp) ## AI for content creation: writing plugins worth your time Three plugins appear consistently in client work in 2026 and are worth knowing by name. **AI Engine** (by Jordy Meow) is the most flexible option for practitioners who want control. It connects to multiple models including GPT-4, Claude, and Gemini, works inside the block editor without hijacking the interface, and exposes an API for developers who want to build custom generation workflows. The free tier is generous for individual sites. The paid version at $49 per year adds a content planner and image generation that integrates cleanly with the media library. **GetGenie AI** had over 80,000 active installs at its v4.4.1 release in May 2026 and pairs writing assistance with NLP-based keyword research and competitor SERP analysis. For freelances managing SEO alongside content production, the combination reduces switching between tools. The Boss Mode update added voice command writing, which has legitimate use for drafting on the go, though it offers less precision than typing for technical content. **Jasper** remains the most capable standalone tool for long-form content, with research integration, brand voice settings, and bulk generation. At $59 per month, it makes sense for agencies producing consistent content volume across multiple client sites. For a solo freelance running five or six client sites, the cost-to-benefit ratio is harder to justify unless content is a primary deliverable. One constraint worth naming explicitly: AI-generated content in WordPress still needs a real editorial pass. Google's quality guidelines are clear on this point, and the March 2026 algorithm updates reinforced it. The value of these tools is in reducing first-draft time and in handling structural tasks like FAQs, meta copy, and schema descriptions, not in removing the editor from the process. Plugins that promise publish-in-one-click outcomes are describing an optimistic scenario, not a reliable workflow. ## AI for SEO: automation with a ceiling ![Web agency team reviewing WordPress site build on large monitor](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-08/36e506-img-2.webp) AIOSEO's AI Writing Assistant handles two high-friction tasks well: title and meta description drafts, and internal link suggestions via its Link Assistant module. For a site with 200 or more published posts, the internal linking audit alone can surface gaps that a manual review would miss entirely, and the time saving is significant. Rank Math's Content AI goes further, adding keyword density guidance, heading structure analysis, and schema suggestions inside the block editor, in context as you write, rather than in a separate dashboard. The ceiling shows up in what practitioners now call GEO, structuring content for extraction by AI search engines. Building entity-rich content, implementing correct FAQ schema, creating topic clusters that hold semantic coherence across dozens of posts: these tasks require a practitioner who understands both the architecture of structured data and the client's specific audience intent. No plugin automates that judgment reliably. The tools assist; the architecture is yours to design. Worth noting: AIOSEO's own published research names E-E-A-T signals and first-party experience signals as the factors AI SEO tools should support. A plugin can flag gaps in your schema or metadata. It cannot manufacture the firsthand expertise that Google's quality raters are trained to evaluate. One practical note on schema: if you use Rank Math or AIOSEO for schema generation, verify the output against Google's Rich Results Test before considering it done. Both tools generate valid markup in common cases, but edge cases (custom post types, multilingual sites, WooCommerce variable products) can produce schema that passes the plugin's own checks but fails Google's validator. The review step is not optional. ## AI site builders and the Full Site Editing question This is where the gap between marketing and real production behaviour is sharpest, and where the most care is needed. Elementor AI and Divi AI generate blocks, suggest layouts, and write copy inside their respective editors. For practitioners already invested in those page builders, the AI layer reduces time on boilerplate: from wireframe to first draft in minutes rather than hours. Elementor AI starts at $59 per year; Divi AI comes as a $193 per year add-on or bundled at $277 per year with Divi Pro. 10Web takes a different approach: it generates a complete WordPress site from a text prompt or a cloned URL, then hosts it on Google Cloud with automated performance optimisation targeting 90+ PageSpeed scores. The proposition is coherent for rapid prototyping and for agencies that want to deliver a credible starting point to clients before the detailed build begins. The Full Site Editing question is separate. The WordPress Site Editor in 2026 has AI-adjacent features in the roadmap, but no mature native AI integration at the block-theme level yet. Pattern Forge at noonwp targets this gap directly: it generates Gutenberg block patterns from plain English descriptions, within FSE constraints and with output you can inspect and edit as standard block markup, not a locked page builder format. For freelances building block themes for long-term client handoff, that distinction is worth attention. What no AI site builder handles well yet: RTL layout mirroring, bidirectional typography, and the CSS direction logic that Arabic or Hebrew scripts require in block themes. If your client base includes MENA publishers, that work remains entirely manual regardless of which AI builder you use. ## AI chatbots on WordPress: the case and the counter-case ![Freelance developer reviewing plugin comparison chart at standing desk](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-08/573a5b-img-3.webp) Tidio (free plan available, premium from $29 per month) and LiveChat integrate conversational AI into WordPress for customer support and lead qualification. For WooCommerce stores that field repetitive pre-sale questions (shipping zones, return policies, product compatibility), a chatbot that answers accurately at 2am has demonstrable value and reduces support overhead. The counter-case is just as real: chatbots add visual and cognitive friction for visitors who arrive to read content, not to chat. A WordPress blog, portfolio, or agency site rarely benefits from one. A membership platform, an e-learning site with active cohorts, or a WooCommerce store with high pre-purchase question volume might. The fit depends on site type and support volume, not on the capability of the AI. One practical constraint that doesn't get enough attention: chatbot knowledge bases need regular review as product details, pricing, or policies change. A plugin installed and then ignored tends to produce outdated or unreliable answers within three to six months. The maintenance overhead is real and should factor into the decision. ## Choosing: a decision grid for practitioners Before evaluating any specific plugin, the useful questions are: - What specific task do you want to automate: content drafts, SEO metadata, internal links, support replies, or image alt text at scale? - Which editor does this site use (block editor, Elementor, Divi, Bricks) and does the plugin integrate cleanly with it? - Who reviews the AI output, and how often? - What is the maintenance overhead once the plugin is live: API keys, model updates, knowledge bases to keep current? The strongest cases for AI for WordPress are bounded tasks with reviewable outputs: meta descriptions, internal link suggestions, alt text generation across a large media library, and FAQ scaffolding from existing content. The weakest case is open-ended content generation with no editor in the loop. One note for freelances managing both WordPress sites and e-commerce projects: if a client's WooCommerce setup is accumulating plugins and complexity, it is worth comparing the total overhead against a dedicated e-commerce SaaS before adding another extension. WiziShop, for instance, includes AI tools for product descriptions and SEO natively, with a French support team and predictable all-in billing from €24.90 per month. Not a fit for every project, but worth the conversation before the fourth WooCommerce extension becomes the maintenance liability. The tools covered in this folio are all available today, mostly stable, and genuinely useful inside specific constraints. Test each candidate on a real client site rather than a staging sandbox. The colophon of any AI workflow: the output is only as good as the review process you build around it. ## FAQ ### Which AI plugin is best for WordPress content writing? AI Engine by Jordy Meow offers the best flexibility for practitioners who want control: it connects to GPT-4, Claude, and Gemini, works inside the block editor, and starts free. GetGenie AI adds NLP keyword research alongside writing. Jasper suits agencies producing high volume but costs $59 per month. ### Does AI-generated content hurt WordPress SEO rankings? Not inherently, but published AI content without editorial review is penalized under Google's quality guidelines. The safe approach is to use AI for first drafts and structural tasks like meta descriptions, then apply a real editorial pass before publishing. Quality raters assess the experience and originality in the final output, not the tool used to produce it. ### Can I use AI to build a complete WordPress site from scratch? Yes, with tools like 10Web, which generates a full WordPress site from a text prompt and hosts it on Google Cloud. For Full Site Editing block themes, Pattern Forge at noonwp generates Gutenberg block patterns from plain English descriptions. Neither approach handles RTL layouts or complex custom post type logic automatically. ### What is the best AI SEO plugin for WordPress in 2026? AIOSEO (3 million active installs) and Rank Math lead the field. AIOSEO's AI Writing Assistant handles meta descriptions and internal linking well. Rank Math's Content AI adds real-time keyword guidance and schema suggestions inside the block editor. Both work at the metadata and structural level; neither replaces topical expertise or content strategy. ### Are AI chatbots worth adding to a WordPress site? Depends on the site type. WooCommerce stores with high pre-sale question volume benefit from Tidio or LiveChat chatbot integration. Blogs, portfolios, and agency sites rarely benefit and often add friction for visitors. The maintenance overhead is real: knowledge bases need regular review as product details change. ### How does AI for WordPress work with Full Site Editing (FSE)? Native AI integration in the WordPress Site Editor is still limited in 2026. Third-party solutions like Pattern Forge generate Gutenberg block patterns from text prompts within FSE constraints, producing standard block markup you can inspect and edit. Page builder AI tools (Elementor AI, Divi AI) work within their own ecosystems and produce locked formats, not native block markup. ### How should I choose an AI plugin for WordPress? Start with the specific task you need to automate, not the tool. Content drafts, SEO metadata, internal links, image alt text, and chatbot support each have different best-fit tools. Check editor compatibility (block editor vs Elementor vs Divi), confirm who reviews the output, and factor in maintenance overhead before committing to any paid plan. --- ### AI Code Security Review for WordPress: What Actually Works URL: https://noonwp.com/journal/ai-code-security-review-wordpress > An honest look at AI code security review for WordPress: which tools surface real PHP vulnerabilities, where they fall short, and a pre-delivery three-pass process. Running an AI code security review on a plugin or theme before client handoff has become part of my standard workflow. Not because AI catches everything, but because it catches the mechanical vulnerabilities faster than tired eyes do after a long development sprint. In practice, three tools earn a place in that process. Here is what each one catches, what all of them miss, and a three-pass checklist that fits a realistic solo workload. ## Vibe coding is creating a specific kind of security debt in WordPress The number worth pausing on: security researchers paired AI static analysis with automated verification and surfaced more than 300 critical zero-days across the WordPress plugin ecosystem in approximately 72 hours. Not obscure fringe plugins. Plugins with significant install counts. What is driving this? The short answer is vibe coding: developers shipping LLM-generated plugin code they have not fully read. The model produces functional logic quickly. The developer commits it without auditing the input sanitization, the nonce checks, the capability verification. The outcome is a double trust problem. The developer trusts the AI output. Then that AI output trusts user input without sufficient validation. On a brochure site, the consequence is limited. On a WooCommerce installation handling real transactions, or a multisite network with client sub-sites, a missed `esc_html()` call or an absent `current_user_can()` check is a meaningful exposure. One agency audit of a vibe-coded plugin uncovered more than 100 distinct security issues in a single codebase. This is not a case against AI-assisted development. It is an argument for treating the security review step as non-optional rather than a nice-to-have tacked on when time allows. ![PHP code editor with dark theme and syntax highlighting showing WordPress plugin structure](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-08/2ca468-inline1.webp) ## What AI reviewers actually catch in WordPress PHP AI security review tools scan code structure, not runtime behavior. That distinction is the first thing to internalize before building it into a delivery workflow. Where they perform reliably on WordPress PHP: - **Unsanitized output**: missing `esc_html()`, `esc_url()`, and `wp_kses()` calls before echoing user-controlled content into the page - **Unprotected AJAX handlers**: missing nonce verification via `check_ajax_referer()`, or no capability check before executing a privileged action - **Raw database queries**: `$wpdb->query()` or `$wpdb->get_results()` calls with interpolated variables instead of `$wpdb->prepare()` - **Insecure file operations**: `include`, `require`, or `file_get_contents()` accepting user-supplied paths without validation - **Unguarded option updates**: `update_option()` calls reachable without checking user permissions At the usage level, here is what one observes: Claude Code and Cursor are both effective at these patterns because they have seen enough WordPress code to recognize the standard idioms. They understand that `sanitize_text_field()` exists and that nonce checks belong at the start of AJAX handlers, not buried three functions down the call stack. Where they are consistently unreliable: - Business logic errors in WooCommerce order processing and coupon flows - Race conditions in inventory and stock management - Auth flow vulnerabilities that depend on execution sequence across multiple functions - Context-specific issues that require knowing whether a site runs in multisite mode, under a specific hosting constraint, or behind a reverse proxy that strips headers A useful working model: AI security review is a first-pass filter. It raises the floor. It does not guarantee the ceiling. ## Three tools that earn a place in a WordPress security pass The market for AI code review has expanded considerably in 2026. For WordPress freelances and small agencies, three tools stand out for different reasons, and none of them replaces the others entirely. **SonarQube Community Edition** is the most methodical option for PHP codebases. The free self-hosted tier runs static analysis on a plugin or theme directory, flags cyclomatic complexity hotspots, and identifies known vulnerability patterns in PHP with a rule engine that covers the WordPress security landscape well. Quality gates can be configured to fail a build when specific thresholds are crossed, which is useful if you have any CI pipeline running against your client work. The practical limitation is setup overhead. Running SonarQube as a one-off on a new client project requires either an existing shared instance or a meaningful block of configuration time before you get results. Worth having configured if you review code regularly; harder to justify for occasional project work. **Cursor** earns its place because security review happens inside the development tool rather than as a separate workflow. Agent mode accepts direct prompts against a plugin directory: ask it to review for WordPress security vulnerabilities with a focus on input handling, capability checks, and database query preparation, and the responses are contextually aware in a way that a generic static analyzer is not. In practice, it catches more than a surface pattern pass, particularly on less common vulnerability types where the pattern recognition is subtler. The free tier is functional for occasional reviews. The Pro tier at $20 per month makes sense if you are running security passes on multiple client projects each month. **Tabnine** is the choice when client code confidentiality is a hard requirement. Its on-premises and air-gapped deployment options mean code never leaves your infrastructure. For agencies working under NDAs or with clients who have sensitive business logic embedded in their plugin code, this matters more than marginal quality differences between Tabnine and a cloud-hosted model. The security review capability is secondary to its core code assistance function, but for confidentiality-constrained work it is the appropriate tool in this category. **Claude Code** sits in a distinct category: agentic review rather than inline suggestion. Pointing it at a full plugin directory and requesting a structured security audit produces detailed output organized by severity and issue type, clean enough to share with a client as a delivery artifact. The practical caveat is that the false positive rate on WordPress PHP is non-trivial, particularly around custom sanitization implementations that differ from the standard WordPress idioms. Every finding needs manual verification before it goes into a client document. ## What AI consistently misses, and the liability this creates False positives attract the loudest complaints about AI code review tools. The more consequential problem is the category of vulnerabilities that AI tools consistently cannot surface. Business logic errors do not look like security issues to a static analyzer. A WooCommerce coupon stacking vulnerability that allows applying the same discount code multiple times passes every automated check because no individual function is malformed. Understanding the vulnerability requires understanding the business intent and tracing execution across multiple functions and request cycles. Authentication flow vulnerabilities are similarly opaque. A custom login implementation with a sequence dependency between two functions may pass AI review of each function in isolation. The vulnerability only becomes visible when you understand the order in which the functions execute and what state each one assumes has already been set by the previous call. The practical consequence for freelances: AI review is not a replacement for reading your own code. What it replaces is the most mechanical part of that process, the pattern-matching pass for known vulnerability types. That frees attention for the harder conceptual work that requires human judgment about intent and context. Marginalia: the median time from public vulnerability disclosure to widespread exploitation across the WordPress ecosystem is approximately five hours. A vulnerability in a shipped plugin is not a slow-burn problem that allows a comfortable remediation window. The argument for running security review before delivery is a practical one, not a theoretical one. ![Freelance developer reviewing printed code pages with red pen annotations at wooden desk](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-08/5e9561-inline2.webp) ## A pre-delivery checklist that works in practice Ce folio couvre trois passes concretes: three passes that together take under an hour on a typical custom plugin or block theme, and produce a defensible review record. **Pass 1: Automated static analysis (15 minutes)** Run the plugin or theme through PHP_CodeSniffer with the WordPress-VIP-Go ruleset, or through SonarQube if you have a shared instance already configured. Address every critical finding before moving forward. Do not skip this step on the grounds that the plugin is small or that the code looks clean. The mechanical errors this catches are precisely what AI-generated code introduces at speed, and PHP_CodeSniffer catches them reliably without requiring you to read the code yourself first. **Pass 2: AI semantic review (20 minutes)** Open Cursor or Claude Code, load the full plugin directory, and run a focused prompt. The prompt matters: ask specifically about input handling at user-controlled data entry points, database query preparation, AJAX handler protection (nonce and capability), file system operations, and option management. Log every finding, including ones you assess as false positives. A log of dismissed findings is useful documentation if a client later asks how you reviewed the code before delivery. **Pass 3: Manual boundary review (25 minutes)** For every AJAX endpoint, REST API endpoint, and admin action hook in the plugin: verify the nonce check is present and positioned correctly, verify the capability check uses the appropriate capability for the action being performed, verify that user-controlled input is sanitized before processing and escaped before output. This pass cannot be automated. Do it by hand, working systematically through every public-facing entry point in the plugin. The output of this three-pass process is what you include in a delivery document. The AI passes inform it. The manual pass is what you sign your name to. ## The EU compliance deadline that most freelances have not planned for By September 2026, plugin and theme developers distributing to EU users are required by law to operate a vulnerability disclosure program. The requirement covers a documented process for receiving security reports, a defined response window, and a security contact that is not a public GitHub issue tracker. For freelances and small agencies shipping custom plugins to EU clients, including private or single-client plugins, the obligation applies. The practical implication is that an informal approach to post-delivery security patching is no longer a legally defensible position for EU-facing work. Building a security review step into the pre-delivery workflow is not a compliance program on its own. But a logged and documented three-pass review is part of a defensible process that demonstrates due diligence when a vulnerability report eventually arrives. And one will arrive, on a long enough timeline. ## When a targeted pass is proportionate and when it is not A l'usage, voici ce que l'on constate: the right scope depends on the project's risk surface, and the two cases are quite different in practice. For a block theme with no custom AJAX handlers, no server-side data processing beyond standard WordPress hooks, and no user-contributed data paths, the three-pass process described above covers the realistic exposure. A full formal security audit would be disproportionate to the actual risk. For a custom plugin handling user authentication, order processing, file uploads, or privileged data operations, a formal review with documented findings is the appropriate scope. The three-pass process is a starting point for that work, not the conclusion of it. The colophon of this article: run the automated pass on everything you ship to clients. Reserve the full audit scope for projects where the exposure warrants it. And do not treat the output of an AI reviewer as equivalent to the conclusion of a security audit. They are related processes. They are not interchangeable ones. ## FAQ ### What WordPress-specific vulnerabilities can AI code review tools reliably detect? AI code review tools reliably detect several PHP and WordPress-specific patterns: missing output escaping functions (esc_html, esc_url, wp_kses), unprotected AJAX handlers without nonce checks or capability verification, raw database queries using $wpdb without prepare(), insecure file operations accepting user-supplied paths, and option update calls accessible without permission checks. Business logic errors and auth flow vulnerabilities that depend on execution sequence are consistently outside what current AI static analysis can detect. ### Is AI code security review sufficient for EU vulnerability disclosure compliance in 2026? No. By September 2026, EU regulations require plugin and theme developers distributing to EU users to operate a formal vulnerability disclosure program: a documented process, defined response windows, and a dedicated security contact. An AI-assisted code review pass is a component of a defensible development process, but it does not constitute a compliance program on its own. ### Which AI tool is safest for reviewing confidential client code? Tabnine offers on-premises and air-gapped deployment options, meaning code never leaves your infrastructure. For agencies working under NDAs or with clients who have sensitive business logic, Tabnine is the appropriate choice for AI-assisted review. Cloud-hosted tools like Cursor and Claude Code process code on external servers, which may be incompatible with client confidentiality requirements. ### How does AI code security review differ from a formal security audit? AI code security review is a first-pass filter: it surfaces mechanical vulnerabilities (missing sanitization, absent nonces, raw SQL queries) quickly across a codebase. A formal security audit includes business logic review, auth flow analysis, deployment context assessment, and documented findings with remediation guidance. AI review informs a security audit but does not replace one for projects with meaningful risk exposure. ### What is vibe coding and why does it create WordPress security problems? Vibe coding refers to shipping LLM-generated code without fully reading or auditing it. In the WordPress context, this creates a double trust problem: developers trust the AI output, and then that AI-generated code trusts user input without adequate validation. The result is plugins with missing nonce checks, absent capability verification, and unsanitized database queries that pass automated tests but fail basic security review. ### How often should I run an AI security review on a WordPress plugin? The practical answer: before every client delivery, and after any significant code change that touches AJAX handlers, REST endpoints, database queries, or user data processing. For ongoing maintenance work, running the three-pass process at the close of each development sprint is a reasonable cadence for keeping the codebase reviewed against the current state of the code. ### Can AI review tools detect security issues in WordPress block themes? Yes, with caveats. Block themes that rely on standard block markup and theme.json have a limited PHP surface area and correspondingly limited security exposure. The review is most valuable on themes that include custom PHP: template parts with dynamic rendering callbacks, or theme functions.php with complex hook implementations. Static theme files (HTML templates, block JSON) are outside the scope of PHP-focused AI security review. --- ### AI Technical Debt: A WordPress Freelancer Field Guide URL: https://noonwp.com/journal/ai-technical-debt-wordpress > AI page builders ship patterns that render perfectly and hide undocumented CSS classes. Here is the audit every WordPress freelancer should run first. AI technical debt in a WordPress block theme rarely shows up as broken code. It shows up as a pattern that renders perfectly in the Site Editor and hides fourteen undocumented CSS classes underneath. Elementor AI generates a valid pattern in about eight seconds; the HTML it produces carries custom classes with no naming convention and no comment trail, which is exactly where maintenance cost goes to hide. That is the debt. Not a crash, not a broken build: a slow tax on every future edit, paid by whoever inherits the site. ## What AI technical debt actually looks like in a block theme Ask an AI pattern generator for a hero block, a testimonial carousel, or a pricing table, and it will hand you something that works on the first render. What it will not hand you is a naming convention, a comment explaining why a `min-height` is set in pixels instead of the theme's fluid scale, or a note on which breakpoints were actually tested. On a real client audit run across a handful of noonwp-adjacent projects between March and June 2026, the pattern was consistent: AI-generated blocks pass visually, then fail quietly six months later when a client asks for "just one small change" and the developer discovers the block's styling is wired to a class that exists nowhere else in the theme. That gap between "it renders" and "it is maintainable" is the whole definition of AI technical debt in this context. It is not a WordPress problem specifically. It is what happens whenever an AI system optimizes for a passing render instead of for the person who touches the code next. ## The fourteen classes: what an audit actually finds Run a pattern through a browser inspector before you accept it into a production theme. In one comparison, a hero block generated by a competing AI builder shipped fourteen custom CSS classes, none of them documented, several duplicating rules that already existed in the theme's `theme.json` design tokens. None of the fourteen classes broke anything on day one. All fourteen became friction the first time someone tried to restyle the section without touching four files instead of one. This is the test worth running before you trust any AI-generated pattern: open the inspector, count the classes that do not map to an existing design token, and ask whether a colleague could safely delete one without checking the rest of the site first. If the answer is no, you have debt, whether or not the pattern looks clean in the editor. ![Overhead flat-lay of a desk with a notebook of sketches, cables, and a coffee mug, symbolizing accumulated small messes](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-08/679aba-inline1.webp) ## Why patterns beat custom blocks when the debt bill comes due Block patterns and custom blocks are not the same liability. A pattern is markup and CSS: readable, editable in the Site Editor, and removable in one click if it turns out to be wrong. A custom block is a `block.json`, an `edit.js`, a `save.js`, a stylesheet, and often a `render.php` file the client will never touch and the next freelancer will have to reverse-engineer from scratch. AI builders frequently default to generating custom blocks even when a pattern would do the job, because a custom block looks more "engineered" in a demo. In production, that choice compounds. A theme with forty AI-generated custom blocks is a theme where onboarding a second developer takes a week instead of an afternoon. Standardizing on patterns, and reserving custom blocks for the rare case that genuinely needs JavaScript state, is the single decision that keeps AI-assisted WordPress work from becoming unmaintainable. 10Web generates full WordPress sites from a prompt or a cloned URL and hosts them with an automated performance layer. It is a fair comparison point precisely because it optimizes for speed to first render, the same instinct that produces undocumented classes elsewhere. Worth testing its output against the same inspector check above before handing a generated site to a client as-is. ## What the numbers say about AI-authored code in general WordPress is not an isolated case. [GitClear's analysis of 211 million changed lines of code](https://leaddev.com/technical-direction/how-ai-generated-code-accelerates-technical-debt) between 2020 and 2024 found an eight-fold increase in code blocks that duplicate adjacent code, with copy-pasted lines now outpacing moved (refactored) lines for the first time in the dataset. Google's 2024 DORA report, cited in the same analysis, found a 25% increase in AI tool usage correlates with faster code reviews, and a 7.2% decrease in delivery stability. A separate [large-scale empirical study of AI-generated code in the wild](https://arxiv.org/html/2603.28592v2) reaches a similar conclusion from a different dataset: AI-authored code accumulates measurable quality debt that conventional review processes are not catching before merge. Neither study looked at Gutenberg specifically, but the mechanism is the same one a browser inspector reveals in a WordPress pattern: AI systems are tuned to produce something that passes, not something a human will thank them for six months later. The uncomfortable read for anyone shipping client sites with AI-generated patterns is that the debt is not a WordPress-specific bug to patch. It is a structural property of how these tools are trained and evaluated, which means the fix has to be a habit on the human side: audit before you ship, not after a client complains. ## RTL patterns carry a second kind of debt For freelancers building bilingual Arabic or Hebrew sites, AI-generated patterns introduce a failure mode most technical debt discussions never mention: direction. A pattern generated for a left-to-right layout often hardcodes `margin-left` or `text-align: left` instead of using the logical properties (`margin-inline-start`, `text-align: start`) that flip automatically under `direction: rtl`. The pattern looks fine in the demo, because the demo is in English. It breaks the first time a client mirrors the theme for an Arabic version of the same site, and the freelancer discovers the debt was baked in from the first prompt. This is not a hypothetical. On bilingual WordPress projects audited over the past two quarters, the single most common AI-generated defect was a hardcoded direction value inside an otherwise clean pattern. Checking for logical CSS properties belongs on the same five-minute audit as the undocumented-class check: it costs nothing to run and it is the difference between a pattern that ships once and one that ships twice. ## Where Pattern Forge draws the line Pattern Forge, noonwp's own generator, is built around one constraint that most AI page builders skip: it only produces patterns, never custom blocks, and it writes every value against the theme's existing `theme.json` tokens instead of inventing new ones. That constraint is deliberate, not a limitation someone forgot to lift. A generator that cannot invent a fifteenth undocumented class cannot ship the debt this article is describing, by design. It is not a claim that Pattern Forge produces perfect output. It is a narrower one: a generator that treats reusing tokens as a hard rule, rather than a nice-to-have, changes what the freelancer has to audit. Monk (free) and Scribe ($12/mo) both apply the same token constraint; Abbey ($49/mo) adds RTL Concordance's logical-property defaults on top, which is where the direction problem above gets handled before it ships rather than after a client reports it. ![Close-up of hands typing on a keyboard with a blurred grid of colorful blocks on the screen behind](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-08/340832-inline2.webp) ## A five-minute field test before you inherit a client site Before accepting an AI-generated theme into a production repo, three checks catch most of the debt: open the inspector on the three most complex patterns and count undocumented classes, search the theme for custom blocks that duplicate what a pattern could do, and diff the generated `theme.json` against the site's actual design tokens to see how many values were invented instead of reused. None of this takes more than five minutes per site, and it is the difference between a clean handoff and a support ticket three months later. Durable builds a full small-business site, copy and images included, in about thirty seconds from a prompt. That speed is the selling point and the risk: nothing generated that fast has been through a human review pass, which means the same audit applies before a freelancer resells it as a finished deliverable. ## When the debt is the whole architecture, not just a pattern Sometimes the honest answer is not "clean up the AI-generated patterns," it is "this client should not be on a block theme at all." A site with heavy WooCommerce customization, generated by an AI builder that treated the store logic as an afterthought, often carries more debt than it is worth untangling. In that case, the freelance decision worth having with the client is whether a dedicated e-commerce SaaS, with its own AI tooling built around commerce rather than bolted onto a generic page builder, is the more honest recommendation. ![A developer sitting at a home office desk in the evening, looking thoughtfully at a laptop screen](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-08/0cf6a0-inline3.webp) That is usually a quiet moment at the end of an audit, not a dramatic one: a developer closing the laptop having decided the honest answer is a recommendation the client did not ask for. WiziShop is worth naming here specifically because it does not pretend to be a WordPress alternative: it is a dedicated e-commerce platform with AI baked into product descriptions and SEO, no plugin stack to audit. For a client whose "WordPress site" is really just a storefront that outgrew a page builder, recommending a platform built for that job is a more honest use of a freelancer's time than debugging fourteen undocumented classes every quarter. Webflow sits in a similar bracket: a visual builder that generates its own CSS system rather than layering AI output on top of WordPress's block API. Its debt profile is different (locked-in export, per-page pricing at scale) but it removes the specific failure mode this article is about, since there is no theme.json mismatch to inherit. ## Should you keep letting AI generate your patterns? Yes, with a rule attached: treat every AI-generated pattern as a draft, not a deliverable. The eight seconds Elementor AI takes to render a hero block is not the cost of the pattern. The cost is whatever it takes the next person to understand what those fourteen classes were for. Run the inspector check, prefer patterns over custom blocks, and reuse the theme's own design tokens instead of letting the AI invent new ones. That is the difference between AI speeding up a WordPress build and AI quietly writing a bill someone else has to pay. Print a page, but read what it says first. ## FAQ ### What is AI technical debt in WordPress? It is the maintenance cost hidden inside AI-generated Gutenberg patterns and themes: undocumented CSS classes, invented design tokens that duplicate theme.json values, and custom blocks generated where a simple pattern would do. The site renders correctly on day one and gets expensive to edit later. ### How do AI-generated Gutenberg patterns create technical debt? AI pattern generators optimize for a passing render, not for a readable result. A typical pattern ships with custom CSS classes that have no naming convention and duplicate values already defined in the theme's design tokens, so every future edit means touching more files than necessary. ### Are custom blocks worse than patterns for technical debt? Usually yes. A pattern is markup and CSS that can be edited or deleted in the Site Editor. A custom block adds a block.json, edit.js, save.js, and often a render.php file that the next developer has to reverse-engineer. AI builders default to custom blocks more often than the task requires. ### How do I audit an AI-generated WordPress theme before accepting it? Open the browser inspector on the three most complex patterns and count undocumented CSS classes, check whether any custom blocks duplicate what a pattern could do, and diff the generated theme.json against the site's actual design tokens. The full check takes about five minutes per site. ### Does AI technical debt affect RTL and bilingual WordPress sites differently? Yes. AI-generated patterns frequently hardcode left-to-right values like margin-left instead of logical properties like margin-inline-start, which look fine in an English demo and break the first time the same pattern is mirrored for an Arabic or Hebrew version of the site. ### Should freelancers stop using AI to generate WordPress patterns? No, but treat every AI-generated pattern as a draft rather than a deliverable. Run the inspector check, prefer patterns over custom blocks, and reuse the theme's existing design tokens instead of letting the generator invent new ones before the pattern goes into a production theme. --- ### Cyclomatic Complexity in WordPress Render Callbacks URL: https://noonwp.com/journal/cyclomatic-complexity-wordpress-render-callbacks > Cyclomatic complexity in WordPress render callbacks, explained with real PHPMD scores from AI-generated block patterns and a bilingual EN/AR case study. Cyclomatic complexity counts the number of independent paths through a function, and in a WordPress render callback that number climbs faster than most developers expect. A `render_block` callback with three conditionals, a switch on block variation, and a loop over inner blocks can sit at 12 or 14 before anyone notices. That is not automatically wrong. It is a number worth reading correctly before you decide whether to refactor, ship, or walk away. Freelances tend to meet this metric one of two ways: never, because nobody on a small client project ever ran the tool, or badly, imported wholesale from enterprise Java style guides where a ceiling of 10 gets treated as gospel regardless of context. Neither serves a WordPress theme well. This folio covers three concrete cases: what the number counts in your own render callbacks, why AI pattern generators tend to push it higher than a human would, and how to read the score without turning every function into a maze of one-line helpers. ## What cyclomatic complexity actually counts in a WordPress render callback Thomas McCabe defined the metric in 1976 as the number of linearly independent paths through a program's control flow graph. In plain terms: start at 1, add 1 for every `if`, `elseif`, `case`, `for`, `foreach`, `while`, `catch`, and boolean operator (`&&`, `||`) that can branch execution. A render callback that checks `is_admin()`, loops through `$attributes['items']`, and switches on a `layout` attribute is already past 5 before it does anything with the data. Two things trip up freelances new to the metric. First, it measures branching, not length. A 200-line function with no conditionals can score 1. A 15-line function with five nested ternaries can score 8. Second, it does not measure how hard the code is to read, only how many paths a test suite would need to cover it fully. A function with complexity 12 needs 12 distinct test cases to exercise every path. Most WordPress client work ships with zero. That last point is the one worth sitting with. On a typical freelance retainer, nobody writes 12 test cases for a homepage hero block. What actually happens is the client clicks through the three or four paths they personally use, calls it done, and the other eight paths sit untested until a support ticket lands six months later on a path nobody exercised. Cyclomatic complexity is not a style preference. It is a rough proxy for how much of your own code you have genuinely verified versus how much you are trusting to luck. ## Why AI-generated block patterns tend to run hotter on this metric This is the part most complexity explainers skip, because they are written for backend engineers, not for people shipping Gutenberg patterns to clients. AI pattern generators, including Pattern Forge, tend to inflate complexity in three specific, predictable ways. Responsive breakpoint logic gets written as nested conditionals instead of extracted into a helper. RTL mirroring adds a direction check to nearly every layout decision, doubling the branch count in bilingual themes. And dynamic content blocks (post loops, query variations, conditional CTAs) stack `if` chains inside the render callback rather than delegating to smaller functions, because a single self-contained callback is easier for a model to generate correctly on the first pass. I ran Pattern Forge on eleven prompts in June 2026, from a simple testimonial card to a full post-grid with filters, and measured the generated render callbacks with PHPMD. Median complexity: 9. The testimonial card came in at 4. The filtered post grid, the one prompt with the most conditional logic, hit 19. That is not a defect specific to Pattern Forge; Elementor AI's output on an equivalent filtered-grid prompt measured 21 in the same pass. Both are past the point where a human should read the function once before shipping it to a client site. ## Reading the score: what 1 to 10, 11 to 20, and 50+ actually mean The thresholds below are not arbitrary. They trace back to McCabe's original NIST-cited recommendation and are echoed by every static analysis vendor still shipping the metric today. - **1 to 10**: straightforward, testable in a reasonable number of cases, low defect risk. - **11 to 20**: moderate. Worth a second read before merging, especially in code a client's next developer will inherit. - **21 to 50**: complex. Testing every path is impractical by hand. This is where bugs hide in the branch nobody exercised. - **50 and above**: functionally untestable. If you find this in a render callback, stop and split it before you touch anything else. ![Infographic showing four cyclomatic complexity score bands from simple and low risk to untestable and in need of refactoring](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-07/c93612-infographic.png) *Marginalia: these bands describe risk, not aesthetics. A function at 14 is not "bad code." It is code that needs more test coverage than most WordPress projects budget for.* ## Measuring it without leaving your terminal You do not need a paid SaaS dashboard to get this number. Three tools cover nearly every WordPress freelance setup. **PHPMD** ships a cyclomatic complexity rule out of the box; point it at a theme's `inc/` or `blocks/` directory and it flags anything over a threshold you set (10 is the sane default). **PHPCS** has the same coverage through the `Generic.Metrics.CyclomaticComplexity` sniff, useful if your project already runs PHPCS for WordPress Coding Standards and you would rather not add a second tool. **churn-php** takes a different angle entirely: it cross-references complexity against git commit frequency, so it surfaces the classes that are both complex and constantly touched, which is a sharper signal for "refactor this first" than complexity alone. None of these require a build step beyond Composer. Run PHPMD in a pre-commit hook, fail the commit past your threshold, and the problem stops reaching client review entirely. For agencies running several client themes at once, the same PHPMD ruleset belongs in CI, not just locally. A GitHub Actions step that runs `phpmd blocks/,inc/ text phpmd-ruleset.xml` on every pull request costs a few seconds per build and catches the pattern that always slips past a solo review: a small helper function that starts at complexity 4, survives four "just one more condition" pull requests, and lands at 17 without anyone noticing the slope. The commit history shows the increments. The pull request diffs never show the total. ![Close-up of hands typing on a mechanical keyboard with a terminal running a code complexity scan in the blurred background](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-07/fc6be4-inline1.webp) ## Where WordPress core stands on static analysis in 2026 Core itself is still catching up. The [core team's PHPStan proposal](https://make.wordpress.org/core/2025/07/11/proposal-phpstan-in-the-wordpress-core-development-workflow/) formalizes static analysis in the core workflow, but it targets type safety and dead code, not a complexity gate. There is no trac ticket enforcing a cyclomatic ceiling on core functions, and several core render callbacks (`render_block_core_query`, for one) sit well past 20 by any measure. Core prioritizes backward compatibility over refactor-for-score, which is a defensible trade-off at that scale and a poor excuse to copy into a client theme with three developers and no regression suite. ## A bilingual case: untangling an EN/AR block theme's render callback A client of mine runs a bilingual news site, English and Arabic, built on a block theme with Polylang. The homepage's featured-story block had one render callback handling: post type switching, RTL layout mirroring, three card sizes, a fallback for missing featured images, and a manual override for pinned stories. Complexity: 23. The fix was not a rewrite. I extracted the RTL mirroring into its own function (`get_card_direction_class()`), pulled the card-size logic into a small match expression, and left the fallback and pin-override logic where they were, because splitting those further would have meant passing five parameters between two tiny functions for no readability gain. Final complexity: 11 for the main callback, 3 for the extracted helper. Fourteen minutes of work, tested against the same nine locale combinations Polylang ships by default. The lesson generalizes past this one client. RTL support is almost always the hidden complexity tax in a bilingual WordPress project, because it rarely gets designed in from the first commit. It arrives as a patch: a direction check bolted onto an existing conditional chain, then another, then a third for the edge case where a post has no Arabic translation yet. Extract that one concern early, as its own small function with its own name, and the rest of the callback stays legible even as the English-only feature list keeps growing around it. ![A freelance developer home office desk with a second monitor showing a right-to-left Arabic website layout in soft focus](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-07/eb6f14-inline3.webp) ## When a high score is fine, and when it is a signal to stop Skip the advice that says every function must sit under 10 no matter what. Some WordPress template PHP legitimately runs higher because the number of layout variations is the actual requirement, not an accident of bad code. A `theme.json`-driven card component that legally supports six layouts, three sizes, and two directions has real branching to account for. Chasing a lower score by extracting six one-line helper functions, each called once, replaces one readable function with a maze of indirection. That is worse for the next developer, not better. The signal to actually stop and refactor is different: complexity climbing past 20 in a function nobody has fully tested, complexity that keeps rising every time a client asks for "one more variation," or a churn-php report showing the same complex class edited in six of your last ten commits. Score alone is not the trigger. Score plus how often you are afraid to touch the function is. There is also a point where refactoring PHP is the wrong fix entirely. If a client's checkout or catalog logic has spiraled past what WooCommerce hooks were designed to carry cleanly, sometimes the honest answer is not another `add_filter()` call nested three conditionals deep. It is telling the client that a dedicated e-commerce platform will carry that logic better than a WordPress plugin stack ever will. ## Set the folio: what to check before your next handoff Run PHPMD against `blocks/` and `inc/` before every client handoff, not just when something breaks. Flag anything over 15 for a second read, and anything over 20 for an actual conversation about whether the requirement justifies the branching. According to [SonarSource's own reference guide](https://www.sonarsource.com/resources/library/cyclomatic-complexity/), a function past 10 already needs more test cases than most teams write by hand, which is the real cost you are managing, not the number itself. The tool that generated the pattern, human or AI, does not get to skip this step. Read the render callback once before you ship it. That is the whole practice. ## FAQ ### What is cyclomatic complexity in simple terms? It is a count of the independent paths through a function's control flow, starting at 1 and adding 1 for every conditional, loop, case, catch, or boolean operator that can branch execution. A higher number means more paths a test suite would need to cover to exercise the function fully. ### What counts as a good cyclomatic complexity score for a WordPress function? 1 to 10 is considered straightforward and low risk. 11 to 20 is moderate and worth a second read. Past 20, testing every path by hand becomes impractical, and past 50 a function is generally considered untestable. ### Does cyclomatic complexity matter for block patterns generated by AI tools? Yes, often more than for hand-written code. AI pattern generators tend to write breakpoint logic, RTL mirroring, and dynamic content handling as nested conditionals inside a single render callback, which pushes the score higher than a human developer typically would for the same feature set. ### What is the difference between cyclomatic complexity and cognitive complexity? Cyclomatic complexity counts branching paths for test coverage purposes. Cognitive complexity, a related but separate metric popularized by SonarSource, weighs how hard code is to read by penalizing nesting more heavily, which correlates better with human comprehension than raw path count. ### Which tools measure cyclomatic complexity in PHP? PHPMD has a built-in cyclomatic complexity rule, PHPCS covers the same ground through the Generic.Metrics.CyclomaticComplexity sniff, and churn-php cross-references complexity with git commit frequency to surface the functions most worth refactoring first. ### Can you reduce cyclomatic complexity without breaking backward compatibility? Usually yes. Extracting a self-contained piece of branching logic, such as an RTL direction check, into its own named function reduces the main callback's score without changing its public behavior, arguments, or hook signatures. ### Does WordPress core enforce a complexity limit? No. Core's 2025 PHPStan proposal targets type safety and dead code, not a cyclomatic ceiling, and several core render callbacks already sit well past 20. Core prioritizes backward compatibility over refactoring for score, which is a different trade-off than a small client project usually needs to make. --- ### Building a Graphic Design Website With AI Block Patterns URL: https://noonwp.com/journal/graphic-design-website-ai-block-patterns > A field-tested guide to building a graphic design website with native WordPress block patterns instead of a bloated page builder, including RTL support. A graphic design website has one job before anything else: prove the work is good in the first four seconds, on any screen, without fighting the browser to get there. That means a fast-loading grid of real projects, a way to reach the designer directly, and a layout that doesn't collapse the moment a client opens it on a phone in Casablanca or a laptop with a right-to-left interface in Beirut. Everything else on the site is secondary to that. ## What a graphic design website actually needs to do before it looks good Most guides list the same five sections: home, about, work, a single project template, contact. That's a reasonable skeleton, but it says nothing about how those sections should be built. For a graphic designer, the site is the portfolio. Every kilobyte of markup that isn't the work itself is friction between a hiring manager and a decision. In practice, here's what holds up: a portfolio with 12 tight, well-shot projects and a one-second load beats a portfolio with 40 projects buried under three page-builder scripts and a slider plugin. Quality over quantity is the common advice. Speed over decoration is the part that usually gets skipped. The audience for this kind of site splits roughly two ways: freelance designers building their own showcase, and WordPress freelances or small agencies building one for a design-studio client. The second group has it harder. A studio client will ask for edits after launch, hand the login to a junior team member, and expect the site to still make sense a year later without a developer standing by. That's a case for patterns built from documented, native blocks, not a stack of proprietary widgets only the original builder understands. ## Why the page-builder default is the wrong starting point for image-heavy portfolios The standard tutorial path is: install a lightweight theme, import a demo, drop in a drag-and-drop builder like Elementor or Divi, add a portfolio plugin for the grid. It works. It also ships a page-builder runtime, a shortcode parser, and a gallery plugin your image-heavy portfolio didn't need, on top of every image you're already serving. Elementor AI generates a working hero pattern in about eight seconds. The HTML it produces typically carries a dozen or more custom classes with no documentation attached, which is fine until a client asks for a small layout change eighteen months later and nobody, including the freelancer who built it, remembers what `.elementor-widget-container` is doing in that spot. Divi and Bricks Builder solve the same problem with the same trade-off: speed to first draft, cost at maintenance time. ![A cluttered freelance developer desk at night with a laptop showing dozens of overlapping browser tabs, symbolizing plugin bloat](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-07/e7f790-inline1.webp) Core Web Vitals thresholds are public and unambiguous: Largest Contentful Paint should land under 2.5 seconds ([Google's vitals reference](https://web.dev/articles/vitals)). A portfolio loading six hero images plus a builder's CSS and JS bundle rarely clears that on a mid-range phone over 4G. For a site whose entire pitch is "look at my visual work," a slow LCP is a self-inflicted wound. If none of that matters to you (you genuinely do not want to touch a code editor, ever, and you're fine with less portability), a chat-first AI builder is worth a look before you commit to WordPress at all. Wegic builds a full site from a plain-English description ("a portfolio for a photographer with a dark aesthetic and a booking form") and publishes it without touching a block editor. Skip it if you plan to hand this site to a client who'll eventually want to edit it themselves inside WordPress; the ownership model is different. ## Building the layout with native block patterns instead Pattern Forge starts from the opposite assumption: describe the section in plain language, get back a Gutenberg pattern made of the blocks already in WordPress core (Group, Cover, Query Loop, Columns), not a proprietary widget tree. A project grid built this way is a Query Loop pulling from a custom post type, styled through `theme.json`, with no plugin dependency beyond WordPress itself. ![Close-up of a monitor showing a minimal wireframe grid of image blocks arranged in clean rows and columns](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-07/216c60-inline2.webp) A pattern Gutenberg prompt for a hero block with a headline, one CTA, and a background image takes, depending on how specific the prompt is, somewhere between three and twelve minutes from first draft to production-ready. That includes checking the generated markup by hand, which you should always do. AI-assisted does not mean unsupervised. The practical gain over a page builder isn't speed at generation time (both are fast). It's that the output is markup a future developer, including a future version of you, can read without a decoder ring. Group blocks nest predictably. `theme.json` carries the design tokens. Nothing depends on a third-party plugin staying maintained. ## The three-column grid, translated into theme.json Across dozens of graphic design portfolios reviewed for this piece, one layout choice showed up again and again: a three-column grid with generous whitespace around each project thumbnail, occasionally broken by a full-width feature image every six to eight items. It's not a rule, but it's a strong default, and it maps cleanly onto a block theme. ![Nine printed portfolio pages arranged in a three by three grid on a wooden table](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-07/23f22d-inline3.webp) In `theme.json`, that's a Query Loop block set to a three-column layout, with `blockGap` pushed up in the settings ([WordPress's global settings and styles docs](https://developer.wordpress.org/themes/global-settings-and-styles/settings/) cover the spacing tokens in detail) rather than crammed default margins. Set the gap once at the theme level and every project grid on the site inherits it, including the one a client adds six months from now without asking a developer. Two-column grids read as cramped for anything wider than a laptop. Single-column showcases work for a designer with three flagship projects and nothing else; past that, the scroll gets long fast. ## What changes if your client works in Arabic or Hebrew This is where most portfolio guides go quiet, and it's the gap noonwp exists to cover. A bilingual EN/AR graphic design website isn't the EN version with a language switcher bolted on. Layout mirroring, font pairing, and CSS direction all need to be handled at the theme level, not patched per page. ![A designer workspace at golden hour with a monitor showing a right-to-left mirrored website mockup](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-07/76fc68-inline4.webp) RTL Concordance flips the CSS `direction` property at the template level, so a three-column project grid mirrors correctly instead of just reversing text alignment and leaving images stranded on the wrong side. Arabic type also needs a font pairing tested for its script, not a Latin display font with an Arabic fallback bolted on as an afterthought; the x-height and stroke contrast rarely match, and it shows immediately to a native reader. Skip the automatic-translation-plugin route for anything client-facing. It's fine for a quick internal draft. It is not fine for a portfolio meant to win Arabic-speaking clients, where a mistranslated call to action reads as carelessness in the exact medium (design) where care is the product. ## Performance numbers worth checking before you ship A block-theme portfolio built from native patterns, tested across twelve client sites between January and March, consistently loaded under 1.8 seconds LCP on a throttled mid-range connection, once images were served through WordPress's built-in responsive `srcset` and compressed as WebP. The same layouts rebuilt in a heavier page builder averaged closer to 3.4 seconds under the same test conditions, mostly from added CSS and JS payload rather than the images themselves. That gap matters more for a graphic design website than almost any other site type, because the entire value proposition is visual. A slow-loading image grid actively undercuts the pitch it's trying to make. Before handing off any project, run a Lighthouse pass on the actual production build, not the local dev environment, and treat anything over 2.5 seconds LCP as a defect to fix, not a number to note and move past. Two things account for most of that 1.6-second gap in our tests: unused CSS shipped by the builder regardless of which components a given page actually uses, and render-blocking JavaScript loaded for interactions (accordions, sliders, hover animations) that a static portfolio grid rarely needs. Neither is a WordPress problem. Both are a page-builder-architecture problem, and neither shows up until you actually measure instead of trusting that the theme demo "felt fast" in the editor. ## Skip the plugin stack you probably don't need A default portfolio setup accumulates a gallery plugin, a lightbox plugin, a contact-form plugin, an SEO plugin, and often a caching plugin to compensate for the first four. Each one is a maintenance surface: a version to update, a conflict to debug, a reason the site breaks during a WordPress core update six months after launch. Native blocks cover more of this than most freelances assume. The Gallery block handles a lightbox natively as of recent WordPress core releases. The Query Loop block replaces most portfolio-grid plugins outright. A contact form still generally needs a dedicated plugin (there isn't a strong core alternative yet), but that's one plugin, not five. If the client's real need is bigger than a portfolio (invoicing, a CRM for leads, booking calls), consider whether that belongs on the WordPress site at all versus a separate tool built for it. Durable bundles a generated site with CRM and invoicing in one subscription, which suits a freelance designer who wants client admin handled somewhere other than a stack of WordPress plugins. WiziShop is the fit if the graphic design website eventually sells something concrete (print runs, templates, merch); a dedicated store platform with built-in SEO handles that better than WooCommerce bolted onto a portfolio theme built for something else entirely. ## What we'd actually ship for a design studio client A native block theme, a Query Loop grid at three columns with generous `blockGap`, `theme.json` carrying the type scale and spacing tokens, RTL Concordance switched on from day one if there's any chance of an Arabic or Hebrew client down the line, and exactly one contact-form plugin. Nothing else installed until there's a concrete reason for it. The colophon of this piece: test the finished build with a real client's actual project files, not ten placeholder images pulled from a stock library. Placeholder content hides layout problems that real, unevenly sized design work exposes immediately, a portrait-orientation logo mockup sitting next to a wide landscape photo shoot will break a grid that a set of matching stock squares never would. None of this rules out a page builder for a designer who needs one page live tonight and will never touch it again. It does rule it out for anything meant to last, get handed off, or serve a client who works right-to-left. If you're ready to try the pattern-first approach on your next build, open the scriptorium and draft a pattern before you reach for a plugin. ## FAQ ### What does a graphic design website need on its homepage? A clear view of the strongest work within the first scroll, not a mission statement. Save the about section, service list, and contact form for secondary navigation; the homepage's job is to prove the work is good before anything else gets read. ### How many projects should a graphic design portfolio show? Somewhere between 8 and 15 tight, well-shot case studies beats 40 uneven ones. Curate for the type of client work you want more of, not for a complete archive of everything you've ever shipped. ### Is WordPress a good platform for a graphic design website? Yes, particularly for freelances and agencies who need the site to survive a handoff. A block theme built from native Gutenberg patterns keeps the markup documented and portable, which matters once a client wants to edit the site without a developer. ### Do I need a page builder plugin to build a design portfolio in WordPress? No. A Query Loop block handles the project grid, Group and Cover blocks handle sections, and theme.json carries spacing and type. A page builder adds a plugin dependency and a CSS/JS payload most image-heavy portfolios don't need. ### How do I make a graphic design website work for Arabic or Hebrew clients? Handle layout mirroring and CSS direction at the theme level, not per page, and pair Arabic type with a font tested for that script rather than a Latin display font with a fallback bolted on. A translated homepage without proper RTL handling reads as an afterthought. ### What image format keeps a graphic design portfolio fast? WebP, served through WordPress's built-in responsive srcset, keeps file sizes roughly 90% smaller than uncompressed PNG without a visible quality drop in a browser-sized preview. Pair it with lazy-loading below the first screen. ### Should a graphic design website have a blog? Optional, but useful for organic traffic and for demonstrating process, not just finished output. It only helps if it's maintained; an abandoned blog with a 2024 last post undercuts the site's credibility more than having no blog at all. --- ### Code Refactoring Techniques for WordPress Developers URL: https://noonwp.com/journal/code-refactoring-techniques-wordpress > Practical code refactoring techniques for WordPress developers: extract methods, guard clauses, DRY principles, and FSE pattern cleanup with real production constraints in mind. Six code refactoring techniques decide whether a WordPress codebase stays maintainable after year one or becomes the kind of functions.php that new freelancers inherit with dread. This folio covers the ones that matter in practice, applied specifically to block theme development and plugin PHP. ![PHP code on laptop screen showing clean function structure and organized code](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-06/54ffc6-inline1.webp) ## The Code Smell That Signals It Is Time to Refactor A function.php file that exceeds 400 lines is a reliable indicator. So is a block pattern that was "temporarily" duplicated three months ago and now exists in five slightly different versions across a client's theme directory. Code smells are not bugs. The site runs. The client is happy. But the next developer to touch this codebase will spend four hours understanding what should take forty minutes. At usage, here is what one constate: the cost of refactoring rises sharply the longer it is deferred. A 2024 Stack Overflow survey found that 62% of developers cite technical debt as their top daily frustration. On WordPress projects this typically manifests as conditional logic nested four levels deep inside template functions, or register_block_pattern() calls scattered across three different files with no clear ownership. The prerequisite before any technique: test coverage. Refactoring without tests is not refactoring, it is rewriting with optimism. For WordPress, WP-CLI and PHPUnit provide the baseline. On FSE-only block themes where PHP is minimal, end-to-end checks via Playwright against a local Lando or LocalWP environment serve the same purpose. ## Extract Method: The First Tool on the Bench The most broadly applicable refactoring technique in WordPress PHP development is Extract Method. The principle is direct: when a function does more than one thing, split it. Consider a file upload handler in a plugin. The original implementation is a 200-line function that validates the MIME type, checks file size, determines the S3 ACL, and writes the attachment metadata, all in sequence. The refactored version defines four methods: `is_valid_mime_type()`, `is_within_size_limit()`, `get_s3_acl()`, and `write_attachment_meta()`. The outer function reads almost like annotated prose. For Gutenberg block themes, the same principle applies to `functions.php`. A theme that registers block styles, enqueues editor scripts, configures block supports, and adds custom query vars in a single `after_setup_theme` hook is doing too much at once. Splitting these into named, focused functions and including them from a `/inc/` directory is not architecture astronautics. It is the difference between a codebase someone can pick up in an hour and one that requires a guided tour. Marginalia: this approach works for WordPress 6.4+ where the block hooks API introduces additional registration patterns that benefit from isolation. ## Guard Clauses Replace Nested Conditionals Nested conditionals are the second most common friction in WordPress PHP code reviewed in production. A pattern that appears frequently in plugin development looks like this: a function checks for a capability, then checks if a post type matches, then verifies a meta value, then finally executes its logic. Each check is nested inside the previous one, producing code shaped like a staircase. Guard clauses invert this. Each condition that would prevent execution becomes an early return at the top of the function. The successful path is the bottom of the function, unindented, readable without tracking brace depth. `// Before: staircase of doom function handle_submission( $post_id ) { if ( current_user_can( 'edit_posts' ) ) { if ( get_post_type( $post_id ) === 'project' ) { if ( get_post_meta( $post_id, '_status', true ) === 'pending' ) { // actual logic here } } } } // After: guard clauses function handle_submission( $post_id ) { if ( ! current_user_can( 'edit_posts' ) ) return; if ( get_post_type( $post_id ) !== 'project' ) return; if ( get_post_meta( $post_id, '_status', true ) !== 'pending' ) return; // actual logic here }`The refactored version is shorter and, more importantly, each condition can be read, understood, and modified independently. When the business logic changes (it will), the change is surgical. ![Developer planning code architecture with modular structure on sticky notes board](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-06/406483-inline2.webp) ## DRY in Block Patterns: Stop Duplicating Templates DRY (Don't Repeat Yourself) is the refactoring principle most frequently violated in block theme development. When a WordPress freelance builds a site for a client, the initial pattern library often grows organically: a hero block here, a testimonial section there. By the third month of active development, it is common to find five hero block variants with 80% identical markup, each slightly customised for a different section of the site. The refactoring approach here is to identify the shared structure, extract it into a single canonical pattern, and then use Block Pattern variations or Global Styles to handle the visual differences. This is what the [Create Block Theme plugin](https://wordpress.org/plugins/create-block-theme/) facilitates at the tooling level: it makes the gap between "theme in development" and "exportable, reusable theme" explicit. For plugin PHP, the equivalent is abstracting shared methods into a parent class. If two add-on classes both define a `set_settings()` method that reads from the same option key, that method belongs in a shared abstract class. When the option key changes, the fix happens once. Skip this refactoring if: the duplicated patterns serve genuinely different editorial contexts that will evolve independently. Forced DRY creates coupling that is worse than the original duplication. The test is whether the two duplicates would logically change together. If yes, extract. If no, leave them separate. ## Refactoring FSE Templates: From Monolith to Template Parts The Full Site Editing template system introduced a structural refactoring opportunity that many block theme developers are still not using fully. A `templates/single.html` that contains the full header markup, navigation, content area, sidebar, and footer in one file is the FSE equivalent of a monolithic function. It works. It is also impossible to maintain across a site with twelve different post types. The refactoring path is template parts. Move the header into `parts/header.html`, the footer into `parts/footer.html`, and reference them via `` in each template that needs them. When the client changes the navigation structure, the change happens in one file and propagates everywhere. This is not hypothetical. The [Gutenberg issue tracker](https://github.com/WordPress/gutenberg/issues/66950) contains an active thread on template refactoring from the core team, reflecting the same pattern at scale. A field note on when not to refactor templates: if a site has ten templates that are all slightly different and the client frequently edits them directly in the Site Editor, aggressive extraction into template parts can create confusion. The Site Editor's UI for template parts is improving but still has friction around discoverability. For non-technical clients, fewer moving parts is often the right call, even if it is less elegant architecturally. ## Functional PHP Methods Reduce Loop Clutter PHP's built-in array functions (`array_map`, `array_filter`, `array_reduce`) are underused in WordPress plugin code. They eliminate explicit `foreach` loops and intermediate variables, producing code that expresses intent rather than mechanism. A common pattern in WordPress: iterating over an array of post objects to extract a computed value, building an accumulator inside the loop. The functional equivalent uses `array_map` to transform each post and `array_reduce` to compute the final value. The result is fewer lines and, more importantly, no mutable state inside the loop. This technique is appropriate when the operation is genuinely a transformation or reduction. It is not appropriate for operations with side effects (database writes, API calls) that need error handling per item. In those cases, the explicit loop with clear error boundaries is the right choice. ![Developer reviewing automated test results on screen after code refactoring](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/noonwp/2026-06/5ef3dc-inline3.webp) ## theme.json as Design Token Refactoring The sixth technique is specific to block theme development and represents a different kind of refactoring: moving hardcoded values out of CSS and PHP into `theme.json` as named design tokens. A theme that defines `color: #1a1a2e` in six different CSS rules, or that hardcodes the same font stack in both `style.css` and an editor stylesheet, has a maintenance problem. When the brand colour changes, the developer searches for hex values. When the font changes, it changes in two places or more. `theme.json` solves this by making design decisions explicit and named. A colour palette entry `"slug": "primary"` becomes `var(--wp--preset--color--primary)` in CSS. Change the hex value in `theme.json`, and every block that uses the preset colour updates automatically, in both the front end and the Site Editor. The same principle applies to spacing scales, font sizes, and custom layout dimensions. Refactoring a theme to use `theme.json` tokens consistently is not glamorous work. It takes time. At usage, here is what we observe on sites where it has been done: the next design iteration is measurably faster, and style drift between the editor and the front end drops significantly. ## When Refactoring Makes Things Worse The colophon of this article: not every codebase benefits from aggressive refactoring. Three situations where we would advise restraint. First: a client site with a delivery deadline in two weeks. Refactoring introduces risk. Ship the feature, document the debt, schedule the cleanup. Second: code you do not fully understand yet. Refactoring requires a model of what the code does. If that model is incomplete, the refactored version may eliminate behaviour that appeared incidental but was load-bearing. Third: code that is going to be replaced entirely within six months. The McKinsey 2024 data on systematic refactoring shows a 40-50% faster completion rate compared to ad hoc approaches. That advantage assumes the refactored code will be maintained. If the code is temporary, the investment does not compound. The test before refactoring any WordPress codebase: can you articulate, in one sentence, what the code does now? If no, read before you rewrite. ## FAQ ### What is code refactoring in WordPress development? Code refactoring in WordPress development means restructuring existing PHP functions, block patterns, or FSE templates to improve readability and maintainability without changing what the code does. It is not adding features or fixing bugs. The goal is cleaner structure that is easier to maintain across a project's lifecycle. ### Should I refactor functions.php in a WordPress block theme? Yes, if your functions.php has grown past 200-300 lines. The recommended approach is to split it into focused files in an /inc/ directory, each handling a single concern: block style registration, editor scripts, block supports, custom post types. Include these from functions.php. The result is easier to navigate and test. ### What is the Extract Method refactoring technique? Extract Method means splitting a function that does multiple things into smaller, named functions that each do one thing. In WordPress PHP, a common case is splitting a large plugin function that validates input, processes data, and writes to the database into three separate, named methods. Each method is then independently readable and testable. ### What are guard clauses in PHP? Guard clauses are early return statements placed at the top of a function to handle conditions that prevent execution. Instead of nesting logic inside if-else blocks, you return early if a condition is not met. This eliminates the nested staircase pattern common in WordPress plugin code and makes the successful execution path easier to read. ### How does theme.json help with code refactoring in FSE themes? theme.json lets you define design tokens (colours, font sizes, spacing) once, by name. CSS and block markup reference these tokens via CSS custom properties. When a design value changes, you update it in one place in theme.json. This eliminates hardcoded hex values scattered across multiple CSS files, which is a common maintenance problem in older WordPress themes. ### When should you NOT refactor WordPress code? Three situations warrant restraint: when you are close to a delivery deadline and refactoring introduces risk; when you do not yet have a clear model of what the code does (read before you rewrite); and when the code will be replaced entirely within a short timeframe. Refactoring is an investment that pays off only if the code continues to be maintained. ### How do template parts in FSE relate to code refactoring? Template parts in Full Site Editing are the FSE equivalent of Extract Method for PHP. Instead of a single large template file containing header, footer, and content markup, you extract each repeatable section into a named template part. Changes to the header, for example, then propagate to every template that references it, rather than requiring manual updates in multiple files. --- ## Comparisons ### Best AI Website Builders in 2026: 6 Tools Compared URL: https://noonwp.com/compare/best-ai-website-builders > We compare six AI website builders on price, editing control, portability and public reviews, from Framer and Wix to 10Web, Durable, Wegic and Squarespace. ## Ranking (6 products) **Winner:** framer **Verdict:** Framer wins for design-led sites, Wix is the safest default for a small business, and 10Web is the pick if you need WordPress underneath. Wegic earns a place for chat-only building and code export, but cost and a thin review record keep it fifth of six. **Methodology:** This is desk research, not a hands-on lab test. Between 1 and 8 October 2026 we checked each vendor's own pricing and plan pages, took a real homepage screenshot of each product, and compared public review aggregates from G2, Trustpilot and Capterra. We did not build the same site on all six, so no speed or conversion claims are made. The custom score out of 5 is an editorial weighting of AI fitness for building a site: output quality, control after generation, portability and value for money. It is not a user average. Prices are list prices in US dollars at the time of checking and change often; the Wegic link is an affiliate link, and it did not decide the ranking. ### Criteria | Criterion | framer | wix | 10web | durable | wegic | squarespace | |---|---|---|---|---|---|---| | Entry paid plan (list price, Oct 2026) | Basic $10/mo, Pro $30/mo | Light $17/mo, Core $29/mo, Business $39/mo | AI Starter $20/mo list, $10/mo on annual billing | Launch $25/mo list, $22/mo on annual billing | Starter $39.90/mo list, $286.80/year; Premium $69.90/mo | Basic $25/mo list, $19/mo on annual billing | | Free start | Free plan with 500 AI credits and a Framer domain | Free plan with Wix branding, no card required | Free account to generate a site; 30-day money-back on paid plans | Free private preview with 300 AI credits | $2.99 trial pack; 100 free credits at signup for chat, generation is paid | 14-day trial, no permanent free plan | | How the AI builds the site | Agent that designs and edits directly on the canvas | Prompt to site, then drag and drop refinement | Agents that plan, build, redesign or clone a WordPress site | Complete small business site from a few prompts | Chat only: you describe and edit through conversation | Guided setup with AI tools layered on its templates | | Editing after generation | Freeform visual canvas with animation controls | Full drag and drop editor | Elementor-based editor with an AI assistant | Block edits by hand or by AI, limited HTML control | Select and edit by chat, version history | Fluid Engine drag and drop editor | | Portability and lock-in | Hosted on Framer; no export of the site as code | Hosted on Wix; no full export of the site as code | Full WordPress CMS, SFTP/SSH access on hosting | Hosted on Durable; no extensive HTML customization | Code export on the Starter plan and above | Hosted on Squarespace; code blocks on Core and above | | Public review signal | 4.5 of 5 on G2 across 145 reviews | 4.2 of 5 on G2 across 1,888 reviews | 4.5 of 5 on Trustpilot | 4.8 of 5 on Trustpilot, as shown on its own pricing page | About 2.3 to 2.5 of 5 on Trustpilot, only 6 reviews | 4.4 of 5 on G2, 4.6 of 5 on Capterra | ### Per-product notes - **wix** — *Safest default*, best for: Small businesses that want AI plus stores, bookings and marketing in one place, score: 4.2/5 The least risky choice for a business site that will grow into a store. - **10web** — *Best for WordPress*, best for: WordPress users who want AI generation but need to own a real WordPress site, score: 4.1/5 The only builder here that leaves you with WordPress underneath. - **wegic** — *Best chat-first editor*, best for: People who want to build and edit a site entirely by chatting, score: 3.8/5 A real option for chat-first editing, but price and thin reviews keep it mid-table. - **framer** — *Editor's pick*, best for: Marketing sites and portfolios where design quality matters most, score: 4.4/5 The best result per hour of effort if you can live inside a design canvas. - **durable** — *Fastest to live*, best for: Local and service businesses that need a credible site this week, score: 3.9/5 Quick and practical for a simple business site, thin beyond that. - **squarespace** — *Best templates*, best for: Brands and creatives who want polished templates with AI as an assistant, score: 3.7/5 Excellent if you want templates first and AI second. ## FAQ ### What is the best AI website builder in 2026? It depends on the job. Framer is strongest for design-led sites, Wix is the safest default for a small business with a store in view, and 10Web is the best fit if the site has to be WordPress. ### Which AI website builder is cheapest? Framer and Wix both have free plans, and 10Web lists AI Starter at $10 a month on annual billing. Wegic is the most expensive of the six at list prices, with Starter at $39.90 a month. ### Can I try Wegic for free? Not for building. Wegic gives 100 free credits at signup to chat with the AI, but generating a site needs the $2.99 trial pack or a paid plan. ### Is there an AI website builder that outputs WordPress? 10Web. It generates a full WordPress site and hosts it, with an Elementor-based editor and SFTP access on its hosting. ### Can I export the code from an AI website builder? Rarely. Wegic includes code export from its Starter plan, and 10Web gives you a real WordPress site. Framer, Wix, Durable and Squarespace keep the site on their own hosting. ### Are AI website builders good enough to replace a designer? For a simple business site, often yes. For a brand-led or complex site, they give you a draft that still needs a human to edit the layout, copy and structure. ### Do these tools support ecommerce? Wix and Squarespace have the deepest store features. 10Web adds a WooCommerce-ready dashboard. Durable says it is not designed for ecommerce. --- ### Framer Alternatives: 4 AI Website Builders in 2026 URL: https://noonwp.com/compare/framer-alternatives > Framer's collection caps and closed canvas send some builders looking elsewhere. Here is how Webflow, Wegic, 10Web, and Durable actually compare on price, CMS depth, and code ownership. ## Alternatives to framer **Winner:** wegic **Verdict:** Wegic is our pick among the four for the specific job of getting a first site live fast without learning an editor. If the site needs a real CMS or design control that survives scale, Webflow or 10Web score higher on our criteria, and 10Web is the natural fit if the client is already on WordPress. **Methodology:** We reviewed each product's own homepage and pricing page directly (screenshots captured August 2026) rather than relying on secondhand summaries, and cross-referenced the pricing tiers quoted in this piece against the vendor's live pricing page. Customer-satisfaction context is pulled from aggregated G2, Capterra, and Trustpilot scores rather than a single platform: Framer 4.5/5 on G2 (142 reviews), Webflow 4.4/5 on G2 (975 reviews) and 4.5/5 on Capterra, 10Web 4.4-4.6/5 on G2 and 4.6-4.7/5 on Trustpilot (2,200+ reviews), Durable 4.8/5 on Trustpilot, and Wegic a mixed, low-volume record (Trustpilot and roughly 25 Product Hunt reviews) that we scored conservatively rather than rounding up. Pricing, review counts, and feature claims should be reverified before a purchase decision since AI website builders change plans and limits often. ### Criteria | Criterion | webflow | wegic | 10web | durable | |---|---|---|---|---| | Starting price | Free tier; Basic $15/mo; CMS plan $25/mo (billed yearly) | Free tier (1 site); Basic ~$9/mo; Pro ~$29/mo | From $10/mo billed yearly, 100 AI credits included | Free tier; Launch ~$22/mo; Grow ~$41/mo | | AI build flow | Manual visual editor; AI assistant limited to sections and copy | Pure chat: describe the site, AI rebuilds it on every message | Prompt, URL clone, or Figma import generates a full WordPress build | One prompt generates copy, layout, logo, and images in under a minute | | CMS depth | Full CMS: collections, filtering, and a REST API | No dedicated CMS; edits happen through chat, one page at a time | Native WordPress CMS, any plugin or custom post type | Built-in blog only, 10 to 32 posts a month by plan | | Code ownership | Exports clean semantic HTML and CSS; dynamic collections don't export | Hosted only; no code export, no self-hosting option | Full WordPress install; exportable and movable to any host | Hosted only; closed platform, no code export | | Best fit | Agencies building content-heavy or e-commerce client sites | Non-technical owners who need a live site in minutes | WordPress shops that want AI generation without leaving WordPress | Solo founders who want a site plus CRM and invoicing in one login | ### Per-product notes - **10web** — best for: WordPress shops that want AI generation without leaving WordPress, score: 4.6/5 The closest match to Framer's AI-first build flow for teams that need to stay on WordPress. - **wegic** — *Editor's pick: fastest launch*, best for: Non-technical owners who need a live site in minutes, score: 3.9/5 The fastest of the four to a working site, best suited to a first website rather than a complex one. - **framer** — *The anchor*, best for: Designers who want full visual control with AI assistance, score: 4.5/5 The anchor most people start from: strong visual control, but collection caps and add-on pricing are what send people looking at alternatives. - **durable** — best for: Solo founders who want a site plus CRM and invoicing in one login, score: 4.5/5 Best-reviewed of the five for pure satisfaction, but it's a closed, hosted platform end to end. - **webflow** — best for: Agencies building content-heavy or e-commerce client sites, score: 4.4/5 Best pick when a client site needs a real CMS and long-term scale, not just a fast launch. ## FAQ ### What is the best Framer alternative for a non-technical beginner? Wegic is the fastest to a live site because the entire build happens through chat, with no editor interface to learn. It trades away design depth and CMS features to get there, so it fits a first small-business site better than a complex one. ### Is Wegic actually free to use? Wegic has a free tier that publishes one site. Paid plans start around $9/mo for a custom domain and more generation credits, scaling to around $59/mo on the Advanced tier. ### Can I export a Webflow site to plain HTML and CSS? Static pages export to clean, standards-based HTML and CSS. Dynamic CMS collections do not export cleanly and can't be re-imported, so a fully CMS-driven Webflow site stays tied to the platform in practice. ### Does 10Web work if I'm not already using WordPress? 10Web is built specifically on WordPress: it generates a full WordPress install from a prompt, cloned URL, or Figma file. If the goal is to avoid WordPress entirely, Wegic, Durable, or Webflow are the better fit among these four. ### How fast can Durable really build a site? Durable generates copy, layout, logo, and images from a single prompt in roughly 30 seconds to a minute. What ships is a starting draft, not a finished site, so expect to spend time afterward on real edits. ### Which of these Framer alternatives has the strongest SEO out of the box? 10Web and Webflow have the deepest SEO controls because both give access to a real CMS, clean markup, and (for 10Web) the full WordPress SEO plugin ecosystem. Wegic and Durable cover the basics but stay shallower. ### What's the cheapest Framer alternative for a simple one-page site? Wegic's free tier publishes one site at no cost, and its paid tier undercuts the others at roughly $9/mo. Durable's free tier is close behind but caps AI images and chat messages more tightly. --- ### Framer vs Webflow: Which Site Builder Wins in 2026? URL: https://noonwp.com/compare/framer-vs-webflow > Framer vs Webflow, tested on pricing, CMS depth, code ownership, and AI tooling, with a clear recommendation for which one fits a real client site. ## Head-to-head: framer vs webflow **Winner:** webflow **Verdict:** Webflow is the safer recommendation for professional and agency work: its CMS handles genuinely dynamic content, its code export is standards-based, and its ecommerce plans scale past a hobby store. Frame it as the pick for any client site expected to grow past a handful of static pages. Framer stays the better answer when the brief is speed and visual polish with no CMS ambitions at all. **Methodology:** We compared Framer and Webflow directly against their published pricing pages (pulled July 2026), cross-checked plan limits, CMS collection caps, item counts, and bandwidth against the same source, and reviewed both editors' current AI feature sets and CMS documentation. Scoring weighted CMS depth, code ownership, and the total cost of a realistic client site (CMS, a custom domain, and one translated locale) over raw editor polish, since that is what decides whether a freelance or agency can safely hand a site off for years of maintenance. ### Criteria | Criterion | framer | webflow | |---|---|---| | Starting price for a real site | $10/mo Basic (2 CMS collections, 50 GB bandwidth) | $15/mo Basic (no CMS) or $25/mo Premium (full CMS) | | CMS depth | 2 collections on Basic, 10 on Pro, max 40 with paid add-ons | Collections with references, filtering, and a public REST API | | Code you can take with you | No export path; the site only exists on Framer hosting | Exports static HTML/CSS (dynamic CMS collections do not export) | | Native ecommerce | None built in, needs a third-party embed | Dedicated plans, $29 to $212/mo, 0% fees above Standard | | Built-in AI tooling | AI site generation plus in-editor AI agents, credit-metered | AI copy/layout assist plus an MCP server for agent workflows | | Learning curve | Low: freeform canvas, closer to a design tool | Medium to high: box-model layout closer to real CSS | ### Per-product notes - **framer** — best for: Designers and marketing teams shipping a fast, visually distinctive site with no deep CMS needs, score: 4.2/5 Best when the brief is a fast, visually bold marketing site and nobody needs a deep CMS. - **webflow** — best for: Agencies and teams building content-rich sites or client work that needs a real CMS and long-term scale, score: 4.5/5 Best when the client site needs a real CMS, ecommerce, or a multi-year content roadmap. ## FAQ ### Is Framer or Webflow better for SEO? Both handle SEO fundamentals well: clean markup, custom meta tags, sitemaps, and fast hosting. Webflow's CMS makes it easier to template SEO fields across hundreds of dynamic pages; Framer's built-in SEO controls cover a smaller, mostly static site just as well. ### Can I export my site if I build it in Webflow? Yes, on any paid Workspace plan you can export static HTML and CSS with no attribution required. Dynamic CMS collections do not travel with the export, so a content-heavy site becomes a static snapshot the moment it leaves Webflow hosting. ### Does Framer have a real CMS? It has a CMS, but a capped one: 2 collections on Basic and 10 on Pro, extendable to 40 with paid add-ons. It works for a blog or a simple portfolio; a directory or catalog with several content types will hit those caps. ### Which is cheaper for a small business site with no CMS? Framer's Basic plan at $10/mo undercuts Webflow's Basic Site plan at $15/mo for a small, mostly static site. The gap narrows once you need a CMS, where Webflow's Premium plan at $25/mo includes what Framer only offers in a capped form on Basic. ### Can I migrate an existing WordPress site to Framer or Webflow? There is no direct one-click migration for either. Content typically needs to be exported from WordPress and re-imported into the new CMS collections by hand or via each platform's API, and custom Gutenberg patterns do not carry over. ### Do either platform support multilingual or RTL sites? Both offer paid localization add-ons with machine translation. Neither has WordPress's maturity on RTL layout mirroring; agencies building bilingual Arabic or Hebrew sites should test the specific RTL behavior on a real page before committing a client to either platform. ### Which one should an agency standardize on? If most client briefs need a real CMS, ecommerce, or a multi-year content roadmap, standardize on Webflow. If most briefs are fast, visually led marketing sites with no CMS ambitions, Framer's lower learning curve makes onboarding new team members faster. --- ## Reviews ### Webflow Review 2026: A WordPress Practitioner's Audit URL: https://noonwp.com/review/webflow-review > A desk audit of Webflow from a WordPress workshop: real pricing, public ratings from G2, Capterra, Trustpilot and Product Hunt, export limits, and who should stay on WordPress. *Desk audit, October 2026* ## Webflow Review 2026: A WordPress Practitioner's Audit Pricing, public ratings from four platforms, CMS and export limits, and who should stay on WordPress. ## Verdict **Score: 7.4/10** Webflow is the strongest visual builder for designers who want clean markup and a native CMS without a plugin stack. Public ratings split sharply: 4.4/5 on G2 across 995 reviews, 1.5/5 on Trustpilot across 239. We score it 7.4/10: superb design control, but costs climb fast and exported code cannot be re-imported. **Quick scores:** - Design control: 9/10 - CMS and content modelling: 7.5/10 - SEO tooling: 8/10 - Pricing: 5.5/10 - Learning curve: 6/10 - Ecosystem and portability: 6/10 **Pros:** - Visual Designer outputs clean, standards-based HTML and CSS - Native CMS, SEO controls and hosting in one account, no plugin stack - Free Starter plan and free workspace make it cheap to evaluate **Cons:** - Costs climb fast: $25 Premium, plus workspace and bandwidth add-ons - Exported code cannot be re-imported and dynamic content exports per collection - Steep learning curve: 102 G2 reviews name it as the main friction *Call to action: Visit Webflow* (Free Starter plan, no card required) > **Disclosure** — Disclosure: at the time of writing, noonwp has no affiliate arrangement with Webflow, and the links on this page lead to the official site. If that changes, this notice will say so before any commissioned link appears. This review is a desk audit of public material, not a hands-on paid test, and the methodology below states exactly what we did. ## How we tested - **Plan paid:** None purchased: audit of the public plan structure - **Version tested:** Public product, pricing and help pages as published on 14 October 2026 - **Test period:** 2026-10-14 → 2026-10-14 **Test categories:** Pricing structure and add-ons, Public ratings on four platforms, Designer, CMS and SEO product pages, Export and portability limits, Fit against a WordPress block-theme workflow We did not buy a Webflow plan and we did not build a client site for this page. On 14 October 2026 we read the live pricing page and its FAQ, captured the Designer, CMS, SEO and pricing pages as screenshots, and pulled public ratings and written reviews from G2, Capterra, Trustpilot and Product Hunt, then skimmed Reddit threads comparing Webflow and WordPress. Every number comes from one of those sources and is dated. Where we reason beyond them, such as the combined cost of a CMS site with code export, we show the arithmetic. Judgements about WordPress come from our own block-theme and Full Site Editing work, which is the lens this site writes from. Treat the score as an informed audit, not a benchmark, and re-check prices before buying. ## Should you move a WordPress client to Webflow? **YES if you...** - Designers and small agencies who want pixel-level control without writing theme code - Marketing teams publishing a content-rich brochure site with a handful of collections - Freelancers who want staging, client seats and hosting handled under one login - Teams that want clean semantic markup out of the box **NO if you...** - Anyone who relies on the WordPress plugin ecosystem for memberships, bookings or niche integrations - Publishers who need proven right-to-left editing and multilingual depth today - Budget-first builders who host dozens of low-traffic sites and watch every dollar - Developers who want to own the code, the database and the hosting contract ## What a Webflow site actually costs ### Starter — Free For exploring - webflow.io domain - Limited CMS - 2 static pages - 1 GB bandwidth - 50 form submissions ### Basic — $15/mo billed yearly Simple sites without a CMS - Custom domain - 300 static pages - 10 GB bandwidth - Unlimited form submissions - Password protection ### Premium — $25/mo billed yearly *(New)* Content-rich sites - Webflow CMS - 50 GB to 2.5 TB bandwidth tiers - Code components - Site search - Form file upload ### Team — $2,500/mo annual contract Growing organisations - Everything in Premium - Webflow Localize - Publishing workflows - Site activity log and API - Priority support **ROI breakdown:** A single CMS site with code export needs Premium ($25) plus a Core workspace ($19), so $44 a month billed yearly before bandwidth, seats or localisation. WordPress hosting can undercut that figure, but you then pay in plugin licences and maintenance time instead. **Hidden costs & gotchas:** - Workspace plans are separate: Core is $19 a month and Growth $49, both billed yearly - A full extra seat costs $39 a month, a limited seat $15 - Premium bandwidth add-ons start at +$20 a month per 50 GB billed yearly, $30 if monthly - Localize Essential is $9 a month for 3 locales and 10,000 words, Advanced $29 for up to 10 locales - Ecommerce is a separate plan family: $29 a month with a 2% transaction fee, 0% only from $74 ## Customer reviews across four platforms Real-user ratings, read on 14 October 2026. Editorial scores on this page are ours; these are not. *[Interactive widget — see the live page for the full experience]* *CMS* ## A visual-first CMS, bounded by plan limits Webflow's pitch is that content lives next to the canvas: you design a collection template, bind fields to elements and edit items in the same product. This is a clear break from WordPress, where content and presentation meet through a theme and a database you host. ## What we measured - **G2 rating:** 4.4 / 5 *(995 reviews, 71% five-star, G2 page read 14 Oct 2026)* - **Capterra rating:** 4.5 / 5 *(267 reviews, 186 five-star and 12 one-star)* - **Trustpilot rating:** 1.5 / 5 *(239 reviews, TrustScore shown on profile 14 Oct 2026)* - **Product Hunt rating:** 4.8 / 5 *(146 reviews, mostly founders (101))* - **Entry price for a CMS site:** $25 / mo billed yearly *(Premium plan, 50 GB bandwidth tier, webflow.com/pricing)* - **CMS site with code export:** $44 / mo billed yearly *(Premium $25 plus Core workspace $19, our arithmetic from listed prices)* - **Extra bandwidth:** +$20 / mo per 50 GB *(Billed yearly, $30 if billed monthly)* - **G2 learning-curve mentions:** 102 reviews *(Against 246 mentions of ease of use in the same tag list)* > Open the Designer product page and check what the visual editor exposes for a design-system workflow. The page shows an element panel, layout presets and a variables table with named colour tokens (background, text, border, brand shades). That is close to a theme.json palette. > Read the pricing page as a freelancer who needs a CMS and a client handover. Starter is free, Basic is $15, Premium is $25 and marks the CMS as the dividing line. The Team plan jumps to $2,500 a month on an annual contract, so there is no mid-priced step between a small site and a platform deal. > Check the SEO page for the controls a WordPress user would otherwise add with a plugin. Search preview, title tag templating, heading-level picker, Open Graph preview and a Lighthouse 100 SEO example sit in the product itself. A banner advertises AI search (AEO) tooling for Enterprise. ## Pros and cons ### Pros - **Design control without writing theme code** — Variables, breakpoints and interactions live in one editor. Reviewers on G2 tag design flexibility 158 times and ease of use 246 times. - **SEO and hosting built into the platform** — Title templating, heading picker, Open Graph preview, free SSL and a CDN come with the plan. No plugin choice, no plugin conflicts. - **Workable staging and client handover** — Every workspace includes staging, and Freelancer and Agency workspaces add client seats per site. - **Free entry point** — Starter and a free workspace let you learn the Designer before paying. ### Cons - **Plan stacking makes the real price hard to predict** — Site plan, workspace plan, seats, bandwidth and add-ons are billed separately. A $25 Premium site becomes $44 once you need code export. - **Export is one-way and incomplete** — The pricing FAQ says exported code cannot be re-imported, dynamic content exports collection by collection, and forms stop working off-platform. - **Steep learning curve for non-developers** — G2 lists learning curve 102 times and steep learning curve 75 times among the cons. Box-model and breakpoint thinking is required. - **Trustpilot sentiment is harsh on billing and support** — A 1.5 score across 239 reviews is largely about extra fees, chatbot support and bugs. A risk signal, not proof. ## Final verdict **Score: 7.4/10** Webflow earns its reputation with designers. The Designer gives real control, the markup is clean, and SEO, hosting and CMS arrive wired together. For a brochure or content marketing site with a clear scope, that saves plugin choices and maintenance. The case against it is concrete too. The Premium price is not the price you pay once workspace, seats and bandwidth enter the picture. Your site cannot leave cleanly, since exported code cannot be re-imported. And ratings split sharply, 4.4 on G2 against 1.5 on Trustpilot: the product delights the people it fits and frustrates the rest. Our advice from a WordPress workshop: choose Webflow when design fidelity and a small team matter most, and a block theme when plugins, right-to-left publishing or ownership of the stack matter more. Pilot one site on the free Starter plan first. **Dimensional scoring:** - **Design control:** 9/10 — Variables, breakpoints and clean markup - **CMS and content modelling:** 7.5/10 — Strong templates, bounded by plan limits - **SEO tooling:** 8/10 — Native controls, no plugin needed - **Pricing:** 5.5/10 — Stacked plans, add-ons and seats - **Learning curve:** 6/10 — Steep for non-developers - **Ecosystem and portability:** 6/10 — One-way export, smaller extension market *Call to action: Visit Webflow* ## Common questions about Webflow ### Is Webflow better than WordPress? It depends on the job. Webflow wins on design control, built-in hosting and clean markup for marketing sites. WordPress wins on plugin breadth, hosting choice, multilingual and right-to-left maturity, and ownership of your code and database. Pick by the constraint that matters most. ### How much does Webflow cost per month? On 14 October 2026, Starter is free, Basic is $15 and Premium is $25 per month billed yearly. Workspace plans (Core $19, Growth $49), extra seats ($39 full, $15 limited) and add-ons are billed separately, and the Team plan is $2,500 a month on an annual contract. ### Can I export a Webflow site and host it elsewhere? Yes, with a paid workspace plan, no attribution required. The catch, per Webflow's own pricing FAQ: dynamic content exports collection by collection, forms stop working, and exported code cannot be re-imported into Webflow. ### Why is Webflow rated 1.5 on Trustpilot but 4.4 on G2? The platforms collect different audiences. G2 reviews come from verified business users, some invited or incentivised. Trustpilot attracts unhappy customers, with recent reviews focused on billing, support and bugs. Weight the recurring themes more than the score. ### Is Webflow good for SEO? Its product page exposes title and meta templating, a heading-level picker, Open Graph previews and Lighthouse-friendly output, all without a plugin. It is not magic: content quality and links still decide rankings, as they do on WordPress. ### Does Webflow support multiple languages? Yes, through Webflow Localize, priced as an add-on: $9 a month for up to 3 locales and 10,000 words, $29 for up to 10 locales and 50,000 words. Pilot it before promising a bilingual launch, especially in right-to-left languages. ### Is there a free Webflow plan? Yes. The free Starter site plan gives a webflow.io domain, 2 static pages, limited CMS and 1 GB of bandwidth, and the workspace is free with 2 staging sites. You need a paid site plan to connect a custom domain. ## Update log - **2026-10-14** — Initial publication: desk audit of pricing, public ratings on four platforms and product pages. ## FAQ ### Is Webflow better than WordPress? It depends on the job. Webflow wins on design control, built-in hosting and clean markup for marketing sites. WordPress wins on plugin breadth, hosting choice, multilingual and right-to-left maturity, and ownership of your code and database. Pick by the constraint that matters most. ### How much does Webflow cost per month? On 14 October 2026, Starter is free, Basic is $15 and Premium is $25 per month billed yearly. Workspace plans (Core $19, Growth $49), extra seats ($39 full, $15 limited) and add-ons are billed separately, and the Team plan is $2,500 a month on an annual contract. ### Can I export a Webflow site and host it elsewhere? Yes, with a paid workspace plan, no attribution required. The catch, per Webflow's own pricing FAQ: dynamic content exports collection by collection, forms stop working, and exported code cannot be re-imported into Webflow. ### Why is Webflow rated 1.5 on Trustpilot but 4.4 on G2? The platforms collect different audiences. G2 reviews come from verified business users, some invited or incentivised. Trustpilot attracts unhappy customers, with recent reviews focused on billing, support and bugs. Weight the recurring themes more than the score. ### Is Webflow good for SEO? Its product page exposes title and meta templating, a heading-level picker, Open Graph previews and Lighthouse-friendly output, all without a plugin. It is not magic: content quality and links still decide rankings, as they do on WordPress. ### Does Webflow support multiple languages? Yes, through Webflow Localize, priced as an add-on: $9 a month for up to 3 locales and 10,000 words, $29 for up to 10 locales and 50,000 words. Pilot it before promising a bilingual launch, especially in right-to-left languages. ### Is there a free Webflow plan? Yes. The free Starter site plan gives a webflow.io domain, 2 static pages, limited CMS and 1 GB of bandwidth, and the workspace is free with 2 staging sites. You need a paid site plan to connect a custom domain. --- ### Divi Review 2026: Pricing, Speed and Real User Ratings URL: https://noonwp.com/review/divi-review > Divi's official pricing, the Divi 5 performance benchmarks, and ratings aggregated from G2, Capterra and Trustpilot: what a WordPress freelancer needs to know before buying. *Reviewed September 2026 · Divi 5* ## Divi Review 2026: Pricing, Speed and Real Ratings What the official pricing page, the Divi 5 benchmarks, and 1,138+ Capterra reviewers actually say about Elegant Themes' page builder. ## Verdict **Score: 7.6/10** This Divi review looked at the current $89/year and $249 lifetime plans, the Divi 5 rebuild released in February 2026, and ratings aggregated across three platforms (G2: 4.9/5, Capterra: 4.8/5, Trustpilot: 4.8). Verdict: Divi remains the strongest lifetime-license page builder for non-developers who want design freedom, but Divi 5's own JavaScript payload of roughly 45kb still trails Bricks Builder's leaner output on raw Core Web Vitals tests. **Quick scores:** - Ease of use: 8.5/10 - Design flexibility: 9/10 - Code output / performance: 6.5/10 - Pricing: 8/10 - Support: 8.5/10 **Pros:** - 2,000+ premade layouts across 200+ full website packs cut build time on client sites - Lifetime license at $249 is the cheapest one-time page builder deal we tracked in this category - Native Flexbox and CSS Grid controls in Divi 5 close most of the gap with block-theme layout tools **Cons:** - Shortcode-based markup still outputs heavier HTML than Bricks or a hand-built block theme, per independent 2026 speed tests - Divi AI, Divi Cloud and Divi Teams are locked behind the separate $277/year Pro tier, not the base plan - Sites built before Divi 5 need manual review before migrating, since the rendering engine changed *Call to action: Visit Divi's official site* (30-day money-back guarantee on every plan) > **Disclosure** — Disclosure: This review is based on Elegant Themes' official product and pricing pages, independently published 2026 performance benchmarks, and customer ratings aggregated from G2, Capterra and Trustpilot. We do not have an affiliate relationship with Elegant Themes for this product at the time of writing, so the call-to-action below points to Divi's official site rather than a tracked affiliate link. ## How we researched this review - **Tested for:** 6 days - **Plan paid:** Not subscribed; evaluated via Elegant Themes' public product, pricing and layout-library pages - **Version tested:** Divi 5 (initial 2026 rebuild), reviewed against Divi 4 for comparison - **Test period:** 2026-09-11 → 2026-09-17 **Test categories:** Pricing and licensing, Layout and module library, Performance benchmarks, Multi-platform customer ratings, Competing page builders Over six days we went through Divi's official product page, its live pricing page and its layout library, capturing our own screenshots of each rather than reusing marketing renders. We cross-referenced Elegant Themes' own Divi 5 performance claims (JavaScript payload down from 276kb to roughly 45kb, 16kb gzipped) against independent 2026 comparison benchmarks that place Divi behind Bricks Builder and Elementor on raw code output. Customer sentiment was pulled directly from G2 (239 reviews), Capterra (1,138 reviews, with sub-scores for ease of use, features, value and support) and Trustpilot (Elegant Themes' company-wide page, roughly 25,000 reviews). We did not run a paid 30-day build ourselves for this cycle; every price, rating and benchmark below is sourced and dated rather than estimated, and we flag that limitation rather than presenting secondary research as hands-on testing. ## Should you buy Divi? **YES if you...** - Freelancers and small agencies who want a lifetime license instead of a recurring plugin bill - Non-developers who need drag-and-drop design freedom without touching theme.json - Anyone building client sites from a library of premade layouts rather than from a blank page - Teams who value phone and live-chat support with a 4.9/5 Capterra support score behind it **NO if you...** - Developers chasing the leanest possible HTML output; Bricks Builder starts from a better baseline - Sites where Core Web Vitals is the top priority over design speed - Anyone who has already invested heavily in a native Gutenberg or FSE workflow and does not want a second builder layer - Budgets that cannot absorb the separate $277/year Pro tier if Divi AI or Divi Cloud become necessary later ## Divi pricing (2026) ### Yearly — $89/year Divi, Extra theme, Bloom and Monarch on unlimited sites - Divi theme + Visual Builder - Extra theme included - Bloom + Monarch plugins - Premium support and updates ### Lifetime — $249one-time *(Best value)* Everything in Yearly, no recurring fee, ever - Same feature set as Yearly - No renewal, ever - Unlimited sites - 30-day money-back guarantee ### Pro (add-on) — $277/year Adds Divi AI, Divi Cloud and Divi Teams to either base plan - Divi AI text and image generation - Divi Cloud asset library - Divi Teams collaboration - Priority support queue **ROI breakdown:** At two client builds a year using premade layout packs instead of custom development, the $249 lifetime plan pays for itself against a single $300-500 custom homepage build, then costs nothing on every site after. **Hidden costs & gotchas:** - Divi AI, Divi Cloud and Divi Teams sit behind the separate $277/year Pro tier, not the base plans - Many third-party child themes and layout packs (Divi Life, Divi Pixel, Divi Supreme) are sold separately - Sites built on Divi 4 may need manual review before adopting the Divi 5 rendering engine *[Interactive widget — see the live page for the full experience]* ## What the numbers actually say - **G2 rating:** 4.9 /5 *(239 reviews, 92% five-star, G2 product page, Sept 2026)* - **Capterra rating:** 4.8 /5 *(1,138 reviews; ease of use 4.6, value for money 4.8, support 4.9)* - **Trustpilot TrustScore:** 4.8 company-wide, ~25,000 reviews *(Elegant Themes' Trustpilot profile, not Divi-specific)* - **Divi 5 JavaScript payload:** ~45 kb (16kb gzipped) *(Down from 276kb in Divi 4, per Elegant Themes' Divi 5 benchmarks)* - **Layout library size:** 2,000+ premade layouts in 200+ website packs *(Elegant Themes layout library, checked Sept 2026)* > Task: open the official Divi layout library and check how premade website packs are organized before starting a client build The library groups layouts into full website packs by industry rather than single pages, which matches the 200+ website packs Elegant Themes advertises. Categories are browsable without logging in, which is unusual for a paid tool. > Task: check the live pricing page for the exact split between the Yearly, Lifetime and Pro plans The pricing page lists Yearly ($89) and Lifetime ($249) as the two core plans, with the $277/year Pro tier presented as an add-on rather than a separate product line, confirming Divi AI and Divi Cloud are not bundled into the base price. ## Divi pros and cons ### Pros - **2,000+ premade layouts cut build time** — Organized into 200+ full website packs by industry, which is a genuine head start compared to building sections from a blank canvas. - **Lifetime license at $249 is a real deal** — No recurring fee for unlimited sites is rare among page builders; Elementor and Bricks both run on annual renewals only. - **Support scores are consistently high** — Capterra's customer-service sub-score sits at 4.9/5 across 1,138 reviews, the highest of any category Divi is rated on. - **Native Flexbox and CSS Grid in Divi 5** — Closes a real gap with block-theme layout tools; earlier Divi versions relied on older float-based layout methods. ### Cons - **Shortcode output is heavier than Bricks or a hand-coded theme** — Independent 2026 speed comparisons consistently place Divi behind Bricks Builder and Elementor on raw HTML weight, even after the Divi 5 rewrite. - **Divi AI and Divi Cloud cost extra on top of the base plan** — Both sit behind the separate $277/year Pro tier, so the advertised AI features are not included in the $89 or $249 base plans. - **Migrating an older Divi 4 site takes deliberate review** — The Divi 5 rendering engine is a genuine rewrite, not a patch, so existing client sites should be checked page by page before switching. ## Final verdict **Score: 7.6/10** Divi earns its ratings. A 4.9/5 on G2, 4.8/5 on Capterra across 1,138 reviews, and a 4.8 TrustScore on Trustpilot are not small samples, and the $249 lifetime plan remains one of the better one-time deals in WordPress page builders. Divi 5's rebuild genuinely cuts its JavaScript footprint, from 276kb down to roughly 45kb, which matters for anyone who inherited a slow legacy Divi site. The honest limitation is code output. Bricks Builder and Elementor both post leaner benchmarks in independent 2026 comparisons, and Divi's shortcode-based markup is still the heavier option even after the rewrite. If your priority is the absolute leanest Core Web Vitals score, Bricks starts from a better baseline. If your priority is a library of ready-made layouts, a lifetime price, and support that clients rarely complain about, Divi is a defensible choice. Recommended for: freelancers and small agencies who value design speed and a one-time license over the cleanest possible markup. Not recommended for: teams whose primary metric is raw performance, or anyone already committed to a native FSE workflow who does not want a second builder layer on top. **Dimensional scoring:** - **Ease of use:** 8.5/10 — Drag-and-drop with a large layout library - **Design flexibility:** 9/10 — 200+ modules, native Flexbox/Grid in Divi 5 - **Code output / performance:** 6.5/10 — Improved, still trails Bricks and Elementor - **Pricing:** 8/10 — $249 lifetime is genuinely competitive - **Support:** 8.5/10 — 4.9/5 on Capterra's support sub-score *Call to action: Visit Divi's official site* ## Common questions about Divi ### Is Divi free? No. Divi has no free tier. Plans start at $89/year or $249 for a one-time lifetime license, both with a 30-day money-back guarantee. ### Is Divi better than Elementor? It depends on the priority. Elementor has the larger third-party add-on ecosystem and a genuinely useful free tier; Divi's lifetime license and premade layout library are stronger for agencies avoiding recurring costs. ### Is Divi slow? Divi 5 cut its JavaScript payload from 276kb to roughly 45kb (16kb gzipped), a real improvement. Independent 2026 benchmarks still place it behind Bricks Builder and Elementor on raw output, so implementation quality matters more than it used to. ### Does Divi include AI features? Divi AI exists, but it sits behind the separate $277/year Pro tier alongside Divi Cloud and Divi Teams. It is not included in the $89/year or $249 lifetime base plans. ### Can I switch away from Divi later? Content built with Divi's modules is stored in Divi's own format, so moving to another builder generally means rebuilding pages rather than a clean export. ### What is the difference between Divi and Divi Pro? Divi Pro adds Divi AI, Divi Cloud and Divi Teams for $277/year on top of either the Yearly or Lifetime base plan; the base plans cover the theme, Visual Builder, Extra theme, Bloom and Monarch. ### How many reviews does Divi have across platforms? As of September 2026: 239 reviews on G2 (4.9/5), 1,138 on Capterra (4.8/5), and Elegant Themes' Trustpilot page carries roughly 25,000 reviews at a 4.8 TrustScore. ### Does Divi work with WordPress block themes? Divi installs as its own theme and builder rather than layering onto a block theme, so it replaces the native Gutenberg/FSE workflow rather than extending it. ## Update log - **2026-09-17** — Initial publication: pricing, Divi 5 performance benchmarks and multi-platform ratings reviewed. ## FAQ ### Is Divi free? No. Divi has no free tier. Plans start at $89/year or $249 for a one-time lifetime license, both with a 30-day money-back guarantee. ### Is Divi better than Elementor? It depends on the priority. Elementor has the larger third-party add-on ecosystem and a genuinely useful free tier; Divi's lifetime license and premade layout library are stronger for agencies avoiding recurring costs. ### Is Divi slow? Divi 5 cut its JavaScript payload from 276kb to roughly 45kb (16kb gzipped), a real improvement. Independent 2026 benchmarks still place it behind Bricks Builder and Elementor on raw output, so implementation quality matters more than it used to. ### Does Divi include AI features? Divi AI exists, but it sits behind the separate $277/year Pro tier alongside Divi Cloud and Divi Teams. It is not included in the $89/year or $249 lifetime base plans. ### Can I switch away from Divi later? Content built with Divi's modules is stored in Divi's own format, so moving to another builder generally means rebuilding pages rather than a clean export. ### What is the difference between Divi and Divi Pro? Divi Pro adds Divi AI, Divi Cloud and Divi Teams for $277/year on top of either the Yearly or Lifetime base plan; the base plans cover the theme, Visual Builder, Extra theme, Bloom and Monarch. ### How many reviews does Divi have across platforms? As of September 2026: 239 reviews on G2 (4.9/5), 1,138 on Capterra (4.8/5), and Elegant Themes' Trustpilot page carries roughly 25,000 reviews at a 4.8 TrustScore. ### Does Divi work with WordPress block themes? Divi installs as its own theme and builder rather than layering onto a block theme, so it replaces the native Gutenberg/FSE workflow rather than extending it. --- ### 10Web Review (2026): Is the AI Website Builder Worth It? URL: https://noonwp.com/review/10web-review > We audited 10Web's pricing, hosting specs, and 2,627 reviews across five platforms. Honest verdict, dimensional scoring, refund complaints included, and who should actually sign up. *AI Website Builder & Hosting · Reviewed July 2026* ## 10Web Review (2026): Is the AI Website Builder Worth It? We audited the pricing, the hosting specs, and 2,627 aggregated reviews across five platforms so you do not have to dig through all of them yourself. ## Verdict **Score: 7.3/10** 10Web bundles an AI website builder, managed WordPress hosting, and an Elementor editor into one $10-a-month plan, and reviewers reward that convenience: 4.6/5 on G2 across 167 reviews. But the aggregate picture is uneven: Capterra sits at 3.8/5 across 44 reviews, and refund disputes recur on Trustpilot and Product Hunt. For a freelancer who wants one bill instead of four, it is a reasonable trade. For anyone who needs pixel control or a no-questions refund policy, look elsewhere first. **Quick scores:** - Ease of use: 8.5/10 - AI output quality: 6.5/10 - Hosting & performance: 8/10 - Pricing value: 6.5/10 - Customer support: 7/10 **Pros:** - One dashboard covers AI site generation, WordPress hosting, and management, so freelancers stop juggling four separate vendor logins - G2 reviewers rate it 4.6/5 across 167 reviews, with ease of use (42 mentions) and fast support (24 mentions) the top-cited strengths - 10Web Booster and Cloudflare Enterprise CDN (from AI Ultimate up) are built in, so a 90+ PageSpeed score needs no extra plugins - 1-click migration and site cloning bring an existing WordPress site over without touching DNS records by hand **Cons:** - Refund disputes recur across Trustpilot, Capterra, and Product Hunt, several citing renewals or trial charges billed without warning - AI credits (100/month on AI Starter) burn fast when you are reworking a stubborn prompt, per several G2 reviewers - Capterra's aggregate sits at 3.8/5, a full point below G2's 4.6/5, a gap wide enough to suggest an inconsistent experience *Call to action: Visit 10Web* (No affiliate relationship · pricing verified July 2026) > **Disclosure** — Disclosure: noonwp has no affiliate or sponsorship relationship with 10Web. This review is built from 10Web's public pricing and product pages plus an aggregation of 2,627 verified user reviews across G2, Capterra, Trustpilot, TrustRadius, and Product Hunt, all accessed in July 2026. Where we quote a number, we name the source. The Visit 10Web link below is a plain, nofollow link to the vendor's site, not a tracked referral. ## How we researched this review - **Version tested:** 10Web agentic AI Website Builder + Managed WordPress Hosting, live product, July 2026 - **Test period:** 2026-07-21 → 2026-07-23 **Test categories:** Pricing & hosting specs, Public builder interface, Aggregated customer sentiment, Competitor cross-check This review is desk research, not a paid 30-day subscription test, and we say so plainly. Over two days in July 2026 we audited 10Web's public marketing site, its pricing page (AI Starter, AI Premium, AI Ultimate, and Agency tiers), its managed-hosting spec sheet, and the public AI Website Builder chat interface, including the Figma import, clone-from-URL, redesign-from-URL options and the five named agents, two still flagged "(soon)". We then aggregated 2,627 verified reviews across five independent platforms: G2 (167), Capterra (44), Trustpilot (2,353), TrustRadius (19), and Product Hunt (44), reading the most-helpful and most-recent entries on each to find recurring themes rather than one-off complaints. Every pricing figure, hosting spec, and review-platform rating cited below is sourced and dated. ## Should you sign up? **YES if you...** - Freelancers who want AI generation, WordPress hosting, and a domain under one $10/month bill instead of stitching four vendors together - Small agencies managing 4-20 low-complexity client sites who value the white-label Agency dashboard over per-site custom builds - Anyone migrating an existing WordPress site who wants 1-click migration instead of a manual host-to-host transfer **NO if you...** - Anyone who has been burned by a no-refund policy before: Trustpilot, Capterra, and Product Hunt reviewers describe repeated friction getting money back - Designers who need pixel-level control over generated layouts; multiple reviewers describe the AI output as generic and template-like - Teams running 100+ small sites on tight per-site margins, who should compare the self-hosted VPS tier against 10Web's per-site add-on cost first ## 10Web pricing (billed annually) ### AI Starter — $10/mo 1 website, 100 AI credits/month - 1 website - 100 AI credits/month - 10GB SSD storage - 10K monthly visitors - Free custom domain (up to $30) - 24/7 chat support ### AI Premium — $15/mo 2 websites, 200 AI credits/month - 2 websites - 200 AI credits/month - 15GB SSD storage - 20K monthly visitors - 24/7 priority support ### AI Ultimate — $23/mo *(Best value)* 4 websites, Google Cloud hosting, Cloudflare CDN - 4 websites - 300 AI credits/month - 25GB SSD storage - 50K monthly visitors - Google Cloud Hosting - Cloudflare Enterprise CDN ### Agency Core — $112/mo 20 websites, white-label dashboard - 20 websites - 300 AI credits/month - 100GB SSD storage - 200K monthly visitors - Branded dashboard & invoices - 7% billing transaction fee **ROI breakdown:** 10Web's own math: AI Ultimate ($23/month annually) covers 4 websites, or $5.75 per site, cheaper than 4 separate WordPress hosts (typically $5-15/month each) plus a separate AI tool. For a single-site freelancer, the math is less obvious: $10/month for one site is not clearly cheaper than a budget WP host plus a free page builder unless the AI generation genuinely saves you build hours. **Hidden costs & gotchas:** - Monthly (no-commitment) billing roughly doubles the price: AI Starter is $20/mo month-to-month vs $10/mo billed annually - AI credits are metered per generation; reworking a stubborn prompt several times can burn a month's Starter allowance fast - Cloudflare Enterprise CDN and Google Cloud hosting are gated behind AI Ultimate ($23/mo), not included on Starter or Premium - Email hosting is not bundled at any tier, per repeated Capterra reviews; budget for a separate mail provider - Additional websites beyond your plan's included count cost $6-10/site/month, which adds up on a 10-20 site freelance book *[Interactive widget — see the live page for the full experience]* ## What we measured - **G2 aggregate rating:** 4.6 /5 across 167 reviews *(85% five-star, 2% one-star, accessed July 2026)* - **Capterra aggregate rating:** 3.8 /5 across 44 reviews *(Customer service sub-score 3.7/5, accessed July 2026)* - **Trustpilot aggregate rating:** ~4.0 /5 across 2,353 reviews *(Trustpilot's own headline rating, accessed July 2026)* - **Entry price:** $10 /month billed annually *(1 website, 100 AI credits/month, 10GB SSD, 10K visits)* - **Hosting uptime claim:** 99.99 % uptime *(10Web's managed-hosting page, Google Cloud infrastructure)* - **PageSpeed target:** 90+ score, desktop & mobile *(Via the built-in 10Web Booster, per the hosting spec page)* > Home page: the agentic AI Website Builder chat panel (accessed July 2026) The builder accepts a text prompt, dragged-in images, a Figma import (paid feature, shown locked), a clone-site-from-URL option, a redesign-site-from-URL option, and a screenshot-to-site option. Five named agents appear in the picker: Website Builder Agent, Editor Agent, and Ecommerce Agent are live; SEO Agent and Hosting Agent are still flagged "(soon)", meaning part of the agentic pitch has not shipped yet. > Pricing page: the four public plan tiers (accessed July 2026) AI Starter through Agency Core scale from $10 to $112/month billed annually, with AI credits (100 to 300+/month) and website counts (1 to 20+) as the two main levers. Cloudflare CDN and Google Cloud hosting only appear from AI Ultimate up, confirming they are not baseline features. > Managed hosting page: infrastructure and security claims (accessed July 2026) 10Web states Google Cloud hosting across 12 data centers, a 99.99% uptime claim, isolated containers per site, automated daily backups, and Cloudflare Enterprise bot/DDoS protection, all included from the entry tier upward. ## Pros & cons ### Pros - **All-in-one billing for builder, hosting, and domain** — One $10-23/month plan replaces a separate WordPress host, a page-builder license, and a domain registrar bill, the single most-repeated advantage across all five platforms we aggregated. - **Fast, named customer support agents** — Product Hunt reviewers name specific support staff unprompted; "excellent customer service" is the single most common Product Hunt tag (23 mentions) and G2's second most common (24 mentions). - **1-click migration and site cloning** — Multiple Capterra and TrustRadius reviewers confirm the migration plugin moves an existing WordPress site over without manual DNS work, though a few flag occasional plugin conflicts after the move. - **Built-in speed optimization hits 90+ PageSpeed** — 10Web Booster bundles caching, WebP image conversion, and Cloudflare CDN into the hosting tier, removing the need for a separate speed-plugin stack. ### Cons - **Refund and billing disputes recur across platforms** — Trustpilot, Capterra, and Product Hunt each carry multiple one-star reviews describing renewals or trial charges processed without clear warning, and a documented no-refund stance on at least one case per a Product Hunt reviewer. - **AI credits run out fast when a prompt needs rework** — The 100 AI credits/month on AI Starter are consumed by every regeneration attempt; several G2 reviewers say troubleshooting a stubborn prompt burns through a month's allowance well before four weeks are up. - **Capterra's score trails G2's by a full point** — Capterra's 3.8/5 across 44 reviews sits noticeably below G2's 4.6/5 across 167, and Capterra's own customer-service sub-score (3.7/5) is the softest number in the whole aggregate, suggesting an inconsistent experience. - **Generated layouts still need manual polish** — Multiple G2 and TrustRadius reviewers describe the AI-generated first draft as generic or template-like, with "accuracy of AI generated content" and "flexibility for advanced customization" both named as explicit cons on TrustRadius. ## Final verdict **Score: 7.3/10** 10Web's pitch is consolidation: one dashboard for AI site generation, managed WordPress hosting, and domain management, priced from $10/month billed annually. On the numbers, that pitch mostly holds up. G2 reviewers rate it 4.6/5 across 167 reviews, Product Hunt sits at 4.3/5 across 44, and the hosting spec sheet (99.99% uptime, 12 data centers, a 90+ PageSpeed target) is concrete and checks out against what reviewers describe experiencing. The softer numbers matter too. Capterra's 3.8/5 across 44 reviews and TrustRadius's 7.5/10 sit noticeably below G2's ceiling, and refund or billing disputes show up independently on three of the five platforms we aggregated, not just one disgruntled corner of the internet. AI credits are metered tightly enough that iterating on a stubborn prompt can eat a month's allowance. For a freelancer or small agency who wants fewer vendor logins and can live with a templated first draft, 10Web's bundle is a fair trade at the AI Starter or Premium tier. If a clean refund policy or pixel-perfect AI output matters more to you than consolidation, read the Capterra one-star reviews before you commit, and budget time to manually adjust whatever the builder hands you. **Dimensional scoring:** - **Ease of use:** 8.5/10 — Most-cited G2 and Product Hunt strength - **AI output quality:** 6.5/10 — Generic layouts, needs manual polish per multiple reviewers - **Hosting & performance:** 8/10 — 99.99% uptime claim, 90+ PageSpeed target - **Pricing value:** 6.5/10 — Fair at annual billing, doubles month-to-month - **Customer support:** 7/10 — Praised by name on Product Hunt, but refund friction recurs *Call to action: Visit 10Web* ## Common questions ### Is 10Web worth it in 2026? If you want AI generation, hosting, and a domain under one bill and can accept a templated first draft, yes, especially at the AI Premium or Ultimate tier. If a strict refund policy or advanced custom design matters most, weigh the Capterra and Product Hunt refund complaints first. ### How much does 10Web cost? Plans run $10 to $23/month when billed annually (AI Starter to AI Ultimate), roughly double month-to-month. Agency tiers start at $112/month for 20 websites, per 10Web's pricing page (July 2026). ### Does 10Web have a free trial? Yes, a short free trial is available before you are billed, per 10Web's own FAQ and multiple Trustpilot and Product Hunt reviewers who mention it. ### Is 10Web good for WordPress freelancers? Reasonably, for freelancers managing several small client sites: the Agency Core plan bundles 20 websites with a white-label dashboard. Compare the per-site add-on cost ($6-10/site) against your current hosting bill before switching. ### What do people dislike about 10Web? The most repeated complaints, aggregated across five platforms, are refund and billing disputes, AI credits running out during prompt iteration, and generic AI-generated layouts that need manual editing. ### Is 10Web better than Elementor or Divi AI? 10Web bundles hosting with its builder, which Elementor and Divi AI do not do natively. If you already have hosting you like, a standalone builder may suit you better; if you want one bill, 10Web's bundle is the differentiator. ### Can I migrate an existing WordPress site to 10Web? Yes. Reviewers on Capterra and TrustRadius confirm the 1-click migration plugin moves an existing site over, though a few note occasional plugin conflicts after the move. ### Does 10Web offer email hosting? No. Multiple Capterra reviewers flag that email is not bundled at any tier, so budget for a separate email provider. ## Update log - **2026-07-23** — Initial publication: pricing, hosting specs, and reviews aggregated across G2, Capterra, Trustpilot, TrustRadius, and Product Hunt (2,627 verified reviews). ## FAQ ### Is 10Web worth it in 2026? If you want AI generation, hosting, and a domain under one bill and can accept a templated first draft, yes, especially at the AI Premium or Ultimate tier. If a strict refund policy or advanced custom design matters most, weigh the Capterra and Product Hunt refund complaints first. ### How much does 10Web cost? Plans run $10 to $23/month when billed annually (AI Starter to AI Ultimate), roughly double month-to-month. Agency tiers start at $112/month for 20 websites, per 10Web's pricing page (July 2026). ### Does 10Web have a free trial? Yes, a short free trial is available before you are billed, per 10Web's own FAQ and multiple Trustpilot and Product Hunt reviewers who mention it. ### Is 10Web good for WordPress freelancers? Reasonably, for freelancers managing several small client sites: the Agency Core plan bundles 20 websites with a white-label dashboard. Compare the per-site add-on cost ($6-10/site) against your current hosting bill before switching. ### What do people dislike about 10Web? The most repeated complaints, aggregated across five platforms, are refund and billing disputes, AI credits running out during prompt iteration, and generic AI-generated layouts that need manual editing. ### Is 10Web better than Elementor or Divi AI? 10Web bundles hosting with its builder, which Elementor and Divi AI do not do natively. If you already have hosting you like, a standalone builder may suit you better; if you want one bill, 10Web's bundle is the differentiator. ### Can I migrate an existing WordPress site to 10Web? Yes. Reviewers on Capterra and TrustRadius confirm the 1-click migration plugin moves an existing site over, though a few note occasional plugin conflicts after the move. ### Does 10Web offer email hosting? No. Multiple Capterra reviewers flag that email is not bundled at any tier, so budget for a separate email provider. --- ### Durable Review 2026: Fast AI Sites, Honest Trade-offs URL: https://noonwp.com/review/durable-review > Nine days with Durable's AI site builder, cross-checked against 317 aggregated reviews. Real pricing, real screenshots, honest verdict for freelancers. *Audited over 9 days · July 2026* ## Durable Review 2026: What a WordPress Freelance Makes of the 30-Second AI Site Builder A freelance WordPress developer's honest look at whether Durable's AI generator earns a place in a lean web-building toolkit. ## Verdict **Score: 6.8/10** This Durable review comes from nine days testing the AI business builder against 317 aggregated user reviews and the live product itself. Verdict: Durable turns a business description into a hosted site in about 30 seconds and bundles CRM, invoicing and SEO tools around it, priced $22 to $41 a month. Fine for a first site with no HTML access. Not a WordPress replacement. **Quick scores:** - Ease of use: 9/10 - Speed to launch: 9.5/10 - Customization: 4.5/10 - Pricing value: 6.5/10 - Customer support: 7.5/10 **Pros:** - Generates a complete site, in about 30 seconds, from a short business description - Bundles CRM, invoicing, bookings and AI SEO tools in the same subscription - Free plan is genuinely usable for testing an idea before paying anything **Cons:** - No HTML or CSS access, so a freelance developer cannot hand off editable code - Templates look visually similar once populated, a recurring Product Hunt complaint - Domain and billing lock-in reported on Trustpilot, including a forced $15 to $25/mo upgrade *Call to action: Open the scriptorium* (Free plan available, no credit card required) > **Disclosure** — Disclosure: Durable has no affiliate programme in our records, so every link below points to Durable's official site and earns noonwp no commission. This review was not sponsored by Durable. It is based on nine days of hands-on evaluation of Durable's live product pages, template gallery and pricing tiers, plus 317 aggregated third-party reviews from named platforms. ## How this Durable review was built - **Tested for:** 9 days - **Plan paid:** Free plan (no paid Durable subscription was purchased for this audit) - **Version tested:** Durable web app and live marketing site, captured late June and early July 2026 - **Test period:** 2026-06-25 → 2026-07-03 **Test categories:** Onboarding and AI generation flow, Template range across industries, Pricing and hidden costs, Third-party review aggregation, Competitor cross-check I did not pay for a Durable subscription for this review. Over nine days between June 25 and July 3, 2026, I walked the live product end to end: the AI website builder page, the template gallery, the AI brand builder, and the full pricing comparison table, all captured as first-party screenshots rather than pulled from a press kit. Alongside that, I aggregated 317 verified user reviews across three platforms: G2 (2 reviews, 4.5/5), Product Hunt (13 reviews, 3.8/5) and Trustpilot (302 reviews, 4.7/5, rated Excellent). I cross-checked the pattern against TechRadar's independent editorial review and two Reddit threads from people who tried Durable for client or personal business work. I did not generate a paid Durable site myself, so speed and output claims below are sourced from Durable's own product pages, video walkthroughs and the aggregated reviews rather than a first-hand generation test. Where a figure comes from Durable's own marketing rather than an independent source, this review says so directly. ## Should a WordPress freelance recommend Durable? **YES if you...** - A solo founder who needs one page live today, with no budget for a developer - A client who explicitly does not want to touch HTML, CSS or a block editor - A side-business owner testing a name before committing to a real WordPress build **NO if you...** - Any client who needs custom Gutenberg block patterns, a multilingual RTL site or bespoke performance work - Agencies that bill for ongoing site edits, since Durable is closed-canvas with no exportable code - Anyone who needs full ownership of the underlying markup if they later migrate away ## Durable pricing ### Free — $0/mo Test an idea - Free .durable.site subdomain - 5 AI images per month - 10 AI chat messages per month - CRM for up to 10 customers - Basic help centre support ### Launch — $22/mo *(Most popular)* For a live small-business site - Free custom domain, up to $20 value - Advanced SEO and weekly visibility ranking - 50 AI images per month - CRM with 20 automated lead replies per month - 10 AI blog posts per month ### Grow — $41/mo For teams handling more volume - Unlimited team members - Personalised onboarding call - 500 AI images per month, unlimited AI chat - 32 AI blog posts and daily AI visibility ranking - 100 automated CRM lead replies per month **ROI breakdown:** For a solo tradesperson who would otherwise pay a freelancer $300 to $800 for a one-page brochure site, Launch at $22/mo breaks even inside the first month if it replaces that one-off spend, though it never stops being a subscription the way a one-off build does. **Hidden costs & gotchas:** - Removing Durable branding and advanced analytics requires the paid Launch tier, not Free - One Trustpilot reviewer described a forced move from a $15 to a $25/mo plan mid-billing-dispute - Exporting the site is not possible; leaving Durable means starting over on a new platform ## What we could verify - **Site generation time:** ~30 seconds, per Durable's own product page and 2 independent video walkthroughs *(Self-reported by Durable, corroborated by TechRadar and unaffiliated YouTube reviews; not independently re-timed by us)* - **Aggregated review volume:** 317 verified reviews across 3 platforms *(G2 n=2 (4.5/5), Product Hunt n=13 (3.8/5), Trustpilot n=302 (4.7/5), captured July 2026)* - **Entry paid tier:** $22 /mo for the Launch plan, custom domain plus 50 AI images/mo *(Verified directly on durable.com/pricing, July 2026)* - **Trustpilot score:** 4.7 out of 5, rated Excellent *(302 reviews total, 107 in the last 12 months, captured from Durable's Trustpilot profile)* - **Claimed install base:** 3,000,000+ businesses built on Durable *(Self-reported by Durable on its own pricing page, not independently audited)* > Durable's public onboarding flow: business type, city and name, no account signup completed by us Durable's own demo and independent video walkthroughs show a generated one-page site with a hero image, a services list, a contact form and a matching logo, delivered inside the stated 30 seconds. We did not create an account to re-run this ourselves, so the timing claim rests on Durable's own capture plus two external video reviews. > Browsing Durable's public template gallery, grouped by small-business category The gallery groups templates by category: services, retail, food, wellness. Several Product Hunt reviewers independently flagged that templates in the same category look near-identical once populated, and the public gallery screenshots show the same shared layout blocks with swapped photos. > Reviewing Durable's AI brand builder demo for logo, font and colour output The brand builder page generates a logo, a font pairing and a colour palette together as one step. That is a genuine convenience next to a Gutenberg workflow, where a freelance typically handles logo, Type Rubric font scale and Palette Librarian colours as three separate tasks. ## Pros and cons, in detail ### Pros - **Generates a working site in about 30 seconds from a short brief** — Consistent across Durable's own product pages and independent video walkthroughs. We did not re-time this ourselves without an account, but no source we found contradicts the 30-second figure. - **CRM, invoicing, bookings and AI marketing bundled in one subscription** — Where a WordPress freelance would typically wire together a form plugin, a calendar plugin and a separate CRM, Durable ships all three under one login starting at $22/mo. - **Customer support is the strongest recurring theme in real reviews** — Both the G2 and Trustpilot review sets independently surface support quality as the top praised theme, with named support staff mentioned repeatedly by different reviewers. ### Cons - **No HTML or CSS access, so nothing is portable to another platform** — Durable's own FAQ confirms it is a closed no-code system. A WordPress freelance cannot hand a client an exportable theme the way they would with a block theme build. - **Templates look interchangeable once populated with real content** — Multiple Product Hunt reviewers flagged this independently, calling the interface rudimentary with limited customization, and the public template gallery shows shared layout structures across categories. - **Domain and billing lock-in shows up repeatedly in negative reviews** — A 2026 Trustpilot review describes losing site access over a forced tier upgrade from $15 to $25/mo, and a separate Product Hunt review reports a multi-month wait to regain a domain after cancelling. ## Final verdict **Score: 6.8/10** Durable does what it says: describe a small business and get a live, hosted site in roughly 30 seconds, with a CRM, invoicing and basic SEO wrapped around it for $22 to $41 a month. For a solo tradesperson who needs one page online this week and will never touch a block editor, that is a fair trade. For anyone reading noonwp, the calculation is different. Durable is a closed canvas: no HTML export, no block patterns, no way to hand a client an editable theme when the relationship ends. Every recurring complaint in the 317 reviews we aggregated points the same direction: generic templates once populated, and support that is excellent until a billing dispute locks the domain. Recommend Durable to a client who wants speed over control. Keep block theme work for clients who want to own what they publish. The two audiences rarely overlap, and pretending otherwise does neither one any favours. **Dimensional scoring:** - **Speed to launch:** 9/10 — About 30 seconds, per Durable and 2 independent video reviews - **Ease of use:** 9/10 — Confirmed by both G2 reviewers and most Trustpilot themes - **Customization and ownership:** 3.5/10 — No code export, no HTML access - **Pricing value:** 6.5/10 — $22/mo Launch is fair against a one-off freelance brochure site - **Support quality:** 7.5/10 — Top praised theme across G2 and Trustpilot, weekend coverage flagged as a gap *Call to action: Illuminate your site* ## Common questions about Durable ### Is Durable actually free? Yes. The Free plan is $0 and includes a subdomain, basic SEO, a CRM for up to 10 customers and 5 AI images a month. The $22/mo Launch plan is needed for a custom domain and to remove Durable's branding. ### Can I edit the HTML Durable generates? No. Durable is a closed no-code builder. Its own help centre confirms there is no HTML export, which matters if you ever want to move the site to WordPress or another host. ### How does Durable compare to a WordPress block theme? Durable is faster to launch and needs zero technical skill, but a block theme built with Pattern Forge or by hand gives full ownership of the markup, RTL support and the freedom to move hosts. They solve different problems for different budgets. ### Is Durable good for e-commerce? Durable says it is not designed specifically for e-commerce, though its own blog documents clients who launched stores on it. For a serious product catalogue, a dedicated e-commerce platform or WooCommerce on WordPress will scale further. ### What do real Durable users complain about most? Across the 317 reviews we aggregated, the two recurring complaints are limited visual customization once a template is populated, and domain or billing friction when downgrading or cancelling a plan. ### Does Durable help with AI search visibility, not just Google? Durable bundles basic SEO metadata, structured data and an llms.txt file aimed at AI assistants on its paid tiers. We have not independently measured ranking outcomes, so treat this as a Durable-stated feature rather than a verified result. ### Can I keep my domain if I cancel Durable? Durable's FAQ says yes, with a transfer that takes a couple of weeks and a minimum subscription period. At least one Trustpilot reviewer reported a rockier experience during a billing dispute, so confirm your account is in good standing before cancelling. ## Update log - **2026-07-04** — Initial publication after a 9-day product and review audit; no paid Durable subscription was purchased. ## FAQ ### Is Durable actually free? Yes. The Free plan is $0 and includes a subdomain, basic SEO, a CRM for up to 10 customers and 5 AI images a month. The $22/mo Launch plan is needed for a custom domain and to remove Durable's branding. ### Can I edit the HTML Durable generates? No. Durable is a closed no-code builder. Its own help centre confirms there is no HTML export, which matters if you ever want to move the site to WordPress or another host. ### How does Durable compare to a WordPress block theme? Durable is faster to launch and needs zero technical skill, but a block theme built with Pattern Forge or by hand gives full ownership of the markup, RTL support and the freedom to move hosts. They solve different problems for different budgets. ### Is Durable good for e-commerce? Durable says it is not designed specifically for e-commerce, though its own blog documents clients who launched stores on it. For a serious product catalogue, a dedicated e-commerce platform or WooCommerce on WordPress will scale further. ### What do real Durable users complain about most? Across the 317 reviews we aggregated, the two recurring complaints are limited visual customization once a template is populated, and domain or billing friction when downgrading or cancelling a plan. ### Does Durable help with AI search visibility, not just Google? Durable bundles basic SEO metadata, structured data and an llms.txt file aimed at AI assistants on its paid tiers. We have not independently measured ranking outcomes, so treat this as a Durable-stated feature rather than a verified result. ### Can I keep my domain if I cancel Durable? Durable's FAQ says yes, with a transfer that takes a couple of weeks and a minimum subscription period. At least one Trustpilot reviewer reported a rockier experience during a billing dispute, so confirm your account is in good standing before cancelling. --- ## Landings ### Best Website Builder for WordPress Freelances and Agencies URL: https://noonwp.com/lp/best-website-builder > How to choose the best website builder for client sites: portability, real markup, RTL support and renewal cost, compared across hosted, plugin and native block options. *For WordPress freelances and agencies* ## Best Website Builder: Already Inside WordPress The best website builder for client work is the one you can hand over. Draft blocks with noonwp, refine them in the Site Editor, keep every file. ## Six tests a website builder should pass Skip the feature checklist. These are the questions that decide whether the builder still serves you in year two. ### Can you leave? Export the site and keep working. If the layout only exists inside one vendor's runtime, you have rented it, not built it. ### Does it use real markup? Standard HTML and block markup can be read, diffed and fixed by any developer. Proprietary widget trees cannot. ### Can a client edit safely? A client should change copy and photos without breaking the layout. Locked patterns and clear templates do that job. ### Does it mirror for RTL? Arabic and Hebrew layouts should flip by default. If it needs manual overrides on every page, the cost shows up later. ### How heavy is the output? Page weight and script load feed straight into Core Web Vitals. Measure a real page, not the vendor's demo. ### What does year two cost? Compare the renewal price per site, not the first month. Agencies running twenty sites feel this fastest. *The honest map* ## Hosted builders, page builders, or native blocks Hosted builders such as Wix and Squarespace bundle design, hosting and editing in one subscription. That is a fair trade for a solo shop with one site and no plans to move. Page builder plugins like Elementor and Divi sit on top of WordPress and add their own layout system. Native blocks use what WordPress already ships. Each fits a different job, and the table below sets them side by side. - Hosted: fastest start, least portability - Page builder plugin: flexible, tied to the plugin - Native blocks: more setup, files you keep ## From brief to handed-over site 1. **Write the brief in plain English** — Describe the section you need: a pricing row, a services grid, a hero with a call to action. Specifics beat adjectives. 2. **Let Pattern Forge draft the blocks** — You get native Gutenberg blocks placed on the canvas, with Palette Librarian colors and Type Rubric scales taken from theme.json. 3. **Refine in the Site Editor** — Move, resize and restyle. This is the part no generator replaces, and it is where your judgment earns its fee. 4. **Save the pattern, hand over the theme** — Commit the pattern to the theme. The client gets files and a login, not a subscription to renew. *The differentiator* ## Built to mirror for Arabic and Hebrew Most comparisons of website builders never mention right-to-left. For MENA publishers it decides the whole project. RTL Concordance writes logical CSS properties into each pattern, so a bilingual EN and AR layout mirrors on the first pass. Check it against real Arabic copy before you promise a client anything, and expect to adjust fonts as well as direction. - Logical CSS instead of hardcoded left and right - Layouts checked with real Arabic and Hebrew text - One theme.json for two reading directions ## Which website builder fits which job | Criteria | noonwp with WordPress | Hosted builder | Page builder plugin | |---|---|---|---| | Where the layout lives | Core block markup in your theme | Inside the vendor platform | Inside the plugin's layout system | | Moving to another host | Straightforward, files are yours | Usually means a rebuild | Possible, plugin must follow | | Full Site Editing | Native | Not applicable | Partial, varies by plugin | | RTL handling | Logical CSS by default | Depends on the template | Often manual overrides | | Best for | Agencies and freelances handing sites over | One-off sites with no migration plans | Teams already invested in that plugin | | Entry price | Monk plan, $0 | Paid plan from the start | Plugin license on top of WordPress | ## Start on one real page, pay when it earns ### Monk — $0/mo - One site - Limited monthly generations - Pattern Forge drafts - Native Gutenberg output ### Scribe — $12/mo - More generations each month - Page Scribe full-page drafts - Palette Librarian and Type Rubric - RTL Concordance ### Abbey — $49/mo - Highest generation allowance - Several client sites - Shared pattern libraries - Priority support ## Choosing a website builder, answered ### What is the best website builder for client work? It depends on what happens after launch. Hosted builders such as Wix or Squarespace are quick to start, but the site stays inside their platform. For freelances and agencies who hand sites over, a WordPress block theme edited in the Site Editor keeps the code portable and the client free to change hosts. ### Is WordPress really a website builder? Since Full Site Editing, yes. The Site Editor lets you build headers, templates and pages from blocks without a separate page builder plugin. It asks more of you than a hosted builder, and it gives you the files in return. ### Where does noonwp fit among website builders? noonwp is not a hosted builder. Pattern Forge drafts native Gutenberg patterns, Page Scribe drafts whole pages, and you refine them in the Site Editor. The output is standard block markup saved in your own theme. ### Do I need Elementor or Divi on top of the block editor? Not for most client sites. Elementor and Divi add their own layout layer, which can speed up some tasks but ties the content to that plugin. Core blocks with a good pattern library cover the common cases. ### Which website builder handles Arabic and Hebrew best? Few builders treat right-to-left as a first-class case. RTL Concordance writes logical CSS properties into each pattern, so a layout mirrors without manual left and right overrides. Always test with real Arabic or Hebrew copy, not placeholder text. ### How much does noonwp cost? Monk is free and covers a single site with limited monthly generations. Scribe is $12 a month and Abbey is $49 a month. Start with Monk on one real client page before deciding. ### Can I switch away from noonwp later? Yes. Patterns are saved as core block markup in your theme, so they keep working if you cancel. There is no runtime to unwind, only files you already own. ## Build one page. Judge the builder. Take a real client brief, draft it with Pattern Forge on the free plan, and see whether you would hand it over. *Call to action: Draft a pattern* ## FAQ ### What is the best website builder for client work? It depends on what happens after launch. Hosted builders such as Wix or Squarespace are quick to start, but the site stays inside their platform. For freelances and agencies who hand sites over, a WordPress block theme edited in the Site Editor keeps the code portable and the client free to change hosts. ### Is WordPress really a website builder? Since Full Site Editing, yes. The Site Editor lets you build headers, templates and pages from blocks without a separate page builder plugin. It asks more of you than a hosted builder, and it gives you the files in return. ### Where does noonwp fit among website builders? noonwp is not a hosted builder. Pattern Forge drafts native Gutenberg patterns, Page Scribe drafts whole pages, and you refine them in the Site Editor. The output is standard block markup saved in your own theme. ### Do I need Elementor or Divi on top of the block editor? Not for most client sites. Elementor and Divi add their own layout layer, which can speed up some tasks but ties the content to that plugin. Core blocks with a good pattern library cover the common cases. ### Which website builder handles Arabic and Hebrew best? Few builders treat right-to-left as a first-class case. RTL Concordance writes logical CSS properties into each pattern, so a layout mirrors without manual left and right overrides. Always test with real Arabic or Hebrew copy, not placeholder text. ### How much does noonwp cost? Monk is free and covers a single site with limited monthly generations. Scribe is $12 a month and Abbey is $49 a month. Start with Monk on one real client page before deciding. ### Can I switch away from noonwp later? Yes. Patterns are saved as core block markup in your theme, so they keep working if you cancel. There is no runtime to unwind, only files you already own. --- ### The Drag and Drop Website Builder Built Into WordPress URL: https://noonwp.com/lp/drag-and-drop-website-builder > See how noonwp turns WordPress's block editor into a real drag and drop website builder, with AI-drafted patterns and native RTL support. *For WordPress freelances & agencies* ## A Drag and Drop Website Builder, Native to WordPress Pattern Forge drafts the Gutenberg blocks. You drag, resize and rearrange them in the Site Editor, no separate page builder plugin needed. ## Six things a native block builder gets right No proprietary widget tree. Every block you drag is markup you can read and keep. ### Drag, resize, reorder Pick up a Group, Cover or Query Loop block in the Site Editor canvas and move it, no separate builder plugin sitting on top of WordPress. ### Pattern Forge drafts the start Describe a hero or pricing section in plain English. Pattern Forge returns native Gutenberg blocks already placed on the canvas, ready to rearrange. ### Palette Librarian, on brand OKLCH palettes matched to a brand brief, written into theme.json so every dragged block picks up the right colors automatically. ### Type Rubric type scales Variable font scales set once in theme.json. Drag a heading block anywhere and the typography stays consistent. ### RTL Concordance built in Arabic and Hebrew layouts mirror correctly by default: logical CSS properties instead of manual left and right overrides after the fact. ### No runtime to unwind later The output is standard block markup saved to your own theme files, not a widget tree tied to a page builder subscription. *Who drags what, in practice* ## Built for a WordPress freelance running more than one client site A one-person practice cannot hand-build a unique hero for every client. The drag and drop part happens in the Site Editor canvas: Pattern Forge drafts the starting blocks, you rearrange, resize and restyle them against the brief, then commit the pattern to the theme. The next client site starts from a library, not a blank canvas. - Pattern libraries reused across a dozen small-budget sites - Client handoff without a page builder subscription to renew - Drag and drop that stays inside core WordPress, not a plugin runtime - Faster iteration once the first few patterns exist *The differentiator most builders skip* ## Drag and drop that mirrors correctly for Arabic and Hebrew sites Most page builders treat right-to-left as an afterthought: manual CSS overrides, a plugin bolted on after launch, spacing that breaks the moment real Arabic copy replaces the placeholder text. RTL Concordance writes logical CSS properties into every pattern by default, so a block dragged into a bilingual EN/AR layout mirrors on the first try, checked against real Arabic and Hebrew content, not lorem ipsum. - Layout mirroring checked against real Arabic and Hebrew text - Logical CSS properties instead of hardcoded left and right - One theme.json, two reading directions ## noonwp vs. Elementor vs. Divi, on the criteria that matter later | Criteria | noonwp | Elementor | Divi | |---|---|---|---| | Where blocks live | Native Gutenberg, core WordPress | Elementor's own widget tree | Divi Builder's own module tree | | Full Site Editing support | Built for FSE block themes | Bolt-on, not FSE-native | Bolt-on, not FSE-native | | RTL layout handling | RTL Concordance, logical CSS by default | Manual CSS overrides typical | Manual CSS overrides typical | | Code if you switch builders | Standard theme.json patterns you keep | Locked to the Elementor runtime | Locked to the Divi runtime | | Entry price | Monk plan, $0 | Paid add-on on top of Elementor Pro | Bundled in Divi, about $89/yr | ## Pricing scoped to how many sites you drag and drop ### Monk — $0 - Pattern Forge, limited generations per month - Standard Gutenberg block output - Community support ### Scribe — $12/mo - Pattern Forge, unlimited generations - Page Scribe for full FSE pages - Palette Librarian, OKLCH palettes - Type Rubric type scales - Email support ### Abbey — $49/mo - Everything in Scribe - RTL Concordance for bilingual sites - Multi-site pattern libraries - Priority support ## Before you drag your first block ### Is the WordPress Site Editor actually a drag and drop website builder? Yes, inside core WordPress. You can pick up a block in the Site Editor canvas, move it, resize it and restyle it without installing a separate page builder plugin. Pattern Forge just drafts the starting blocks faster. ### Do I still need Elementor or Divi alongside Pattern Forge? No. Pattern Forge and Page Scribe output native Gutenberg blocks that live in the Site Editor. A page builder plugin adds its own widget tree on top, which is exactly what this setup avoids. ### What happens to the patterns if I stop paying for noonwp? You keep the code. Output is standard Gutenberg block markup saved to your own theme files, not a runtime rented from a plugin subscription. ### Can I drag and drop on an existing WordPress site, or only a fresh install? A block theme built for Full Site Editing works best. On a classic theme, Pattern Forge can still draft blocks for the content area, but full-canvas dragging needs FSE support. ### How does RTL Concordance handle Arabic or Hebrew during drag and drop? It writes logical CSS properties into the pattern by default, so a block dragged into a bilingual layout mirrors correctly instead of needing manual left and right overrides afterward. ### Is there a free plan to try the drag and drop workflow? Monk, for $0, covers a single site with a limited number of monthly generations: enough to see what a real Gutenberg pattern looks like before committing to Scribe or Abbey. ### How is this different from Elementor AI or Divi AI? Elementor AI and Divi AI generate content for their own proprietary builder runtimes. Pattern Forge generates native Gutenberg blocks, which stay portable if a client later switches hosts or themes. ## Set the folio for your next client site Start on Monk, free, and see what a dragged Gutenberg pattern looks like before you commit to a plan. *Call to action: Set the folio* ## FAQ ### Is the WordPress Site Editor actually a drag and drop website builder? Yes, inside core WordPress. You can pick up a block in the Site Editor canvas, move it, resize it and restyle it without installing a separate page builder plugin. Pattern Forge just drafts the starting blocks faster. ### Do I still need Elementor or Divi alongside Pattern Forge? No. Pattern Forge and Page Scribe output native Gutenberg blocks that live in the Site Editor. A page builder plugin adds its own widget tree on top, which is exactly what this setup avoids. ### What happens to the patterns if I stop paying for noonwp? You keep the code. Output is standard Gutenberg block markup saved to your own theme files, not a runtime rented from a plugin subscription. ### Can I drag and drop on an existing WordPress site, or only a fresh install? A block theme built for Full Site Editing works best. On a classic theme, Pattern Forge can still draft blocks for the content area, but full-canvas dragging needs FSE support. ### How does RTL Concordance handle Arabic or Hebrew during drag and drop? It writes logical CSS properties into the pattern by default, so a block dragged into a bilingual layout mirrors correctly instead of needing manual left and right overrides afterward. ### Is there a free plan to try the drag and drop workflow? Monk, for $0, covers a single site with a limited number of monthly generations: enough to see what a real Gutenberg pattern looks like before committing to Scribe or Abbey. ### How is this different from Elementor AI or Divi AI? Elementor AI and Divi AI generate content for their own proprietary builder runtimes. Pattern Forge generates native Gutenberg blocks, which stay portable if a client later switches hosts or themes. --- ### AI for Software Development on WordPress | noonwp.com URL: https://noonwp.com/lp/ai-for-software-development > AI for software development, scoped to WordPress: generate Gutenberg patterns and FSE pages from plain language, then review the code before it ships. *For WordPress freelances & agencies* ## AI for Software Development on WordPress Turn a plain-language brief into Gutenberg patterns and full FSE pages, then read the markup before it ships to a client site. ## Five tools, one flux de travail Each tool produces something you can inspect in the Site Editor, not a black box widget. ### Pattern Forge Describe a hero, a pricing table, or a testimonial row. Pattern Forge returns native Gutenberg block markup, not a proprietary shortcode. ### Page Scribe Draft a full FSE page, template parts included, from a short brief. You still choose what ships to production. ### RTL Concordance Bilingual EN/AR and EN/HE layouts with direction-aware CSS handled by default, not bolted on after launch. ### Type Rubric A type scale built from variable fonts and written straight into theme.json, ready for a block theme. ### Palette Librarian OKLCH color palettes matched to a brand brief, exported as design tokens your theme.json can read. ## Four steps, one of them is reading the code 1. **Describe the brief** — Write what the block or page needs to do, in plain English. No prompt syntax to learn. 2. **Generate the pattern** — Pattern Forge or Page Scribe returns Gutenberg block markup you can open straight in the Site Editor. 3. **Read the markup** — Check the HTML, the class names, and how it behaves in RTL before it touches a client site. 4. **Ship and iterate** — Commit the pattern to the theme, adjust with Type Rubric or Palette Librarian, and move to the next page. *Who this is built for* ## Built for freelances who ship on a deadline, not a demo A one-person WordPress practice cannot hand-code every hero section for every client. noonwp is aimed at that gap: the freelance or small agency that needs AI for software development inside a WordPress workflow specifically, not a general-purpose coding assistant that has never seen a block theme. The output is markup you own, not a rented widget tree. - Bilingual EN/AR sites for charities and small publishers - Client handoff without a proprietary builder lock-in - Pattern libraries reused across a dozen small-budget sites - RTL-safe layouts without manual CSS overrides each time ## noonwp vs. Elementor AI vs. Divi AI | Criteria | noonwp | Elementor AI | Divi AI | |---|---|---|---| | Output format | Native Gutenberg blocks | Elementor widgets (proprietary) | Divi Builder modules (proprietary) | | Full Site Editing support | Built for FSE block themes | Bolt-on, not FSE-native | Bolt-on, not FSE-native | | RTL layout handling | RTL Concordance built in | Manual CSS overrides typical | Manual CSS overrides typical | | Code portability if you switch | Exports to standard theme.json patterns | Locked to the Elementor runtime | Locked to the Divi runtime | | Entry price | Monk plan, $0 | Paid add-on on top of Elementor Pro | Bundled in Divi, ~$89/yr | ## Pricing built around how many sites you run ### Monk — $0 - Pattern Forge, limited generations per month - Standard Gutenberg block output - Community support ### Scribe — $12/mo - Pattern Forge, unlimited generations - Page Scribe for full FSE pages - Palette Librarian, OKLCH palettes - Type Rubric type scales - Email support ### Abbey — $49/mo - Everything in Scribe - RTL Concordance for bilingual sites - Multi-site pattern libraries - Priority support ## Before you draft your first pattern ### Is noonwp AI for software development in general, or just WordPress? Just WordPress, on purpose. noonwp does not write Python or a React app. It generates Gutenberg block markup, FSE templates, and theme.json tokens: a scoped slice of software development, not a general-purpose coding assistant. ### If I stop paying, do I keep the code Pattern Forge generated? Yes. Output is standard Gutenberg block markup saved to your own theme files. There is no proprietary runtime to unwind, unlike a page-builder widget tree. ### How does RTL Concordance actually handle Arabic or Hebrew? It writes direction-aware CSS into the pattern by default: logical properties instead of hardcoded left and right, and layout mirroring checked against real Arabic and Hebrew content, not lorem ipsum. ### Can an agency use one account across multiple client sites? The Abbey plan is built for that: multi-site pattern libraries so a header built for one client can be adapted for the next without starting from a blank prompt. ### What is the difference between Pattern Forge and Page Scribe? Pattern Forge generates a single block or section. Page Scribe assembles a full FSE page, template parts included, from the same kind of plain-language brief. ### Does the free Monk plan work for a real project? For a single small site, yes, within the monthly generation limit. Most freelances outgrow it once they are running more than one client site at a time. ### How is this different from Elementor AI or Divi AI? Elementor AI and Divi AI generate content for their own proprietary builder runtimes. noonwp generates native Gutenberg blocks, which stay portable if a client later switches hosts or themes. ## Set the folio for your next client site Start on Monk, free, and see what a real Gutenberg pattern looks like before you commit to a plan. *Call to action: Set the folio* ## FAQ ### Is noonwp AI for software development in general, or just WordPress? Just WordPress, on purpose. noonwp does not write Python or a React app. It generates Gutenberg block markup, FSE templates, and theme.json tokens: a scoped slice of software development, not a general-purpose coding assistant. ### If I stop paying, do I keep the code Pattern Forge generated? Yes. Output is standard Gutenberg block markup saved to your own theme files. There is no proprietary runtime to unwind, unlike a page-builder widget tree. ### How does RTL Concordance actually handle Arabic or Hebrew? It writes direction-aware CSS into the pattern by default: logical properties instead of hardcoded left and right, and layout mirroring checked against real Arabic and Hebrew content, not lorem ipsum. ### Can an agency use one account across multiple client sites? The Abbey plan is built for that: multi-site pattern libraries so a header built for one client can be adapted for the next without starting from a blank prompt. ### What is the difference between Pattern Forge and Page Scribe? Pattern Forge generates a single block or section. Page Scribe assembles a full FSE page, template parts included, from the same kind of plain-language brief. ### Does the free Monk plan work for a real project? For a single small site, yes, within the monthly generation limit. Most freelances outgrow it once they are running more than one client site at a time. ### How is this different from Elementor AI or Divi AI? Elementor AI and Divi AI generate content for their own proprietary builder runtimes. noonwp generates native Gutenberg blocks, which stay portable if a client later switches hosts or themes. --- ## Tools ### AI Wireframe Generator: Free Page Layout Tool (2026) URL: https://noonwp.com/tools/ai-wireframe-generator > Pick a page type and a layout style, then watch a real low-fidelity wireframe redraw live. A free planning step before you touch the block editor. ## AI Wireframe Generator: Block Out a Page Layout in Seconds Pick a page type, a layout style, and a section count. A real low-fidelity box layout redraws live, before a single Gutenberg block gets placed. ## Sketch your page layout Choose the page type you are building, a layout style for the content area, and how many sections it needs. The boxes below update on every change. *[Interactive widget — see the live page for the full experience]* ## Built on layout conventions, not on guesses ### F-pattern and Z-pattern reading order Stacked content bands follow the F-pattern that eye-tracking research keeps finding on text-heavy pages. A centered hero with the headline, subheadline, and call-to-action in a row follows the Z-pattern instead, the shape a reader's eye traces on a sparse, decision-first screen. ### Page-type presets built on real conventions A dashboard keeps a persistent left navigation column no matter what else changes, the way admin panels are actually built. A blog post pairs a main article column with a sidebar. A product page splits into a gallery and a buy box above the fold, then stacks detail sections below. ### Grid math that actually responds The grid layout uses CSS auto-fill so cards reflow on their own as the section count changes, and every arrangement, grid, stacked, or sidebar, collapses to one column under about 480px wide. No manual breakpoint tuning to check on a phone. ## Three settings, one draft 1. **1. Pick the page type** — Landing page, blog post, dashboard, product page, portfolio, or contact form. This sets the header, the hero shape, and the footer to match what that page type actually needs. 2. **2. Choose a layout style** — Stacked bands, a grid of cards, or a sidebar next to a main column. Each page type opens with the style most builders reach for, and you can override it. 3. **3. Set the section count** — Slide from two to eight content sections. The wireframe below adds or removes boxes live, keeping the same header, hero, and footer in place. ## A draft you can put in front of a client before touching the Site Editor A wireframe this rough is not meant to survive contact with real copy. It is meant to get a page's skeleton agreed on fast: how many sections, what sits above the fold, whether the blog needs a sidebar at all. Once that skeleton is settled, building the matching Group, Cover, and Query Loop blocks in the Site Editor is a much shorter conversation, because nobody is arguing about structure anymore, only about the words and the images that go inside it. - Agree on section count before opening the Site Editor - Show a client two layout styles in the same call - Check the mobile version on the same screen as the desktop draft ## Common questions about the wireframe generator ### Is this AI wireframe generator free? Yes. It runs fully in your browser with no signup and no usage limit. There is no server call: the layout math happens on your device the moment you move a control. ### Does it store or send my inputs anywhere? No. Page type, layout style, and section count stay in the page's memory only. Nothing is written to a database and nothing is sent to a server, aside from an anonymous tool-run beacon used to measure how many visitors try the tool. ### Where do these layout patterns come from? From documented, widely cited UX research rather than guesswork: the F-pattern and Z-pattern eye-tracking studies (Nielsen Norman Group), the persistent-sidebar-nav convention used across admin dashboards, the split gallery-plus-buy-box pattern common on product pages (a Baymard Institute finding), and the single-column layout that usability research consistently finds converts best for short forms. ### Can I export this wireframe as a real Gutenberg pattern? Not directly. This is a planning step, not a code generator: it helps you agree on a structure with a client or a teammate before you open the Site Editor and build the matching Group, Cover, and Query Loop blocks by hand. ### Why does the dashboard page type always keep a left sidebar, no matter what layout I pick? Because a persistent navigation column is a structural convention of admin dashboards, not a stylistic choice. The layout selector still changes how the widgets inside it are arranged (a grid of cards or a stacked list), but removing the nav column would misrepresent how real dashboards are built. ### What layout style should I use for a landing page? Grid of cards is the default for landing pages and portfolios, since feature and project sections are usually scannable side by side. Stacked bands suit a product page or a form, where you want visitors reading one thing at a time. ### Does the wireframe work on a small phone screen? Yes. Every layout collapses to a single column under roughly 480px wide, including the grid and the sidebar-plus-main arrangement, so you can check a mobile draft on the same screen as the desktop one. ### Will more page types get added later? Landing page, blog post, dashboard, product page, portfolio, and contact form cover the page types freelance WordPress builders draft most often. If a clear gap shows up in practice, it gets added to the preset list. ## More WordPress tools worth keeping open in a tab noonwp covers Gutenberg, Full Site Editing, and RTL WordPress for people who ship client sites, not just read about them. *Call to action: Open the scriptorium* ## FAQ ### Is this AI wireframe generator free? Yes. It runs fully in your browser with no signup and no usage limit. There is no server call: the layout math happens on your device the moment you move a control. ### Does it store or send my inputs anywhere? No. Page type, layout style, and section count stay in the page's memory only. Nothing is written to a database and nothing is sent to a server, aside from an anonymous tool-run beacon used to measure how many visitors try the tool. ### Where do these layout patterns come from? From documented, widely cited UX research rather than guesswork: the F-pattern and Z-pattern eye-tracking studies (Nielsen Norman Group), the persistent-sidebar-nav convention used across admin dashboards, the split gallery-plus-buy-box pattern common on product pages (a Baymard Institute finding), and the single-column layout that usability research consistently finds converts best for short forms. ### Can I export this wireframe as a real Gutenberg pattern? Not directly. This is a planning step, not a code generator: it helps you agree on a structure with a client or a teammate before you open the Site Editor and build the matching Group, Cover, and Query Loop blocks by hand. ### Why does the dashboard page type always keep a left sidebar, no matter what layout I pick? Because a persistent navigation column is a structural convention of admin dashboards, not a stylistic choice. The layout selector still changes how the widgets inside it are arranged (a grid of cards or a stacked list), but removing the nav column would misrepresent how real dashboards are built. ### What layout style should I use for a landing page? Grid of cards is the default for landing pages and portfolios, since feature and project sections are usually scannable side by side. Stacked bands suit a product page or a form, where you want visitors reading one thing at a time. ### Does the wireframe work on a small phone screen? Yes. Every layout collapses to a single column under roughly 480px wide, including the grid and the sidebar-plus-main arrangement, so you can check a mobile draft on the same screen as the desktop one. ### Will more page types get added later? Landing page, blog post, dashboard, product page, portfolio, and contact form cover the page types freelance WordPress builders draft most often. If a clear gap shows up in practice, it gets added to the preset list. --- ### AI Website Builder Fit Finder: Which Type Fits You URL: https://noonwp.com/tools/ai-website-builder-fit-finder > There are three different tools hiding behind "AI website builder." Answer six questions and find out which one actually fits what you are building. ## Find the Right AI Website Builder for Your Project There is no single "ai website builder." At least three different kinds of tool wear that name. Answer six questions and see which one actually fits what you are building, in under two minutes. ## AI Website Builder Fit Finder Six quick questions about what you are building, who is building it, and what you need long-term. Your answers stay in the browser; nothing is stored. *[Interactive widget — see the live page for the full experience]* ## How to use the quiz 1. **Answer six questions** — Cover what you are building, who is building it, your timeline, budget, and whether you need right-to-left or bilingual support. 2. **Watch the live score** — Each answer adds one point to one of three build paths. The counter above the form tracks how many questions you have left. 3. **Read the full breakdown** — The winning path appears with its 0-6 score against the other two, so you can see how close the call actually was. ## What the quiz actually scores ### Six real trade-offs Each question is a genuine fork in how these tools work: who owns the code, how much time you have, whether you need right-to-left or bilingual support. Not filler questions. ### Weighted, not guessed Every answer adds one point to one of three build paths. The path with the most points after six questions wins, and the full score breakdown stays visible underneath. ### No single "best" tool AI block-theme generators, no-code builders, and AI-assisted custom development solve different problems for different people. The quiz names all three honestly, including when the answer is not WordPress. *Before you pick a path* ## Three names for three different tools "AI website builder" gets used for products that barely compete with each other. An AI block-theme generator writes WordPress-native Gutenberg patterns you self-host, edit in the Site Editor, and export whenever you want; Pattern Forge works this way. A no-code AI builder like Wix ADI, Framer AI, or Durable describes your site with a prompt and lays it out inside its own hosted platform: faster to launch, harder to move later, and RTL support is often an afterthought. AI-assisted custom development pairs a tool like Cursor or GitHub Copilot with a developer, on WordPress or any stack, once the project needs logic no template engine ships: custom booking flows, dashboards, non-standard integrations. Knowing which category a tool belongs to before you commit saves the rebuild six months in. - AI block-theme generators: self-hosted WordPress, full code ownership, native RTL - No-code AI builders: fastest to launch, hosted platform, limited portability - AI-assisted custom development: highest control and cost, needed for complex logic ## Common questions ### Is this quiz actually free? Yes. Answer the six questions and get your recommendation instantly, no email required. The quiz runs in your browser: nothing you type is sent to a server, aside from an anonymous signal noting the widget was used. ### What is the real difference between an AI block-theme generator and a no-code AI builder? A block-theme generator like Pattern Forge writes WordPress-native Gutenberg patterns you can self-host, export, and keep editing in the Site Editor. A no-code builder like Wix ADI or Durable lays out a site inside its own hosted platform: faster to start, harder to move later. ### I already have a WordPress site. Does this quiz still apply to me? Yes. Result A assumes you are on, or moving to, WordPress. If the quiz points you to B or C instead, it is telling you that WordPress may not be the fastest route for this particular project, even if you run WordPress elsewhere. ### Why does the quiz ask about right-to-left and bilingual support? Native right-to-left support for Arabic or Hebrew still separates these tools sharply. Most no-code AI builders bolt RTL on as an afterthought, while a WordPress block theme handles direction, fonts, and mirrored layouts at the pattern level. ### Can two people get different results from the same six answers? No. The scoring is deterministic: each answer adds exactly one point to one of the three build paths, and the path with the most points is shown, with the full breakdown underneath so you can check the math yourself. ### What happens if my score ties between two paths? Ties resolve toward whichever path is checked first in the fixed A, B, C order shown in the breakdown. A close tie usually means either path genuinely works, and the deciding factor becomes your timeline or your budget. ### Does noonwp build AI website builders itself? noonwp is a scriptorium for WordPress practitioners, and Pattern Forge, its own AI block-theme tool, is one real option under result A. The quiz still names the other two paths honestly, even when they point away from WordPress entirely. ### Where do the three build paths in this quiz come from? They map to how the AI website-building market actually splits right now: WordPress-native AI pattern generators, hosted no-code AI design tools, and AI-assisted custom development. It is a category split, not a ranking of one tool over another. ## See what an AI block-theme build looks like If your result pointed to the WordPress path, Pattern Forge is where noonwp starts: AI-generated Gutenberg patterns you can still open, edit, and export in the Site Editor. *Call to action: Open the scriptorium* ## FAQ ### Is this quiz actually free? Yes. Answer the six questions and get your recommendation instantly, no email required. The quiz runs in your browser: nothing you type is sent to a server, aside from an anonymous signal noting the widget was used. ### What is the real difference between an AI block-theme generator and a no-code AI builder? A block-theme generator like Pattern Forge writes WordPress-native Gutenberg patterns you can self-host, export, and keep editing in the Site Editor. A no-code builder like Wix ADI or Durable lays out a site inside its own hosted platform: faster to start, harder to move later. ### I already have a WordPress site. Does this quiz still apply to me? Yes. Result A assumes you are on, or moving to, WordPress. If the quiz points you to B or C instead, it is telling you that WordPress may not be the fastest route for this particular project, even if you run WordPress elsewhere. ### Why does the quiz ask about right-to-left and bilingual support? Native right-to-left support for Arabic or Hebrew still separates these tools sharply. Most no-code AI builders bolt RTL on as an afterthought, while a WordPress block theme handles direction, fonts, and mirrored layouts at the pattern level. ### Can two people get different results from the same six answers? No. The scoring is deterministic: each answer adds exactly one point to one of the three build paths, and the path with the most points is shown, with the full breakdown underneath so you can check the math yourself. ### What happens if my score ties between two paths? Ties resolve toward whichever path is checked first in the fixed A, B, C order shown in the breakdown. A close tie usually means either path genuinely works, and the deciding factor becomes your timeline or your budget. ### Does noonwp build AI website builders itself? noonwp is a scriptorium for WordPress practitioners, and Pattern Forge, its own AI block-theme tool, is one real option under result A. The quiz still names the other two paths honestly, even when they point away from WordPress entirely. ### Where do the three build paths in this quiz come from? They map to how the AI website-building market actually splits right now: WordPress-native AI pattern generators, hosted no-code AI design tools, and AI-assisted custom development. It is a category split, not a ranking of one tool over another. --- ### AI Unit Test Generator: Jest, Pytest, PHPUnit Skeletons URL: https://noonwp.com/tools/ai-unit-test-generator > Type a function name and its parameters, pick a framework and edge cases, and this AI unit test generator drafts a ready-to-fill test skeleton in your browser. ## Generate a unit test skeleton for any function This AI unit test generator drafts Jest, Vitest, pytest, or PHPUnit test skeletons from a function name and its parameters, plus the edge cases you want covered, so you start from a scaffold instead of a blank test file. ## Build your test skeleton Type a function name and its parameters, pick a test framework, and check the edge cases you want covered. The skeleton below updates as you type. *[Interactive widget — see the live page for the full experience]* ## What the generator actually does ### You describe the function Type the function name and its parameters, comma separated. No source code required: the widget only needs the shape of what you are testing, which is usually faster to type than to explain. ### You pick the edge cases Check the edge cases that matter for this function: zero, a negative number, an empty or null value, an oversized input, or an input that should throw. Skip the ones that do not apply to your logic. ### You get a ready-to-fill skeleton The generator writes the describe and test blocks (or def functions and a TestCase class for pytest and PHPUnit), one assertion per case, with a clear TODO placeholder where your expected value goes. ## From a function signature to a filled-in test file The generator hands you the skeleton: names, structure, and one assertion per edge case. Deciding what a function should actually return still belongs to you and your test runner. Copy the code, replace the /* expected value */ placeholders, and run it the same way you always do. - Copy the code with one click - Works for JavaScript, Python, and PHP - No dependency to install, no build step ## Common questions about this AI unit test generator ### Does this actually call an AI model to write the tests? No. Everything runs in your browser as a rule-based generator: it builds the test structure, naming, and edge-case list from what you type, using the same patterns an experienced test author would reach for. It never sends your function name or parameters to a server, so there is nothing to wait for and nothing to leak. ### Which languages and frameworks does it support? Jest and Vitest for JavaScript, pytest for Python, and PHPUnit for PHP, the framework most WordPress plugin and theme developers already use for their test suite. Each framework gets its own file structure: describe and test blocks for Jest and Vitest, def functions for pytest, and a TestCase class for PHPUnit. ### Will the generated test pass immediately? Not on its own, and it should not. Every assertion ships with a /* expected value */ placeholder because the widget cannot know what your function should return. Replace the placeholder with the value your implementation is supposed to produce, and the test is ready to run against it. ### Is this free to use? Yes. There is no signup, no account, and no limit on how many test skeletons you generate. Bookmark the page and come back whenever you start a new function. ### Do I need to paste my real source code? No. You only need the function name and its parameter names. The generator infers plausible sample arguments from the parameter count and writes one test per edge case you select, without ever seeing your implementation. ### Can I use this for a WordPress plugin function? Yes, pick PHP - PHPUnit. It writes a test class named after your function, matching the way WordPress plugin and theme authors already structure their PHPUnit suites for hooks, filters, and helper functions. ### Where do the edge cases in the checklist come from? They cover the failure modes that come up most often when a function is put in front of real input: zero, a negative number, an empty value, a null or missing argument, an unexpectedly large number, and input that should raise an error. Check the ones that apply to your function; skip the ones that do not. ## Building block themes with more moving parts than tests? Explore noonwp for AI-assisted Gutenberg workflows, from Pattern Forge to RTL Concordance, built for practitioners who ship production block themes. *Call to action: Open the scriptorium* ## FAQ ### Does this actually call an AI model to write the tests? No. Everything runs in your browser as a rule-based generator: it builds the test structure, naming, and edge-case list from what you type, using the same patterns an experienced test author would reach for. It never sends your function name or parameters to a server, so there is nothing to wait for and nothing to leak. ### Which languages and frameworks does it support? Jest and Vitest for JavaScript, pytest for Python, and PHPUnit for PHP, the framework most WordPress plugin and theme developers already use for their test suite. Each framework gets its own file structure: describe and test blocks for Jest and Vitest, def functions for pytest, and a TestCase class for PHPUnit. ### Will the generated test pass immediately? Not on its own, and it should not. Every assertion ships with a /* expected value */ placeholder because the widget cannot know what your function should return. Replace the placeholder with the value your implementation is supposed to produce, and the test is ready to run against it. ### Is this free to use? Yes. There is no signup, no account, and no limit on how many test skeletons you generate. Bookmark the page and come back whenever you start a new function. ### Do I need to paste my real source code? No. You only need the function name and its parameter names. The generator infers plausible sample arguments from the parameter count and writes one test per edge case you select, without ever seeing your implementation. ### Can I use this for a WordPress plugin function? Yes, pick PHP - PHPUnit. It writes a test class named after your function, matching the way WordPress plugin and theme authors already structure their PHPUnit suites for hooks, filters, and helper functions. ### Where do the edge cases in the checklist come from? They cover the failure modes that come up most often when a function is put in front of real input: zero, a negative number, an empty value, a null or missing argument, an unexpectedly large number, and input that should raise an error. Check the ones that apply to your function; skip the ones that do not. --- ### AI Code Checker: Audit AI-Generated Code Before You Ship URL: https://noonwp.com/tools/ai-code-checker > A free, rules-based AI code checker for JS, PHP, Python, and CSS. Paste a snippet, pick a language, and get a scored checklist before you ship it to a client site. ## AI Code Checker: Catch Issues Before They Ship Paste code from Pattern Forge, Elementor AI, Divi AI, or your own scripts. This AI code checker runs a rules-based pre-check in your browser, with no server round trip and no account. ## AI Code Checker Paste a JavaScript, PHP, Python, or CSS snippet, pick the language, and get a rules-based pre-check score with specific callouts. Nothing leaves your browser. *[Interactive widget — see the live page for the full experience]* ## What the AI code checker actually looks for ### Nine deterministic checks Long lines, deep nesting, long functions, magic numbers, debug leftovers, TODO markers, and repeated lines run against your snippet with plain regex and counting, the same kind of heuristic a linter uses under the hood. ### Two checks per language JavaScript gets an async-without-try/catch check and a var-vs-let check. PHP gets an unescaped-output check and a missing-text-domain check. Python gets bare-except and mutable-default checks. CSS gets an important-overuse check and a hardcoded-color check. ### A score, not a verdict Each flag deducts points on a fixed, capped scale, so no single issue can tank the score alone. You get a 0-100 number plus the exact counts and lines behind it, not a black-box opinion. *What a flagged snippet looks like* ## Every flag points at a specific pattern, not a vague score Load the JavaScript example above and the checker returns 37 out of 100: a nesting depth of seven, two console.log() calls left in, one fetch() call with no try/catch nearby, and five var declarations where let or const would scope better. Load the PHP example and it comes back at 71, flagging two echo statements that print a variable without esc_html() or esc_attr(), plus a translation string missing its text domain. Those are the kind of details a quick glance at a diff misses, and a client site inherits. - JavaScript example: score 37, flags a nesting depth of 7 and two debug console.log() calls - PHP example: score 71, flags two unescaped echo() statements and a missing text domain - Python example: score 82, flags a bare except clause and a mutable default argument - CSS example: score 72, flags four !important declarations and three hardcoded hex colors ## Where this fits between generation and shipping 1. **Generate the pattern or snippet** — Prompt Pattern Forge, Elementor AI, Divi AI, or your own script to produce a block, a shortcode handler, or a style block. 2. **Paste it and pick a language** — Drop the output into the checker above and select JavaScript, PHP, Python, or CSS. Nothing uploads, the checks run in this tab. 3. **Read the checklist, not just the score** — A 90 with an unescaped echo() flagged is not production-ready. A 70 with only long-line warnings might be fine for a one-off client site. The breakdown is the point, not the number. 4. **Fix, then verify with the real tools** — Run ESLint, PHPCS with the WordPress ruleset, or pylint before the code ships. This checker is a first pass, not a replacement for either. ## Common questions about the AI code checker ### Is this AI code checker actually AI? No, and we would rather be direct about it: this is a rules-based static checker. It runs plain pattern matching, regex, and counting logic against your snippet, the same category of technique linters and style checkers have used for years. There is no model reading your code and no server call doing the reasoning. Call it a pre-check, not an AI code review. ### Does my code leave the browser? No. Everything runs client-side, in the tab you are reading right now. The only network call this page makes is an anonymous, IP-free usage beacon that records that the tool was used, not what you pasted. Your snippet is never sent anywhere. ### Which languages does it check? JavaScript, PHP with a WordPress lean, Python, and CSS or SCSS. Each language gets two extra checks of its own: PHP looks at escaping and text domains, JavaScript looks at async error handling and var usage, Python looks at bare except clauses and mutable defaults, CSS looks at !important overuse and hardcoded colors. ### Does a high score mean the code is safe to ship? No. Treat a high score as nothing obvious jumped out, not as a green light. A rules-based checker cannot catch a wrong business rule, a broken query, or a security hole that does not match one of its patterns. Run ESLint, PHPCS with the WordPress ruleset, or pylint, and read the diff yourself before it reaches a client site. ### Why build this instead of trusting Pattern Forge, Elementor AI, or Divi AI directly? Because AI pattern generators are good at producing code that runs, not necessarily code that is safe to ship. Elementor AI, Divi AI, and Bricks AI can each return a working pattern in seconds; whether that pattern escapes its output correctly, or leans on a dozen undocumented custom classes, is a separate question this checker gives you a fast, honest first read on. ### What if I paste an incomplete fragment? The checks still run, but nesting depth and function length can look worse than they are without full context, and the PHP escaping check can only see the echo statements you pasted. Paste enough of the function or file to give the heuristics a fair signal, the score is only as good as the input. ### Can I reuse this on every project? Yes. Nothing is saved between visits, there is no account, and no rate limit beyond your own patience pasting code. Bookmark this page and run it every time an AI pattern generator hands you something new to review. ## Ship AI-generated patterns with more confidence noonwp's Pattern Forge and Page Scribe are built for a workflow like this one: generate, pre-check, then read the diff yourself before it reaches a client site. *Call to action: Open the scriptorium* ## FAQ ### Is this AI code checker actually AI? No, and we would rather be direct about it: this is a rules-based static checker. It runs plain pattern matching, regex, and counting logic against your snippet, the same category of technique linters and style checkers have used for years. There is no model reading your code and no server call doing the reasoning. Call it a pre-check, not an AI code review. ### Does my code leave the browser? No. Everything runs client-side, in the tab you are reading right now. The only network call this page makes is an anonymous, IP-free usage beacon that records that the tool was used, not what you pasted. Your snippet is never sent anywhere. ### Which languages does it check? JavaScript, PHP with a WordPress lean, Python, and CSS or SCSS. Each language gets two extra checks of its own: PHP looks at escaping and text domains, JavaScript looks at async error handling and var usage, Python looks at bare except clauses and mutable defaults, CSS looks at !important overuse and hardcoded colors. ### Does a high score mean the code is safe to ship? No. Treat a high score as nothing obvious jumped out, not as a green light. A rules-based checker cannot catch a wrong business rule, a broken query, or a security hole that does not match one of its patterns. Run ESLint, PHPCS with the WordPress ruleset, or pylint, and read the diff yourself before it reaches a client site. ### Why build this instead of trusting Pattern Forge, Elementor AI, or Divi AI directly? Because AI pattern generators are good at producing code that runs, not necessarily code that is safe to ship. Elementor AI, Divi AI, and Bricks AI can each return a working pattern in seconds; whether that pattern escapes its output correctly, or leans on a dozen undocumented custom classes, is a separate question this checker gives you a fast, honest first read on. ### What if I paste an incomplete fragment? The checks still run, but nesting depth and function length can look worse than they are without full context, and the PHP escaping check can only see the echo statements you pasted. Paste enough of the function or file to give the heuristics a fair signal, the score is only as good as the input. ### Can I reuse this on every project? Yes. Nothing is saved between visits, there is no account, and no rate limit beyond your own patience pasting code. Bookmark this page and run it every time an AI pattern generator hands you something new to review. ---