Building instant-on web applications at scale have been elusive. Real-world sites need tracking, analytics, and complex user interfaces and interactions. We always start with the best intentions but end up with a less-than-ideal site.
Let's look into the anatomy of a slow site and dissect it to find out how each issue got there and why fixing it is not a trivial exercise. Understanding the problem is the first step. Next is to think about possible solutions to prevent this.
- Anatomy of a slow site
- Understanding the PageSpeed budget
- Third-party code
- First-party code
- Hydration problem => front load JS
- Lazy loading problem => can't lazy-load visible components
- Resumability is a possible solution => but it is hard
Sign up to receive updates about NG Poland, including workshops, speaker previews, ticket launches, NG Awards, Behind the Code Magazine, CFP details and other exclusive content. We won’t spam you and will only send you emails we genuinely think you’ll find interesting. You can unsubscribe at any time and you can find more information here.