Changelog

WebVitals.tools publishes content on a daily cadence. This page is the canonical update log, maintained alongside the site itself and updated automatically every day at 10 AM EDT. Each entry below corresponds to a named milestone from the internal progress log: a date, a short description of what shipped, and a representative deep-link so you can jump directly to the content. The log runs from Day 0 -- the initial launch on April 4, 2026 -- through the current build. Entries are grouped into three development phases that reflect how the scope of the project evolved over its first 30 days. If you want to understand the editorial standards behind these decisions, read the methodology page. To learn who maintains the site, visit About WebVitals.tools. To see all pages indexed together, use the human-readable sitemap.

The three phases below -- Foundation, Scale and Authority, and Optimization and Refinement -- were not planned up front. They emerged from the natural rhythm of the build: the first ten days established the minimum viable reference (metric guides, core fix pages, first blog content, and interactive tools); the next ten days expanded coverage across frameworks, content types, and CrUX-backed data; the final ten days focus on quality, discoverability, and the credibility infrastructure you are reading now. Each phase entry includes the publication date, a brief summary, and a link to the affected content.

Phase 1 -- Foundation (Days 1-10)

The first ten days established the core reference layer: the four Core Web Vitals metric guides, the initial fix pages targeting the most popular JavaScript frameworks, the first blog content, and the interactive tools that let developers apply the guidance to their own numbers. By the end of Day 10 the site had a complete glossary and over 40 cross-linked pages.

2026-04-04 Day 0 -- Launch

Site launched with five pages: homepage, LCP guide, LCP-Next.js fix, blog index, and the first blog post. The initial deployment established the static HTML architecture, design system, and URL structure that every subsequent page inherits. View homepage

2026-04-05 Day 1 -- Metric Guides

CLS, INP, and TTFB metric guides shipped, completing the full set of Core Web Vitals reference pages. Each guide covers measurement, thresholds, common causes, and framework-specific fixes with structured FAQ sections. CLS Guide

2026-04-06 Day 2 -- React Ecosystem Fixes

Six React-ecosystem fix pages shipped: cls-nextjs, inp-nextjs, lcp-react, cls-react, inp-react, and ttfb-nextjs. Each page pairs a concise diagnosis with code-level fixes specific to the framework and metric combination. LCP in React

2026-04-07 Day 3 -- Vue and Angular Fixes

Eight fix pages for Vue and Angular shipped, covering LCP, CLS, INP, and TTFB in both frameworks. This extended the fix library to every major JavaScript framework in active use. LCP in Vue

2026-04-08 Day 4 -- CMS and No-Code Fixes

CMS and no-code fix pages for WordPress, Shopify, Webflow, and Squarespace launched alongside the Fixes index page. The index brings all fix pages together under a single browsable surface organized by metric and platform. Fixes index

2026-04-09 Day 5 -- Comparison Blog Posts

Three comparison blog posts published: Next.js vs Remix performance, React vs Vue performance, and WordPress vs Shopify Core Web Vitals. Each post draws on lab data and public CrUX evidence rather than anecdote. Next.js vs Remix

2026-04-10 Day 6 -- Interactive Tools

Two interactive tools launched: the Performance Budget Calculator and the Core Web Vitals Score Explainer. Both run entirely client-side and help developers translate raw metric values into actionable targets without leaving the browser. Tools

2026-04-11 Day 7 -- Internal Linking Audit

A full internal linking audit added over 150 new cross-links across all existing pages, strengthening the topical graph that connects metric guides, fix pages, and blog content. Contextual link placements were prioritized over footer dumps. LCP Guide

2026-04-12 Day 8 -- CrUX Data Analysis

An original data analysis blog post published using the April 2026 CrUX snapshot queried via BigQuery. The post presents p75 pass rates across LCP, CLS, and INP segmented by device type and framework, establishing the site's data-journalism credibility. CrUX analysis post

2026-04-13 Day 9 -- Emerging Framework Fixes

Fix pages for Astro, SvelteKit, Remix, and Nuxt shipped, covering the emerging and rapidly growing segment of the JavaScript framework ecosystem. These pages address performance patterns unique to each framework's rendering model. LCP in Astro

2026-04-14 Day 10 -- Glossary

A 46-term glossary launched with DefinedTermSet structured data, providing a shared vocabulary for all site content. Terms range from foundational concepts like LCP and INP to advanced ideas like layout shift attribution and Time to First Byte waterfall segmentation. Glossary

Phase 2 -- Scale & Authority (Days 11-20)

The second phase pushed into content types that establish topical depth and editorial authority: how-to tutorials, case studies, a comprehensive FAQ hub, hosting and infrastructure fix pages, and the video tutorial series. A sitewide content refresh in Day 14 touched 45 pages and added 49 new cross-links. By the end of Phase 2 the site had been submitted to Search Console and wired to the Indexing API for real-time crawl requests.

2026-04-15 Day 11 -- How-To Tutorial Posts

How-to tutorial blog posts published, expanding the blog beyond comparison and analysis content into step-by-step walkthroughs. These posts address specific developer workflows such as auditing a page cold and reading a Lighthouse report for the first time. Blog

2026-04-16 Day 12 -- Issue-Specific Fix Pages

Cross-framework issue-specific fix pages shipped, targeting common performance failure modes that appear regardless of which framework a team uses -- for example, unoptimized hero images and render-blocking third-party scripts. Fixes

2026-04-17 Day 13 -- Resource Pages

Two resource pages launched: a curated performance tools directory and an actionable performance checklist. Both pages aggregate external and internal references in a format developers can bookmark and return to during a performance sprint. Performance tools

2026-04-18 Day 14 -- Sitewide Content Refresh

A sitewide content refresh touched 45 pages: 49 new cross-links added, 39 new FAQ entries written, and meta descriptions tuned for accuracy. This pass also aligned structured data across all pages with the publisher Organization node. Homepage

2026-04-19 Day 15 -- Case Study Blog Posts

Case study blog posts published, including a detailed account of how a production site reduced its LCP by 60 percent over two weeks. Case studies translate abstract performance guidance into concrete engineering decisions, timelines, and measured results. LCP case study

2026-04-20 Day 16 -- Hosting and Infrastructure Fixes

Hosting and infrastructure fix pages launched for Vercel, Netlify, Cloudflare, AWS, and others. These pages address TTFB and LCP issues that originate at the deployment layer rather than the application layer, filling a gap in the fix library. TTFB on Vercel

2026-04-21 Day 17 -- Video Tutorials

Four video tutorial walkthroughs launched alongside the tutorials index: Lighthouse Audit Walkthrough, Chrome DevTools Performance Panel, WebPageTest Complete Guide, and Real User Monitoring Setup. Each tutorial page pairs written steps with a video recording. Tutorials

2026-04-22 Day 18 -- FAQ Hub

A comprehensive FAQ hub launched at /faq/, consolidating the most common questions from across all metric guides, fix pages, and blog posts into a single searchable index. Questions are organized by topic and linked back to the authoritative source page. FAQ hub

2026-04-23 Day 19 -- Fix Pages Batch 6

A further batch of programmatic fix pages shipped for additional frameworks and platform combinations, extending coverage to less common but actively used stacks. These pages follow the same structured template as earlier fix pages for consistency. Fixes

2026-04-24 Day 20 -- Search Console and Indexing API

Search Console ownership verified and the Google Indexing API wired to automatically submit newly published pages for crawling. This ensures that content published each morning reaches Google's index the same day rather than waiting for the passive crawl schedule. Homepage

Phase 3 -- Optimization & Refinement (Days 21-30, in progress)

Phase 3 focuses on quality signals and long-term credibility: a content audit, meta description rewrites, sitemap enhancements, best-practices guides, a second comparison batch, more fix pages, a second sitewide content refresh, and the set of credibility pages you are reading now. These changes do not add net new topics so much as strengthen the existing content graph and make the site easier to trust and navigate.

2026-04-25 Day 21 -- Content Audit and Meta Description Rewrites

A full content audit ran across all published pages: meta descriptions rewritten to accurate 155-160 character targets, residual emoji removed, and duplicate phrasing consolidated. This pass improved click-through clarity without altering the substantive content of any page. Homepage

2026-04-26 Day 22 -- Sitemap Enhancement

The XML sitemap was enhanced with accurate priority and changefreq values, and a human-readable /sitemap/ index page launched so that both crawlers and readers have a single place to see all published pages at a glance. Sitemap

2026-04-27 Day 23 -- Best-Practices Guides

Four best-practices guides launched: image optimization, JavaScript performance, CSS performance, and font loading. These guides sit above the metric-specific fix pages in the content hierarchy, providing principle-level guidance that applies across all frameworks and platforms. Image optimization guide

2026-04-28 Day 24 -- Comparison Pages Batch 2

A second batch of comparison pages shipped, including a CDN comparison for 2026 and a Static vs SSR performance analysis. These pages complement the Phase 1 framework comparisons with infrastructure-level data relevant to teams choosing or evaluating their deployment stack. CDN comparison 2026

2026-04-29 Day 25 -- Fix Pages Batch 8

Eight fix pages in the final programmatic batch shipped, completing the intended framework coverage matrix. This concludes the systematic approach to fix-page generation and shifts future fix work to a demand-driven model based on reader requests. Fixes

2026-04-30 Day 26 -- Content Refresh Day 2

A second sitewide content refresh bumped dateModified values across the metric guides and added cross-link cards within the LCP, CLS, INP, and TTFB guide bodies, making the connections between related content visible inline rather than only in the footer or sidebar. LCP Guide

2026-05-01 Day 27 -- About and Credibility Pages

Four credibility pages launched: About, Methodology, Changelog (this page), and Contribute. Together these pages document who builds the site, how it tests, what has shipped, and how the community can participate. This completes the credibility infrastructure required for long-term editorial trust.

What's next

Days 28 through 30 will complete the Phase 3 roadmap. Planned work includes additional best-practices content, a second pass on the FAQ hub incorporating reader questions gathered from GitHub issues, and further structured data improvements to ensure all pages satisfy Google's rich result requirements. The changelog will be updated each morning alongside the daily publish.

If you want to understand the principles behind these publishing decisions -- how pages are tested, what sources we cite, how we handle metric thresholds that change over time -- read the methodology page. If you want to learn about the people and organization behind the site, visit About WebVitals.tools. If you want to help shape what ships next, the contribute page explains how to propose new pages, report errors, or submit pull requests against the open-source repository.

This changelog is the single source of truth for site history. If you notice an entry that is inaccurate or a milestone that is missing, open an issue on GitHub or refer to the contribution guidelines. Every correction is welcome.