Technote
Cutting image weight without giving up visual quality — formats, sizing, responsive images and lazy loading, matched to how WordPress actually behaves.
8 articles
Performance optimization Intro
Photographs and flat graphics compress on completely different principles. Choose accordingly and the file shrinks while the picture on screen does not change.
Performance optimization Intro
Upload a camera original and the page still looks fine, which is why the problem surfaces late. Knowing what WordPress does behind the scenes gives you a rule.
Performance optimization Practical
One upload produces several files. Any of them never used on screen clutters both your disk and your srcset at the same time.
Performance optimization Practical
srcset gives the browser candidates; sizes tells it which one to pick. Get one right and the other still ruins the outcome.
Performance optimization Practical
Lazy loading is right for nearly every image. Apply it to the large image in the first screen and you delay the very thing the metric measures.
Performance optimization Practical
Icons and diagrams need not be image files. Kept as vectors they need no size variants, and their colour can be driven from CSS.
Performance optimization Practical
The player loads whether or not anyone presses play. A poster-first approach charges that cost only to the people who actually click.
Development workflow Advanced
The hard part is not deleting but proving nothing uses a file. Once you know where references hide, a safe order appears.