Cases

Real problems met while building PageBrick: what was decided, how it was checked and what came out of it, including what got worse. Every case links to the release, the tests and the decision log.

Speed16–22 Oct 2026 · PageBrick 1.8.0 and theme 2.2.0

From a PageSpeed report to the fix

pagebrick.org runs on PageBrick, so its PageSpeed report is the product’s own report. In under a week the mobile score went from 95 to 98 and the biggest finding disappeared, measured the same way on the same page. Two secondary numbers got worse, and they are in this case too.

Read the case

Integration21 Oct 2026 · PageBrick 1.11.0

A field that accepts one script and nothing else

Path Ranker, a site-diagnostics tool from the same maker, needed its behaviour collector on sites that run PageBrick. The answer was one field in Settings that accepts that script and nothing else, built, tested and released the same day.

Read the case

Plugins15–16 Oct 2026 · PageBrick 1.6.0, 1.7.0 and 1.7.1

From a client’s request to a release

Staff at a client’s site opened the same screen every day, and it was hidden behind the Plugins icon. Asked on 15 October, out on 16 October, in a form that changed nothing for any other site.

Read the case

Installation15 Oct 2026 · PageBrick 1.4.1

The installer that proves the panel opens

A new site on a shared cPanel host finished the installer and showed the host’s own 404 page. The installer now proves that the panel opens before it says it is done.

Read the case

Want to see the code behind it?

PageBrick is open source under the MIT License. Read it, run it, report what is wrong.

See it on GitHub