Web Performance Fundamentals, v2 vs Complete Intro to Containers (feat. Docker)

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.

The course stands apart from typical Docker tutorials by opening with a module called "Crafting Containers by Hand," where students manually implement chroot, Linux namespaces, and cgroups before Docker is introduced. This first-principles approach is the most-cited reason learners say the course made containers finally click, rather than just memorising Dockerfile syntax. The curriculum then progresses through Docker images, Dockerfiles, Node.js containerisation, layer caching strategies, Alpine Linux for smaller images, multi-stage builds, distroless containers, static asset optimisation, bind mounts, volumes, dev containers, Docker networking, Docker Compose, and a practical introduction to Kubernetes and Kompose. The open-source companion notes at btholt.github.io/complete-intro-to-containers are freely available under a Creative Commons licence, which allows learners to revisit content without re-watching videos. The course does cover the original version's content well; a v2 update on Frontend Masters addresses cgroups v2 changes and dependency freshness, so learners should verify which version they are accessing. Minor critiques include the relative brevity of the Kubernetes module, which is treated as a brief orientation rather than a deep dive, and the Node.js-heavy examples, which assume JavaScript familiarity even though the container concepts themselves are language-agnostic.

Brian Holt brings over a decade of engineering and product management experience across Netflix, LinkedIn, Reddit, Microsoft (VS Code team), Stripe, Snowflake/Streamlit, and Databricks, giving him genuine production-grade context for every concept he teaches. On Frontend Masters, he has authored more than a dozen "Complete Intro" courses, making him one of the platform's highest-volume and most-reviewed instructors. Learner feedback consistently uses the same descriptors across multiple courses and years: "excellent," "clear," "fun," "great teacher." His containers course specifically is praised for making systems-level Linux concepts approachable to web developers who have never opened a man page. Holt openly acknowledges when a topic is dense — he describes the course as "pretty dense with a lot of systems-level stuff thrown at you in a short time" — but frames each piece incrementally so the cognitive load stays manageable. His tendency to explain the why behind each tool (why cgroups exist, why Alpine saves hundreds of megabytes, why distroless containers matter in CI/CD pipelines) is cited by multiple reviewers as what separates this from documentation-style instruction. The only consistent criticism is that his pace can feel quick for learners coming from a pure frontend background with no prior Linux exposure, and those learners are advised to take his Complete Intro to Linux and the Command-Line first.

Access to the course requires a Frontend Masters subscription, priced at $39 per month or $390 per year (effectively $32.50 per month). The subscription model is the most common source of neutral and negative sentiment across the 38 opinions analysed, as it compares unfavourably to a one-time Udemy purchase for learners who only want a single course. The value calculation improves significantly if the learner is already subscribed for other Frontend Masters content or plans to take additional courses in the same month. Within that framing, reviewers consistently describe the subscription as worthwhile given the breadth and depth of the catalog. The course notes for Complete Intro to Containers are freely published on GitHub and btholt.github.io under a Creative Commons licence, which Holt explicitly designed so that financial barriers do not block access to the curriculum. Learners on a tight budget can follow the full written curriculum for free, losing only the video walkthroughs. Several blog posts note that this free-access policy, combined with the open-source code examples, makes the course more transparent than most paid offerings at a similar price point.

Rather than a single end-to-end application, the course uses a progression of hands-on exercises that directly reinforce each module. Students begin by creating a containerised environment entirely from Linux primitives — chroot, unshare, cgroups — using command-line tools directly in the terminal. Subsequent exercises containerise a real Node.js application, iterating through progressively optimised Dockerfiles: first a basic image, then one with explicit layer ordering for faster rebuilds, then an Alpine-based version that is roughly 80% smaller than the Debian default, then a multi-stage build, then a distroless variant. The Docker Compose module adds a MongoDB service alongside the Node app, creating a practical multi-container scenario that mirrors real development setups. Pre-built Docker images are provided so that slow internet connections do not block workshop progress. Reviewers note the exercises feel production-relevant rather than toy examples, and the GitHub repository (945 stars, 181 forks) demonstrates ongoing community use. The Kubernetes exercises are more abbreviated — primarily using Kompose to convert a Compose file — and learners who want deep Kubernetes practice will need a dedicated course afterwards.

Container knowledge has become a baseline expectation for full-stack and backend developers at most organisations that deploy to the cloud, and this course maps directly to the most common production patterns: writing Dockerfiles for Node.js services, reducing image sizes for faster CI/CD pipelines, using multi-stage builds to separate build and runtime environments, structuring multi-service applications with Docker Compose, and understanding how Kubernetes orchestrates containers at scale. The dev containers module is particularly relevant to modern team workflows, covering how to use containers to create reproducible development environments that eliminate "works on my machine" problems. Holt draws on his experience across Netflix, Reddit, and cloud infrastructure roles at Stripe and Databricks to ground each concept in how it is actually used in production. Multiple blog post reviewers describe going directly from the course to containerising services at work. The Kubernetes coverage is acknowledged as introductory rather than comprehensive, and learners moving into DevOps or platform engineering roles will need further study. For web developers adding Docker competency to an existing JavaScript skill set, however, this is the most practically oriented course in the Frontend Masters catalog.