Go & Vanilla JS: Fullstack Without Frameworks vs Web Performance Fundamentals, v2
Same Bayesian formula, same rubric — so the difference in scores reflects the difference in the courses, not the difference in how we evaluated them.
Frontend Masters · Web Development
Go & Vanilla JS: Fullstack Without Frameworks
Frontend Masters · Web Development
Web Performance Fundamentals, v2
Per-criterion
Ten hours eleven minutes covering the full stack end-to-end: Go project setup and architecture, a JSON REST API with structured handlers, Postgres integration via a repository interface pattern, Vanilla JS web components, a client-side SPA router built from scratch, View Transitions API, search/filter/sort, and a complete JWT authentication flow covering registration, login, server-side middleware, and client-side route guards. Published May 27, 2025 — compatible with Go 1.22+ and modern browser APIs. The course deliberately avoids backend frameworks (no Gin, Echo, or Fiber), relying on Go's standard library, keeping outcomes transferable to any Go project.
Maximiliano Firtman is a prolific Frontend Masters instructor with prior courses on Mobile Web Development, Progressive Web Apps, and JavaScript Performance. The course holds a 4.9/5 star platform rating — among the highest for full-stack courses on Frontend Masters. Students consistently cite his habit of explaining architectural decisions and trade-offs rather than simply typing out code, and his willingness to debug real issues live during recording rather than presenting pre-cleaned output. Reviewers describe him as a "true master" whose teaching style emphasises the reasoning behind every decision.
Access requires a Frontend Masters subscription (~$39/month or ~$390/year for individuals) rather than a one-time purchase. Strong value for learners using the broader catalog — Frontend Masters covers JavaScript, TypeScript, React, CSS, Node.js, and dozens of related tracks under one subscription. Weaker for those taking only this course. No free tier beyond a short preview. The subscription cost is the dominant frustration across otherwise positive reviews, consistent with complaints across the entire Frontend Masters catalog.
The course builds a complete movie catalogue application end-to-end: a Go REST API with structured JSON handlers, a Postgres layer using a repository interface pattern, AIR-powered live-reload during development, full JWT authentication (registration, login, server-side middleware, golang-jwt token generation), and a Vanilla JS SPA with a hand-rolled client-side router, View Transitions, web components for every UI element, a search/filter/sort feature, and authenticated user pages (My Account, Favorites, Watchlist). Full authentication including client-side route guards distinguishes this course from most full-stack offerings that leave auth as an exercise or third-party library call.
The deliberate no-framework approach teaches patterns that transfer to any technology choice: the router is built from scratch, web components replace UI libraries, state management uses the Proxy pattern. Students report that this improves their ability to evaluate frameworks critically, because they understand what each framework is solving. Go's standard library — net/http, database/sql, log/slog — maps directly to production Go codebases. The Postgres repository pattern, AIR for live-reload, and Postman-tested API routes represent practices encountered in real engineering teams.
The course covers the full stack of modern web performance knowledge in approximately six hours — a tight, well-curated curriculum that avoids the padding common in longer Udemy-style recordings. It opens with the psychology of perceived performance (drawing on David Maister's "Psychology of Waiting Lines"), then moves through Core Web Vitals metrics (LCP, CLS, and INP, which replaced FID as an official Google signal in March 2024), measurement APIs, synthetic testing with Lighthouse and WebPageTest, Real User Monitoring with CrUX, and finally concrete optimization tactics for each metric — TTFB, FCP, LCP, layout shift prevention, and interaction latency. The October 2024 update brought the curriculum fully current with the INP transition, so learners are not working with obsolete tooling or metrics. What sets the content apart from generic performance tutorials is its insistence on real user data before optimization. The recurring lesson — "focus on your worst metric, fix the most basic thing first, and confirm with RUM" — is a workflow, not just a collection of tips. The course also links performance work directly to business outcomes: conversion rate, SEO rankings, and user retention statistics are woven into the justification throughout, which gives engineers the language they need to advocate for performance work with non-technical stakeholders. The GitHub workshop repository (113 stars, 87 forks as of mid-2026) demonstrates the exercises have genuine uptake in the developer community.
Todd Gardner is one of the most credentialed practitioners teaching web performance in any format. As co-founder of TrackJS and Request Metrics, he has spent years building commercial RUM tools and working directly with thousands of development teams on performance problems — a background that produces very different teaching than a course built purely from documentation. His Frontend Masters blog articles (published November 2024 on INP and February 2025 on image optimization) extend the same practical, measurement-first methodology into the broader developer community. Student feedback collected from the official course page is unusually consistent in citing his teaching clarity as a differentiator. Anurag Bhandari wrote "Wonderfully planned and executed. Such a heavy topic explained in such simple terms." Pedro Antônio Pereira called it "a masterclass in how to understand web performance." Ryan Davidson, recommending it broadly, wrote: "Great blend of breadth and depth in the performance space. All web engineers — backend or frontend, junior or senior — should be taking this course!" The breadth of that recommendation — extending to backend engineers — reflects how Gardner anchors the course in concepts (HTTP caching, server response times, rendering pipelines) that apply regardless of whether you write CSS or database queries.
The course is included in a Frontend Masters subscription, priced at approximately $39/month or $390/year (annual plans have carried a 17-20% discount in 2025-2026). A seven-day free trial is available. For a subscriber who accesses even two or three courses, the per-course cost is minimal, and the Web Performance Fundamentals course is among the most immediately actionable in the entire library — the techniques taught apply to any existing project without needing to rebuild or refactor an architecture. Deeptiman Mallick's testimonial captures the evergreen value: "This course is like a bookmark to come back to when we're working on performance." Unlike courses that you complete once and set aside, the performance metrics and tools taught here — Lighthouse, WebPageTest, CrUX — are ones practitioners return to on every new project or optimization sprint. The value proposition is strongest for working developers with a real codebase to optimize; the course is less compelling as a purely theoretical exercise for learners with no project to apply it to. There is no standalone purchase option, so non-subscribers must commit to at least one month of the full subscription.
The hands-on component uses a real Node.js + Express e-commerce project — "Developer Stickers Online" — which is deployed to multiple regions and available on a global CDN with HTTP/3 support, making it possible to test real network conditions rather than synthetic localhost scenarios. Students work with actual Lighthouse scores, WebPageTest waterfalls, and CrUX field data rather than simulated metrics, which bridges the gap between tutorial and professional practice. The workshop's focus on a single, realistic project (rather than a series of disconnected toy exercises) is appropriate for the subject: web performance work lives in real measurement data, and the course correctly models that. The project repository's 87 forks suggest learners actively run the exercises rather than just watching. The main limitation is scope: the project is a static storefront, so learners working primarily on Single Page Applications, server-rendered frameworks like Next.js, or complex state-heavy UIs will need to extrapolate some of the tactics. There is no separate project tier with more complex application types.
Web performance is one of the highest-ROI skills a working web developer can acquire in 2024-2026: Core Web Vitals are a confirmed Google Search ranking signal, and the business case studies cited throughout the course (eCommerce and SaaS conversion improvements correlated with performance gains) are drawn from real production data. Gardner's background running RUM tools for thousands of teams means the tactics are not academic — they are the same ones practitioners reach for when a client's LCP score drops. Multiple student reviews specifically noted immediate applicability: Álex Castelo wrote that the course made them realize "how easy it can be to boost a website's performance exponentially," and Yuganshu Mohan distilled the practical lesson as "focus on the worst metric and perform the most basic fixes." The methodological frame — measure with real user data first, then fix, then confirm — transfers directly to professional performance audits. Taran Bains, writing an extended reference post from the course material in August 2025, used it as the foundation for a comprehensive web performance guide, which is a reliable signal that the content holds up as a reference long after the initial watch-through.
Scoring methodology applies identically to every course on the site — see the formula.