Migrating a WordPress website often involves changes like switching hosting providers, moving to a new domain, or launching a redesigned site.
While these changes can improve your website, they can also affect performance if important settings are lost during the process.
After a migration, many websites suddenly fail Core Web Vitals tests. Caching may be disabled.
Images may no longer be optimized. CDN connections, scripts, or fonts may also load differently. These small changes can quickly slow down your site.
In this guide, you’ll learn why WordPress sites often fail Core Web Vitals after a migration and how to fix the most common issues step by step.
By the end, you’ll know exactly what to check and how to restore your site’s performance.
See the full guide on how to improve Core Web Vitals in WordPress.
What Are Core Web Vitals?
Core Web Vitals are performance metrics created by Google to measure how fast and stable a website feels for users. They focus on real user experience, not just technical speed scores.
These metrics help Google understand whether your website loads quickly, responds smoothly, and stays visually stable.
There are three main Core Web Vitals:
Largest Contentful Paint (LCP)
Largest Contentful Paint measures how long it takes for the main content of a page to load. This is usually the largest image, banner, or heading visible on the screen.
For a good user experience, your LCP should happen within 2.5 seconds. Slow hosting, large images, or render-blocking files often increase LCP time.
Interaction to Next Paint (INP)
Interaction to Next Paint measures how quickly a page responds when a user interacts with it, such as clicking a button or opening a menu.
A good INP score is 200 milliseconds or less. Heavy JavaScript, too many plugins, or background scripts can cause slow interactions.
Cumulative Layout Shift (CLS)
Cumulative Layout Shift measures how much the page layout moves while it is loading. For example, when text or buttons suddenly shift because images, ads, or fonts load late.
A good CLS score is 0.1 or lower. Layout shifts often happen when space is not reserved for images, ads, or dynamic content.
Why Core Web Vitals Matter
Core Web Vitals affect both SEO and user experience.
- Google uses them as part of its ranking signals.
- Faster sites keep visitors engaged longer.
- Stable pages prevent users from clicking the wrong elements.
- Responsive pages make websites feel smoother and more professional.
In short, strong Core Web Vitals help your site rank better, load faster, and create a better experience for visitors.
Why Core Web Vitals Fail After a WordPress Migration
A WordPress migration can change many parts of your website behind the scenes.
Even if the site looks the same on the surface, important performance settings may have changed or disappeared during the move.
Caching may stop working. CDN connections can break. Images, scripts, and fonts may start loading differently.
These changes increase loading time, create layout shifts, and slow down page interactions.
Below are the most common reasons WordPress sites fail Core Web Vitals after a migration.
1. Hosting Performance Changed
Your hosting environment plays a major role in website speed.
When a site is migrated, it may move to a different server with different hardware, configurations, or performance limits.
One common issue is slower server response time. If the server takes longer to respond to requests, the browser must wait before it can begin loading page content.
This delay directly increases loading metrics like Largest Contentful Paint.
Another factor is the type of hosting used. Shared hosting often places many websites on the same server. When other sites use more resources, your site may slow down.
Managed WordPress hosting usually provides better performance because resources are optimized for WordPress, and server-level caching is often included.
When hosting performance drops, the impact appears quickly in Core Web Vitals. Pages load more slowly, which increases LCP, and interactions may feel delayed, which affects INP.
2. Cache Settings Were Lost
Caching is one of the most important performance optimizations for WordPress. During a migration, caching systems are often reset or disabled.
Many caching plugins require reconfiguration after a migration.
If these settings are not restored, the site may begin generating pages dynamically again instead of serving cached versions. This significantly increases loading time.
Another common issue is page caching being disabled. Without page caching, every visitor triggers new database queries and PHP processing.
This adds unnecessary work for the server and slows page delivery.
Browser caching can also disappear. When browser caching is missing, returning visitors must download the same files again instead of loading them from their device.
This increases load times and affects performance metrics.
Re-enabling caching is often one of the fastest ways to restore Core Web Vitals after a migration.
3. CDN Not Configured Correctly
Content Delivery Networks (CDNs) improve speed by delivering static files from servers located closer to visitors. However, CDN connections often break during migrations.
If the CDN becomes disconnected, images, scripts, and stylesheets start loading directly from the origin server.
This increases latency, especially for users who are far from the hosting location.
DNS changes can also affect how traffic is routed.
When domain records are updated during a migration, the CDN may no longer sit between visitors and the server. As a result, performance benefits disappear.
Another issue is static files not being served from edge servers. When files are not cached on CDN nodes, they must be retrieved from the origin server repeatedly.
This increases load times and slows down page rendering.
Properly reconnecting the CDN and verifying DNS settings usually resolves this problem.
4. Images Are No Longer Optimized
Images are often the largest elements on a webpage. If image optimization is missing after a migration, page size increases quickly.
Many websites rely on image optimization plugins to compress and convert images automatically.
If these plugins are not installed or configured again after the migration, images may load in their original large formats.
Redesigns during migration can also introduce larger images. Designers sometimes upload high-resolution images without resizing them for web use.
Large images significantly increase loading time and affect Largest Contentful Paint.
Modern image formats like WebP or AVIF may also stop working if the plugin or server configuration changes.
When these formats are not used, browsers must download heavier JPEG or PNG files.
Optimizing images again is essential to restore fast loading speeds.
5. JavaScript and CSS Optimization Disabled
WordPress performance plugins often optimize JavaScript and CSS files by reducing their size and delaying unnecessary scripts. These settings can disappear during a migration.
If minification is disabled, CSS and JavaScript files remain larger than necessary. Larger files take longer to download and process.
Another issue is the return of render-blocking resources.
When CSS or JavaScript loads before the page can render, the browser must pause page display until these files finish loading. This delays visible content and increases LCP.
Many optimization plugins also delay non-critical JavaScript. When these delay settings are lost, scripts load earlier than necessary and block the main thread, slowing page interaction.
Restoring JavaScript and CSS optimization helps reduce loading time and improve responsiveness.
6. Third-Party Scripts Added During Migration
Migrations and redesigns often introduce new third-party tools. While these tools add features, they also increase the number of external scripts loaded on a page.
Common examples include analytics tools, tracking scripts, advertising networks, and marketing platforms. Each script adds additional network requests and processing time.
Chat widgets are another common cause of performance issues. These tools often load large JavaScript files and connect to external servers.
Too many third-party scripts can slow both page loading and interaction speed. They increase JavaScript execution time, which negatively affects INP and sometimes LCP.
Reviewing and limiting third-party scripts can significantly improve performance.
7. Theme or Plugin Changes
A migration sometimes includes installing a new theme or adding additional plugins. These changes can affect performance more than expected.
Some themes include large frameworks, page builders, animations, or unnecessary scripts. These features increase page size and loading complexity.
Plugins can also add heavy functionality. Some plugins load scripts on every page, even when they are not needed.
Others perform slow database queries or load multiple CSS and JavaScript files.
Poorly coded plugins can slow both loading and interactions. This affects both LCP and INP.
After migration, it is important to review which plugins are truly necessary and remove anything that adds unnecessary load.
8. Lazy Loading Configuration Issues
Lazy loading delays images until they are about to appear on the screen. When used correctly, it reduces initial page weight and speeds up loading.
However, migration can change how lazy loading is configured.
In some cases, lazy loading may be disabled entirely, causing all images to load immediately. This increases page load time.
Another common mistake is lazy loading the LCP image. The LCP element is usually the main image or banner visible when the page first loads.
If this image is delayed by lazy loading, the browser cannot render the main content quickly.
Correct lazy loading settings ensure that off-screen images are delayed while important images load immediately.
9. Database Optimization Issues
The WordPress database can accumulate unnecessary data over time. During migrations, this data often moves with the site and may grow even larger.
Post revisions, expired transients, and temporary data can build up in the database. When the database becomes cluttered, queries take longer to complete.
Slow database queries increase server processing time and delay page generation. This can increase server response time and negatively affect loading performance.
Cleaning and optimizing the database helps reduce processing delays and improve page delivery speed.
10. Font Loading Problems
Fonts may seem small, but they can significantly affect performance when not configured correctly.
Many themes load fonts from external services. When fonts load from remote servers, additional network requests are required before text can appear on the screen.
Another common issue is missing font preload settings. Without preloading, the browser may delay downloading fonts until later in the loading process.
This can slow the display of visible text.
Design changes may also introduce multiple font weights and styles. Each font variation requires a separate file download, increasing page size and load time.
Reducing the number of font files and optimizing font loading helps prevent delays in content rendering.
How to Diagnose Core Web Vitals Issues After Migration
When Core Web Vitals drop after a migration, the first step is to identify what changed. Performance problems rarely come from a single issue.
They are usually caused by a combination of slow server response, heavy scripts, unoptimized images, or broken caching.
The key is to use the right tools to locate the exact problem. The tools below help you see where delays occur and which elements affect your Core Web Vitals.
Using PageSpeed Insights
PageSpeed Insights is one of the fastest ways to analyze your site’s Core Web Vitals. It shows real-world user data and highlights performance problems on a specific page.
Start by visiting the PageSpeed Insights website and entering your page URL. The tool will run a test and display both mobile and desktop performance results.
Focus on the Core Web Vitals section first. This will show whether your page passes or fails LCP, INP, and CLS.
Scroll down to the diagnostics and opportunities sections. These areas explain what is slowing down your page.
For example, you may see warnings about large images, render-blocking scripts, unused CSS, or long server response times.
Another helpful feature is the Largest Contentful Paint element preview. This shows exactly which element is counted as LCP.
If that element is a large image or slider, you immediately know where to start optimizing.
Run PageSpeed tests before and after fixes to confirm improvements.
Using Google Search Console Core Web Vitals Report
Google Search Console provides a broader view of Core Web Vitals performance across your entire website.
Instead of testing a single page, it groups pages based on real user data collected by Chrome users.
Open Search Console and go to the Core Web Vitals report. You will see separate reports for mobile and desktop performance. Each report categorizes pages as:
- Good
- Needs Improvement
- Poor
Click on any issue group to see which pages are affected. For example, you might see warnings such as “LCP issue: longer than 2.5 seconds” or “CLS issue: more than 0.1.”
Search Console also provides example URLs so you can investigate specific pages.
This helps you determine whether the problem affects your entire site or only certain templates, such as blog posts or product pages.
Because this report uses real user data, improvements may take time to appear. However, it is one of the most reliable ways to confirm long-term performance fixes.
Using Chrome DevTools
Chrome DevTools allows you to inspect exactly how your page loads inside the browser. It provides detailed information about network requests, scripts, and rendering behavior.
Open your website in Google Chrome. Right-click anywhere on the page and select Inspect, then open the Lighthouse or Performance tab.
Running a Lighthouse audit gives a full performance analysis similar to PageSpeed Insights.
It also shows suggestions for improving loading speed, reducing JavaScript execution time, and fixing layout shifts.
The Network tab is also useful. It lists every file loaded on the page, including images, scripts, stylesheets, and fonts. You can quickly identify files that are unusually large or slow to load.
If a migration introduced new scripts or large assets, DevTools will reveal them immediately.
Checking Server Response Time (TTFB)
Server response time, often called Time to First Byte (TTFB), measures how long it takes for the server to respond to a request.
A slow TTFB usually indicates server-side problems, such as:
- Slow hosting
- Missing caching
- Heavy database queries
- Server configuration issues
You can check TTFB using tools like PageSpeed Insights, GTmetrix, or Chrome DevTools.
As a general guideline, a good server response time should be under 800 milliseconds.
If the server takes longer than this to respond, the browser must wait before it can begin loading page content.
Slow server response directly increases Largest Contentful Paint and can delay page interaction.
If TTFB is high after a migration, review your hosting environment, caching setup, and database performance.
Fixing server response time often produces immediate improvements in Core Web Vitals.
How to Fix Core Web Vitals After Migration
Once you identify the issues affecting your website, the next step is fixing them.
Most Core Web Vitals problems after migration come from settings that were reset, tools that stopped working, or new files that increased page weight.
The goal is to restore the performance optimizations your site had before the migration.
Start with the most important fixes first. Small improvements in several areas can quickly bring your Core Web Vitals back to healthy levels.
1. Re-Enable Caching
Caching is one of the most effective ways to improve WordPress performance.
If caching stops working after a migration, every page request must be built from scratch by the server. This increases load time and server workload.
Page caching should be enabled first. Page caching saves a ready-to-serve version of your pages so visitors receive a static file instead of waiting for WordPress to generate the page.
This dramatically reduces loading time and improves Largest Contentful Paint.
Next, enable browser caching. Browser caching allows returning visitors to load images, stylesheets, and scripts from their own device instead of downloading them again.
This reduces network requests and speeds up page rendering.
You should also enable object caching if your hosting supports it. Object caching stores database query results in memory.
When the same data is requested again, the server can deliver it instantly without repeating the query.
Together, these caching layers reduce server load and significantly improve page speed.
2. Optimize Images
Images are often the largest files on a webpage. After a migration, image optimization tools may stop working or be removed entirely. This causes pages to become heavier and slower.
Start by compressing images. Compression reduces file size without noticeably affecting quality. Smaller files download faster and improve loading performance.
Next, convert images to modern formats such as WebP. These formats provide better compression than traditional JPEG or PNG files while maintaining good visual quality.
Most modern browsers support WebP, making it a strong option for improving speed.
You should also resize large images before uploading them. Many websites upload images that are much larger than the display size.
For example, a 4000-pixel image used in a small content area wastes bandwidth and slows loading. Resize images to match their actual display dimensions.
Optimized images reduce page weight and improve LCP performance.
3. Configure CDN Properly
If your site used a Content Delivery Network before the migration, you should confirm that it is still connected and working correctly.
First, reconnect the CDN to your website if needed. Migration often changes domain settings or server configurations, which can break the CDN integration.
Next, confirm that static assets are cached by the CDN. These include images, CSS files, JavaScript files, and fonts.
When cached at edge servers, these files are delivered from locations closer to the visitor, reducing latency.
You should also verify that your DNS settings correctly route traffic through the CDN.
If DNS records bypass the CDN, visitors will load files directly from your origin server, which removes the performance benefits.
A properly configured CDN speeds up content delivery for users around the world.
4. Optimize CSS and JavaScript
CSS and JavaScript files can significantly affect loading performance when they are not optimized.
Start by minifying files. Minification removes unnecessary spaces, comments, and formatting from code. This reduces file size and helps browsers download resources faster.
Next, remove unused CSS where possible. Many themes and plugins load styles that are never used on the page.
Eliminating these files reduces page weight and speeds up rendering.
You should also delay non-critical JavaScript. Some scripts are not required immediately when the page loads.
Delaying them allows the browser to display visible content first, improving loading metrics and user experience.
Proper script optimization reduces render-blocking behavior and improves both LCP and interaction performance.
5. Review Plugins and Theme
Plugins and themes can have a large impact on performance. A migration often introduces new tools that were not present on the original site.
Start by removing unnecessary or heavy plugins. Each plugin can add scripts, stylesheets, or database queries. Too many plugins increase complexity and slow the site.
Next, evaluate whether your site is using a lightweight theme. Some themes include large frameworks, animations, or page builders that add extra code.
A well-optimized theme keeps the design clean and loads only essential resources.
You should also audit plugin performance. Identify which plugins load large scripts or cause slow database queries. If a plugin significantly slows your site, look for a lighter alternative.
Keeping plugins and themes efficient helps maintain fast loading speeds.
6. Fix Font Loading
Fonts can delay page rendering when they are not loaded efficiently. After a migration, font settings may change, or new fonts may be added.
First, preload important fonts. Preloading tells the browser to download key font files early in the loading process. This ensures text appears faster on the screen.
Next, reduce the number of font weights and styles used on your site. Each variation requires a separate file download. Using fewer fonts reduces the total number of requests.
Finally, consider self-hosting your fonts instead of loading them from external services.
Hosting fonts locally removes extra external requests and gives you better control over caching.
Optimized font loading ensures text appears quickly and helps prevent layout shifts during page rendering.
Best Practices to Prevent Core Web Vitals Issues During Migration
The following best practices help keep your website fast during and after a WordPress migration.
Test Performance Before Migration
Before starting a migration, record your current performance metrics. This gives you a clear baseline to compare against after the move.
Run tests using tools like PageSpeed Insights or Lighthouse and note the scores for Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift.
Pay attention to the elements responsible for LCP and any warnings related to scripts, images, or fonts.
You should also measure server response time and page size. These details help you understand how the site performs under its current environment.
Once the migration is complete, run the same tests again. If performance drops, comparing the results will help you quickly identify what changed.
Use Staging Environments
A staging environment is a copy of your website used for testing changes before they go live. This is one of the safest ways to perform a migration.
Instead of moving the site directly to a new server or configuration, migrate the site to staging first.
This allows you to test functionality, design, and performance without affecting real visitors.
During this stage, check whether caching, image optimization, CDN integration, and script optimization are working properly.
If something breaks, you can fix it before the public site is updated.
Using staging reduces risk and prevents performance issues from reaching live users.
Reconfigure Performance Plugins
Many WordPress performance plugins reset their settings during migration. Even if the plugin is still installed, its configuration may no longer be active.
After the migration, open your performance plugin and review every major setting. Confirm that page caching, browser caching, file minification, and lazy loading are enabled.
If your site used features like JavaScript delay, database cleanup, or image optimization, make sure these options are turned on again.
Some plugins require reconnecting services such as CDNs or image compression APIs.
Taking a few minutes to review plugin settings can restore many lost performance optimizations.
Run Performance Tests Immediately After Migration
Once the migration is complete and the site is live, run performance tests immediately. This helps you detect problems before search engines or users experience slow pages.
Start by testing your main pages, such as the homepage, blog posts, and important landing pages.
Check loading time, Core Web Vitals scores, and any warnings related to scripts, images, or server response time.
If issues appear, fix them as soon as possible. Small configuration problems can often be resolved quickly if detected early.
Tools to Monitor WordPress Performance
- PageSpeed Insights
Analyzes your website’s performance using real user data and provides recommendations to improve Core Web Vitals and overall page speed. - Lighthouse
A built-in Chrome tool that audits performance, accessibility, SEO, and best practices while showing detailed suggestions to improve page loading. - GTmetrix
Provides in-depth performance reports, including page load time, page size, and detailed waterfall charts that show how each resource loads. - WebPageTest
Allows advanced performance testing from different locations and devices while providing detailed insights into loading behavior and server response time. - Google Search Console
Shows real-world Core Web Vitals data from actual users and helps identify pages on your site that need performance improvements.
Final Thoughts
Core Web Vitals drops after a WordPress migration are very common.
Many performance settings change during the move, even when the website itself looks the same.
Most problems come from lost configurations, such as caching, CDN settings, image optimization, or script optimization.
These issues are usually easy to fix once you know where to look.
By testing performance, restoring optimization settings, and monitoring your site after the migration, you can quickly recover your Core Web Vitals and keep your website fast for both users and search engines.
Explore our complete WordPress Core Web Vitals optimization guide.
FAQs
Why did my Core Web Vitals drop after migrating WordPress?
Core Web Vitals often drop because caching, CDN settings, image optimization, or script optimization stop working during the migration.
How long does it take for Core Web Vitals to recover after migration?
Performance improvements can appear immediately in testing tools, but Google Search Console data may take several weeks to update.
Does changing hosting affect Core Web Vitals?
Yes. Slower hosting can increase server response time, which directly affects loading speed and Core Web Vitals metrics.
Can plugins break Core Web Vitals after migration?
Yes. Some plugins add heavy scripts, styles, or database queries that can slow page loading and interactions.
Should I test performance before and after a WordPress migration?
Yes. Testing before and after migration helps you quickly identify performance changes and fix issues early.