Aubrey Portwood  ## Metadata - Author: [[Aubrey Portwood]] - Full Title: Aubrey Portwood - Category: #articles - Document Note: --- tags: - #wordpress - #freelancing - #performance Author: Aubrey Portwood Source: Personal website Reference: https://aubreypwd.com/?p=6873 date created: 2025-09-17 00:00 --- # Title: Freelancing? — Exploring WordPress Performance as an Independent Path ## Table of Contents: - 🔗 [📝 Summary](#-summary) - 🔗 [📖 Main Content](#-main-content) - 🔗 [🗒️ Notes](#️-notes) - 🔗 [📖 References](#-references) - 🔗 [🗣️ Paraphrase](#️-paraphrase) - 🔗 [📰 Newsletter](#-newsletter) - 🔗 [✅ Action Items](#-action-items) - 🔗 [🧪 Hypotheses](#-hypotheses) - 🔗 [📊 Methodology](#-methodology) - 🔗 [❓ Questions](#-questions) - 🔗 [🔮 Future Research](#-future-research) - 🔗 [💡 Implications](#-implications) - 🔗 [🧠 Learning Styles Assessment](#-learning-styles-assessment) - 🔗 [📊 Accessibility Assessment](#-accessibility-assessment) - 🔗 [🌍 DEIB Assessment](#-deib-assessment) - 🔗 [✅ Logical validity](#-logical-validity) - 🔗 [🔍 DARVO Analysis](#-darvo-analysis) - 🔗 [🔍 SEO Evaluation](#-seo-evaluation) - 🔗 [🎯 Conclusion](#-conclusion) ### References: - Aubrey Portwood, “Freelancing?” (personal blog post). Link above. ## 📝 Summary: Aubrey reflects on seriously exploring freelancing for the first time, specifically as a WordPress optimization and performance specialist. He lists long-standing hesitations (survival, collaboration, finances, business ops, non-core work, comfort with current job), then outlines a focused service area (Core Web Vitals, server/WordPress/code optimizations, bug fixing). Two paths emerge: join an agency/host to do this work, or start a business. After connecting with practitioners—all business owners—he leans toward freelancing, guided by excitement during a sabbatical, committing to learning via books, videos, conversations, and trial gigs. He credits creators like Daya for impactful guidance and invites others to check them out. ## 📖 Main Content: Aubrey frames freelancing as a deliberate exploration rather than a public solicitation. He defines a niche in WordPress performance, from Core Web Vitals to low-level server and code tuning, emphasizing problem-solving joy (bug fixing). He contrasts employment (constraints, AI-era direction-setting) with independence (agency, alignment). Emotional signals—excitement—serve as heuristics during a sabbatical. He adopts a learning-first approach: resources, mentorship, and small experiments to test fit. Community influences (e.g., Daya’s content) provide models and confidence. ### 🗒️ Notes - Decision context - Not an open call for gigs; a learning phase. - Longstanding fears: survivability, collaboration fit, finances, operations, scope creep, comfort inertia. - Niche clarity - Core Web Vitals focus. - Server and WordPress-level optimizations. - Code performance and bug remediation. - Outcome: “getting your site to run its best.” - Path options - Agency/hosting employment vs. independent business. - Concern: external direction-setting, especially amid AI-driven mandates. - Learning approach - Books, YouTube, conversations with freelancers. - Trial freelance gigs to evaluate personal fit. - Signal-based decision-making: follow excitement during sabbatical. - Community influence - Practitioners he admires mostly run their own business. - Daya’s content singled out as highly helpful. ## 📖 References: - Aubrey Portwood’s blog post (link above). - Mentions “Daya” as a resource creator (no direct link provided in the article). ## 🗣️ Paraphrase: - Original idea: “I’m not…up for any freelance gigs… I am in the process of looking into it.” - Paraphrase: I’m not announcing availability; I’m intentionally exploring whether freelancing is right for me. - Original idea: “Two options: get a job at an agency/host… or start my own business.” - Paraphrase: The route is either join an org and practice performance under their umbrella, or build an independent practice. ## 📰 Newsletter: This week we’re diving into the indie path for WordPress performance pros. Thinking about Core Web Vitals, server tuning, and surgical code fixes? Many specialists who thrive here run their own shops—citing autonomy and the joy of bug hunting. If you’re on a similar journey, set up small experiments: audit a site’s LCP/CLS, profile queries, trim render-blocking assets, and test server caching layers. Pair that with learning sprints—books, YouTube deep-dives, and conversations with experienced freelancers. One creator consistently recommended lately is Daya, whose practical guidance demystifies pricing, positioning, and pipelines. Wherever you land—agency or solo—optimize for excitement and impact. Bonus: share your favorite Web Vitals wins and the plugins that made the difference (Performance Lab? Query Monitor?). ## ✅ Action Items: Prompt for aligning articles with your advocacy and OSPO trajectory: - For each article, identify: - How the content supports open-source sustainability within WordPress (funding models, contributor pathways, governance clarity). - Concrete tactics for onboarding and retaining contributors (documentation, mentorship ladders, first-issue labeling, async cohorts). - Educational assets you can produce (workshops on PHP/JS/HTML/CSS/Git/GitHub, labs on Core Web Vitals, reproducible demos). - Evidence or case studies to inform OSPO policies (licensing, compliance, security disclosure, metrics for impact). - Transparency and inclusivity commitments (accessible learning materials, code of conduct enforcement, multilingual docs). - External stakeholder alignment (hosts, agencies, plugin authors) and how to orchestrate collaboration. - Calls-to-action for community engagement (office hours, contributor days, mentorship programs). - Measurable outcomes (learning objectives, contributor growth, time-to-first-PR, Core Web Vitals deltas). - Risks and mitigations (maintainer burnout, funding gaps, governance bottlenecks). - Messaging you can use on stage and in writing to connect education with advocacy. ## 🧪 Hypotheses: - H1: Practitioners who follow intrinsic excitement during career pivots achieve higher persistence and satisfaction in freelancing. - H2: Specializing in WordPress performance (Core Web Vitals) increases client acquisition speed versus generalist web dev positioning. - H3: Early community mentorship and resource immersion reduce the ramp-up time to sustainable freelancing revenue. - H4: Trial gigs before full transition improve service-market fit and pricing accuracy. ### 📊 Methodology: - Mixed-methods: - Quant: Survey freelancers on satisfaction, revenue stability, time-to-first-client; correlate with specialization and learning behaviors. - Qual: Semi-structured interviews on decision heuristics (excitement), AI-era autonomy, and community influence. - A/B: Landing page tests comparing niche performance offers vs. general dev offers; measure conversion. - Data sources: WordPress community forums, Slack groups, LinkedIn cohorts, newsletter lists, GitHub activity, Core Web Vitals before/after client metrics. - Analysis: Regression on predictors of sustainability; thematic coding of interview transcripts. ### ❓ Questions: - What minimum viable service package best communicates performance value to non-technical clients? - Where does AI guidance enhance vs. constrain expert judgment in performance work? - Which community channels most effectively translate interest into paying engagements? - How much specialization is optimal before it narrows opportunity? ### 🔮 Future Research: - Longitudinal study of freelancers transitioning from agencies to solo performance practices. - Pricing frameworks tied to Web Vitals outcome guarantees. - Standardized playbooks for WordPress performance audits. ### 💡 Implications: - Can guide training programs, contributor onboarding, and OSPO policy around independent contributors. - Helps agencies and hosts collaborate with specialists on measurable Web Vitals improvements. ### 🧠 Learning Styles Assessment: - Reading level: General professional; approachable and reflective; short-form blog. - Visual: Minimal. Improve with diagrams of performance stacks, before/after Web Vitals charts. - Aural: None. Add audio - Summary: Stoic, Husband, Girl-Dad², Independent WordPress Performance and Optimization Specialist, Tennis Player, & Vintage Computer Tinkerer. - URL: https://aubreypwd.com/?p=6873  [### Freelancing?](https://aubreypwd.com/?p=6873) So I think I need to write this: ***I am looking into freelancing****.* I’m not writing that because I want everyone to know that I am up for any freelance gigs (*quite the contrary*), but that I am in the process of *looking into it*. Freelancing has always been something I wanted to do, but I never tried. There have been a lot of reasons: 1. Will I survive? 2. Can I work with people? 3. Finances 4. Can I run a business? 5. Do I want to do all the *other* work? 6. My job now is fine… …etc. So I’ve never really entertained it. I’ve spent the last few months learning about *what* I want to do—**WordPress Site Optimization & Performance**: * Core Web Vitals * Server Optimizations * WordPress Optimizations * Code Optimizations * Fixing issues with sites (*I’ve always loved fixing bugs*) …just basically getting your site to run it’s best! Now I’m trying to figure out *how* I was going to do that. For me there were two options: 1. Get a job at an agency or hosting company and ask them to let me do this stuff 2. Start my own business As a part of my learning process I have learned *so much* through the people I have connected with that already do the work I want to do…and how do *they* do it? That’s right, most of them (*actually all of them*) run their own business. And so that got me thinking about freelancing again, and all the same fears came up again. The idea of jumping out there into another company who is going to tell me *how* to do things—especially with AI—wasn’t feeling great, and I didn’t know why at first. I have used the sign of *excitement* in this sabbatical to alert me to things I should gravitate towards: and when I started thinking about freelancing I started to feel some excitement around it. This time I decided I was going to do something I never did before: **actually learn about freelancing**. I have the time! So yes, that has meant reading *more* books, watching *more* YouTube videos, and talking with freelancers—and of course *trying out some freelance work!* I just want to learn if I’m cut out for it, because honestly I don’t know, but I’m excited to find out. I can’t say enough how much these resources have helped me just over the past couple of weeks: The content Daya posts—*especially—*has been insurmountable in helping me understand what I might be looking forward to. Check them out if it’s something you’re also looking into… September 17, 2025, Aubrey Portwood, Aubrey Portwood, 01k5cjqd1wykxa6zfet552svdm.