Editorial process

How we source information

This site does not sell web development services. It is a blog. That distinction shapes how we research: we are not trying to convince anyone to hire us, we are trying to describe accurately what a setting does, what a tool measures, and where the two disagree.

Specialist cross-referencing documentation on a laptop and printed notes at an organized home office desk
Cross-checking a CMS setting against its published documentation before writing about it

Where the information comes from

Four places we check before publishing

Official documentation

  • Browser vendor documentation for image loading behavior and format support
  • Google's published Core Web Vitals and search documentation
  • Official docs for the compression and conversion tools we mention

Direct testing

  • We run through the exact steps in a CMS admin panel before writing a walkthrough
  • Screenshots come from those test sessions, not stock interface mockups
  • We note when a setting's exact wording or location changes between versions

Measurement tools

  • Browser developer tools network and performance panels
  • Publicly available Core Web Vitals field and lab data reports
  • Before and after file size comparisons using the tools discussed in each post

Ongoing review

  • Image format support changes as browsers update, so older posts get revisited
  • CMS interfaces change their menus regularly, and walkthroughs are checked against current versions
  • Corrections are made openly rather than quietly editing a claim after the fact
Specialist adjusting a quality slider in a free image compression tool while comparing preview thumbnails
Testing a compression setting before recommending it in a tutorial

What we do not do

No development services, no paid placements

This site is a blog about image optimization concepts and free tools. It does not offer custom web development, CMS installation, or paid consulting services. When a tutorial recommends a tool, it is because we tested it and found the free tier does what the tutorial describes, not because of a partnership.

We also avoid presenting a single number as universal truth. Compression results, format savings and loading behavior all vary by image content, hosting configuration and CMS version. Where a range is more honest than a single figure, we use a range.

How often is content reviewed after publishing?

Posts covering format support and CMS settings are reviewed on a rolling basis, since browser and platform updates can change what is accurate. There is no fixed publishing calendar promised, and review timing depends on how much a given topic tends to change.

Last review of this page:

See the process in action

The screenshot walkthroughs are built the same way described here: tested first, documented after.

View the walkthroughs