How I had problems optimizing my site with Lighthouse
I had never seen such a rigid framework before
These days producing and improving my portfolio while looking for ideas to style, I decided to insert Quality Assurance (QA) technologies.
To improve the situation, I reached a point where I was using Jeqt, Vitest, Lighthouse, Playwright, Eslint, Jscpd and Lizard
Producing E2E tests, inserting even Storybook, these totally over-engineered decisions broke my code multiple times, to reach the 100% on Lighthouse.
Even with several scripts to facilitate automation, I still had the courage to challenge myself
However, currently I have found difficulties to reach 100% again in the results
Reasons I am using Lighthouse: it forces you to optimize your site well, the metrics make sense, however combined with Next.js, a Slop-Generated framework, it turns into chaos
Analyze my suffering
I ended up with an absurd tick to reach 100 in all scores, but I always had something to improve, as any developer would do, I researched and analyzed that my agent and tests were ignoring the Next.js cache, who would have thought..
I had to change the layout, pages, images, coverages, typewriter and so on, another day existing thanks to the
