lysyweb.pl is WordPress with a custom block theme and one companion plugin, with no builder and no separate plugins for SEO, forms or security. It runs in Docker on my own server. In Lighthouse tests on production it scores 96-99 on phone and 100 on desktop. Below I describe where those results come from, how I handle security and how I check every change before deployment.
What performance looks like
I measure four page types (home page, services, case study and article) with Lighthouse on phone and desktop, three runs each, and take the median. On production the results are:
| Measurement | Phone | Desktop |
|---|---|---|
| Lighthouse score | 96-99 | 100 |
| Largest element (LCP) | 1.9-2.2 s | under 0.5 s |
| Main thread blocking (TBT) | up to 44 ms | up to 16 ms |
| Layout shift (CLS) | about 0 | about 0 |
Where the results come from
- Scripts are about 70 KB and styles 16-20 KB. No jQuery and no builder.
- Fonts are self-hosted, and the most important ones are preloaded.
- Animations (GSAP, also self-hosted) load only after the fonts and after the browser is idle, so they don’t get in the way of the first render.
- The first screen doesn’t wait for JavaScript: the content is visible without it, and motion only adds to it. The “reduce motion” setting turns animations off completely.
- Photos are WebP, sized to fit their place, and lazy-loaded below the first screen.
These are lab tests with an emulated slow network, not data from real users. I use them to compare before and after every change. More about the method itself in the article How to speed up WordPress.
Security
- XML-RPC and the file editor in the dashboard are switched off.
- Software versions and usernames are hidden (no author pages and no user list in the API).
- Limited login attempts and two-factor login.
- Security headers, including a content security policy (CSP), for now in report-only mode.
- PHP execution is blocked in the uploads directory.
- A security.txt file with a contact for people who find a vulnerability.
I described the full list with reasons in the article How to secure WordPress: 12 steps.
How I keep quality up
Every change goes through several automated checks before it reaches the server:
- Editor. I write templates by hand, so a script opens them in the real site editor and checks that no block shows the “Attempt recovery” message.
- Accessibility. An axe test against WCAG 2.2 AA on all page types, in light and dark theme. The goal: zero violations.
- Layout. No horizontal scrolling at five widths, from 390 to 1920 pixels.
- Motion. The content must be visible with animations, without them, without JavaScript and when the animation library fails to load.
- Performance. A Lighthouse measurement and a comparison with the previous version. The budget is thread blocking under 100 ms and a largest-element time no more than 300 ms worse.
What’s next
On my list is switching the content security policy (CSP) from report-only to enforcing once I have looked through the reports from production, and more articles in the Guide. You can find screenshots and the full description in the case study of this site, and if you want a similar site for yourself, see WordPress websites.
Key takeaway
A fast, secure WordPress means little third-party code, add-ons loaded last and automated checks before every deployment.