I wanted to share an experiment that drives Next.js 13 SSR and SSG features to its limit. I built a website with 5000 SSR pages to see how Next.js ...
For further actions, you may consider blocking this person and/or reporting abuse
Wow 🤩😍
I'm just blown away by the amount of work you've put into this. This article is so awesome 😎 If we can get a video I'll be grateful 😁
I'm blown away by the page speed insights for such a big site, it's insane how everything works out of the box most of the time.
If I want to clarify, please this means you did not use Vercel for hosting, but rather AWS amplify right?
Correct me if I'm wrong please.
The homepage lists 10 products with one image each, and it takes 3.1 seconds to load entirely even when the page is loading from the browser cache?
And a dynamic page lists a single product with a single image, and it takes 2.1 seconds to load entirely?
If these numbers are as I described, then this is too slow. I have PHP code that creates an entire page in 3 seconds; from zero to completed with a multi-level panel menu, search form with multiple selectboxes and datepickers, and 100 records with related fields included and multiple buttons for each record (that are created on the server based on multiple fields of that specific record), and at least 20 images.
Is this because of NextJS?
Amazing article ! Thank you for the effort and for sharing it. It would also be interesting to do a stress test with multiple connections to see how it behaves.
Thanks for this post!
I think this would not work in production since revalidation only happens when a page is hit with a user's request. Next itself does not schedule revalidation compared to a cron job, the revalidation duration is just the minimum cache time and can be compared to stale-while-revalidate caching.
You really worked hard on this one, hmm?
I wonder what makes you doubt about this in first place?
Good luck on your next experiment 👍
Amazing how much work you put into this. Thanks for sharing!