web.dev

What you will find there

web.dev is part publication, part course library. The articles cover performance, accessibility, security, identity and new platform features. Alongside them sit complete free courses you can work through in order:

• Learn HTML, Learn CSS and Learn JavaScript, which build the fundamentals with a modern, standards-first view.
• Learn Performance, which explains how the browser loads and renders a page and what actually slows it down.
• Learn Accessibility, a practical grounding in making interfaces usable by everyone.
• Learn AI, a newer course on using AI features on the web.

It also tracks Baseline, the label that tells you whether a web feature works across all major browsers, with regular digests of what has become broadly available.

Why performance advice from here carries weight

The Core Web Vitals, including Largest Contentful Paint, Cumulative Layout Shift and Interaction to Next Paint (which replaced First Input Delay), are documented here by the team that defines them. That matters because they affect real outcomes, including how Google Search evaluates pages. Articles on web.dev explain how each metric is measured in the field, what moves it and which popular optimisations make little difference. Tutorials elsewhere often repeat advice written for older versions of the metrics, so check them against the source.

The part people skip

Learn Accessibility. Many teams treat accessibility as optional polish, yet it is increasingly a legal requirement and it affects a large share of users. The course is short, free and practical: semantic structure, focus, keyboard use, colour contrast and testing. Working through it removes a lot of guesswork from everyday UI work.

How to use it well

• If CSS layout still feels like trial and error, do Learn CSS end to end before anything else.
• If a site feels slow, start with the Learn Performance course, then measure your own pages and read the article for whichever metric is failing.
• Use Baseline status to decide whether a feature is safe to ship without a fallback.
• Pair it with MDN for exact reference details; web.dev explains why and when, MDN documents how.

The site reflects the Chrome team's perspective. Its guidance is standards-based, but cross-check browser support rather than assuming Chrome behaviour is universal.

Common questions

Is everything free? Yes. The articles and all the Learn courses are free and need no account.

Is it suitable for complete beginners? Learn HTML and Learn CSS are approachable if you have written a little HTML before. For a first ever introduction to the web, MDN's learning area or freeCodeCamp is gentler, and web.dev is an excellent second step.

How long do the courses take? They are self-paced, split into short modules, and none of them states a fixed duration. Working through Learn CSS properly, with practice, is a few weeks of evenings.

Does it only apply to Chrome? No. The guidance is standards-based and Baseline status is about all major browsers, but it is written from the Chrome team's point of view, so check support tables for anything new.

What you will be able to do afterwards

Read a Lighthouse or field-data report and know which metric is failing and why, fix the common causes (unoptimised images, layout shifts from late-loading content, long JavaScript tasks), write CSS layouts on purpose rather than by trial and error, and build interfaces that work with a keyboard and a screen reader. Those are skills interviewers and team leads notice quickly.

Best for: front end developers responsible for performance or accessibility, which is most of them.