Website

Tune WordPress caching and speed settings safely, with before/after test

A safe, approved change plan for your WordPress speed settings, with Core Web Vitals measured before and after.

When to use it

When your WordPress site feels slow on mobile and you want to speed it up without breaking forms or call buttons.

What you get

A reviewed set of up to 5 speed setting changes, applied only after your approval, with a before/after Core Web Vitals table.

Does it change anything in my account?

Only with your approval. The assistant first shows a preview of every change and waits for your go-ahead.

Works with

WordPress, SEO Intelligence

Fill in before sending

[site][main service page URL]

My WordPress site [site] feels slow on mobile, and that is where my phone leads come from. Improve its speed settings without breaking the site. 1. Read the current setup with wordpress_performance. I want to know which caching plugin runs, which optimisations are on, and which ones are flagged as risky for this site. 2. Measure a baseline with core_web_vitals on mobile for these pages: the homepage, [main service page URL] and the contact page. Report LCP, INP and CLS. 3. Propose up to 5 setting changes. For each change, give the expected effect and the risk level. Leave out anything flagged as risky, such as aggressive JS delay that can break call buttons or forms. 4. Show me the exact changes as a preview and wait for my approval. Do not apply anything before I confirm. 5. After I approve, apply the changes, purge the cache and re-run core_web_vitals on the same pages. 6. Give me a before/after table. If any metric gets worse, or the click-to-call button or the form stops working, tell me right away. Then offer to undo the change in one step.

My WordPress site [site] feels slow on mobile, and that is where my phone leads come from. Improve its speed settings without breaking the site.

1. Read the current setup with wordpress_performance. I want to know which caching plugin runs, which optimisations are on, and which ones are flagged as risky for this site.
2. Measure a baseline with core_web_vitals on mobile for these pages: the homepage, [main service page URL] and the contact page. Report LCP, INP and CLS.
3. Propose up to 5 setting changes. For each change, give the expected effect and the risk level. Leave out anything flagged as risky, such as aggressive JS delay that can break call buttons or forms.
4. Show me the exact changes as a preview and wait for my approval. Do not apply anything before I confirm.
5. After I approve, apply the changes, purge the cache and re-run core_web_vitals on the same pages.
6. Give me a before/after table.

If any metric gets worse, or the click-to-call button or the form stops working, tell me right away. Then offer to undo the change in one step.

Open in Claude Open in ChatGPT Discuss in the forum

More prompts

WebsiteChanges after your approval

Rewrite meta titles and descriptions for pages with low organic CTR

Finds page-one pages that get impressions but few clicks, compares them to your site-wide CTR, and rewrites their meta title and description around the queries that actually bring them traffic.

When to use itWhen your pages rank on page one and get impressions but few clicks, so your titles and descriptions are probably not convincing.

Use Search Console property [Search Console property] and WordPress site [WordPress site].

Step 1. Baseline. Pull the last 90 days with dimension "date" and add up total clicks and total impressions. Site average CTR = total clicks / total impressions. Show this number first.

Step 2. Candidates. Pull the last 90 days by page, sorted by impressions. Keep pages with at least 500 impressions, an average position between 1 and 10, and a CTR below 2%. Take the top 10 by impressions.

Step 3. For each of those 10 pages:
- Pull the queries for that page only (dimension "query", filtered to the page URL, sorted by impressions) and keep the top 5.
- Find the matching WordPress post or page ID by searching for its slug. If a URL has no clear match (archive, category, home page), mark it and move on.
- Read its current meta title and meta description from the SEO plugin.

Skip any page whose current title already contains its main query AND whose CTR is within 20% of the site average from Step 1. Say why you skipped it.

Deliver a table with these columns: URL, post ID, impressions, CTR, position, main queries, current title, current description, proposed title, proposed description.
- Proposed title: max 60 characters, main query near the start.
- Proposed description: max 155 characters, one concrete benefit and a call to action.
- Use only facts that are on the page. Do not invent prices, guarantees or numbers.

This table is the preview. Do not write any SEO field until I approve. After I approve, write only the approved rows (overwrite the existing values only for those rows), then purge the cache so the new tags go live, and read the SEO fields back for each changed page to confirm they landed.

WebsiteChanges after your approval

Rebuild the site menu around pages that actually convert

Matches GA4 landing-page performance against your WordPress menus, flags valuable pages missing from the navbar, dead weight and broken links, and proposes a leaner main menu.

When to use itWhen your site menu feels cluttered or outdated and you suspect it does not point visitors to the pages that actually bring conversions.

Compare my navigation menu with what actually converts.

From GA4 property [GA4 property], pull the last 90 days by landing page: sessions and key events. Calculate key event rate as key events / sessions.

Then read every menu on [WordPress site], including the main navbar and the footer, with all their links.

Match menu links to GA4 rows by URL path (ignore the domain, trailing slashes and query strings). Where a link has no GA4 row, treat it as zero sessions and say so.

Check every menu link for problems:
- Fetch each linked URL and record its HTTP status. Anything 4xx or 5xx is broken; redirects are worth noting.
- Flag links that point to draft or private pages, to old slugs, or to http instead of https.

Deliver three lists:
1. Pages with at least 20 key events that are not in the main menu.
2. Menu links pointing to pages with fewer than 50 sessions or zero key events in 90 days.
3. Broken or outdated links, with the reason for each.

Then propose a new main menu:
- Max 7 top-level items, ordered by commercial importance.
- Exact labels of 2 to 3 words, in plain language a customer would use.
- The contact page stays as the last item.
- Move low-value pages to the footer menu instead of deleting them.

Show the current menu and the proposed menu side by side, with the exact list of menu actions you would run (add, rename, relink, reorder, remove), as a preview. Do not edit anything until I approve. After approval, apply the changes, purge the cache and read the menus back to confirm the final structure.

WebsiteChanges after your approval

Plugin and tracking health check before it breaks your conversions

A plugin-by-plugin action list that flags outdated, duplicate and conflicting plugins and double-firing tags.

When to use itWhen your WordPress site has too many plugins, updates piling up, or you fear duplicate tags are inflating the conversions your ads optimize toward.

WebsiteChanges after your approval

Replace an old phone number everywhere on the site, safely

A full map of where the old number appears, a dry-run diff of the bulk replace, and a list of places that need manual fixes.

When to use itWhen your phone number has changed and you need to be sure the old one no longer shows anywhere on your website.