A page can be visually polished and still feel slow when its resources compete for attention or its scripts delay interaction. Learn Performance, Google’s public course on web.dev, helps you understand those costs. It introduces the loading and execution decisions behind a faster, more responsive website so that optimisation becomes an informed process.
The course starts with performance fundamentals and progresses through resources, media and JavaScript. You can use it to review a site you maintain or to make better decisions while building a new one. It is a written, self-paced course with demonstrations where practical, rather than a promise of a particular speed score.
Course at a glance
| Provider | |
|---|---|
| Platform | web.dev |
| Level | Intermediate |
| Language | English |
| Format | Self-paced written course covering web performance fundamentals |
| Starting point | For newcomers to performance; basic HTML, CSS and JavaScript help with implementation |
| Access | Free public lessons and independent local browser practice |
| Recognition | Learn Performance developer-profile badge offered after completion confirmation |
| Accounts | No account needed to read; free standard developer profile for the badge |
What you’ll learn
- Connect speed to user experience: consider both how a page appears and how it responds to input.
- Understand the initial load: examine HTML delivery and the critical rendering path, including blocking resources.
- Prioritise useful resources: investigate loading strategies and resource hints rather than treating every request equally.
- Reduce media overhead: explore image sizing and delivery, video loading and web-font considerations.
- Defer work appropriately: learn about JavaScript code splitting and delayed loading of suitable images and embedded content.
- Explore advanced loading and execution: examine prefetching, prerendering, service-worker precaching and web workers.
Skills you’ll gain
- Resource loading
- Critical rendering path
- Image optimisation
- Font performance
- JavaScript loading strategies
- Web worker fundamentals
Follow the journey from HTML to interaction
The opening technical material places HTML delivery in context. Before someone sees the page, the browser needs its document and the resources required to render it. Understanding which requests and operations hold up that process helps you identify where a change belongs.
The course then examines the files a page uses. A photograph, stylesheet, font and script have different jobs and different costs. The image lesson, for example, addresses dimensions, responsive sources, formats and compression. It helps you think about the asset someone needs on their device instead of automatically delivering the largest available file.
Later lessons introduce choices about when work happens. Some JavaScript can be loaded when needed, and some computational work can move away from the main thread through a web worker. These are techniques to understand and evaluate, not universal switches that automatically make every application faster.
Who will find the material useful?
The provider introduces the course for people who are new to web performance. The Intermediate site level reflects the practical benefit of already recognising HTML, CSS and JavaScript. You do not need prior performance-specialist experience, but basic development knowledge makes the implementation details easier to follow.
Frontend developers can connect the lessons to resources they control. Designers and site owners can use the conceptual material to ask better questions about image size, fonts and loading decisions. Some delivery topics concern a server or hosting environment; reading those lessons does not require buying or changing hosting.
Compare one change at a time
For optional independent practice, create a small local page with an image, a stylesheet and a short script. Use your browser’s built-in developer tools to inspect the resources and observe how the page behaves. Save a baseline before changing anything.
Try an appropriately sized image or adjust when a nonessential resource loads. Repeat your observations under similar conditions and note what changed. Explain both the benefit and any tradeoff, such as reduced image quality. This is a personal exercise rather than a provider assessment or proof of production performance.
Local practice is enough to investigate many browser-side concepts. Features that depend on a server, service worker or particular application setup need the appropriate environment; do not assume that every example works directly from a file opened on your computer.
Free learning without a paid testing stack
The lessons are publicly readable, and a browser with its built-in developer tools plus a text editor provides a free independent practice route. You do not need a paid monitoring service, subscription, card or trial to study the material. No fixed total course duration was verified.
The completion-confirmation page offers a Learn Performance badge. Google’s standard developer profile is available at no cost. This is profile recognition, not a formal qualification, guaranteed audit result or promise that a website will meet a particular business target.
Frequently asked questions
Do I need performance experience before starting?
No. The course begins with performance fundamentals. Familiarity with basic web development helps when applying the technical examples.
Do I have to purchase hosting or monitoring tools?
No purchase is required for the advertised public lessons and local browser practice. Server-specific topics can be studied conceptually until you have a suitable environment.
Will completing the course guarantee a perfect speed score?
No. Results depend on the website, devices, connections and implementation choices. The course teaches concepts and techniques that help you evaluate those decisions.
Questions & discussion
Share a useful question or correction. Comments appear after moderation. Please avoid personal or sensitive information.