Intermediatenote 03 of 0803 reasons · 03 notes
HTMLIntermediate
Keep heading order meaningful
Headings should describe document structure, not only match a visual size.
Code example
Copy, adapt, and ship.
Read the numbered lines, copy the complete snippet, then adjust the values for your project.
<main> <h1>Image Optimization Guide</h1> <section> <h2>Compression Settings</h2> <h3>Quality Range</h3> </section></main>Why this matters
The production reason.
- 01
Headings are document structure, not just font sizes.
- 02
Skipping levels or using headings for visual emphasis makes pages harder to scan for users and search engines.
- 03
Choose the heading level based on the section hierarchy, then style it however the design needs.
How it holds up outside a demo.
- HTMLOne clear h1 per page is still a strong practical default.
- CMS editorsDo not choose h3 because it looks smaller; style the h2 instead.
- SEOHeadings should match search intent and page sections.
Explore other stacks
Jump into a different technology.
08 HTML notes on this shelf, and six more stacks beside it.
Use next/image for image optimization
Next.js image optimization starts with next/image sizing, lazy loading, modern formats, and predictable dimensions.
Open the noteKeep state close to the interaction
Local state avoids unnecessary parent renders and keeps component intent obvious.
Open the noteAbort stale fetch requests
Cancel outdated browser requests so fast UI changes do not render old data.
Open the noteBuild a CSS gradient generator with code export
A CSS gradient generator should preview color stops, preserve accessible contrast, and export clean CSS code.
Open the noteFix WordPress H1 SEO issues
Fix WordPress SEO issues by keeping one clear H1, escaping template output, and compressing images before WordPress upload.
Open the noteReduce LCP with image optimization
Reduce LCP with image optimization by resizing, converting, and compressing images before they reach production.
Open the note