Skip to content
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

🐛 layoutBackgroundBlur + showRecent leads to laggy homepage #907

Closed
jamesbraza opened this issue Aug 12, 2023 · 2 comments
Closed

🐛 layoutBackgroundBlur + showRecent leads to laggy homepage #907

jamesbraza opened this issue Aug 12, 2023 · 2 comments

Comments

@jamesbraza
Copy link
Contributor

jamesbraza commented Aug 12, 2023

Describe the bug

When working on my portfolio website, I observed homepage settings layoutBackgroundBlur = true with showRecent = true and showRecentItems = 12 lead to a laggy homepage when scrolling down. I disabled layoutBackgroundBlur, and the issue went away.

Looking at this site (config), it seems to have the same issue (as of 8/12/2023).

To Reproduce

Steps to reproduce the behavior:

  1. Set layoutBackgroundBlur = true and showRecent = true (with showRecentItems >= 10) in [homepage] section of params.toml
  2. Go to homepage and scroll down

The lag happens for both a Namecheap shared hosting (what I use) and GitHub Pages (linked site).

Desktop (please complete the following information):

  • OS: macOS Monterey version 12.6
  • Browser: Google Chrome 115.0.5790.170
  • Site: Hugo 0.116.1, Blowfish 2.38.3

Here's a Speedtest result, to show I have decent internet speeds:

screenshot of speedtest
@ragibson
Copy link
Contributor

Popping in here as well from the other issue to note that I found a lot of documentation saying to avoid these blur filters entirely as they are extremely intensive and often do not perform well on mobile.

The pull request linked above improves the draw calls in Firefox by ~2x when using the blur features, but a remaining ~100x would come from a better CSS implementation that avoids backdrop-filter entirely.

@nunocoracao
Copy link
Owner

Should be fixed. Please re-open if the issue persists

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants