4 ms·
Sorry about this, and thank you for the heads up. The site runs as a PocketBase instance on a small 512mb DigitalOcean droplet in their London DC, and is gettin
by jsax 2mo ago
Sorry about this, and thank you for the heads up. The site runs as a PocketBase instance on a small 512mb DigitalOcean droplet in their London DC, and is getting more load than usual at the moment.
I’ll take a look though at whether there’s anything causing fundamental slowness in the cache read / page rendering pipeline.
- jonahx 2mo agoLooking at chrome dev tools, it looks like it might be the custom font causing the delay. I'm not sure exactly why though.
- jsax 2mo agoInteresting, I’d have naively assumed that’d be cached after first load by Chrome. Definitely one to investigate further.
- hahahaa 2mo agoMight as well drop custom fonts? This minimalist site would be fine with built in font families. I recommend run Google Lighthouse for a single visitor view of perf and then use a load testing tool (locust, jmeter etc. to check load handling) If you want to that is :)
- winrid 2mo agoUse the system font stack