new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Vue · Guide · all subjects

performance/page-load

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Avoid pure client-side SPA for page load sensitive applications

If your use case is sensitive to page load performance, avoid shipping it as a pure client-side SPA. Pure client-side rendering suffers from slow time-to-content. Instead, use Server-Side Rendering (SSR) or Static Site Generation (SSG) where the server sends HTML containing the content users want to see. You can also use a traditional backend server to render the HTML and enhance it with Vue on the client if your app doesn't have rich interactivity requirements.

Separate marketing pages from main SPA application

If your main application has to be an SPA but has marketing pages (landing, about, blog), ship them separately. Marketing pages should ideally be deployed as static HTML with minimal JS using SSG.

Patch flags and tree flattening improve SSR hydration

Both patch flags and tree flattening improve Vue's SSR hydration performance. Single element hydration can use fast paths based on the vnode's patch flag. Only block nodes and their dynamic descendants need traversal during hydration, achieving partial hydration at the template level.

Give your agent this brain