AuraEvent is an event agency based in Sofia. Weddings, corporate parties, kids' celebrations with entertainers. Their website worked — it just worked slowly, and their inbox was filling up with inquiries that didn't smell like real clients.
Two problems sat on the table at once. First: the site scored 81 on Google's mobile PageSpeed test. Not a disaster, but enough to lose ranking and to make a visitor wait a beat longer than they should — and on mobile, that beat decides whether someone stays or closes the tab.
The second problem was stranger. The inquiry form started receiving requests for an event in New Zealand. An agency in Sofia. The client couldn't tell a real inquiry from a bride in Plovdiv apart from an automated bot spraying contact forms across the internet. Everything got deleted in bulk — including, quite possibly, a real inquiry buried in the noise.
We didn't touch the site's logic. Same menus, same pages, same structure — the client knows his site, and we weren't going to make him relearn it. We touched the machinery underneath.
We went through the site the way an electrician follows a wire — looking for where current stops, where it leaks. We found three leaks:
We built an automatic process on the server that checks the admin panel for new photos every 10 minutes and converts them to WebP — in three sizes: 480, 960, and 1600 pixels. The browser picks the right size for the screen on its own. The organizer keeps uploading photos exactly as before — snap, upload, done. Everything else happens behind the scenes.
We inlined the critical styles directly into the page — the browser has them in hand the moment it receives the html, no second request needed. Fonts moved local, onto the same server. And the most boring but most important fix: nothing in the first screen moves while the page loads. A banner that pops in, a button that shifts down half a second late — small things like that quietly kill the Speed Index score, even when they look harmless.
| Metric (mobile test) | Before | After |
|---|---|---|
| Performance | 81 | 100 |
| Accessibility | — | 100 |
| Best Practices | — | 100 |
| SEO | — | 100 |
The result is checkable right now at pagespeed.web.dev against the live site — we'd rather you verify it than take our word.
The full redesign took about two days, in a premium gold-toned theme chosen together with the client — the look changed, but the page and menu logic stayed the same, so neither the client nor his visitors lost their bearings.
For the spam, we didn't build a filter that deletes. We built a scoring system — it checks the match between language, message content, and a handful of simple bot-behavior signals — and routes the result into a separate "Spam" tab in the admin panel, not the trash. Nothing real disappears without a trace. The algorithm isn't perfect; when it misfires, the client can still open the tab and check for himself instead of wondering what got erased for good.
The site also had an interactive game for kids' parties — Party Magic, used for entertainer-led celebrations. It used to depend on an external embed. We rewrote it natively, directly into the site's code. Faster, steadier, and no longer at the mercy of a third party that might raise its price or shut down tomorrow.
Finally, we moved the entire domain to Cloudflare — without a single second of downtime. We lowered the TTL ahead of the switch and checked every record carefully, so neither the mail nor any subpage dropped during the cutover.
Honestly: we don't have sales growth numbers — we didn't measure them, and we won't quote a figure we haven't seen. What we do know for certain, and what anyone can verify: the site loads instantly on a phone, Google shows a perfect score across all four metrics, and the admin no longer spends her morning guessing which inquiry is real and which came from the other side of the planet.
If we started over, we'd put spam scoring in place from day one of the project, not as a second step after the problem had already been annoying someone for weeks. The lesson is simple: when a client says "I'm getting strange inquiries," that's not a minor detail to handle later — it's a signal that the form is too open, and something, or someone, has already found it.
If your site scores below 90 on a mobile test, or your inbox looks like a bot dumping ground — describe your situation in one sentence to the live agent at pentimento.pro and see what a fix could look like, right there in the conversation.
PENTIMENTO