Numbers that speak for themselves!
Let’s start with what matters: hard metrics.
After enabling automatic WebP conversion and implementing targeted backend optimizations, the coreX homepage was tested again. The result:
| Metric | Before | After |
|---|---|---|
| Transferred Data | 6.74 MB | 1.48 MB |
| Load Time | 670 ms | 322 ms |
| DOMContentLoaded | 465 ms | 227 ms |
| TTFB (Server Response) | — | ~80ms |
78% less data. 52% faster. And this was not a caching trick.
TTFB — the time until the server delivers the first byte — was around ~80 milliseconds at the time of testing. For comparison: a typical WordPress installation without a caching plugin takes 200–800 ms. With a plugin, maybe 80–150 ms. coreX needs ~80 ms. Without plugins. Without cache. Just like that.
This is not coincidence — this is architecture.
What’s really behind these numbers
No plugin layer, no overhead
Other content management systems execute dozens of plugin hooks on every page request, load additional files, and initialize classes that may never even be needed. coreX loads exactly what the requested page requires — and nothing more. Database queries are precise, and PHP output is direct.
WebP — automatic, not optional
If you want to deliver WebP images in WordPress, you usually need a plugin (Imagify, ShortPixel, EWWW Image Optimizer). These plugins may even cost money, require API keys, and sometimes process images on external servers.
coreX handles this directly during upload — locally on the server, without third parties, without subscriptions:
- Upload a JPEG or PNG → automatically converted to WebP
- Wider than 1920 pixels? → automatically scaled proportionally to Full HD
- The original file is replaced, the filename stays the same, and the media library stays synchronized
- An 8 MB high-resolution image becomes ~300–500 KB WebP
Nobody has to know it’s happening. It simply works.
Structured data — built in by default
If you want Rich Snippets in Google search results with WordPress — article dates, authors, breadcrumbs — you install Yoast SEO or RankMath. Both are bloated plugins that add their own database entries, tables, and admin menus.
coreX automatically outputs complete BlogPosting JSON-LD data for every blog post — including author, date, image, category, and publisher. Additionally, all CMS pages receive WebPage schema data. Open Graph for Facebook/LinkedIn, Twitter Cards — everything included, everything automatic, everything built directly into the core.
No plugin. No subscription. No “Pro version required”.
Hero images with loading priority
Google directly evaluates LCP (Largest Contentful Paint) as a ranking factor. The LCP is usually the largest visible element — in coreX, typically the hero image in the page header.
coreX automatically applies fetchpriority="high" and a <link rel="preload"> inside the <head> for this image — meaning it loads before the browser even finishes building the layout. This is exactly what Google recommends in PageSpeed Insights. In coreX, it happens automatically without configuration.
The permissions system: clean, granular, expandable
While other content management systems only differentiate between Administrator, Editor, Author, Contributor, and Subscriber — and require plugins for granular permissions — coreX includes its own role and permission system directly in the database:
- Every admin function can be secured individually
- New permissions can be added via migrations and automatically assigned to the admin role
- Covered areas include content, news, media, settings, user management, and system toggles
No plugin managing permissions. No chaos if the plugin gets disabled.
Updates that don’t break everything
Every WordPress user knows the feeling: click plugin update, open the site — layout broken. Or worse: white screen.
Structurally, this does not happen with coreX because there are no third-party plugins. Updates only affect internal code. The architecture controls what changes — and the update system deploys changes in a controlled way, including migration support for database changes.
What coreX already does better today
| Feature | WordPress | coreX |
|---|---|---|
| TTFB without cache | 200–800 ms | ~80 ms |
| WebP conversion | Plugin (paid) | automatic, free |
| JSON-LD / Rich Snippets | Yoast / RankMath | built into the core |
| Granular permissions | Plugin required | native role system |
| Update risk | high (plugins) | low (no third-party code) |
| Clean database structure | wp_posts / wp_postmeta | purpose-built tables |
| Plugin dependencies | 10+ for basics | 0 |
What’s coming next
The roadmap is packed. Planned features include:
- Sitemap Generator — automatically generated from all active pages and news posts
- Organization Schema — structured company data on the homepage
- Login Protection — rate limiting and IP blocking after failed login attempts
- Page Versioning — “restore previous version” functionality
- 2FA — TOTP-based two-factor authentication for the admin area
The foundation is already there. Everything built on top of it will be just as well thought out as what already exists.
coreX is not a WordPress clone. It’s what a CMS in 2026 should be.
Lean. Fast. Secure. Under your control.