Lighthouse · Core Web Vitals · Technical SEO · Accessibility
Starting point
Unstructured optimization
→
What I deliver
Audit → prioritize → validate
→
What this enables
Evidence-based quality
Responsible for the work described
Anny Gabrielly
Where to access
On GitHub · View code link
Project stage
20 GitHub stars
Original result capture · skill repository
The problem
A visually appealing delivery can still load slowly, shift content or be hard to navigate. Isolated changes without a baseline and validation make it difficult to understand what improved.
What I built
I created a reusable skill to guide website audits, identify bottlenecks, prioritize changes and validate again. It brings images, fonts, CSS, JavaScript, metadata, semantics and accessibility into the development process.
Decisions behind the solution
Measure before optimizing
Record the stack, build and available metrics so changes can be compared with the initial state.
Prioritize what people experience
Main-content loading, visual stability, responsiveness and keyboard access guide priorities.
Validate the whole delivery
Validate the build, images, links, metadata and accessibility to avoid trading functionality for a score.
Reuse knowledge
A checklist and references make quality more consistent across projects and reduce the need to rebuild the process.
Three preserved captures below with all four categories.
Recorded results
Score order: Performance · Accessibility · Best Practices · SEO. Desktop measurements according to repository documentation.
98 / 100 / 100 / 100Open full capture100 / 100 / 100 / 100Open full capture100 / 94 / 100 / 100Open full capture
Results in context
These are recorded results from specific projects, not a universal promise. The captures do not provide a comparable baseline or enough identification to assign the scores to the three clients in this portfolio. Device, network, hosting and third parties affect measurements.
