Custom Website Development When the Web Changes
When the web changes, a site from our custom website development work can be updated as one coordinated change, with your OK, because it was written for one business and carries only what that business needs. We do not put a deadline on that work, and we do not promise a better score, a higher ranking, or more leads. In March 2024, web.dev reported that Interaction to Next Paint is a stable Core Web Vital, replacing First Input Delay. [1] This article explains what that change watches, how we apply a shift like it on a site we built, and when WordPress or a template builder is still the better choice.
A responsiveness score changed in March 2024
Core Web Vitals are the small set of experience measures web.dev asks site owners to pay attention to. The Web Vitals guide, last updated in October 2024, names three: Largest Contentful Paint for loading, Interaction to Next Paint for interactivity, and Cumulative Layout Shift for visual stability. [3] Interaction to Next Paint is listed there as stable. The same guide notes that a stable metric can later be replaced, and that this is what happened to First Input Delay when Interaction to Next Paint became a stable Core Web Vital in 2024. [3]
On March 12, 2024, web.dev wrote that Interaction to Next Paint had become a stable Core Web Vital, replacing First Input Delay. [1] The same post said Chrome tools would no longer guarantee First Input Delay, and it gave developers until September 9, 2024 to switch. [1] We are not describing a newer swap. First Input Delay looked at the wait before the first interaction's handlers could start. Interaction to Next Paint looks across the whole visit. [2] The March 2024 replacement is a change in how responsiveness is described. It is not, by itself, an order to rebuild a website.
What the new score actually watches
web.dev's Interaction to Next Paint guide, last updated in September 2025, says the metric assesses overall responsiveness by taking in the latency of click, tap, and keyboard interactions through the life of a visit. [2] Scrolling, hovering, and zooming are not part of that count. [2] The guide draws a line against the older metric. First Input Delay covered only the input delay of the first interaction. Interaction to Next Paint starts at that input, continues through the event handlers, and stops when the browser can paint the next frame. [2] A menu tap, a button tap, or a key press counts. The first tap after load is not the whole story.
The same guide calls an INP of 200 ms or less a good mark on its scale, and an INP above 500 ms a poor one, judged at the 75th percentile of page loads split by mobile and desktop. [2] Those cutoffs are web.dev's, from a page last updated in September 2025. They are not a target we are offering. An update on a site we built is not a promise that the number will land at or under 200 ms, or that the number will move at all.
An interaction has three parts in that guide. Input delay is the wait before event handlers start, and long tasks already on the main thread can cause it. Processing duration is the time those handlers take. Presentation delay is the wait until the next frame is painted. [2] A hero image can matter for loading. That question belongs to Largest Contentful Paint, a different vital. [3] A picture is a weak place to look first when the complaint is a tap or a keypress. The guide says the page's INP is figured when the visitor leaves, and that a lab check only includes the interactions someone actually performed. [2]
A heavy script can stall more than one tap
web.dev's optimization guide, also last updated in September 2025, says input delay can come from other work on the main thread, including scripts that are loading, being parsed, and being compiled. [4] Depending on the size of a script, that work can introduce long tasks, and those tasks can delay the browser from responding to other user interactions. [4] Event handlers are a separate part of the wait: they add their own time before the next frame is painted. [4]
The late moment is often not the photograph at the top of the homepage. It is a script, or a menu's event work, running while someone tries to tap. We do not treat that guide as proof that every responsiveness problem covers the whole site. The page does not say that. If one script can delay other interactions on the page, the useful edit is often that script, or a sluggish menu tied to it, not a single image swap. [4]
On a site we built, that script or menu is usually one pattern used in more than one place. With your OK, we change it once, in the code those pages share. On a theme site, the same behavior may live in the theme, in a plugin, and in a few shortcodes.
What updating looks like when we built the site
A site built for one business carries only what it needs. There is no shared theme file waiting on a vendor, and there is no pile of macros to search before a rule can change. Our Forged Sites page shows the shape of that build: custom-coded, static-first, and no plugin marketplace. Fewer moving parts is the benefit we mean. When a rule on the web shifts, the pages that need the change are pages we wrote, so the edit can cover the whole site we built, with your OK, as one coordinated change.
For a shift like Interaction to Next Paint, the work starts by naming the pattern. We look for the heavy script or the sluggish menu, the thing a person meets on more than one page, rather than retouching a hero image and calling the job done. You approve that scope before we treat it as the change. Then we edit the pattern where it lives, and the pages that use it pick up the same change together. That is not a rebuild, not a theme overhaul, and not a hunt through shortcodes that were pasted into posts at different times.
We do this from Charlotte for owners who want the site to stay specific to the business. You still decide whether the change happens. We tell you the scope, you say yes or no, and the work follows that agreement. The header, the script, and the page patterns sit in one place.
WordPress is built to fit everyone, and that is a real strength
WordPress is great open source, built so a theme and a set of plugins can fit many kinds of businesses. We keep sites on it when that fit is what the owner wants. We move some sites off it when the shared machinery is the thing in the way. The weight of "built for everyone" is a feature until a rule change has to pass through pieces you did not write.
The theme handbook on WordPress.org says a theme represents the design of the website and can control everything from colors, to fonts, to the entire layout. Themes control the presentation of content. [6] The handbook also notes thousands of themes in the WordPress.org theme directory, plus more from third-party shops, and it notes that many businesses commission a bespoke theme. [6] A theme is allowed to be custom. The friction we describe is the common case, where the layout is a product shared with everyone who installed that theme. The theme author has to ship a release that still works for that crowd. Your page is one consumer of the presentation layer, not the only one. [6]
The plugin handbook describes shortcodes as macros that perform dynamic interactions with the content, such as creating a gallery from attached images or rendering a video. [5] A shortcode can accept parameters, so each use can behave a little differently, and the markup itself stays out of the post. [5] That is useful when an owner is composing pages by hand. It is also a place where behavior hides. A menu, a form, or a script hook can be a token in one page, a different token in another, and a plugin setting underneath both. Three places can all be "the menu," and a responsiveness change may need all three before a tap behaves the same way on every page. [5]
If you want to edit every page yourself, WordPress, or a template builder with the same hands-on model, can be the better fit. We would rather match the setup to the way you work than talk you into a custom site you will resent. The handbook's own split is a fair one: themes handle presentation, and plugins handle behavior and features. [6] A builder template makes a similar trade even when the product is not WordPress. Your text sits in a shared frame. When that frame has to change, you often wait on the publisher, or you rebuild the page in a newer template. For some businesses that trade is the right one. On a site we built, the pattern sits in the code for that one business, so with your OK we change it once instead of waiting on a theme shop to clear the change for every other customer.
What we will not promise
We will not promise that the update improves a Core Web Vitals number, a loading time, a ranking, or a count of leads. web.dev publishes thresholds. Reaching them is a separate question from whether the pattern was edited where it actually lives. [2] A clean edit can still leave a number where it was.
We will not pretend a single hero image is the usual fix for a tap or a keypress. The guides point at main-thread work, event handlers, and the wait until the next paint. [2][4] If a photo is the problem for loading, that is the other vital, and it should be talked about as that. [3]
We will not describe the site as untouchable, and we will not borrow someone else's project to make the point. If staying on WordPress is the better fit so you can edit every page, we will say that. The Web Vitals guide says these metrics evolve, and that updates come with notice. [3] Our job on a site we built is to name the pattern a change actually touches and bring you a scope. Your job is the yes or the no.
Practical takeaways
- In March 2024, Interaction to Next Paint replaced First Input Delay as a Core Web Vital. It watches clicks, taps, and key presses across the visit, from the input until the next paint, not a single hero image. [1][2]
- On a site we built, a heavy script or a sluggish menu can be changed once, across the pages that use it, with your OK. That edit is not a promise of a better score, ranking, or lead count. [4]
- If you want to edit every page yourself, WordPress or a template builder can be the better fit. A theme controls presentation, from colors and fonts to the layout. [6] On a shared theme, a rule change often waits on a theme update, a plugin, or a rebuild.
How we can help
Have more questions or want to get in touch? Idea Forge Studios is at our contact page, by phone at (980) 322-4500, and by email at [email protected].
Citations
- web.dev, "Interaction to Next Paint is officially a Core Web Vital" (2024-03-12)
- web.dev, "Interaction to Next Paint (INP)" (last updated 2025-09-02)
- web.dev, "Web Vitals" (last updated 2024-10-31)
- web.dev, "Optimize Interaction to Next Paint" (last updated 2025-09-02)
- WordPress Developer Resources, "Shortcodes" (last updated 2023-12-14)
- WordPress Developer Resources, "What Is a Theme?" (last updated 2023-12-14)
