We've shipped a wave of improvements to the platform this month, and the best part is that almost none of them ask anything of you. Your sites are now better protected against attacks, load faster for visitors on real-world networks, and give you a far clearer picture of who's actually visiting — all without a single setting to change.
Here's what's new, and what it means for your sites.
If you run WordPress, your login page is under constant, automated attack.
Bots roam the internet around the clock, hammering wp-login.php with thousands
of username and password guesses, hoping to stumble onto a weak credential.
It's relentless, it's noisy, and even when it fails it costs you real server
resources.
We now stop these automated attacks at the network edge — before they ever reach your site.
A lightweight check confirms that a real browser actually loaded your login form before any login attempt is accepted. The bots that blindly POST guesses straight at the login endpoint never make it through. A per-source rate limit backs this up, capping any single abusive address. Both run before any of your site's PHP code executes, so attack traffic no longer burns your CPU and memory.
What this means for you:
On sites that were under active attack, automated login attempts reaching the application fell by roughly 97–99% once this went live — while legitimate logins were completely unaffected.
Do you need to do anything? No. It's on automatically for every site.
Our control panel has long offered a set of one-click WordPress security controls — things like blocking XML-RPC, disabling the built-in file editor, blocking PHP execution in your uploads folder, turning off directory browsing, and adding protective security headers.
Those toggles now apply reliably across every hosting stack we run, including our high-performance LiteSpeed-based tier. Whatever plan your site is on, flipping a security setting now dependably takes effect.
Why it's worth a look:
Do you need to do anything? This one is optional, but recommended. Take a minute to visit WordPress → Security for your sites and switch on the protections you want.
We've enabled HTTP/3 — the newest version of the protocol browsers use to load websites — across our edge. Modern browsers automatically upgrade to it on their next visit; everyone else keeps working seamlessly over HTTP/2 and HTTP/1.1.
What your visitors get:
All of your existing protections — rate limiting, our web application firewall, IP rules — apply to HTTP/3 traffic too. Nothing changes for you, and nothing changes for visitors on older browsers.
Do you need to do anything? No. It's automatic for every site, negotiated transparently by each visitor's browser.
This is the biggest visible upgrade this month. The Site Traffic page has grown from a simple daily total into a genuine analytics view.


Why you'll like it:
Going forward, your traffic is recorded permanently into your analytics history (kept for around 12 months), independent of raw web-server logs. We've backfilled recent history where we could — and your full, detailed history builds from here forward.
Do you need to do anything? No. Just open the Site Traffic page — the data accumulates automatically.
| What's new | What it means for you | Anything to do? |
|---|---|---|
| WordPress login protection | Far fewer attacks, more stable & secure sites | Nothing — it's on |
| One-click WordPress hardening | Reliable security toggles on every plan | Optional — enable in the panel |
| HTTP/3 (QUIC) | Faster, more resilient page loads | Nothing — it's on |
| Hourly + daily traffic drill-down | Understand visitors, spot spikes | Nothing — just visit the page |
| 30-minute analytics refresh | Near-real-time traffic visibility | Nothing — it's on |
Faster, safer, and more transparent — automatically. That's the goal with every release, and there's more on the way.
As always, if you have questions about any of these, our support team is happy to help.