Organic SEO is not just about adding keywords to a website.
It is also about making sure the website itself is healthy, fast, stable, readable, and technically sound. Search engines need to understand the structure of a website, but visitors also need the site to load quickly, respond smoothly, and feel reliable. Recently, Traverse City Web Design completed a cleanup and optimization project for a Michigan law firm’s WordPress website. The goal was pragmatic: improve the technical foundation of the site so future SEO work would have a stronger platform to build on.
This was not a flashy redesign. It was the kind of under-the-hood work that many websites need after years of plugin updates, hosting changes, database buildup, and older server settings.
The Starting Point
The law firm’s website was already live and functioning, but it had performance issues that were limiting its effectiveness.
Before the cleanup, speed testing showed:
- Page load times over 5 seconds
- A page size of 2.8 MB
- 65 page requests
- A Google PageSpeed performance grade of 73/100
- A Largest Contentful Paint score of 5.7 seconds
- A Total Blocking Time of 450 milliseconds
Those numbers matter because they affect both user experience and organic SEO.
A slow website can frustrate visitors before they ever read a headline, fill out a contact form, or call the office. For a law firm, that matters. Many potential clients are looking for help quickly. If the site feels slow or unresponsive, they may simply move on.
Fast loading websites are also important because search engines pay attention to how usable a website is. Page speed is not the only ranking factor, but it is part of the overall experience search engines are trying to evaluate. A website that loads quickly, responds smoothly, and allows visitors to find information without delay creates a better experience for both people and search engines.
Speed also affects visitor behavior. When a page takes too long to load, people are more likely to leave before they read the content. That can mean fewer phone calls, fewer contact form submissions, and fewer potential clients moving deeper into the site. For service-based businesses, performance is not just a technical issue. It is part of the sales process.
Step One: Backing Up the Website
Before making technical changes, we ran a full backup of the website. This is always the first step.
Website optimization can involve plugin updates, PHP changes, caching rules, database cleanup, and server-level adjustments. Any one of those changes can create conflicts if the site has older code or abandoned plugins.
A backup gives us a safe restore point.
Once the work was completed, we also created another backup after the server-level improvements were in place.
Step Two: Updating WordPress Plugins and Themes
We updated several WordPress plugins and backup themes.
This kind of work is basic, but important. Older plugins can create security concerns, performance problems, compatibility issues, and unnecessary clutter.
For this project, we updated:
- 6 WordPress plugins
- 2 backup themes
This helped bring the site into better alignment with the current WordPress environment.
Step Three: Upgrading PHP
One of the most important changes involved upgrading PHP.
PHP is the server-side language that powers WordPress. If a WordPress site is running on an older PHP version, it can slow the site down and create compatibility problems.
When we attempted to update PHP, the site initially produced a critical error. The issue came from outdated WP Engine-related plugin files still present in the site’s must-use plugin folder.
In plain English: the site was carrying old hosting-related code that no longer belonged in its current environment. Once that conflict was identified and disabled, we were able to successfully upgrade the website to PHP 8.3.
This was one of the biggest performance improvements in the project. After the PHP upgrade and related PHP setting adjustments, the site’s Pingdom load time dropped from an average of about 5.72 seconds to about 2.06 seconds.
That is roughly a 64% improvement in load time.
Step Four: Adjusting PHP Settings
We also adjusted several PHP settings to make the server environment more reasonable for a modern WordPress site.
These settings included:
- Maximum execution time
- Maximum input time
- Maximum input variables
- Upload file size
- Post size
This helps prevent common WordPress issues during updates, content editing, form submissions, and media uploads. The point is not to make the server unlimited. The point is to give WordPress enough room to operate properly without creating unnecessary risk.
Step Five: Turning On OPcache
We enabled OPcache at the server level.
OPcache stores compiled PHP code in memory. That means WordPress does not have to reprocess the same PHP files every time someone visits a page.
Because WordPress loads many PHP files for each page request, OPcache can make a real difference. This is the kind of server-level improvement that visitors never see directly, but they feel it when the website responds faster.
Step Six: Enabling Server-Level Compression
We turned on server-level content compression.
Compression reduces the size of files sent from the server to the visitor’s browser. Smaller files usually mean faster load times, especially for people on mobile devices or slower connections.
For SEO, this matters because speed and user experience are connected.
A website does not need to be perfect to benefit from compression. It just needs to send less unnecessary weight across the network.
Step Seven: Setting Up LiteSpeed Cache
We configured LiteSpeed Cache for the website.
Caching allows the server to store ready-made versions of public pages. Instead of building each page from scratch every time someone visits, the server can deliver a cached version much faster.
After enabling caching, the site reached one of its best Pingdom test results:
1.89 seconds
Compared to the original average load time of 5.72 seconds, that represented about a 67% improvement.
This is one reason caching is often one of the most effective practical improvements for WordPress websites.
For visitors, caching can make the difference between a website that feels sluggish and one that feels immediate. That matters because people often make quick decisions online. If a website loads quickly, visitors are more likely to stay, read, click, and contact the business.
For search engines, caching helps support stronger technical performance. Faster server response, quicker page delivery, and smoother loading behavior all contribute to a healthier website experience. While content and relevance remain essential, a fast technical foundation helps that content perform better.
Step Eight: Cleaning the WordPress Database
Over time, WordPress databases collect clutter.
This can include spam comments, old plugin settings, orphaned metadata, transients, trackbacks, and leftover entries from features that are no longer active.
For this law firm website, we removed a significant amount of database clutter, including:
- 319 pending spam comments
- 96 leftover plugin option entries
- 6 trackbacks
- 3,812 orphaned post meta entries
- 206 orphaned user meta entries
- Additional orphaned user meta entries
- Expired transient entries
- Transient table entries
We also optimized the database tables after the cleanup.
This kind of cleanup does not usually change the visual design of a website, but it can make the site easier to maintain and reduce unnecessary backend clutter.
For organic SEO, this matters because a technically cleaner site is easier to manage, update, expand, and improve.
Step Nine: Removing Unnecessary Cron Jobs
We removed 5 unnecessary cron jobs.
WordPress cron jobs are scheduled background tasks. Some are useful. Others are left behind by old plugins or outdated functionality. Unnecessary cron jobs can create extra background work for the server. Removing them helps reduce noise and keeps the site leaner.
Step Ten: Minifying and Combining CSS and JavaScript
We also minified and combined CSS and JavaScript files.
This reduced the number of requests and lowered the page size.
Before this step, the site had:
- 65 requests
- 2.8 MB page size
After CSS and JavaScript optimization, the site had:
- 34 requests
- 1.9 MB page size
This also improved the performance grade from 73/100 to 92/100.
There was one practical tradeoff: the Pingdom load time increased slightly compared to the cache-only test. However, the Google PageSpeed score improved substantially.
Because Google’s performance measurements are more relevant to organic search, we kept the CSS and JavaScript optimization in place. That is an important lesson: optimization is not always about chasing one number. It is about understanding which measurements matter most for the goal of the project.
The Results
The website showed clear improvement after the cleanup and optimization work.
Pingdom Improvements
Before optimization:
- Average load time: 5.72 seconds
- Requests: 65
- Page size: 2.8 MB
- Performance grade: 73/100
After PHP upgrade and server optimization:
- Load time: about 2.06 seconds
- Requests: 64
- Page size: 2.8 MB
- Performance grade: 73/100
After caching:
- Load time: 1.89 seconds
- Requests: 65
- Page size: 2.8 MB
- Performance grade: 73/100
After CSS and JavaScript optimization:
- Load time: 2.4 seconds
- Requests: 34
- Page size: 1.9 MB
- Performance grade: 92/100
The final version reduced the page size, reduced requests, improved the performance grade, and kept the website much faster than where it started.
Google PageSpeed Improvements
Google’s lab data also showed meaningful improvement.
Before optimization:
- Largest Contentful Paint: 5.7 seconds
- Cumulative Layout Shift: 0.002
- Total Blocking Time: 450 milliseconds
After optimization:
- Largest Contentful Paint: 4.2 seconds
- Cumulative Layout Shift: 0.002
- Total Blocking Time: 60 milliseconds
The biggest improvement was Total Blocking Time.
That number dropped from 450 milliseconds to 60 milliseconds, moving from “Needs Improvement” to “Good.”
In practical terms, the site became more responsive for visitors.
This matters because visitors do not experience a website as a technical score. They experience it as waiting, clicking, scrolling, reading, and deciding whether to take the next step. A faster website makes that experience smoother and gives visitors fewer reasons to leave.
It also matters for organic search because search engines want to send people to pages that are useful and usable. A strong technical foundation helps search engines crawl, evaluate, and recommend a website with more confidence.
Why This Matters for Organic SEO
Organic SEO is often discussed as if it only involves keywords, titles, and blog posts.
Those things matter. But they work best when the website has a solid technical foundation.
A slow or cluttered website can limit the value of future SEO work. If the site loads slowly, has outdated server settings, carries old plugin code, or contains years of database clutter, then content improvements are being built on unstable ground.
Website speed is part of that foundation. Search engines want to provide results that help people quickly find what they need. If two websites offer similar information, the one that loads faster and provides a smoother experience often has the better practical advantage.
Fast loading also supports the human side of SEO. Visitors are more likely to stay on a fast website, move through multiple pages, and complete important actions such as calling, submitting a form, or reading more information. Those behaviors help a website do its job better.
For this project, the SEO value came from strengthening the foundation.
We improved:
- Site speed
- Server performance
- WordPress stability
- Database health
- Page weight
- Request count
- Responsiveness
- Long-term maintainability
That gives future organic SEO work a better chance to succeed.
The Practical Lesson
This project is a good example of what organic SEO often looks like behind the scenes.
It is not always glamorous.
Sometimes it means finding an old plugin conflict. Sometimes it means cleaning thousands of orphaned database entries. Sometimes it means testing PHP changes carefully. Sometimes it means comparing Pingdom results against Google PageSpeed results and making a judgment call.
But that work matters.
A website that loads faster, responds better, and runs on a cleaner WordPress environment is a better website for visitors. It is also a better website for search engines.
Fast loading is especially important because it affects the first impression a visitor has of the business. Before someone reads the content, sees the design, or understands the services, they experience the speed of the page. A fast website feels more professional, more trustworthy, and easier to use.
Final Thoughts
For this Michigan law firm, Traverse City Web Design helped turn an older, slower WordPress environment into a cleaner, faster, better-optimized website.
The site went from load times over 5 seconds to a final tested load time around 2.4 seconds, with caching tests reaching under 2 seconds. Page requests were cut nearly in half. Page size was reduced. Google’s Total Blocking Time improved dramatically. The database was cleaned. The server environment was modernized.
That is organic SEO in practical terms with real results.
