Qwik is a new bread of frameworks with a goal of instant-on interactivity for your site, even on low-power, slow-network devices. Qwik is a resumable framework that starts its execution on the server and seamlessly transitions to executing on the client in a very lazy and incremental way. The seamless transition from server to the client provides an instant on-user experience which leads to lower bounce rates, more conversions, and higher sales.
With Partytown for third-party scripts and Qwik for your first-party applications, your browser main thread has never been so bored. Qwik and Partytown are new bread of open-source web technologies that are designed with startup performance first as the main objective, and all other design decisions follow from that goal. When Qwik and Partytown are combined with an edge-delivery network, it is possible to get your application fully interactive into users' hands in as little as 50 ms setting a new standard of startup performance.
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