Webmaster (WordPress) for ongoing support — payment per task
Webmaster (WordPress) for ongoing support — payment per task
About the project: website on WordPress (niche: services/delivery). A person is needed “on standby” for edits and performance optimization for PageSpeed/Core Web Vitals (mobile-first).
What needs to be done (upon request)
add/edit pages and blocks (Elementor / WPBakery / ACF);
update texts, photos/banners, meta tags;
minor layout (HTML/CSS), sometimes light JS;
fix layout/script errors, update plugins;
speed optimization (PSI/CWV): critical CSS,
font-display: swap, preload fonts/images,defer/delay JS, lazy-load, WebP/AVIF, DevTools Coverage, config WP Rocket / Autoptimize / Perfmatters + Cloudflare.
Requirements (mandatory)
WordPress (themes/plugins), Elementor or WPBakery, ACF;
confident HTML/CSS, basic JavaScript;
practical experience with PageSpeed/Lighthouse/Core Web Vitals (LCP/INP/CLS);
tools: WP Rocket / Autoptimize / Perfmatters (at least one — confidently), Cloudflare (Brotli/Minify/Cache Rules), Google Tag Manager (delay/consent, basic
dataLayer);attention to detail, quick feedback.
Will be a plus: WooCommerce; GTM server-side (not mandatory).
Format and payment
Payment: fixed for each task, after acceptance (Escrow/Secure agreement).
Guideline for evaluation: 300–600 UAH/hour (for forming a fixed rate). Actual payment — fixed for the terms of reference.
Minimum for a small task: 300–500 UAH (min. billing 30 min).
Process: evaluation (time/price) → confirmation → execution → verification → payment.
If the volume becomes stable — a transition to hourly/subscription may be possible (by mutual agreement).
How to apply
Send:
3–5 links to WP projects with support/optimization;
1–2 cases PSI Mobile “before/after” (screens + briefly what was done);
your minimum price for a small terms of reference and Telegram.
Paid test task: complete optimization of PageSpeed/Core Web Vitals for the entire site
Goal: improve the performance of the entire site (mobile-first).
What to do (briefly)
CSS: critical CSS inline; main styles — async (preload+onload) / Remove Unused CSS.
JS:
defer/delay; third-party (GTM/FB/shares) — after interaction.Images:
loading="lazy"for everything outside the fold; LCP image — without lazy, withfetchpriority="high", correctwidth/height, WebP/AVIF,srcset/sizes.Fonts:
font-display: swap, preload necessary styles (self-host/subsetting — a plus).Cloudflare: Brotli, Minify, correct cache/TTL rules for static; cache TTFB where possible.
Focus on typical pain points: render-blocking
style.min.css/layouts/*.css,jquery.min.js, heavy GTM/FB, offscreen images, small fonts in reviews.
Acceptance criteria (Definition of Done)
PSI Mobile on key pages:
no warnings “Render-blocking resources” and “Defer offscreen images” (or total savings ≤ 50 KB);
LCP ≤ 2.0 s or improvement ≥ 30% from the start;
INP ≤ 200 ms, CLS ≤ 0.1 (lab).
TTFB (cache) ≤ 0.4 s where pages are cached.
Nothing is broken (layout/functions/analytics, SEO tags preserved).
What to provide as output
Brief report: what was changed (in list) + screens PSI “before/after” for pages.
Export/screens of optimizer settings (WP Rocket/Autoptimize/Perfmatters).
List of remaining recommendations (if any).
Access and payment
Access: staging/copy of the site; WP admin, SFTP (rw), Cloudflare/GTM (read-only). Backup before starting — mandatory.
Payment: fixed for the entire site after acceptance (Escrow).