# Subpar PageSpeed Insights scores

**URL:** <https://forum.builder.io/t/subpar-pagespeed-insights-scores/6791>\
**Category:** Technical Questions\
**Created:** [November 19, 2024, 2:04pm UTC](https://forum.builder.io/t/subpar-pagespeed-insights-scores/6791 "2024-11-19T14:04:29Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![hfrid](https://avatars.discourse-cdn.com/v4/letter/h/4af34b/32.png) [@hfrid](https://forum.builder.io/u/hfrid)\
**Post date:** [November 19, 2024, 2:04pm UTC](https://forum.builder.io/t/subpar-pagespeed-insights-scores/6791/1 "2024-11-19T14:04:29Z")

</div>

We’re getting subpar pagespeed scores on our [Builder.io](http://Builder.io) pages, example:  
[https://pagespeed.web.dev/analysis/https-onceupon-photo-sv-se-fotobocker/nospdaim0j?form\_factor=mobile](https://pagespeed.web.dev/analysis/https-onceupon-photo-sv-se-fotobocker/nospdaim0j?form_factor=mobile)

Would really appreciate help on how to optimize!

---

<div class="post-metadata">

**Author:** ![Stephane](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@Stephane](https://forum.builder.io/u/Stephane)\
**Post date:** [November 19, 2024, 2:09pm UTC](https://forum.builder.io/t/subpar-pagespeed-insights-scores/6791/2 "2024-11-19T14:09:33Z")

</div>

Hi Henrik,

Here’s a detailed article on the topic, which I hope will help you address your Insight Score:

> **[Optimizing Web Performance with Builder - Builder.io](https://www.builder.io/c/docs/perf-best-practices)**
>
> Optimize web performance with Builder. Learn best practices for enhancing speed, user experience, and SEO rankings in your web applications.

---

<div class="post-metadata">

**Author:** ![hfrid](https://avatars.discourse-cdn.com/v4/letter/h/4af34b/32.png) [@hfrid](https://forum.builder.io/u/hfrid)\
**Post date:** [November 19, 2024, 2:12pm UTC](https://forum.builder.io/t/subpar-pagespeed-insights-scores/6791/3 "2024-11-19T14:12:53Z")

</div>

Thanks for the quick reply Stephane! I’m looking for guidance on our specific issues though 🙂

---

<div class="post-metadata">

**Author:** ![Stephane](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@Stephane](https://forum.builder.io/u/Stephane)\
**Post date:** [November 19, 2024, 3:04pm UTC](https://forum.builder.io/t/subpar-pagespeed-insights-scores/6791/4 "2024-11-19T15:04:19Z")

</div>

While each site is built differently, and our recommendations can be generic, switching between mobile and desktop on the tool you used to measure performance does seem to indicate a significantly higher score on Desktop than mobile.

Here is an article which should help:

> **[How To Improve Lighthouse Scores by Avoiding Layout Shifts](https://www.builder.io/blog/how-to-improve-lighthouse-scores-by-avoiding-img-layout-shifts)**
>
> The correct aspect ratio will improve your Lighthouse scores. Layout shifts can happen for many reasons, dive into how images can have a negative effect.

---

<div class="post-metadata">

**Author:** ![hfrid](https://avatars.discourse-cdn.com/v4/letter/h/4af34b/32.png) [@hfrid](https://forum.builder.io/u/hfrid)\
**Post date:** [November 20, 2024, 9:41am UTC](https://forum.builder.io/t/subpar-pagespeed-insights-scores/6791/5 "2024-11-20T09:41:04Z")

</div>

CLS is not as big of a problem as LCP is. I would really appreciate some on hands help to get this resolved 🙂

---

<div class="post-metadata">

**Author:** ![Stephane](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@Stephane](https://forum.builder.io/u/Stephane)\
**Post date:** [November 22, 2024, 12:42pm UTC](https://forum.builder.io/t/subpar-pagespeed-insights-scores/6791/6 "2024-11-22T12:42:36Z")

</div>

Relaying a post from my colleague @veronikapilipenko which did not publish:

My name is Veronika and I am a Customer Engineer here at Builder. I was able to take a look at the Metrics you sent over and can see that the LPC is taking 7.4 seconds to load.

I have also taken a look at the diagnostics that PageSpeed Insights provided and have gathered some ideas on optimizing site performance. Based on the metrics, the screenshot I added of the carousel is your LPC.

One way we can look into optimizing the carousel is utilizing responsive layouts and ensuring that the carousel is responsive to different screen sizes. You can use attributes such as `aspect-ratio` and `object-fit` to maintain the image’s aspect ratio and adjust the image scaling. This prevents layout shifts that might adversely affect user experience and performance. Another way to try and do this this is by implementing the `srcset` attribute to serve appropriately sized images based on the user’s device, which would improve latency.

Another thing you can do for image content to use attributes such as lazy loading (`loading=“lazy”` ) and `fetchpriority="low”` for non-critical images. This will improve initial load times. I can see the carousel has an attribute of `fetchpriority="high"` meaning it’s important, but perhaps the other content on the page can have lower priority, improving performance.

Also, are you using any third-party scripts in your application? Using web-workers can help free up the main thread for rendering critical issues.

Some other things to consider may be to use the `defer` attribute to delay the execution of non-essential JS, allowing main content to load first.

Another thing to look out for are hydration errors - which can negatively impact your page performance by forcing client-only rendering. One of the biggest performance gains you can achieve is by using SSR (server side rendering). Since SSR pre-renders content on the server, this reduces the load on the client’s side and improves initial load times.

Let me know if you try any of these and have any further questions, I’m happy to continue digging into this for specific use cases and if you have any other LPC that you feel is slowing down site performance, I’m happy to look into that as well.

Thank you,

 ![Screenshot 2024-11-21 at 3.23.03 PM](https://us1.discourse-cdn.com/flex020/uploads/builder/original/2X/1/11ac63549edcd66ed73e86e4b233abafa282b8f1.png)
