Skip to content
Contents
WordPress

WordPress: Where to Start

What KapsuleHost does for a WordPress site, what you still do yourself, and which guide to read for each job.

WordPress runs most of the web, and it is the default choice for most KapsuleHost sites. When you create a site as WordPress or WooCommerce, an extra WordPress group appears in the site's left menu with tools that only make sense for WordPress: updates, security, caching, and payments on stores. The application performance view (APM) sits under Performance and is for WordPress and WooCommerce sites only. This page maps them.

Installing and Getting In

Create the site as a WordPress site and the install is done for you, including the database and the admin account. You choose the admin username, password and site title during setup.

The WordPress admin password is shown once during setup. Save it in your password manager before you continue. Recovering it later is possible but slower than writing it down now.

If you cannot get into wp-admin, work through WordPress Admin Access and, if the password is the problem, Resetting the WordPress Password. The reset path in the panel does not depend on your site being able to send email, which is why it works when the "lost password" link does not.

Start here: Installing WordPress and WordPress Admin Access.

The WordPress Menu

Open Websites, click your site, and the WordPress group holds:

TabWhat it is for
WordPressThe main WordPress panel for the site
UpdatesCore, plugin and theme update handling
SecurityHardening and integrity checks
CachingPage and object caching controls
APMApplication performance, which requests are slow and why. In the site's left menu it sits under Performance, not in this group
PaymentsWooCommerce payment configuration, stores only

Updates: The Thing That Breaks Sites

Almost every "my site went down and I did not change anything" ticket turns out to be an update. Not because updates are bad, but because an unattended update of a plugin with a compatibility problem can take a site out at three in the morning.

The safe pattern is boring and works:

  1. Take a backup, or confirm today's automatic one exists. Taking a Backup.
  2. Apply the update on staging. Staging Environments and The WordPress Staging Workflow.
  3. Click through the parts of the site that matter: the homepage, a post, the checkout.
  4. Push to live.

If you would rather the platform handled the routine ones, see Automatic Updates. Read WordPress Updates and WordPress Plugins for what to update and what to be careful with.

Update one plugin at a time when you are on a site that matters. If something breaks, you know exactly which one did it. Bulk-updating twenty plugins turns a two-minute fix into an afternoon.

Speed

In rough order of how much difference they make for how little effort:

  1. Caching. Serve a stored copy instead of rebuilding the page for every visitor. Start at the Caching tab. See Site Caching.
  2. The CDN. Put the cached copy near your visitors instead of near your server. Availability depends on your plan and requires a custom domain. See Enabling the CDN.
  3. PHP version. Newer PHP is meaningfully faster. See Changing PHP Version.
  4. Images and plugins. The two things that most often make a WordPress site slow are enormous uploaded images and plugins doing work on every request. The APM tab shows you which requests are slow.
  5. Memory. If pages die halfway rather than loading slowly, you are hitting a limit, not a speed problem. See WordPress Memory Limit and PHP Extensions and Settings.

For the general version of this, see Website Speed and Site Slowness and Resource Limits.

The Classic WordPress Failures

Each of these has a specific, known cause and a specific fix. Do not guess.

WooCommerce

A store is a WordPress site with money in it, which raises the stakes on everything above. Backups matter more, updates need staging every time, and the Payments tab is where the gateway configuration lives. See WooCommerce, Site Payments and, if you would like the platform team involved, Care for WooCommerce.

For Developers

Security

WordPress is targeted constantly, mostly by automated scanners looking for one unpatched plugin. The Security tab covers hardening; the rest is habit.

See Security for the whole picture, and Site Security for the site-level controls.

Moving an Existing WordPress Site In

Use the migration wizard under Migrations. See Migrations, Migrating to KapsuleHost and Migrating From cPanel.

Still stuck? Opening a Support Ticket, or start from Websites and the Hosting Glossary.

Was This Helpful?

Are You an AI? Read This Page as Markdown

Related Articles

Installing WordPressWordPress is the most widely used website platform in the world, and KapsuleHost makes installation automatic. This guide covers two installation paths, how to manage your credentials, accessing the…WordPress Auto-UpdatesAuto-updates keep WordPress core, plugins and themes current without you watching for release notes, and they do it safely: a full backup is taken before every update, the site is checked…Payment Gateways for a WooCommerce StoreThe Payments tab lists the payment gateways available to your WooCommerce store, shows which are installed and which are switched on, and gives you one-click install and enable so you can go from a…Increasing the WordPress Memory LimitWhen WordPress or a plugin dies with a memory exhaustion error, the fix is to raise the PHP memory limit, and on KapsuleHost that is a dropdown in KPanel rather than a file edit. This guide covers…

Still Stuck?

Ask Kora, it knows your account, or contact our team.

Contact UsEmail Support