-
Notifications
You must be signed in to change notification settings - Fork 9.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
Page loads very slowly due to CSS.enable #16118
Comments
I can reproduce this. #15890 this issue was related to CSS rule usage tracking but perhaps we should try to prevent the entire CSS domain from being enabled during a run. This will be more challenging than #15890 though because enabling the CSS domain is the only way to track transient style sheets. |
|
I have no idea what you are talking about. This is driving me crazy. I do
not mean to ignore your emails. Thank you for contacting me but I need to
speak with someone directly to help me figure this out.
…On Tue, Jul 23, 2024, 7:16 AM Paul Irish ***@***.***> wrote:
Closed #16118 <#16118>
as completed via #16121
<#16121>.
—
Reply to this email directly, view it on GitHub
<#16118 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BG6SWCCBUV3BBCFPNRYWE43ZNZQVLAVCNFSM6AAAAABLAA77XKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGYYTMNRTGE3TMOA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
@Hayzlee11 please stop responding to emails from github.com, you are spamming a forum for collaboration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
FAQ
URL
http://www.kennametal.com/store/us/en/kmt/login.html
What happened?
The page is stuck loading for quite a while. Recording a trace shows that it's related to StyleEngine calls.
What did you expect?
The page should load with a similar speed to visiting it normally in Chrome.
What have you tried?
I tried bypassing any CSS.enable calls, and the page loads as expected.
Not sure if this is still related to this issue? #15890
How were you running Lighthouse?
CLI
Lighthouse Version
12.1.0
Chrome Version
126
Node Version
No response
OS
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: