Page loads significantly more JavaScript than typical
This check measures the total amount of JavaScript a page sends to the browser. This site's page loads significantly more than typical, over 1MB compressed or 3MB uncompressed. Because parsing and running JavaScript happens on a single thread in the browser, this directly delays how quickly the page responds to clicks and taps. Excess JavaScript is one of the most direct causes of a sluggish-feeling site, since the browser has to finish working through it before it can respond smoothly to visitor interaction, and it is a heavier fix than most other performance issues. Your developer should run a bundle visualiser, built into tools like Vite or Rollup, to identify the largest contributors, then apply code-splitting, tree-shaking, and a dependency audit, replacing heavyweight libraries such as Moment.js or Lodash with lighter alternatives like Day.js or native JavaScript methods. This is a substantial piece of work, realistically one to two weeks of focused effort.
Why this matters
Excess JavaScript is one of the most direct causes of a sluggish-feeling site, since the browser has to finish working through it before it can respond smoothly to visitor interaction, and it is a heavier fix than most other performance issues.
How to fix it
Your developer should run a bundle visualiser, built into tools like Vite or Rollup, to identify the largest contributors, then apply code-splitting, tree-shaking, and a dependency audit, replacing heavyweight libraries such as Moment.js or Lodash with lighter alternatives like Day.js or native JavaScript methods. This is a substantial piece of work, realistically one to two weeks of focused effort.