WordPress specialist for outages, malware and performance

7 min read
Guide

I’m Mariusz Szatkowski, and I have built and repaired WordPress sites since 2006. As a specialist I take the incidents a general developer could not close: an outage after an update, malware, poor Core Web Vitals, a WooCommerce store that fails under load. Broken stores go to the WooCommerce rescue sprint. New builds are on the WordPress developer page.

I work alone: no team, no agency staff, no subcontractors. The code you receive is code I wrote, and your credentials stay with me.

#Who does the work

Mariusz Szatkowski, a senior WordPress developer. I have published more than 25 free plugins on WordPress.org and I organise WordCamp Gdynia.

#What the work covers

Diagnosis after outages, malware cleanup and hardening, WooCommerce checkout and ERP integration, custom plugins and REST endpoints, Gutenberg blocks, and Core Web Vitals measured on real visitors.

#Where I work from

Remotely from Gdynia, Poland, on Central European Time, for clients in the UK, Ireland and elsewhere. I communicate by email, written documents and the repository. If you need a call, ask.

#How pricing works

Every job is quoted individually after I have seen the brief: a fixed price for a defined scope, time and materials for open-ended diagnosis, a monthly fee for maintenance. Rates are on the pricing page, not here.

#When do you need a WordPress specialist?

When your agency or in-house team is stuck. The usual cases:

  • Outage or hack: a critical error after an update, redirects to strange domains, spam pages in Google.
  • Custom development: a plugin, REST endpoint or block when no existing plugin fits the process.
  • Performance: slow admin, slow checkout, Core Web Vitals failing in field data.
  • WooCommerce: checkout, payment webhooks and ERP synchronisation on larger stores.

#WordPress specialist vs generalist developer

The difference shows up in problems that have no Stack Overflow answer. Three failure patterns I see on sites past their first year:

  • Slow admin behind a fast front end: page caching hides the problem from visitors while editors wait seconds per screen. A frequent cause is the autoload data in wp_options, swollen by rows that deactivated plugins left behind, or by an active plugin that rewrites a serialised array on every admin request. A generalist adds PHP memory. The fix is trimming the autoloaded options.
  • Editors who may publish in some categories only: when one category sits behind a paywall taxonomy, role settings are not enough. A clean solution needs map_meta_cap on edit_post plus a capability set tied to the taxonomy term. ACF Pro stops at field-level permissions.
  • One identity, different roles per site on multisite: shared user tables mean a user keeps one account but needs a different role on each site, and super admin rights do not propagate to new sites by themselves. A small mu-plugin that applies role assignments on new site creation handles it. No plugin does.

#Which WordPress APIs a specialist should know

WP_Query and the posts_clauses filter for queries that need joins, register_rest_route with a real schema and permission_callback, InnerBlocks and block patterns for editorial teams, pre_get_posts for changing the main query without breaking pagination, and the capability and meta-capability system. Plugin internals matter too: how WooCommerce stores orders after the HPOS migration, how Yoast regenerates sitemaps, how Polylang and WPML rewrite query parameters.

#How a specialist engagement starts

Rarely with “build something new”. First I find out what is already broken, then I decide together what stays.

#Custom Gutenberg block development

Editorial teams want a block they can configure, with consistent styling, a locked structure and an editor preview that matches the front end. Technically that is InnerBlocks with allowedBlocks and a template lock, registered through block.json with proper attribute schemas and an edit component in React. Page builders cannot offer this because their structure lives outside the post content.

#Secure WordPress REST API endpoints

Registering an endpoint is easy. Registering it properly means a real args schema with validate_callback and sanitize_callback per parameter, a permission_callback tied to a capability, rate limiting when the endpoint is open to anonymous traffic, and a versioned namespace (yourbrand/v1) from day one. Many REST problems I inherit come from permission_callback => '__return_true'.

#Why WordPress is slow and how to fix it

Generic advice (lazy loading, HTTP/2, a CDN) applies to any site. On WordPress I start with the autoloaded options, plugins that call get_post_meta($post_id) without a key, duplicate WP_Query calls in the header, meta_query lookups that belong in a taxonomy, and posts_per_page => -1 left in widgets. Redis helps only after the data layer is clean. In front of a bloated autoload table it caches the wrong thing faster.

#How to clean up a hacked WordPress site

Recovery from a real compromise is forensic work before it is cleanup. I read the access logs for the entry point and compare files against a clean copy of core, the active theme and the installed plugin versions. Most reinfections happen because a site was restored from a backup that was already infected, or because a backdoor sat in wp_options as a base64 payload in an autoloaded option. Scanning the options table is part of every cleanup.

Hardening follows: file editing disabled in the admin, xmlrpc.php restricted at the web server, REST user enumeration blocked, all API keys and database credentials rotated, and a firewall with rules for WordPress attack patterns.

#What a technical audit gives you

An audit should help you decide what to do first. I start with context: what the site is for, where it loses money, what the constraints are. Then I go through the layers: theme and plugins, PHP and server, database and cron, technical SEO (canonicals, hreflang, sitemaps, redirects). Findings end up in three groups: fix now, schedule next, consider later. Whether the answer is repair or rebuild follows from the audit, not from a first impression.

#Maintenance after stabilisation

Maintenance covers uptime monitoring every 1 to 5 minutes, backups kept for at least 30 days in EU countries, and updates I test on staging before production. Before I get access to a site that holds personal data, I sign a data processing agreement under Art. 28 GDPR. I do not offer 24/7 on-call or guaranteed response or repair times. You choose the hosting provider, I work with the existing stack.

Graphic design and wireframes come from you. I implement them and keep the code in a Git repository you can access.

#WooCommerce under high order volume

At higher volume, weak assumptions in checkout, stock handling and integration timing get expensive. I start from the transaction path: which steps must run synchronously, which integrations can be queued, which validations are redundant at checkout. Moving non-critical work out of the request lowers the risk of timeouts during payment. Filters, search and product metadata are the second pressure point, handled with query work, indexes and object caching.

#Reliable integrations with CRM and ERP

Integrations need a defined owner for each data object, validation, retries with limits, idempotency and visible errors. Without them, data drifts silently and someone corrects records by hand. Logs with an order or transaction ID make it possible to see where a record got stuck.

#Next step

If the store is already down or checkout is failing, start with the WooCommerce rescue sprint. After a breach or malware, use the WordPress security audit. For ongoing care after stabilisation, see the Store Reliability Plan. You can also send a short written brief.

Recommendations from LinkedIn

Recommendations and reviews of working with WPPoland

Recommendations from people in the WordPress, WordCamp and e-commerce communities. They write about delivery on time, technical depth and a business-minded approach to site development.

Karolina Czapla

Karolina Czapla

Marketing Strategist, Performance & Digital Strategy

“Working with Mariusz on WordCamp has shown me how rare it is to combine deep technical skill with genuine leadership. He plans, coordinates and delivers with precision, while giving the team space to grow and contribute. When others say 'it can't be done', he quietly finds a way.”

Co‑organiser, WordCamp Gdynia 2024 & 2025

Anna Kamińska

Anna Kamińska

Talent Acquisition Specialist / HR People Partner

“Mariusz's portfolio speaks for itself. It reflects his precision, versatility and sense of responsibility. You can trust him to guide a project from idea to delivery, keep stakeholders informed and make sure things are done properly and on time.”

Worked on the same team

Sarah‑Luisa Kwolek

Sarah‑Luisa Kwolek

IT Project Management & Product Owner, Web/App

“For over two years I could always rely on Mariusz to handle WordPress tasks calmly and professionally, from styling and templating to third‑party integrations. He brings steadiness to the team and keeps the frontend side of projects under control.”

Mariusz was her client for WordPress work

Argert Boja

Argert Boja

Senior Full‑Stack Developer

“Mariusz is the teammate everyone hopes for: strong full‑stack WordPress skills, clear explanations and a positive attitude even under pressure. He moves easily between custom plugins, performance work and Gutenberg layouts while keeping the bigger picture in mind.”

Worked alongside Mariusz on WordPress projects

Varun Patil

Varun Patil

Growth & CRM Lead

“Beyond development, Mariusz understands SEO, analytics and growth. He talks directly with stakeholders, asks the right questions and ships solutions that move business metrics, from AMP to tracking to performance.”

Managed Mariusz on growth initiatives

Rafał Osiński

Rafał Osiński

Founder @ EasyTrips.pl, Senior WordPress Dev

“I've known Mariusz through the WordPress community for many years. He's reliable, deeply involved and consistently shows up, at meetups, WordCamps and in projects. If you care about long‑term collaboration and someone who treats your site like his own, he is the right person.”

WordPress community co‑organiser

Daniel Blossfeld

Daniel Blossfeld

Process Optimization & Digitalization Consultant

“I had the pleasure of working with Mariusz for almost three years. During that time, his WordPress development skills proved invaluable across a range of projects, from website builds to online member areas and even Shopify integrations. He's a reliable and capable developer.”

Mariusz was his client for WordPress work

Natalie Wiszczor

Natalie Wiszczor

CRM & E-Mail Marketing Manager

“I had the great pleasure of working with Mariusz for over 4 years in the technical field. During this time, he proved to be a competent and reliable colleague. What stood out in particular was his friendly nature and his remarkable perseverance in solving complex technical challenges. Even in stressful situations, he always kept a clear head and contributed significantly to a positive and productive working atmosphere with his upbeat attitude. 🙏🏻🚀”

Worked with Mariusz on different teams

Mark Chalklen

Mark Chalklen

Head of Design & Build at Itineris Limited

“Mariusz is a great member of the team, always happy to get stuck into any task and happy to learn new things. A great communicator and all round nice guy to work with. Hard to beat on our weekly Strava leader board though!”

Managed Mariusz directly

Jessica Di Pasquale

Jessica Di Pasquale

Leading SEO initiatives with data-driven growth strategies.

“Mariusz is a very skilled, patient and expert guy. Always ready to help and to fix errors, I really appreciated working with him. He is such a great colleague!”

Managed Mariusz directly

Biki John

Biki John

Content Marketing Aficionado & SEO Enthusiast

“It was great to work with Mariusz. I really appreciated his extensive knowledge of WordPress and how that came in handy whenever I needed support navigating the CMS. I commend Mariusz totally for his patience, good nature and expertise in his craft, he will be thoroughly missed by all.”

Worked with Mariusz on different teams

Rafal Borowiec

Rafal Borowiec

Software Developer, Consultant, Manager and Lecturer

“I had an opportunity to work with Mariusz for 7 months. He excels in technical optimization for search engines (SEO). Mariusz has also strong expertise in AMP development, GTM, and GA. Mariusz feels very comfortable with WordPress - he worked on a variety of WordPress related projects and tasks, including landing pages development, performance improvements and much more. If you are looking for a solid WordPress expert specializing in SEO, tracking, performance, and development - don't hesitate to get in touch with Mariusz.”

Managed Mariusz directly

Belinda Koch

Belinda Koch

Web-Tracking Analyst at TUI

“Mariusz is a great person to work with. He is extremely motivated to learn new things and share his knowledge, and is very knowledgeable on a wide range of topics. We worked together on digital analytics and tracking topics and I am very grateful for all the energy, support, and insights he brought to the projects.”

Worked with Mariusz on digital analytics and tracking topics

Ali Nezamolmaleki

Ali Nezamolmaleki

Growth, SEO, Analytical thinking, AMP

“Mariusz is an extremely talented person in his field of work. He is always capable of giving a new perspective to solve problems and to think out of the box in situations where everything seems to be locked. Working with him is always a pleasure because of his positive personality and can-do attitude.”

Worked with Mariusz on the same team

Karol Jakubcewicz

Karol Jakubcewicz

Front-end / JavaScript Developer

“Mariusz is an incredibly experienced WordPress developer and SEO/SEM specialist I've had the pleasure to work with for almost two years. As a pilot of the team responsible for AirHelp's website development, he's been one the key figures in charge of constant load time and page rank improvement. I admire his skills and knowledge vital for such complex, multilingual and highly customized WordPress project. Lots of experience, tons of positive attitude - I highly recommend cooperating with Mariusz in any web development project.”

Worked with Mariusz on the same team

Paweł Lewczuk

Paweł Lewczuk

Front-end developer, WordPress developer

“I collaborated with Mariusz on several projects and our cooperation was always exemplary. I believe there are many more joint projects ahead of us. Highly recommended!”

Mariusz was Paweł's client

Przemek Wroblewski

Przemek Wroblewski

Software Developer with 20+ years of experience

“I found Mariusz as someone with great expertise and profound knowledge of frontend solutions. Powerful, knowledgeable and accountable WordPress developer. Has an easiness to build interpersonal relations with others. He had vision to see the benefits and the passion to turn that into measurable results for AirHelp. Absolutely someone I'd want to have on my team.”

Worked with Mariusz on different teams

All recommendations on LinkedIn

Frequently asked questions

Questions about scope, delivery, pricing, and execution quality.

WordPress specialist, what does WPPoland actually do?#
WPPoland is Mariusz Szatkowski, a WordPress developer since 2006. I take the incident a general developer could not close: an outage after an update, malware, poor Core Web Vitals, a WooCommerce checkout that fails under load. I work alone and do the work myself. New builds are on the WordPress developer page.
What is the difference between a WordPress specialist and a general web developer?#
A general developer can build a theme and wire up a contact form. A specialist knows the platform internals: the hook system, the options and meta tables, capabilities, how WooCommerce stores orders after HPOS, how caching plugins interact with the REST API. That knowledge decides whether a problem gets diagnosed or guessed at.
How does a WordPress specialist approach performance differently from a caching plugin?#
A caching plugin hides slow pages from anonymous visitors. It does not fix oversized autoloaded options, plugins that load every meta field on every request, expensive meta queries or render-blocking scripts. I measure where the time goes, using field data where it exists, then fix the data layer before adding an object cache.
What does a WordPress security audit and hardening cover?#
Manual review of active plugins and custom theme code, file integrity against clean core and plugin versions, a scan of the options table for hidden payloads, user and capability review, and server configuration. Hardening then covers two-factor login for administrators, disabled file editing, restricted xmlrpc.php, rotated keys and a firewall with WordPress-specific rules. No one can guarantee a site will never be attacked, and I do not.
When does a retainer make more sense than a one-off project?#
A one-off project fits a defined job: cleanup after a hack, a performance sprint, a migration, an audit. Monthly maintenance fits a site that earns money and needs updates tested on staging, uptime monitoring every 1 to 5 minutes and backups kept 30+ days in EU countries. I do not offer 24/7 on-call or guaranteed response times.