Performance promise
What the widget shows, what I actually commit to.
The Speed Compare widget on the home page demonstrates what this site achieves. Your site's realistic target differs by platform, content, and third-party scripts. This page is the honest version.
What the widget proves
The widget measures webdesigner.ph's own Core Web Vitals. The numbers are real: the site is static HTML built with Astro, zero third-party scripts on critical paths, typography as imagery (no hero photo), and fonts subset to just the characters used. It is the minimum-weight configuration of a marketing website.
Seeing your site alongside ours is meant to do one thing: show you there's a gap worth closing. The gap is real; how far it closes depends on what your site needs to do.
What's realistic for your site
Achievable targets by project type.
These are honest ranges I'd put in a contract, with margin. Google's "green" thresholds are LCP < 2.5s, CLS < 0.1, INP < 200ms. All tiers below hit green on the typical build I'd deliver.
Ranges are p75 mobile targets measured on a 4G-class connection. Individual page scores vary; we measure a representative sample.
What I commit to in writing
Contract commitment · included on every project
Google Core Web Vitals in the green on p75 mobile at launch: LCP < 2.5s, CLS < 0.1, INP < 200ms. Measured via CrUX within 28 days of launch. If the site doesn't meet these numbers because of my work, I fix it before final invoice at no additional charge.
Faster than your competitors · benchmarked in writing
I benchmark 3–5 comparable Philippine sites in your category during discovery. Your launched site will beat the median of that benchmark on all three CWV metrics. The benchmark list and results are documented in your launch report.
Enforced at build time · no silent drift
Performance budgets are a gate in the deploy pipeline. If a later change breaks them, the build fails until the regression is fixed. Monthly care-plan reports include current CWV numbers.
The budgets I enforce
- Home page total weight
- < 150 KB (home)
- Initial JavaScript
- < 30 KB gzipped
- Critical CSS
- < 14 KB gzipped, inlined
- Font payload
- < 80 KB across all families
- Core Web Vitals
- All green on p75 mobile
What limits the ceiling
The honest list of what gets in the way.
Every item below is a genuine constraint. None of them are blockers; each is a tradeoff we navigate together.
- 01
Images above the fold
A 12-product grid cannot beat a page with zero images. We mitigate with AVIF/WebP, responsive srcset, lazy-load for below-the-fold, blurred placeholders. But bytes still travel.
- 02
Third-party scripts you request
GTM, Meta Pixel, live chat, Hotjar, Mailchimp popups, cookie banners — each adds 20–150 KB from an origin with unpredictable latency. Two or three together can push a site from green to orange. We budget and flag.
- 03
Platform and CMS choice
Astro/static hits 0.8s. Well-built WordPress hits 1.5–2.5s. Shopify with 10 apps hits 2.8s+. Your platform sets the ceiling.
- 04
Hosting tier
Cheap shared hosting has a latency floor we can't get under. Managed hosting (Cloudways, Kinsta, SiteGround) moves it. The extra ₱1,500–₱3,500/month is usually worth it.
- 05
Content growth after launch
A site at 1.5s LCP on launch day drifts to 3s+ after 80 blog posts, 40 photos, and 2 new plugins added without review. Care plans police this; otherwise numbers degrade.
- 06
Geographic variance
Lab numbers measure Manila-4G conditions. A real user in Samar on 3G experiences something slower regardless. CrUX p75 is always higher than lab.
What's not in the promise
To be explicit — these outcomes depend on factors outside what I control, so I don't promise them:
- Specific search rankings ("page 1 for [term]")
- Specific conversion rate targets
- Specific revenue or lead-volume outcomes
- Performance numbers on devices/connections outside the p75 mobile envelope Google measures
- Ongoing performance if content or scripts are added post-launch outside of a care plan
If a builder promises you these numbers, be cautious. They depend on your product, market, content, and execution — not just the site.
Still fast. Just honestly so.
The 4× speed gap the widget shows is real. The improvement you'll typically see on your own site is 2–3×. That is genuinely the most impactful single change you can make for conversion rate on a Philippine SME site.
Book a strategy call