Who writes this blog

I run a WordPress agency and have been building and managing WordPress sites professionally for over seven years. The agency handles e-commerce, lead generation, and media projects — across hosting providers including Kinsta, Cloudways, and self-managed VPS setups.

This blog exists because most WordPress advice online is either outdated, written by people who have never run a live site in production, or exists primarily to push affiliate commissions without honest evaluation.

Everything published here comes from direct experience:

• Hosting benchmarks are measured from real production sites with real traffic, not from synthetic tests on clean installs.
• Plugin comparisons are based on running the plugins across multiple production environments and observing what breaks and what works.
• Performance guides reflect the actual process of moving a site from PageSpeed 40 to PageSpeed 95 — including the steps that did not work.
• Security recommendations reflect what has happened on real sites, not theoretical threat models.

Affiliate disclosure

Some links on this site are affiliate links. When you sign up for a hosting service or purchase a plugin through one of these links, this site earns a commission at no extra cost to you.

Affiliate relationships do not influence recommendations. Services are recommended because they are genuinely good for the use case described — and rejected or criticised honestly when they are not. The Tools page lists every affiliate relationship with full disclosure.

What this blog covers

• Hosting — real benchmark data on managed WordPress hosts, VPS setups, and WooCommerce-specific performance
• Speed & Performance — Core Web Vitals, caching, CDN, image optimisation, and PageSpeed troubleshooting
• SEO — technical SEO for WordPress, schema markup, sitemap configuration, and duplicate content fixes
• WooCommerce — checkout optimisation, payment gateways, SEO, and performance for e-commerce
• Security — hardening checklists, plugin comparisons, and incident response
• Agency — tools, workflows, and processes for running a WordPress maintenance business

Corrections & editorial policy

WP Depth is written and published by one person — Dobromir Dechev — not an editorial staff. There's no separate fact-checking desk, so transparency about sourcing and mistakes matters more here, not less.

• Every article shows its publish date, and its last-updated date if it's been revised since. Substantive changes to a published article are noted in the article itself, not made silently.
• Time-sensitive posts — CVE disclosures, WordPress core/plugin releases, algorithm updates — cite the vendor advisories, CVE records, or official release notes they're based on, so you can check the primary source directly rather than take the summary on faith.
• If you spot an error — a wrong version number, an outdated claim, a broken fix — email it in. Confirmed errors get corrected promptly, with a note if the correction is material (e.g. a wrong patched-version number in a security post).

Contact

For questions, corrections, or content suggestions — use the contact page. Most practical WordPress questions are answered in one of the 50+ articles here; use the search to find existing coverage first.