Performance

LCP (Largest Contentful Paint): < 2.5s (what users see as \"loaded\") INP (Interaction to Next Paint): < 200ms (responsiveness) CLS (Cumulative Layout Shift): < 0

SEOContentCRO
bySamuelca63991,214 words

What is Performance?

What this skill does

The Performance skill guides marketers and developers on optimizing Core Web Vitals to improve user experience and search rankings. It focuses on achieving key metrics like Largest Contentful Paint (LCP) under 2.5 seconds, Interaction to Next Paint (INP) below 200 milliseconds for responsiveness, and minimizing Cumulative Layout Shift (CLS) to less than 0.1 for visual stability. The skill covers practical techniques such as image optimization, font loading strategies, CSS performance tuning, and efficient JavaScript handling to reduce load times and prevent layout shifts.

By implementing these optimizations, users can ensure faster page loads, smoother interactions, and stable layouts, which directly impact SEO performance and conversion rates. This skill distills complex front-end performance best practices into actionable steps relevant to content, SEO, and conversion rate optimization (CRO) efforts.

Who it's for

This skill is designed for performance marketers managing SEO and CRO who need to improve page speed and user engagement metrics. Agency strategists working with clients on technical SEO audits will find it valuable for prioritizing frontend fixes that affect Core Web Vitals. Additionally, growth leads coordinating between developers and marketing teams can use this skill to align technical improvements with business goals like reducing bounce rates and increasing conversion velocity.

Key workflows

First, audit the site’s Core Web Vitals using tools like Google PageSpeed Insights or Web Vitals Chrome extension to identify bottlenecks in LCP, INP, and CLS. Next, optimize images by converting to next-gen formats (WebP, AVIF), setting explicit width and height attributes to prevent layout shifts, and applying lazy loading to below-the-fold assets. Then, improve font delivery by preloading critical fonts with WOFF2 format, using font-display swap to avoid invisible text flashes, and limiting font files to reduce payload. Finally, refine CSS and JavaScript by avoiding expensive properties during scroll, deferring non-critical scripts, debouncing event handlers, and batching DOM updates to prevent layout thrashing and improve responsiveness.

Common questions

How do I reduce CLS effectively? Always set width and height on images and media elements and reserve space for dynamic content to prevent unexpected layout shifts. Can I use Google Fonts without hurting performance? Self-host fonts in WOFF2 format and preload them to avoid extra DNS lookups and improve load times. What’s the best way to defer JavaScript? Use the `defer` attribute for non-essential scripts and `async` for independent analytics or third-party scripts to prevent render blocking.

How to use in Metaflow

Attach the Performance skill to any Metaflow agent task that involves SEO audits, content optimization, or frontend performance improvements. The agent will provide targeted recommendations based on Core Web Vitals and practical optimizations for images, fonts, CSS, and JavaScript. Expect actionable insights that translate technical metrics into marketing impact, helping prioritize fixes and monitor performance trends over time. This skill integrates smoothly with workflow steps focused on technical SEO and CRO, enabling data-driven decisions around page speed and user experience.

For broader context, see our roundup of marketing skills claude, and read Claude skills for SEO for related setup guidance.

Related skills

Technical Blog Writing

Technical blog post writing with structure, code examples, and developer audience conventions. Covers post types, code formatting, explanation depth, and developer-specific engagement patterns. Use for: engineering blogs, dev tutorials, technical writing, developer content, documentation posts. Triggers: technical blog, dev blog, engineering blog, technical writing, developer tutorial, tech post, code tutorial, programming blog, developer content, technical article, engineering post, coding tuto

View →

Paywall & Upgrade Flow Optimization

When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users

View →

Social Media Content Engine

When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' or 'grow my following.' Use this for any social media content creation, repurpos

View →

SERP Analysis

SERP analysis techniques for intent classification, feature identification, and competitive intelligence. Use when analyzing search results for content strategy.

View →

Schema Markup & Structured Data

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search

View →

User Onboarding & Activation Optimization

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are si

View →