Termerly logo

Bugs, Performance & Reliability

Report bugs, performance issues, availability problems, or document update delays. Describe when it happens and how it affects publishing or legal validity.

Share your comment

  • The header navigation has a row of tabs (Pages, Stats, Banners, Project). For a long time, when you navigated to a route that was not one of those primary tabs — like /settings or /profile — one of...

  • Auth screens (sign-in, sign-up, password recovery, email confirmation) had no business loading analytics widgets, tag management scripts, or the entire charting library on first paint. Those script...

  • Our authentication SDK was bundled into the entry JavaScript chunk of the admin app, meaning every visitor — including the ones who never reach a sign-in form — downloaded and parsed the entire aut...

  • There was a frustrating bug in the sign-out flow: under certain conditions, after clicking Sign out, you ended up staring at a 404 page on /sign-in. The cause was a stale service worker cache that ...

  • First-paint is the metric that defines how Termerly feels. Customers do not care about your bundle size in megabytes — they care that the dashboard appears the moment they tap the link. With that i...

  • Your dashboard stats now load reliably. There was a timing issue where the numbers could occasionally come up wrong or empty on first load; that race condition is fixed, so the figures you see are ...

  • The site now loads noticeably faster, especially on slower connections. We put a lightweight layer in front of the app that compresses pages and assets before they reach you.Less data travels over ...

  • Signing in and out is now more reliable. If you arrived on a public page after your session had already expired, the app could briefly hold on to that old session, leaving you in a confusing in-bet...