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

[BUG] Improve Largest Contentful Paint (LCP) by optimizing image loading #677

Open
2 tasks done
Recxsmacx opened this issue Mar 28, 2025 · 2 comments · May be fixed by #699
Open
2 tasks done

[BUG] Improve Largest Contentful Paint (LCP) by optimizing image loading #677

Recxsmacx opened this issue Mar 28, 2025 · 2 comments · May be fixed by #699
Labels
bug Something isn't working

Comments

@Recxsmacx
Copy link
Contributor

Describe the bug.

Largest Contentful Paint (LCP) marks when the largest content element (usually an image or block of text) is rendered. Currently, our LCP score is 0.00, which means our largest visible element, the paint image, is taking too long to load. This significantly affects the perceived speed of our website and user experience.

Expected behavior

With optimized loading of the paint image, the LCP score should improve, leading to a better user experience and potentially higher SEO rankings.

Screenshots

Image

How to Reproduce

--

🖥️ Device Information [optional]

No response

👀 Have you checked for similar open issues?

  • I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

Are you willing to work on this issue ?

Yes I am willing to submit a PR!

@Recxsmacx Recxsmacx added the bug Something isn't working label Mar 28, 2025
@Siddhant-Pragyan-Sinha
Copy link

Hey @Recxsmacx , I see the issue you raised as very interesting. I would love to collaborate on this issue with you

@ashmit-coder
Copy link
Collaborator

@Recxsmacx you can go ahead and create a pr for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants