After migration
A migration should not inherently make a website slower, but changed PHP versions, caching, DNS, external services and application configuration can affect the result. Capture a baseline and compare the same pages.
Measure before and afterTest the same URLs, device and location.
Match the applicationPHP, extensions and scheduled jobs can differ.
Optimise with evidenceFind the slow layer before changing limits.
Before switching
Test the home page, a typical content page and an uncached dynamic action such as login or checkout. Record response times and note any existing errors. A single synthetic score does not describe database, administration or logged-in performance.
After switching
www hostnames.If it is slower
Send the exact URL, time of test, whether you were signed in, measured before/after timings and any browser or application error. This is more actionable than “the site feels slow”.
Actual speed still depends on the application, database and page content, so verify rather than assume.
Article feedback
