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

improve home page LCP #434

Closed
Vandivier opened this issue Mar 17, 2025 · 4 comments · Fixed by #438
Closed

improve home page LCP #434

Vandivier opened this issue Mar 17, 2025 · 4 comments · Fixed by #438
Labels
good first issue Good for newcomers

Comments

@Vandivier
Copy link
Owner

https://search.google.com/search-console/core-web-vitals/drilldown?resource_id=sc-domain%3Aladderly.io&item_key=CAMQAhgC

@Vandivier Vandivier added the good first issue Good for newcomers label Mar 17, 2025
@Vandivier
Copy link
Owner Author

png -> webp reduced the main logo size by 80%
this was the prod LCP constraint
pre-fix lighthouse:

Image

@Vandivier
Copy link
Owner Author

three prod pre-fix incognito lighthouse trials gave 88,89,88

fix v1 trials gave preview env 85,86,85

with this code structure:


          <Image
            alt="Ladderly Logo"
            className="m-6 block rounded-lg shadow-lg"
            height={330}
            priority={true}
            quality={85}
            sizes="(max-width: 640px) 270px, (max-width: 1024px) 330px, 400px"
            src="/logo.webp"
            style={{ alignSelf: 'center', maxHeight: '200px' }}
            width={330}
            loading="eager"
            decoding="async"
          />

@Vandivier
Copy link
Owner Author

v2 cancels eager loading
i get 86,97,86

shipping to prod...maybe prod loads faster...? the main change is smaller webp file

@Vandivier
Copy link
Owner Author

after shipping to prod, fixed lighthouse gave 90,90,90 incognito!

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

Successfully merging a pull request may close this issue.

1 participant