Plugin, host, freelancer or agency: who should fix it?

Compare four ways to fix a slow site: plugins and tools, your host, a freelancer and an agency. What each can reach, where it falls short, and how to choose.

In this guide

The four routes
What a plugin can and cannot do
What your host can do
Freelancer or agency
Matching the route to the situation
Combining the routes
Keep control of your site
Mistakes to avoid
Check your own page
Sources

The four routes

Route	What it can reach	Where it falls short	Best when
Plugins and tools you run yourself	Page caching, image compression, file minifying, lazy loading, script settings, inside the site	Cannot change the server, the host's limits or the design. Needs your time to choose settings and test	The problems are simple, you are comfortable testing, and the site is not critical
Your hosting provider	Server speed, PHP and database versions, server-level caching, a CDN, sometimes migration	Many plans stop at the server. Little help with themes, plugins, images or scripts	The slow part is the server response, or a plan upgrade or move is likely to help
A freelancer	Diagnosis and fixes across images, scripts, plugins and settings, with one person you can talk to	One person: limited hours, one set of skills, and a risk if they become unavailable	Small and medium sites with a clear list of fixes
An agency or specialist team	The same, plus several skills, process, testing and longer-term care	More structure, and often a longer lead time	Larger or higher-stakes sites, or work that spans design, code and hosting

What a plugin can and cannot do

The WordPress Handbook's optimization page is direct about the first step: deactivate and delete unnecessary plugins, because the number of plugins and their performance has a huge impact. It also points to caching as the quick win. Caching plugins store pages as static files and serve them to visitors, which the Handbook says can improve performance several hundred times over for fairly static pages. It adds that a page with a lot of dynamic content makes caching more complex.

A plugin works inside the site. It cannot change the web server, the version of PHP, the hardware or the distance to your visitors. The Handbook lists those as separate performance factors: the hosting environment, WordPress configuration, software versions, and the number and size of images. A plugin can help with some of them and cannot reach the rest.

Plugins also cost speed. One more plugin is one more bundle of code and settings to understand, and tools that combine, delay or rewrite scripts can break forms and payment pages. See WordPress themes and plugins and WordPress caching.

What your host can do

The Handbook says the techniques open to you depend on your hosting setup:

Shared hosting: the company manages the web server, and you have very little control over server settings.
Managed hosting: a locked-down set of software stacks managed by the provider, with limits on what you can install.
A virtual private server or dedicated server: control of the whole server, and the responsibility that goes with it.

The Handbook also notes that a good hosting provider will upgrade or move your account to an up-to-date server, but not all of them will help you tune it, because that is usually outside what a plan offers. If you cannot do the server tasks yourself, it suggests asking the host, seeking external help such as a freelancer, or choosing managed WordPress hosting. See WordPress hosting for speed and choosing hosting.

Freelancer or agency

Neither is better by default. Both can do excellent or poor work, and the difference lies in how they work, not in what they are called. Compare them on the points that matter to you:

Point	A freelancer	An agency or specialist team
Who does the work	The person you meet	Sometimes someone else. Ask who
Range of skills	The person's own, which may be deep and narrow	Several people with different skills
Availability	One person's calendar	Cover for absence, but possibly queues
Process	Varies widely. Ask for it in writing	Usually more formal, which helps with testing and records
After the project	May be hard to reach later	Often offers ongoing care, at a cost
Risk	Depends on one person	Depends on the team's habits
Fit	Defined jobs on smaller sites	Larger sites, or work that crosses design, code and hosting

Use the questions in questions to ask a speed optimizer with both. The answers matter more than the label.

Matching the route to the situation

Your situation	A sensible start
A small brochure site on a shared host, with slow images and no caching	A caching setting or plugin, image compression, and a host plan check
The server is slow even after caching	Your host, or a move to better hosting
An online store that must keep taking orders	A freelancer or agency with a staging site and a test plan, and care with checkout and caching
A site built with a heavy page builder or theme	A specialist who can judge whether to configure, replace or rebuild. See optimize or redesign
A site that gets slower every few months	An ongoing arrangement or an internal owner, plus budgets and monitoring. See why websites get slower
You want to learn and do it yourself	The Handbook and the guides here, with a freelancer for the hard parts

Combining the routes

Real projects often use more than one. A typical mix:

A specialist diagnoses the site and writes the list of fixes.
The host fixes the server side: versions, server caching, a CDN.
A plugin or built-in setting handles page caching and image compression.
The specialist or you handle the remaining changes, one at a time, with testing. See how to test speed changes safely.
A monitoring routine keeps the gains.

Keep control of your site

Whoever you choose:

Keep accounts in your name: the domain, the host, the CDN and the analytics.
Insist on a backup before any work starts.
Get a written scope and a list of what changed.
Keep a copy of the before and after numbers, measured the same way.
Know how to undo each change.

Mistakes to avoid

Stacking several optimization plugins that do the same job.
Expecting a plugin to fix a slow server.
Paying for a rebuild when the findings call for fixes.
Handing over every login with no scope.
Choosing on price or looks alone.
No plan for after the project.

Check your own page

Run the free audit and sort the top findings by who can fix them: the plugin or a setting, the host, or a specialist. The longest column suggests where to start.

Sources

Optimization in the WordPress Advanced Administration Handbook: performance factors, hosting types, plugins and caching.
Cache in the same handbook: what the different kinds of cache do.