Today I discovered something I honestly should have explored a long time ago: Google Lighthouse.
Funny enough, revamping my portfolio is one of those projects I kept pushing forward with the classic “I’ll do it tomorrow” mindset — and somehow tomorrow kept winning. But today I finally sat down and started improving it, and during that process, I came across Lighthouse.
For anyone who hasn’t heard of it yet, Google Lighthouse is an open-source automated tool designed to help developers improve the quality of web pages. You can run it on almost any page — whether it’s public or behind authentication.
What immediately caught my attention is that it audits things like:
Performance
Accessibility
SEO
Best Practices
And probably a few more things I’m still discovering
You can run Lighthouse directly inside Chrome DevTools, through the command line, or even as a Node.js module.
The process is simple:
You give Lighthouse a URL, it scans the page, runs a series of audits, and then generates a detailed report showing how your website performs.
What makes it powerful is that it doesn’t just tell you what’s wrong it also explains:
_

• Why the issue matters
• How it affects users
• And how you can fix it _ As a beginner software engineer and developer, I’m slowly realizing that writing code is only one part of building great applications. Performance, accessibility, maintainability, and user experience matter just as much. And honestly, tools like Lighthouse make the learning process feel less overwhelming because they point you in the right direction. One thing I’ll say though don’t fall into the trap of chasing a perfect Lighthouse score instead of building useful projects. A lot of developers start optimizing numbers before validating whether the product itself solves a real problem. Lighthouse is a guide, not the final goal. For my portfolio specifically, Lighthouse exposed a few weaknesses immediately:
• Large unoptimized images
• Accessibility issues
• Slow-loading assets
• Missing metadata Things I probably would have ignored before. Small discoveries like this make development more exciting for me because every new tool feels like learning how to sharpen my sword a little better.

Until next time, fellow coffee addicts.

Maybe next time I’ll uncover another trick to become a better developer.

Adios ☕