Я исправлю ошибки WordPress после обновления или конфликта плагинов, отредактирую вашу тему и ускорю работу вашего сайта

Most WordPress trouble starts with a change: a core, theme or plugin update, a new plugin, a move to another host. This service is for business sites and blogs that worked until something like that happened. I have worked with WordPress a lot, including writing theme and plugin code in PHP.

Starter fixes one problem: a white screen or critical error, a page that broke, a form that stopped sending, a plugin conflict. Standard takes up to three problems and adds a written summary. Advanced handles up to six fixes or theme changes, with the theme changes made in a child theme, and includes a speed pass measured before and after.

How I work on a live site: I take a backup or work on a staging copy first. Changes to a theme go into a child theme, and changes to behavior go into a small custom plugin, never into WordPress core or a third-party plugin's files, so the next update does not wipe them. Conflicts are isolated one plugin at a time, and errors are read from the debug log rather than guessed. For 14 days after delivery, I fix anything that does not work as we agreed, free of charge.

On speed, I measure first and fix what the measurement points to: heavy images, plugins loading on every page, missing caching, slow database queries. You get the numbers before and after. I don't promise a specific PageSpeed score, because one third-party script can cap it whatever else is done.

Not included: Shopify, Wix and other site builders, or a full redesign.

We talk in the order chat, not on calls, and you get everything in writing: what I found, what I changed, and how to check it.

Steps for completing your project
1. Access and backup - You create an administrator account for me and share hosting or SFTP access. Before changing anything, I make a backup or a staging copy.
2. Pin down the cause - I reproduce the problem and trace it through the debug log, the plugin list and the theme, then tell you in writing what is wrong.
3. Fix it the safe way - Any code the fix needs goes into a child theme or a small plugin of its own, so updates keep it. Where possible, I test it on the staging copy first.
4. Check the whole site - After the fix, I click through the main pages, the forms and the checkout if you have one, not just the page that was broken.
5. Written handover - What was wrong, what changed and where the change lives. On Advanced, the speed numbers before and after.