A new client called last week asking why their site felt slower than the day it launched. They had bought a popular ThemeForest theme — the kind with a six-figure sales count, hundreds of demos, and a banner promising ‘unlimited’ design possibilities. The site was eighteen months old. Adding a contact field to one page required editing four shortcodes across three plugin panels.
This is the conversation we have at least once a quarter. It is why we stopped quoting ThemeForest themes for paid client work in 2016. The reasons keep stacking up.
The kitchen-sink problem
A theme that needs to sell to fifty thousand buyers has to look like it can do everything. Real estate, restaurant, agency, e-commerce, photography portfolio — every demo has to be in the box. So the theme ships with twelve sliders, eight gallery types, six contact form integrations, and a page builder that overrides Gutenberg entirely.
Your client website needs maybe ten percent of that. The other ninety percent loads on every page request anyway. We have audited theme bundles that ship over two megabytes of CSS before a single line of content renders. That is not a budget you can claw back later.
You don’t own what you build
The bigger issue is structural. ThemeForest themes wire their content into custom shortcodes, options frameworks, and proprietary post types. Move the site to a different theme three years later — which most clients want to do eventually — and the content does not move with it. The visual editor stops working, the shortcodes leak raw markup into post bodies, and the meta fields disappear.
We had a client in 2016 who wanted to rebuild on a clean theme after their ThemeForest pick was abandoned by its author. Migrating six years of blog posts cost more than the original build. The shortcode-to-block conversion alone was forty hours.
Updates are a gamble, not a guarantee
Marketplace themes get bought, sold, abandoned, or simply forgotten. We checked the top fifty themes from 2014 — twenty of them have not had a meaningful update since 2016. Some of them still get sold today. When WordPress 4.8 dropped TinyMCE 4 compatibility shifts, those themes shipped broken admin screens to every existing customer overnight.
A paid client expects the site to work in three years. ThemeForest does not give you that guarantee. The author can disappear. The included plugins can stop receiving security patches. The license is per-site, so adding a staging URL costs another forty dollars.
The ‘included plugins’ trap
Most premium themes bundle Visual Composer, Revolution Slider, or LayerSlider as part of the package. The author gets a wholesale license — they pay once and ship the plugin to fifty thousand sites. But the plugin updates only flow through the theme. If the theme author waits two weeks to push an update, every site running that bundled plugin sits on a vulnerable version for two weeks.
This is not theoretical. The 2014 Revolution Slider vulnerability hit so many sites this way that it became one of the most-exploited WordPress holes of the decade. The fix was published quickly. The themes that bundled it took months to push it through.
What we use instead
For most projects we start from Underscores or a minimal starter theme and write the parts the client actually needs. Custom post types use ACF Pro or native register_post_type. Layouts use Gutenberg block patterns or a thin block theme. Everything stays in the database in a portable format — post content, post meta, taxonomies. Nothing locked behind a shortcode parser only one plugin understands.
The first build takes longer. Forty to eighty hours instead of the ten the client expected when they showed us the ThemeForest demo. But three years later, the site still updates cleanly, the content still moves between themes, and we are not having the ‘why is it slow’ conversation.
When ThemeForest is fine
If the project is unpaid, time-boxed, or genuinely throwaway — a one-event landing page, a side project, a quick proof-of-concept — a ThemeForest theme is faster than building anything custom. The same logic applies to internal tools nobody outside the company will ever see.
Anything else, anything someone is paying real money to maintain for years, deserves a foundation that does not depend on a marketplace author still being around when the next major WordPress release ships.
The honest math
A typical ThemeForest theme costs sixty dollars. The annual plugin renewals cost another two-fifty if you keep them current. The first ‘just add this small feature’ request hits a shortcode wall and costs an extra ten hours of developer time. Repeat that four times a year, and the cheap theme has cost more than a custom build by month fourteen.
Clients who hear this argument up front almost always pick the custom route. The ones who do not usually call us in year two asking why their site feels slower than the day it launched.