Website

Tune WordPress speed settings with before/after measurement

A prioritised list of WordPress speed optimisations, applied one at a time after approval and re-measured, with rollback if anything gets worse.

When to use it

When your WordPress site feels slow or fails Core Web Vitals and you want safe speed fixes with proof they worked.

What you get

A before/after table of mobile Core Web Vitals after up to 5 approved speed changes, with any change that made things worse rolled back.

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][key landing page URL]

On WordPress site [site], show the current speed setup: - which caching plugin is running - which optimisations are on - which optimisations are flagged as risky on this site Also list the active plugins that have updates waiting. Measure mobile Core Web Vitals for the homepage and for [key landing page URL]. This is the baseline. Propose up to 5 changes, such as page cache, image lazy-load, deferring JS, or minifying CSS. Order them by expected impact on LCP and INP. Leave out anything flagged as risky on this site. For each change, give: - what it does - which metric it should improve - what could break Show me the full plan and wait for my approval. After I approve, work as follows: 1. Apply the approved changes one at a time. 2. After each change, purge the cache. 3. Check that both pages still return HTTP 200 and that the HTML still renders the main content. 4. Re-measure both pages. If any metric gets worse, or a page breaks, undo that change immediately and tell me. End with a before/after table.

On WordPress site [site], show the current speed setup:
- which caching plugin is running
- which optimisations are on
- which optimisations are flagged as risky on this site

Also list the active plugins that have updates waiting.

Measure mobile Core Web Vitals for the homepage and for [key landing page URL]. This is the baseline.

Propose up to 5 changes, such as page cache, image lazy-load, deferring JS, or minifying CSS. Order them by expected impact on LCP and INP. Leave out anything flagged as risky on this site.

For each change, give:
- what it does
- which metric it should improve
- what could break

Show me the full plan and wait for my approval.

After I approve, work as follows:
1. Apply the approved changes one at a time.
2. After each change, purge the cache.
3. Check that both pages still return HTTP 200 and that the HTML still renders the main content.
4. Re-measure both pages.

If any metric gets worse, or a page breaks, undo that change immediately and tell me. End with a before/after table.

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.