Best image formats for websites in 2026: A complete guide

[aishwaripahwa12]

Latest SEO blog

[appwrite]

Appwrite Website

Project ID: 69d7efb00023389e8d27

Sites (1)

Site	Status	Logs	Preview	QR
website 69d7f2670014e24571ca	Ready	View Logs	Preview URL

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

Sites (1)

Site	Status	Logs	Preview	QR
website 68496a17000f03d62013	Queued	View Logs	Preview URL

---

Tip

Silent mode disables those chatty PR comments if you prefer peace and quiet

[greptile-apps]

Greptile Summary

This PR adds a new SEO blog post, "Best image formats for websites in 2026," along with its cover image and a corresponding .optimize-cache.json entry. The post is currently marked unlisted: true.

• The Markdoc file introduces a complete guide covering AVIF, WebP, JPEG, PNG, SVG, and GIF — including a comparison table, decision guide, <picture> fallback code example, and an Appwrite Storage CTA.
• The <picture> HTML code block and surrounding formatting issues flagged in the previous review appear to have been corrected.
• A duplicate explanatory paragraph appears back-to-back after the code example (the same "the browser uses the first format it understands" content is written twice with only minor wording variation).

Confidence Score: 4/5

Safe to publish once the duplicated paragraph is removed; no structural or rendering breakage otherwise.

The post has one real content defect: the explanatory paragraph immediately after the code block is written twice, back-to-back, with only minor wording differences. Leaving both in the published article looks unpolished and sends a duplicate-content signal to search crawlers — the opposite of the SEO goal this post is meant to serve. Everything else — the code block, table, FAQ, and frontmatter — looks correct.

src/routes/blog/post/best-image-formats-for-websites-in-2026-a-complete-guide/+page.markdoc — remove one of the two duplicate paragraphs after the code example before publishing.

Important Files Changed

Filename	Overview
src/routes/blog/post/best-image-formats-for-websites-in-2026-a-complete-guide/+page.markdoc	New SEO blog post on image formats; the HTML code block and formatting issues from the previous review appear resolved, but an identical explanatory paragraph appears twice back-to-back after the code example.
.optimize-cache.json	Adds cache entry for the new blog post cover image; extension mismatch (cache references .png, committed file is .avif) is intentional per project convention.

_{Reviews (5): Last reviewed commit: "Update +page.markdoc" | Re-trigger Greptile}