What to Ask a WordPress SEO Agency About Plugins and Site Speed

Before hiring a WordPress SEO agency, ask how it will decide which plugins to keep, prove what slows your pages and make changes without breaking enquiries or sales. A recommendation to install another optimisation plugin is not a diagnosis.

For a Canadian business, the useful outcome is a dependable mobile website that lets customers find a service, submit a form or complete a purchase. A higher performance score matters only alongside those outcomes, not instead of them.

Use the questions below in discovery calls and request written answers in the proposal. You are looking for a clear baseline, a prioritised implementation plan and evidence that the agency can work safely inside your WordPress setup. Keep the same questions for every bidder so you can compare the work being offered, rather than the confidence of the sales pitch.

What should a WordPress SEO agency inspect before recommending plugins?

Expect the agency to investigate your actual site before prescribing a plugin stack. That means reviewing representative pages, the active theme, the hosting environment and existing performance tools, not just running the homepage through a scanner.

The starting inventory should record each active plugin’s purpose, licence owner, maintenance status and dependencies. Include must-use plugins and features supplied by the host, because they can affect caching even when they are absent from the usual plugin list.

Ask: “Which finding would make you recommend configuration changes rather than a new plugin?” A useful answer might identify duplicate caching, an oversized homepage image or a chat widget loading across every page.

Also ask how the agency separates technical SEO from performance work. An XML sitemap can support discovery, but it will not fix slow server responses. Likewise, a faster theme does not resolve incorrect canonical tags.

If you need background on the underlying settings, MarketingFlow’s WordPress SEO guide explains the wider setup. In the proposal, however, insist on site-specific findings: affected URLs, observed symptoms, recommended action and who will implement it. A generic checklist is not evidence that your site has been assessed.

Request read-only discovery access where possible. Credentials should be shared securely, and an initial audit should not require unrestricted permission to modify your live website or purchase new software.

Which plugins are necessary, duplicated or risky?

Your WordPress SEO agency should justify plugins by function and measured impact, not promise an arbitrary maximum number. Five resource-heavy extensions can cause more trouble than twenty lightweight ones.

Ask which system owns each overlapping task:

You generally want one clearly identified owner for each function. That does not mean one plugin must do everything. For example, an SEO plugin can coexist with a separate performance tool when their responsibilities are clear.

Names such as Yoast SEO, Rank Math or All in One SEO are not proof of a strategy. Ask why a particular option fits your requirements and what changes if you keep your current tool.

If a switch is proposed, request a migration plan for metadata, redirects and structured data settings. Uninstalling the old plugin first can remove settings you still need.

The agency should also explain what happens when a premium licence expires or its relationship with you ends. A site should not quietly lose an important function because a subscription belongs to someone else.

Ask how unused plugins will be retired safely. Deactivation, deletion and database cleanup are different steps; settings or shortcodes can remain in content, so removal needs a dependency check and backup.

How will you prove what is actually slowing the site?

Ask your WordPress SEO agency for a test plan that distinguishes the server, theme, plugins and third-party scripts. “WordPress is slow” is not an actionable finding.

The plan should cover a small set of meaningful templates: homepage, service page, article and lead form. Add product, category, cart and checkout pages for a store. Test mobile layouts and logged-out visitors rather than relying on an administrator’s browsing experience.

Record the test URL, tool, date, location, device profile and cache state. Repeat comparable runs, since one unusually fast test can flatter the result. Request both first-visit behaviour and repeat-visit behaviour where relevant.

For suspected plugin problems, ask how the agency will isolate the cause in staging. A controlled disable-and-retest exercise can help, but removing a dependency without checking its effects proves very little.

Browser network traces and server diagnostics should support the recommendation. A slow initial response may point towards hosting or uncached work; a page that arrives quickly but remains unresponsive may have excessive JavaScript.

For a store, ask for an uncached test as well. A fast cached homepage can hide the slower requests shoppers encounter when searching products, updating quantities or moving through checkout.

The deliverable should be a short chain of evidence: symptom, likely cause, proposed change and validation method. If the agency cannot explain that chain in plain language, you cannot meaningfully approve the work.

Which site speed targets will you use?

A WordPress SEO agency should distinguish real-user experience from a laboratory score. The Core Web Vitals reference defines three good-experience thresholds:

The thresholds are assessed at the 75th percentile, with mobile and desktop considered separately. A single successful test does not establish that visitors meet them.

Ask whether reporting uses URL-level Chrome User Experience Report data or broader origin-level data. An origin combines experiences across a site and must not be presented as proof that one specific landing page improved. Lower-traffic pages may lack sufficient public field data.

CrUX field reporting reflects a rolling 28-day window, so it will not instantly reflect a deployment. Lab tests are useful for diagnosing changes immediately, but a standard Lighthouse page-load run does not directly measure real-user INP.

A credible commitment is to named improvements and validation, not a guaranteed green score on every device. Google’s ranking guidance also makes clear that good Core Web Vitals do not guarantee top rankings.

What changes will you make to caching, hosting and the theme?

Ask the WordPress SEO agency to explain what each proposed change fixes before agreeing to a hosting migration or theme rebuild. Those projects can be justified, but they should not be default upsells.

Page caching can reduce repeated work for public pages. An object cache may help repeated database operations. Neither automatically fixes a large hero image, an overloaded page builder or a third-party booking script.

Request an explanation of cache exclusions and invalidation. If your address or opening hours change, how quickly will visitors see the update? Who clears the relevant caches, and how is that checked?

For ecommerce, cart, checkout and account experiences require careful handling. Some plugins also depend on dynamically generated values, so the correct rules depend on the implementation rather than a universal settings recipe.

A content delivery network can help deliver static assets across distances. It does not automatically resolve slow server processing. Ask where tests will run relative to your customers instead of assuming that Canadian hosting alone guarantees speed.

If database cleanup is proposed, ask exactly what will be deleted and how recovery works. Removing expired temporary data is different from deleting order records, customer information or settings used by active plugins.

Finally, request a separate price for structural work. A full rebuild should come with evidence that smaller changes would not reasonably solve the problem, plus a migration plan that preserves important URLs and SEO settings.

How will you protect forms, bookings and measurement?

Ask your WordPress SEO agency what it will test after changing image loading, script execution or CSS delivery. An optimisation that breaks your main enquiry form is not a successful release.

A test plan should include mobile navigation, click-to-call links, form validation, confirmation messages and actual message delivery. If you use online payments or scheduling, include a complete transaction in an appropriate test environment.

Pay particular attention to JavaScript delay. A booking calendar might appear only after someone interacts, while a delayed analytics tag can change which visits or conversions get recorded. Compare tracking behaviour before and after the change so a measurement failure is not mistaken for improved conversion rates.

Ask whether prominent images will be excluded from lazy loading when appropriate. Deferring the main above-the-fold image can make the page feel slower, even if other assets load later.

Consent tools, spam protection and security controls also belong in functional testing. The agency should explain any proposed trade-off, rather than disabling safeguards to improve a score.

Ask whether accessibility checks are included when replacing menus, sliders or interactive elements. A faster interface that customers cannot operate with a keyboard or assistive technology still fails the business objective.

Get written acceptance criteria: which actions must work, on which page types and devices, and who confirms the result before the change goes live.

Who deploys changes and how are failures reversed?

The WordPress SEO agency should name the person responsible for implementation, not leave you between an SEO consultant, a developer and your host when something breaks.

Ask to see the release workflow. It should include a current backup, a staging test where practical, approval for material changes and a defined rollback process. Establish who can authorise an urgent reversal and how they can be reached.

A rollback must suit the site. Restoring an old database on a busy store can overwrite new orders; reverting code or configuration may be safer. The agency should explain how it will protect new transactions and form submissions during recovery.

Staging needs its own controls. It should not become an indexable duplicate of your live site, and staging restrictions must not accidentally reach production. Production checks should include crawlability, canonical tags and important redirects, not just appearance.

Request a change log showing what changed, when, why and which checks passed. Agree on monitoring after deployment and the response window if a customer reports a failure.

If another developer maintains your site, clarify who owns compatibility fixes and routine updates. Otherwise, an approved performance change can be overwritten during the next theme update.

For plugin updates, ask whether automatic updates are enabled and which components require review first. The answer should balance security, compatibility and the availability of someone to investigate failures.

What evidence shows that your speed work helped?

Request an anonymised before-and-after example with comparable conditions, not just a screenshot of a high score. The agency should identify the original problem, the actual change and any remaining limitations.

A strong example separates three outcomes: technical improvement, search visibility and business results. Faster pages may improve usability without immediately changing rankings. Traffic can also rise because of new content or seasonal demand, so timing alone does not prove causation.

Ask which page templates improved and whether the results held after normal plugin updates. Where permissions allow, confirm the scope with a client reference. Never assume that an attractive case study involved the same WordPress setup or level of access as yours.

Your own reporting should keep performance metrics beside organic landing-page traffic and completed enquiries or purchases. For phone-driven businesses, record useful call outcomes where feasible rather than treating every tap as a qualified lead.

Ask the WordPress SEO agency to annotate deployment dates in its reports. Changes in consent settings, analytics tags or call tracking must also be documented, because they can alter reported totals.

Monthly reporting should show what was implemented, what remains blocked and what happens next. A dashboard without that explanation makes it difficult to judge whether the underlying problem is being solved.

Have the agency show one improvement that did not work as expected. A specific explanation of testing, rollback and revised diagnosis is more useful than claiming every optimisation delivers an immediate win.

How does the plan reflect Canadian local customers?

An agency serving Canadian businesses should connect performance priorities to the locations and actions that matter. A nationwide retailer and a local drain specialist do not need identical testing plans.

Consider a homeowner searching for drain and sewer services in Kingston during a backup. For that type of visit, a readable service page, a working phone link and clear service-area information matter more than an animated banner. That priority applies regardless of whether the underlying site uses WordPress or another platform.

Ask the WordPress SEO agency to test important service and location pages on mobile connections and to keep urgent contact details usable while other assets load. If an embedded map, review widget or chat tool is expensive to load, ask how its value will be weighed against its performance cost.

Google Maps visibility is a separate workstream. A faster website does not replace accurate business information, relevant service content or a properly maintained Google Business Profile.

For bilingual sites, ask how language plugins, alternate-language URLs and caching rules will be tested together. If the proposal includes location-based testing, specify the customer regions that matter rather than accepting “Canada” as a single test location.

These questions reveal whether the agency understands your customers, not just your software.

What does the price include and who owns the work?

The proposal should separate diagnosis, implementation and ongoing maintenance. “Speed optimisation included” is too vague to compare.

Ask your WordPress SEO agency whether the quoted fee covers developer hours, premium licences, image processing, hosting changes and troubleshooting third-party integrations. Identify recurring costs and one-time work, along with any approval threshold for additional spending. Specify who pays for ongoing plugin renewals.

Low-cost SEO packages can be useful, but extensive performance remediation may require separate development work. Compare the actual scope, not a starting price borrowed from a different service.

Ownership should be explicit. Your business should retain control of its domain, hosting, WordPress administrator account, analytics and Google Search Console. Give the agency named, appropriately limited access rather than sharing one master login.

Clarify how custom code and settings are handed over. Request documentation for cache rules, exclusions and any plugin licences that would need replacing after cancellation. Set expectations for removing agency access without disabling your site.

Ask who is responsible for vulnerabilities and compatibility issues after delivery. A one-time fix does not automatically include indefinite monitoring or support for every future plugin update.

The proposal should also state communication frequency, turnaround expectations and what counts as completed work. For your wider evaluation, use MarketingFlow’s framework for comparing SEO providers to keep evidence and deliverables ahead of sales language.

Can you put the plan into one comparable brief?

Send each shortlisted agency the same request. The WordPress SEO agency that answers with specifics will be easier to evaluate than one offering broad assurances.

Keep the brief focused:

• Baseline: Named URLs, mobile and desktop tests, field-data availability and current conversion checks.
• Diagnosis: Evidence for the main bottlenecks and a plugin inventory with overlapping responsibilities identified.
• Implementation: Prioritised changes, expected benefits, responsible person and dependencies.
• Safety: Staging, backups, rollback details and functional acceptance tests.
• Commercials: Fees, licences, access ownership, reporting and post-launch support.

Ask the agency to rank proposed changes by likely impact, effort and risk. That helps distinguish a small configuration fix from a project that needs development time.

You can also request a limited paid diagnostic before approving a rebuild. Its deliverable should stand on its own, with findings that you can give to another developer if needed. Avoid an arrangement where the diagnosis remains hidden unless you buy the larger package.

Compare answers against your actual constraints: budget, available developer support, busy trading periods and the features customers rely on. The best proposal is the one you can safely execute and verify.

Frequently asked questions

Do I need an SEO plugin and a speed plugin? Not necessarily. Ask your WordPress SEO agency to inventory existing tools first. An SEO plugin manages tasks such as metadata and sitemaps, while performance tools address different problems. Your host may already provide caching.

Should an agency promise a 100 PageSpeed Insights score? No. A lab score varies with test conditions and does not guarantee good real-user experience, more enquiries or higher rankings. Request agreed performance targets and functional checks instead.

Can I keep my existing theme and page builder? Often, but the answer needs testing. Ask which measured limitations require replacement and whether image, script or configuration changes would deliver a reasonable improvement without rebuilding.

How much should I budget for specialist help? There is no single price for a specialist engagement. An audit, monthly SEO support and custom development are different scopes. Request itemised costs, licence obligations and the approval process for additional work.

How soon should performance improve? A deployed fix can show up in lab testing immediately. Public field data takes time to reflect new visits, and organic search or lead changes follow no guaranteed timetable. Separate release validation from longer-term outcome reporting.

Request a diagnosis before approving more plugins

Choose a WordPress SEO agency that can explain what is wrong, show how it knows and protect the customer actions that keep your business running.

MarketingFlow offers technical optimisation, local SEO and monthly performance reporting for businesses across Canada, with SEO plans starting at $99 per month and no long-term contracts. Confirm the scope and pricing for any WordPress development or specialist performance work rather than assuming it is included in an entry-level plan.

If you need implementation support, discuss your priorities through MarketingFlow’s technical SEO services. Bring your key landing pages, current plugin list and enquiry or sales goals. Ask for a prioritised plan with named responsibilities, testing requirements and clear costs before approving changes.