SEO Considerations During a Website Redesign


The homepage looked polished. The service pages read well. Mobile layout was clean enough to demo in a stakeholder meeting.

Then I ran PageSpeed Insights on a phone connection and the Largest Contentful Paint (LCP) landed above four seconds. The hero image was full width and uncompressed. A chat widget loaded before the main content. On scroll, a promo banner pushed the contact button down and the layout jumped.

Nobody had checked rankings yet. Real users were already feeling the slowness and instability. For business websites where the goal is inquiries, bookings, or signups, Core Web Vitals are not an abstract SEO metric. They describe whether the site feels trustworthy and usable on the device most people actually use.

I work on technical SEO and performance optimization alongside development teams. This checklist is what I use when a business site needs practical CWV fixes, not a generic "make it faster" slide deck.


What Core Web Vitals actually measure

Google's Core Web Vitals focus on three user-facing signals:

LCP (Largest Contentful Paint): How long until the largest visible content element (often a hero image, heading block, or video poster) renders. Slow LCP feels like a slow load.

INP (Interaction to Next Paint): How responsive the page feels when someone taps, clicks, or types. High INP means buttons lag or scrolling stutters after interaction.

CLS (Cumulative Layout Shift): How much the layout moves unexpectedly while the page loads. High CLS means users mis-tap buttons or lose their place while reading.

These metrics describe experience quality. Search Console can surface them at scale, but the underlying fixes are almost always front-end, hosting, or third-party script decisions.


Why business sites fail CWV more often than blogs

Marketing-heavy business sites stack features that blogs often skip:

  • Full-width hero images and background videos on every template
  • Slider plugins and animation libraries on the homepage
  • Live chat, heatmaps, and A/B testing snippets in the header
  • Google Tag Manager loading a dozen tags before first paint
  • Web fonts loaded from multiple families and weights
  • Page builders that output heavy CSS and nested DOM
  • Embedded maps, review widgets, and booking iframes without reserved space

Each item can be justified for conversion or brand. Together they push LCP, INP, and CLS out of a healthy range on mobile, which is where Google evaluates page experience for most sites.


LCP checklist

LCP improvements usually start with the hero and the critical rendering path.

Images and media

  • Serve hero images in modern formats (WebP or AVIF) with fallbacks where needed
  • Size images to the display width, not the camera resolution
  • Compress aggressively without obvious quality loss on mobile
  • Preload the LCP image when it is above the fold
  • Avoid lazy-loading the LCP candidate (lazy load below-the-fold media only)

Server and delivery

  • Improve Time to First Byte (TTFB): caching, CDN, lean server response
  • Use HTTP/2 or HTTP/3 where hosting supports it
  • Review redirects chains on the homepage and top landing pages

Render blocking

  • Defer non-critical JavaScript
  • Inline critical CSS for above-the-fold content or split CSS by template
  • Move tag managers and chat widgets to load after main content when possible

Templates to test first: Home, top service page, contact, and any paid landing page with a hero image.


INP checklist

INP problems often show up as "the site works on desktop but feels sticky on mobile."

JavaScript weight

  • Audit third-party scripts (chat, analytics, ads, social embeds)
  • Remove or delay scripts that are not essential on first visit
  • Break up long tasks on the main thread; split heavy work across frames where frameworks allow

Interaction handlers

  • Debounce scroll and resize handlers
  • Avoid expensive DOM queries inside click handlers on large pages
  • Test forms on mid-range Android devices, not only on a developer laptop

Framework and CMS behavior

  • Client-side hydration can delay interactivity on JavaScript-heavy stacks
  • Page builders may attach listeners to large DOM trees; simplify templates where INP fails

If INP is poor on one template, fix that template before rolling changes site-wide.


CLS checklist

CLS issues frustrate users because the page feels broken, not just slow.

Reserve space

  • Set explicit width and height on images and video embeds
  • Reserve space for ad slots, review widgets, and map iframes before they load
  • Avoid inserting banners or cookie bars that push content down without a reserved slot

Fonts

  • Use `font-display: swap` or subset fonts to reduce invisible text periods
  • Preload primary web fonts used in headings above the fold
  • Limit font families and weights loaded on marketing pages


Dynamic content

  • Do not inject content above existing content after load unless space is reserved
  • Load skeleton placeholders for async blocks (testimonials, pricing tables, feeds)
  • Test cookie consent, promo bars, and sticky headers on mobile scroll

A layout that jumps once is enough to fail CLS on a template that otherwise looks fine in a desktop screenshot.


How to test (practical stack)

You do not need every tool. A small stack is enough for business sites:

  1. PageSpeed Insights: Field data (when available) plus lab scores for mobile and desktop on priority URLs
  2. Google Search Console: Core Web Vitals report grouped by URL groups; start with "Poor" and "Needs improvement"
  3. Lighthouse (mobile): Repeatable lab checks in Chrome DevTools during development
  4. Real device spot check: Mid-range phone on 4G or throttled Wi-Fi for LCP and INP feel

Run the same four templates each time so comparisons are meaningful. Fix, redeploy, retest after 28 days when field data updates in Search Console.


Before launch vs after launch

Before launch: Baseline home, service, contact, and key landing templates. Set image dimensions, defer third parties, and confirm LCP element is identified correctly in Lighthouse. Do not wait for traffic to discover a four-megabyte hero.

After launch: Monitor Search Console CWV groups weekly for the first month. Traffic patterns and real devices can surface issues lab tests missed. Pair CWV monitoring with analytics: if organic landing pages have high bounce and poor LCP, prioritize those URLs first.

Pre-launch SEO covers broader foundations (structure, metadata, analytics). Redesign projects often regress CWV when new themes add weight. This checklist is the performance layer those projects still need.


Prioritized fix order

When everything is red, I fix in this order:

1. LCP image and font loading on home and top landing pages (often the fastest win)

2. CLS from images and embeds without reserved dimensions

3. Defer or remove third-party scripts that block or delay interactivity

4. Server and CDN tuning** if TTFB is consistently high

5. Template-level INP work** on pages with heavy JavaScript or page-builder output

6. Platform or replatform decisions** only after the above are exhausted on critical URLs

Replatforming is expensive. Most business sites can improve CWV materially without a rebuild if the team focuses on templates that drive leads.


Business website Core Web Vitals checklist

Use this numbered list on your next audit:

  1. Identify the LCP element on home, top service, contact, and main landing pages
  2. Compress and resize hero images; use modern formats where supported
  3. Preload LCP image and critical fonts; avoid lazy-loading the LCP candidate
  4. Set explicit width and height on images, videos, maps, and embeds
  5. Defer non-critical JavaScript; delay chat and secondary widgets after main content
  6. Audit third-party scripts loaded via tag manager; remove unused tags
  7. Test mobile INP on a mid-range device for forms, nav, and primary CTAs
  8. Fix layout shift from cookie bars, promo banners, and dynamic content injection
  9. Run PageSpeed Insights and Lighthouse mobile after each template change
  10. Review Search Console Core Web Vitals report monthly for URL groups still marked Poor
  11. Retest field data after 28 days following production fixes
  12. Document baseline and post-fix scores so stakeholders see progress, not just green arrows in a slide


Key takeaways

  • Core Web Vitals describe load, responsiveness, and visual stability, not vanity Lighthouse scores in isolation.
  • Business websites fail CWV when heroes, widgets, fonts, and tag managers stack on mobile templates.
  • Fix LCP and CLS on money pages first; then tackle INP and third-party weight.
  • Test with PageSpeed Insights, Search Console, Lighthouse, and at least one real phone.
  • Performance work belongs in launch and redesign scope, not only in a post-launch SEO ticket.

Which CWV metric bites your projects most often: LCP, INP, or CLS? I see LCP and CLS on marketing homepages more than teams expect.

If you want help auditing templates, prioritizing fixes, or tying performance work into a broader SEO program, that is the kind of work covered under technical SEO for websites, apps, and software platforms.


Comments

Post a Comment

Popular posts from this blog

Technical SEO Audit: What to Fix Now vs What Can Wait

You paid for a technical SEO audit. The PDF arrived with forty, eighty, or two hundred line items. Half sound urgent. Half sound like jargon. Your developer says some fixes are quick. Your agency says others need a sprint. Nobody agrees on what to do Monday morning. That overwhelm is normal. An audit is an inventory, not a to-do list sorted by business impact. The goal of this guide is to help you triage findings without becoming an SEO specialist overnight: what to fix now, what to schedule this month, and what can wait while you monitor results. We run technical SEO audits for business websites with teams who need a clear sequence, not a wall of red rows. These are the buckets we use when a report lands on a founder or marketing lead's desk. What a Technical SEO Audit Covers (and What It Does Not) A solid technical SEO audit reviews how search engines and real users experience your site: crawl paths, indexation, URLs, metadata, redirects, structured data, mobile usability, perfo...
Read more

Why User Experience Comes First in SEO (Before Keyword Lists)

You opened an SEO checklist and the first column was keywords. Fifty phrases. Density targets. Exact-match headings. Nobody asked whether the page actually helped a customer decide anything. That gap is why so many beginner SEO efforts stall. Search engines reward sites that solve problems for people. Keyword lists without useful structure are noise. We work on SEO for websites, apps, and software platforms with teams at every stage. The pattern we see repeatedly: pages that perform over time put user experience first, then layer technical basics on top. Keyword stuffing rarely survives either test. What "User Experience" Means for SEO Beginners User experience (UX) in SEO is not a design award. It is whether a visitor can: Understand what the page is about within seconds Find the answer or next step without hunting Trust that the content matches the promise in search results Google's public guidance has leaned this way for years: helpful, people-first content beats mani...
Read more