Page Speed Optimizer
Analyze and optimize page speed metrics to improve user experience and search engine rankings.
Use This When
Articles, service pages, AEO/GEO content, interlinking, SERP-informed briefs.
Inputs Needed
URL, target keyword, audience, competitors, location, search intent, internal links, products/services.
Expected Output
SEO brief or content draft with search intent, outline, on-page elements, internal links, FAQ, schema suggestions.
The Workflow Prompt
You are a technical SEO strategist and editorial content lead. Objective: Page Speed Optimizer Context: Analyze and optimize page speed metrics to improve user experience and search engine rankings. Original task: You are a world-class Core Web Vitals and page speed expert who has improved site speed for 1,000+ websites, resulting in 20-45% traffic increases from speed improvements alone. Your expertise includes server optimization, caching strategies, image optimization, code minification, JavaScript optimization, rendering optimization, and Core Web Vitals mastery. You understand the technical relationships between server infrastructure, code performance, and user experience metrics.Create a comprehensive page speed optimization plan for [YOUR_DOMAIN]. Deliver:1. **Current Performance Audit**: Conduct full-page speed analysis using PageSpeed Insights, GTmetrix, and real user data (CrUX); benchmark against competitors2. **Core Web Vitals Analysis**: Measure LCP (Largest Contentful Paint), FID (First Input Delay), and CLS (Cumulative Layout Shift); identify problematic pages3. **Server Response Time Optimization**: Analyze TTFB (Time to First Byte); recommend server/hosting improvements, CDN implementation, and database optimization4. **Caching Strategy**: Design comprehensive caching strategy (browser cache, server-side caching, reverse proxy caching, CDN caching)5. **Image Optimization**: Audit all images; recommend format conversion, responsive sizing, lazy loading, and compression6. **JavaScript Optimization**: Identify render-blocking scripts; recommend bundling, code splitting, defer/async loading, and third-party script management7. **CSS Optimization**: Minimize CSS, remove unused styles, inline critical CSS, and recommend code-splitting strategies8. **Font Optimization**: Optimize web fonts through subsetting, preloading, system fonts, and variable font implementation9. **Third-Party Script Audit**: Analyze third-party tools (analytics, ads, tracking); recommend optimization, removal, or deferred loading10. **Rendering Optimization**: Identify layout shifts, paint events, and composite opportunities; recommend optimization techniques11. **Mobile Speed Optimization**: Address mobile-specific performance issues and optimize for mobile traffic patterns12. **Technical Implementation Plan**: Provide prioritized list of changes with estimated impact, ease of implementation, and timeline Inputs I may provide: URL, target keyword, audience, competitors, location, search intent, internal links, products/services. Operating instructions: - First, restate the objective in one clear sentence. - If critical information is missing, ask up to 5 focused questions. If there is enough information to proceed, make practical assumptions and label them. - Use a Detailed response style. - Be specific to the business, audience, channel, and constraints provided. - Avoid generic AI advice. Give concrete recommendations, examples, templates, copy, or steps I can use. - When current facts, competitors, laws, prices, policies, or market claims matter, use current research and cite sources. - Do not expose hidden chain-of-thought. Provide a concise rationale or decision summary instead. - End with a short QA checklist that helps me verify the output. Required output: SEO brief or content draft with search intent, outline, on-page elements, internal links, FAQ, schema suggestions. Caution: Use live web research or source documents before finalizing claims.
QA Follow-Up Checklist
After the AI returns its output, verify against:
- Output is specific to the provided business/context.
- Assumptions are clearly labeled.
- No unsupported claims without source checks.
- Next actions are clear and usable.
- Search intent, internal links, FAQ, and on-page elements are included.
Follow-Up Prompt
Now turn the result for 'Page Speed Optimizer' into a client-ready version: tighten wording, remove fluff, add missing assumptions, and provide the next 3 actions.
Avoid / Cautions
Use live web research or source documents before finalizing claims.
How Different Verticals Use This Workflow
Restaurant & Hospitality
A 12-location restaurant chain's online ordering page loads in 6.2s on mobile and abandons 38% of carts before submit. The audit identifies three killers: a 1.8MB hero video, a chat widget loading on every page, and an unused analytics script from a 2022 vendor. Two days of dev work drops LCP to 2.1s, mobile cart completion lifts 22%, and weekly online order revenue moves from $84K to $103K — the audit pays for itself in week one.
Retail & E-commerce
A Shopify store doing $4M/year fails Core Web Vitals on 60% of product pages because of a stacked review widget, a wishlist app, and an Instagram feed embed. The audit prioritizes a lazy-loading rebuild of the PDP template that holds all three but defers everything below the fold. Mobile LCP moves from 4.1s to 1.9s, organic traffic to category pages lifts 18% over three months, and bounce rate drops 9 points.
Professional Services & B2B
A B2B SaaS marketing site has a beautiful homepage that takes 8s to load on mobile because of an autoplaying video, embedded Hubspot forms, and a Calendly widget firing on initial paint. The audit recommends a static image hero with a video CTA, defers the Hubspot script until form interaction, and removes the persistent Calendly. Time-on-page lifts 31%, demo-form conversion lifts 14%, and the marketing team stops getting 'site is slow' complaints from sales reps in the field.
Beauty & Personal Care
A boutique skincare brand's product pages are gorgeous and unusable — 22 high-res images per PDP, an Instagram shoppable feed, and a quiz widget. The audit converts hero images to WebP with proper srcset, lazy-loads everything below the first viewport, and replaces the quiz widget with a lighter alternative. LCP improves from 5.8s to 2.0s on mobile, organic traffic to PDPs lifts 28%, and the brand reclaims a top-3 ranking for their best-selling SKU.
Local & Trade Services
A regional roofing company's lead form page takes 7s to load on mobile and ranks #6 for their most valuable local term. The audit fixes a render-blocking jQuery dependency, compresses three before/after gallery images, and removes a Facebook pixel firing twice. Mobile LCP drops to 2.3s, the page moves from #6 to #3 over six weeks, and lead form submissions lift 41% — at a $9K average job value, that's $180K+ in new pipeline from a $4K audit.
Frequently Asked
What's the realistic traffic uplift to expect from a serious page speed project?
5-15% on organic traffic for most sites already at 'okay' speed, 25-40% on sites currently failing Core Web Vitals on mobile. Anyone promising more is selling a fantasy or has cherry-picked a single page case study. The bigger win is usually conversion rate — a 1-second improvement on mobile checkout typically lifts CR 7-12% on ecom, which dwarfs the SEO impact in revenue terms.
What input data does this prompt actually need to give a useful answer?
Your real CrUX data (not just a one-time PageSpeed Insights run, which lies), your CMS or framework name, your CDN setup, and the top 5 pages by traffic. Without CrUX you're optimizing for synthetic Lighthouse scores that don't reflect what real users on real networks experience — and Google ranks based on real user data, not lab scores.
Should I run this audit before or after a redesign?
Before — every time. Speed budget gets set during scoping or it never gets set at all. After-the-fact speed optimization on a freshly launched site that ships with 14 third-party scripts is six months of triage. Build the audit into the design brief: 'mobile LCP under 2.5s on a Moto G4 over 4G is a launch gate.' Designers and devs will hate you in week one and thank you in month three.
When is page speed the wrong thing to be optimizing?
When your site already passes Core Web Vitals on the pages that matter and you're below a 50K monthly visitor floor. At that scale, content gaps and link authority drive 10x more traffic than shaving 200ms off LCP. Speed work is a marginal lever once you're at the threshold — the absolute ROI is in content and links until you're competing for genuinely contested keywords.