Afrexai Web Performance Engine

What This Skill Does

The Afrexai Web Performance Engine by 1kalin is a comprehensive suite designed for web developers, SEO specialists, and site maintainers to audit, diagnose, and optimize web performance without needing a massive stack of paid tools. It centralizes performance management by providing a structured, tiered approach to identifying bottlenecks—ranging from critical rendering blocks to minor polish issues. The engine maps the performance waterfall (DNS, TTFB, CSSOM, LCP, etc.) and provides a clear decision tree to resolve issues systematically. It supports manual analysis via external tool integration like Google PageSpeed Insights and WebPageTest while providing a standardized YAML-based report format to track page weight, request distribution, and Core Web Vitals.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/1kalin/afrexai-web-performance-engine Ensure you have active internet permissions enabled, as the skill may perform external API calls to fetch performance metrics from third-party services.

Use Cases

• Pre-Launch Audits: Perform a full Tier 1-3 scan to ensure a new site release meets SEO and user experience standards.
• Bottleneck Diagnosis: When users report a slow site, use the included decision tree to determine if the issue is server-side (TTFB), blocking resources (FCP), or interaction-heavy (INP).
• Competitor Benchmarking: Analyze competitors to see how their resource distribution (JS, CSS, Images) compares to your own.
• Legacy Optimization: Systematically reduce page weight and request count on bloated legacy applications.

Example Prompts

1. "Run a Tier 1 performance audit on https://example.com and tell me if the LCP issue is related to the hero image or layout shift."
2. "I am seeing a TTFB of 1.2s on my staging site. Based on the Web Performance Engine, what server-side checks should I prioritize?"
3. "Can you generate a summary report in YAML format for my current project, detailing the total JS weight and third-party request count?"

Tips & Limitations

• Manual Context: While the skill provides a clear logic tree, it relies on your input or integration with external tools like Lighthouse. If data isn't provided, use the suggested web_fetch commands to gather the baseline.
• Tiered Focus: Don't get distracted by 'Polish' issues (Tier 3) until your 'Critical' issues (Tier 1) are resolved. A site with a high CLS needs priority over font loading improvements.
• Accuracy: Ensure the 'device' and 'connection' fields in the YAML template match your target audience profile for the most accurate diagnostic results.