Skip to content

Services

Services

Everything that can be done to keep a WordPress site running — from the server to the plugins. Content and marketing are not on the list, on purpose.

Operations

Updates, backups, monitoring — regular and documented

Outdated components, weak access control and misconfiguration widen the attack surface. Regular updates, monitoring and verified backups reduce the risk and limit the impact of incidents.

WordPress updates

Core, plugins, theme and the PHP version kept current, tested, with a backup taken before each update.

  • A backup before every update, a check after it
  • Critical updates tested in a staging environment
  • Auto-update settings decided deliberately, not left to chance
Technical details
  • WordPress core, plugins, themes, translations
  • PHP version and extension lifecycle
  • Post-update functional check (home, form, login, cart)
  • Rollback from backup when an update breaks something

Provably restorable backups

What matters is not whether a backup exists but whether it restores. We test that regularly.

  • Daily database and file backups with an off-site copy
  • Regular restore tests, documented
  • Retention, encryption and size anomalies watched
Technical details
  • Last successful backup, database and file backups separately
  • Off-site copy, retention, encryption
  • Backup duration, size, deviation from the usual size
  • Restore test, last successful restore, RPO/RTO
  • Higher plans: scheduled restore test, sandbox restore, automatic application health check after restore

Monitoring

We check more than whether the site is up: whether the functions that matter actually work.

  • Availability, certificate, DNS, response time
  • Synthetic function tests: form, login, cart, payment
  • WordPress- and server-level monitoring depending on access
Technical details
  • HTTP/HTTPS, status code, redirect chain, TTFB, page load
  • Certificate expiry and chain, TLS version, HSTS
  • DNS records and their changes, SPF, DMARC, DNSSEC
  • Critical API endpoints, WooCommerce cart and checkout
  • In full: see the access levels

Staging and restore

A separate environment where an update or a change can break before it reaches the live site.

  • A staging environment for risky updates
  • Restore from backup with a tested procedure
  • Disaster recovery planning in the larger plans

Server operations

Where we have access to the server, we keep that in order too: updates, services, security, capacity.

  • Operating system and security updates
  • Nginx, Apache, PHP-FPM, MySQL/MariaDB, Redis, cron, fail2ban
  • Capacity, disk, logs and lifecycle watched
Technical details
  • OS version and lifecycle, reboot required, package updates
  • PHP lifecycle, OPcache, worker saturation, slowlog
  • MySQL: slow queries, buffer pool, connections, table growth
  • Redis: memory, hit ratio, evictions
  • Filesystem integrity, permissions, unexpected PHP files

Security

Smaller attack surface, faster detection, handled incidents

Security is not a plugin but several layers: current components, hardened settings, monitored vulnerabilities, and a procedure for when something happens anyway.

Hardening

WordPress and server defaults tuned to shrink the attack surface.

  • Access protection: login, XML-RPC, REST user enumeration
  • File permissions, editor disabled, version and error leakage removed
  • Security HTTP headers
Technical details
  • wp-login and wp-admin protection, XML-RPC restriction, REST user enumeration disabled
  • readme, license, directory listing, error leakage, exposed backups, .git, .env, SQL and log files
  • HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, CORS, cookie security
  • At server level: SSH key login, firewall, fail2ban, permissions

Vulnerability monitoring and management

Known vulnerabilities in installed plugins and themes are watched continuously and dealt with before they become a problem.

  • Installed versions matched against known vulnerabilities (CVE)
  • Abandoned, unmaintained plugins flagged
  • Patch, replace or temporarily isolate — whichever the situation calls for
Technical details
  • Plugin and theme versions, update status, latest available version
  • Vulnerability databases, CVEs, repository status, compatibility
  • Inactive and unnecessary plugins

Malware detection and cleanup

File integrity monitoring and malware scanning, and when needed, removal of the infection together with the way in.

  • Modified core, plugin and theme files detected
  • Unexpected PHP files, executable files among uploads
  • Cleanup, closing the entry point, a written report
Technical details
  • External malware and blacklist checks even without access
  • File integrity: core, plugins, themes, wp-config, permissions, symlinks
  • At server level: suspicious processes, outbound connections, rootkit checks

Incident response

When something goes wrong there is a procedure: contain, investigate, recover, learn.

  • Investigation of critical incidents begins with priority
  • Recovery time depends on the extent of the compromise and the infrastructure involved
  • A written incident report, and what changed afterwards

Access security

Who has access to the site and the server, and what happens when that changes.

  • Administrator accounts and role changes monitored
  • Weak usernames, inactive admins, two-factor state
  • On the server: SSH logins, new users, sudo usage, key changes

Performance

A fast site for measurable reasons

Speed is not a plugin you switch on but the whole chain: PHP, database, cache, CDN, and what the browser actually loads. We measure, change, and measure again.

WordPress and PHP tuning

WordPress and the PHP runtime configured for the real load.

  • PHP version, OPcache, memory and time limits, worker counts
  • Slow queries and slow pages identified
  • Autoloaded options, revisions, transients, needless load reduced
Technical details
  • OPcache hit rate, PHP-FPM max_children and saturation, slowlog
  • wp_options and autoload size, postmeta growth, Action Scheduler tables
  • WP-Cron and loopback request state

MySQL and Redis

The database and the object cache tuned so WordPress stops waiting needlessly.

  • MySQL/MariaDB parameters, slow queries, indexes
  • Redis object cache set up and monitored
  • Database cleanup and optimisation
Technical details
  • InnoDB buffer pool and hit ratio, temp tables, locks, connection count
  • Redis memory, hit ratio, evictions, fragmentation, maxmemory
  • Table growth, binlog, replication, corruption checks

Caching and CDN

Page, object and browser caches plus a CDN, coordinated so they do not fight each other.

  • Page-level cache and invalidation
  • CDN and Cloudflare setup, compression, HTTP/2 and HTTP/3
  • Cache headers and static asset delivery

Core Web Vitals

The user experience as Google measures it: loading, responsiveness, visual stability. Measured, improved, tracked.

  • LCP, INP, CLS, FCP, TTFB measured and trended
  • Page size, request count, JS, CSS and image payload
  • A concrete fix list, in priority order

Technical search compatibility

So that search engines can read the site without technical obstacles. This is not SEO content and not link building — that is not our desk.

  • Indexability, robots, sitemap, canonical, redirects
  • HTTP statuses, crawlability, structured data
  • Not included: keyword research, SEO copywriting, link building

Infrastructure

Order underneath WordPress too

Server, DNS, certificate, CDN, web server. Rarely visible, but everything else stands on them — and most mysterious faults start here.

Migration

WordPress, hosting or server migration without downtime, tested, with a way back.

  • Full migration with a rehearsal before the switch
  • DNS cutover with minimal downtime, redirects preserved
  • Checked afterwards: forms, e-mail, payments, cache

DNS, SSL/TLS, Cloudflare

The domain, the certificate and the edge, set up and monitored.

  • DNS records put in order, SPF, DKIM, DMARC, DNSSEC
  • Certificate issuance, renewal, chain and HSTS
  • Cloudflare: proxy, cache, firewall rules, CDN
Technical details
  • A, AAAA, CNAME, NS, MX, TXT records and their changes monitored
  • Certificate validity, expiry, hostname match, TLS version

Server setup

Linux, Nginx or Apache, PHP-FPM, MySQL, Redis — sized and hardened for WordPress.

  • New servers installed and configured, existing ones reviewed
  • Web server configuration, PHP-FPM pools, caching
  • Firewall, fail2ban, SSH key login, automatic security updates

Staging environments

A test environment matching the live site, where a change can be tried first.

  • Staging with a copy of the live database, protected from indexing
  • Updates and development tested in advance
  • A simple path to production

Development

If a technical function is missing, we build it

Custom plugins, WooCommerce extensions, integrations with external systems. Engineering work, not page-builder clicking: version-controlled, tested, documented.

Custom plugins and WooCommerce extensions

What off-the-shelf plugins cannot do, or do only with too much baggage: a focused, lean solution.

  • A custom WordPress plugin built for the actual need
  • WooCommerce extensions: product, cart, checkout, shipping, payment
  • Replacement of outdated or abandoned plugins

API integrations

CRM, PMS, invoicing, payment systems, warehouse — connected to the WordPress site, both ways.

  • REST- and webhook-based integration
  • CRM, PMS, invoicing and payment integrations
  • Import, export, scheduled synchronisation

Automation and SSO

Repetitive tasks handed to machines, single sign-on where several systems meet.

  • Automated processes and scheduled tasks
  • Single sign-on (SSO) with existing credentials
  • Webhooks served and processed

Cannot find what you need? Tell us what is going on: if it belongs to how the site runs, it is probably our desk.

Let us start with a report.

Send us your site's address and we will decide which assessment level fits. The result is a written WPdoki Lelet — and if we then run the site, the fee is credited.

Services — WordPress operations, security, performance, infrastructure | WPdoki