WordPress Developer in Chennai for WooCommerce, Kadence & Custom Plugins

1. Two plugins fighting over the same hook

When two plugins both hook into the same WooCommerce action — commonly around the cart or checkout template — the conflict often fails silently. The admin dashboard loads fine, but checkout breaks for customers. I trace this by enabling WP_DEBUG_LOG and going through the active plugin list directly, rather than deactivating everything and hoping the problem goes away.

2. A theme or page builder update changes the markup underneath you

Page builder and theme updates sometimes rename CSS classes or restructure block markup without warning, which silently breaks custom CSS you or a previous developer added. I fix this by rebuilding the customisation properly inside the theme's own settings — for Kadence that means using theme.json and Kadence's own hooks — so it survives the next update.

3. The catalog outgrows a shared hosting database

Once a WooCommerce catalog passes a few thousand products or the wp_options table bloats with abandoned transients, unindexed queries start showing up as real page-load delays — sometimes 6-12 seconds on mobile. I fix this by optimising slow queries, cleaning up autoloaded options, and setting up proper object caching so the same lookups aren't repeated on every page view.

4. Payment goes through but the order doesn't show up

If a customer pays but the order never appears in WooCommerce, the webhook call from the payment gateway is usually failing quietly — often an SSL certificate issue, a wrong callback URL, or a security plugin blocking the request. I fix this by checking server headers directly and tracing exactly where the call is failing, for gateways like Razorpay and Cashfree.

Note: These are typical ranges, not quotes. You'll get an exact estimate after a free review of your site's plugins, hosting limits, and customization history.

Core Web Vitals. This means removing render-blocking plugins, deferring tracking tags that aren't needed immediately, and setting explicit image dimensions — the specific things Google's LCP and INP metrics actually measure.

Server-side & object caching. Caching expensive database query results so WordPress isn't re-running the same lookups every time someone loads a popular category or product page.

Image compression. Converting product and media images to .webp or .avif, setting up lazy loading, and serving properly sized images instead of full-resolution files scaled down in the browser.

Plugin audits. Removing or replacing plugins that load scripts and styles site-wide when they're only needed on one page — usually the single biggest win on a slow WooCommerce store.

Kadence Theme & Kadence Blocks. Kadence is block-editor native, so styling lives in theme.json rather than a proprietary settings panel — that means fewer conflicts and a faster page than most page-builder-based themes. I build custom Kadence Blocks patterns, configure global styles through theme.json, and add child-theme hooks for anything the built-in customiser doesn't expose, so changes survive Kadence's own updates.

Custom block themes & Full Site Editing. For businesses that need full design control or the fastest possible load time, I build bespoke block themes from a blank theme.json, or classic PHP-templated themes when that fits the project's complexity better than the block editor does.

Legacy page builders (Elementor, Divi, WPBakery). If you've inherited a site built on one of these, I can maintain, extend, or migrate it. Each stores its layout data differently under the hood, and I work directly with that structure rather than guessing at settings.

Schema markup that matches the page. I implement Product, Review, FAQ, Article, LocalBusiness, and Breadcrumb structured data depending on what's actually on the page — mismatched or generic schema can get rich results suppressed rather than earn them.

FAQ content built for AI Overviews and voice search. Search results increasingly pull direct answers from clearly structured Q&A content. I write FAQ sections as genuine, specific answers — paired with FAQPage schema — rather than keyword-stuffed filler.

Core Web Vitals as a ranking input. Google continues to factor page experience signals into ranking. A WooCommerce store that's slow on mobile is fighting an uphill battle regardless of content quality, which is why speed work and SEO work aren't really separate projects.

Clean, semantic markup over div-soup page builders. Block-editor themes like Kadence output leaner, more semantic HTML than heavy visual builders, which makes it easier for crawlers — and AI answer engines — to actually understand your page structure.

E-E-A-T signals in code, not just copy. Author schema, HTTPS, clear business/contact information, and a fast, secure site all feed into how much trust Google places in a page — these live at the development layer, not just the content layer.

Being based in Chennai, Tamil Nadu means we work in the same hours. When checkout breaks during your morning sales rush, you get a reply in minutes — not a response from an outsourced queue the next day.

I work with sites across Anna Nagar, Velachery, Adyar, Guindy, Ambattur, Porur, and OMR, and I'm familiar with the Indian payment gateways and delivery services most Chennai stores actually integrate with.

I'm also available across Tambaram, Avadi, Chromepet, Perambur, KK Nagar, Ashok Nagar, Sholinganallur, and Medavakkam — and remotely for businesses in the Middle East, Europe, and the US, entirely over WhatsApp and email.