Web performance
Make enterprise Next.js sites fast, and keep them fast
Most slow Next.js sites are slow for ordinary reasons.
A route rendered on every request that could have been static. Analytics and marketing scripts competing with the page for the main thread. A hero image or a font that arrives last.
We find those causes and fix them. Monogram designs and builds Next.js sites on Vercel, and performance is part of the build, not a pass at the end.
On Newfront's ABD Portal, which we rebuilt in Next.js on Vercel, Largest Contentful Paint is 0.5 seconds on desktop and First Contentful Paint is 0.2 seconds. Its Google PageSpeed Insights scores sit in the high 90s to 100 across Performance, Accessibility, Best Practices and SEO.
What we deliver
We resolve the technical issues behind poor Core Web Vitals, and we build new sites to start fast. On Kasada we optimized hero media and the way marketing and analytics tools load, so those tools do not degrade Core Web Vitals.
What we check first
- Rendering per route
A marketing page can be static while the dashboard beside it renders per request. We choose the rendering strategy route by route.
- Third-party scripts
Tag managers, analytics and ad pixels compete with your own code for the main thread. We decide which scripts load, when and where.
- Hero media and fonts
The largest element on the page is usually an image or a headline. On a workflow mini-site we built for Vercel, optimizing fonts and embeds earned a perfect PageSpeed Insights score.
What a load test cannot tell you
A k6 virtual user issues requests. It does not run your bundle or hydrate the page, so a page that is slow because of client JavaScript still looks healthy under load. A load test has to sit beside Core Web Vitals measured in a browser, not replace them.
The open source edition of Gatling drives load from one machine. It tells you whether a change made things worse, not what happens at real peak.
Common questions
We can. We rebuilt Newfront's ABD Portal in Next.js on Vercel, and it now scores in the high 90s to 100 on PageSpeed Insights, with a Largest Contentful Paint of 0.5 seconds on desktop. On Kasada's Next.js site we kept third-party marketing and analytics tools from degrading Core Web Vitals.
Make your site fast and keep it fast.
Send us the URL and the pages that matter most. We will tell you where the time goes and what it would take to fix.
Talk to an engineer
