# \[Resolved\] Performance degradation with Chrome version 135

**URL:** <https://community.holistics.io/t/resolved-performance-degradation-with-chrome-version-135/2440>\
**Category:** News from Holistics\
**Created:** [April 11, 2025, 11:22am UTC](https://community.holistics.io/t/resolved-performance-degradation-with-chrome-version-135/2440 "2025-04-11T11:22:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![datbth](https://community.holistics.io/user_avatar/community.holistics.io/datbth/32/1414_2.png) [@datbth](https://community.holistics.io/u/datbth)\
**Post date:** [April 11, 2025, 11:22am UTC](https://community.holistics.io/t/resolved-performance-degradation-with-chrome-version-135/2440/1 "2025-04-11T11:22:02Z")

</div>

Hi folks,

We are seeing a performance degradation when using Holistics with **Chrome** version **135**.  
If you are experiencing symptoms like stuttering UI or “page is not responding”, **please try to use Firefox or Safari for now**.

We are working hard to resolve the issue as soon as possible.

Our apologies for any inconvenience caused.

Best regards,

---

<div class="post-metadata">

**Author:** ![datbth](https://community.holistics.io/user_avatar/community.holistics.io/datbth/32/1414_2.png) [@datbth](https://community.holistics.io/u/datbth)\
**Post date:** [April 14, 2025, 8:24am UTC](https://community.holistics.io/t/resolved-performance-degradation-with-chrome-version-135/2440/2 "2025-04-14T08:24:49Z")

</div>

Hi all,

We have made some optimizations to mitigate the performance issue with Chrome 135. According to our internal testing, the optimizations have brought the performance back to normal usability. **Thus, you should now be able to use Holistics on Chrome 135 normally.**

Nevertheless, we will still be looking for any remaining issues with Chrome 135 and make further optimizations if needed. Please do not hesitate to contact Holistics Support if you still encounter any stuttering UI or “page is not responding” symptoms.

Thank you for your patience.

---

<div class="post-metadata">

**Author:** ![Bear\_Stonem](https://community.holistics.io/user_avatar/community.holistics.io/bear_stonem/32/2153_2.png) [@Bear\_Stonem](https://community.holistics.io/u/Bear_Stonem)\
**Post date:** [April 15, 2025, 11:11pm UTC](https://community.holistics.io/t/resolved-performance-degradation-with-chrome-version-135/2440/3 "2025-04-15T23:11:42Z")

</div>

Out of curiosity what was the core issue? I’m having similar issues on my personal project with chrome 135 that uses react and remix.

---

<div class="post-metadata">

**Author:** ![datbth](https://community.holistics.io/user_avatar/community.holistics.io/datbth/32/1414_2.png) [@datbth](https://community.holistics.io/u/datbth)\
**Post date:** [April 16, 2025, 2:06am UTC](https://community.holistics.io/t/resolved-performance-degradation-with-chrome-version-135/2440/4 "2025-04-16T02:06:29Z")

</div>

Hi,

On the surface, we saw that Chrome 135 is slower across the board when calculating any stylings. Thus, our mitigation was to remove some of the most costly stylings that we found.

---

<div class="post-metadata">

**Author:** ![datbth](https://community.holistics.io/user_avatar/community.holistics.io/datbth/32/1414_2.png) [@datbth](https://community.holistics.io/u/datbth)\
**Post date:** [April 17, 2025, 2:41am UTC](https://community.holistics.io/t/resolved-performance-degradation-with-chrome-version-135/2440/5 "2025-04-17T02:41:50Z")

</div>

We also filed this issue for Chromium: [https://issues.chromium.org/issues/409714585](https://issues.chromium.org/issues/409714585). We haven’t gotten to the bottom of it yet, but it might have some helpful information.