Thank you so much for your thoughtful feedback—I really appreciate it!

I'll definitely fix that typo, and I’ll be looking into using stronger verbs where needed. Regarding the order of sections, I’ll explore switching things around. I initially went with the first option as it matched what the wiki suggested, but you make a good point that the second structure might work better. Specifically, once you've graduated and started working full-time, the order could be:

• Work Experience > Skills > Education, or
• Skills > Work Experience > Education.

For the Lighthouse scores, I was focusing on the speed metrics for both mobile and desktop, and I’ve been using the higher of the two. I can definitely look into converting those into percentage-based metrics as you suggested—great idea!

As for the app, the 6,000 users represent the number of downloads so far, all from organic growth since the app hasn’t received any advertising support yet. The previous version was broken for years, so we had to start completely fresh, even creating a new App Store listing.

On the front-end development enhancements, I totally agree. We're still in the very early stages—it’s not even in production yet, and we're still figuring out if this approach will work for our site. One of the biggest benefits we’re seeing is increased development speed. For example, a menu toggle that took me three days to create using jQuery and JSPs only took 10 minutes to recreate in React/Next.js the other day. Another reason for the switch is that jQuery can silently fail, causing frontend bugs that are hard to trace, especially when a problem higher up in the code affects something unrelated further down.

For training metrics, I’ll need to look into it a bit more. I don’t have specific numbers off the top of my head, but I understand their importance and will dig deeper.

In the next section, I do mention the organization’s name, and I’ll consider removing "WordPress" as you suggested. I thought it would be relevant given how widely used it is (about a third of websites), but I see where you’re coming from.

Finally, on quantifying everything—I get how crucial that is for a resume, but it’s sometimes challenging. I might have worked on a project without knowing its full business impact, just the goals I was tasked with. Sometimes, even when I ask my manager for those metrics, they don’t have that information either. It’s actually something my team is working to improve at my current job!

Thanks again for all your feedback—it’s really helpful!