Managed WordPress Hosting built different 💪

pressypress
Plan & billing

How to read your usage and health

Every figure on the Overview is measured for your site, against your plan's own limits — not a shared-account average, and not the server's totals. That is possible because your Pressy is its own container rather than a folder inside somebody else's account.

The four meters

Memory, Storage, vCPU and Bandwidth this month, each shown against its ceiling. Where you have bought extra, the meter says so — the base from your plan plus what you added — so a 3 vCPU limit is visibly 1 included and 2 bought rather than a number with no story.

Figures are cached and the age is shown. Refresh forces a fresh read, throttled, because a six-hour-old number with no way to check it reads as a wrong number.

The health panel

Measured live, every minute. Seven rows, and the last two are the ones worth learning:

RowWhat it means
ProcessesHow many processes your container is running
Disk IOPSDisk operations per second
Disk read / Disk writeThroughput against the disk
vCPU throttlingMoments your vCPU cap paused the site
Out of memoryMoments the memory limit killed something

Storage and the three disk rows are different quantities on purpose. Storage is the quota you buy; IOPS and read/write are throughput against the device. The meter above does not govern them.

Reading it as a decision

  • vCPU throttling climbing, memory fine — you are vCPU-bound. Add a vCPU rather than a memory tier; it is the cheaper dial and the one actually binding.
  • Out of memory above zero — something was killed mid-request, which is what a white screen during a plugin install usually is. Add memory.
  • Storage near its limit — add storage in 5 GB units, which is €1 a month each, rather than moving up a whole tier.
  • Everything comfortable and the site still slow — the constraint is not resource. Look at PHP caching and the error log before spending money.

Storage is also the one dial that can block a downgrade: you cannot shrink below what the site is already using.

Visitors and bandwidth

Counted from server requests, not sessions, so the figures will not match Google Analytics — a page with twenty assets is one visit there and rather more requests here. The screen says so rather than letting you assume the two should agree. Bots are counted separately.

The most recent period is still being counted and is drawn as a dashed line, so a "drop" at the right-hand edge of the chart is usually just the hour not being over yet.

There is no separate Analytics screen. It was folded into the Overview beside the meters, because "how much traffic" and "how much of my plan is left" are one question.

When the numbers say you need more, changing size takes about a minute and is pro-rated to the day.

Didn’t solve it?

Write to us with your Pressy’s address and what you were doing when it went wrong. Answered by the people who built it.

Last updated