Loving how this perf tool we're making is coming along
Most tools show what *could* improve, but poorly quantify what will make a real difference
Spoiler alert: excessive JS is more of an issue than you think
More examples and how it works in 🧵:
Most tools show what *could* improve, but poorly quantify what will make a real difference
Spoiler alert: excessive JS is more of an issue than you think
More examples and how it works in 🧵:
How does it work? We ingest the page, modify the code, and then run the new page through @____lighthouse to test the impact of each possible optimization
We are seeing the same clear patterns among sites large and small: loading up your site with JS is crushing your performance
We are seeing the same clear patterns among sites large and small: loading up your site with JS is crushing your performance
So what do you do about it? You need to free yourself from this heavy JS dependency
This is why we are making Partytown and @QwikDev
Partytown: moves third party scripts to a web worker
Qwik: removes all first party JS until absolutely needed
Results are exactly as hoped:
This is why we are making Partytown and @QwikDev
Partytown: moves third party scripts to a web worker
Qwik: removes all first party JS until absolutely needed
Results are exactly as hoped:
@QwikDev Oh yeah, and @builderio is fully optimized for both, letting you make insanely fast web content with our without code
Also worth noting: it was clear that we can get a 90+ score on virtually any site by optimizing just those 3 buckets
- Images (use next gen compression, correct sizing/srcset/etc)
- CSS (remove unused, use font-display, etc)
- JS (remove as much as possible for page load)
- Images (use next gen compression, correct sizing/srcset/etc)
- CSS (remove unused, use font-display, etc)
- JS (remove as much as possible for page load)
In our research, we would consider the images and CSS optimizations largely solved problems.
There are good off the shelf solutions for making sure you have modularized CSS and compressed/sized/lazy images.
But the JS problem is the most impactful has been the most unsolved
There are good off the shelf solutions for making sure you have modularized CSS and compressed/sized/lazy images.
But the JS problem is the most impactful has been the most unsolved
I think the reason why JS is hard is that it is a "death by a thousand cuts"
All sites start small and fast, but as you add components, business logic, 3rd party scripts, it cuts you down.
Lazy loading is not enough
All sites start small and fast, but as you add components, business logic, 3rd party scripts, it cuts you down.
Lazy loading is not enough
Conventional advice stops working at a certain scale, but business needs don't stop
That's why we only believe in solutions that scale
@QwikDev remains equally fast regardless of how complex your site becomes
And Partytown can offload as many 3P scripts you need to a worker
That's why we only believe in solutions that scale
@QwikDev remains equally fast regardless of how complex your site becomes
And Partytown can offload as many 3P scripts you need to a worker
@QwikDev If you made it this far, thank you for attending my ted talk lol
• • •
Missing some Tweet in this thread? You can try to
force a refresh
