-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[docs] Improve lighthouse performance score #15758
Conversation
Details of bundle changes.Comparing: df50ea7...9e5bb30
|
It remembers me: #14299 |
I'm not you should actually lazy load main fonts. Didn't find anything in the lighthouse docs. What I am wondering though is if we shouldn't extract the font paths and preload them. Not sure if the *.woff paths change very often but currently this results in a waterfall from doc -> fonts.googleapis -> gstatic. fonts.googleapis is also a bit wasteful since it loads greek, vietnames etc. Though it does document a |
@eps1lon Anything missing for leaving the "Draft" state? |
Yes |
Well done. |
Yeah I was hoping to gain a bit more but I guess there are some false positives from lightouse. At least the input latency doesn't make much sense. |
Maybe it's something to explore: https://www.webpagetest.org/result/190525_2S_ba02c243c6318fd2a192baeae34e4e47/. The rendering gap in the middle is strange. Bandwidth is low, CPU usage is low, and yet, the main thread is busy for 1s: |
Hi, @eps1lon @oliviertassinari , this doesn't work for lighthouse any more.
works as expected. |
Doing some lighthouse perf auditing. Starting with using font-display: swap.
Only auditing the landing page in this PR. Should have the most potential.
lighthouse report from this PR