Alan Perfume
Diagnosed site-speed problems across hosting, CDN and cache, reviewed the WooCommerce setup, and delivered concrete optimization recommendations.
Services
Web Performance & Core Web Vitals
The symptom is that the site is slow. The symptom is never the cause. A site cannot be optimized by guessing which layer is responsible, and installing another optimization plugin before identifying the bottleneck usually makes diagnosis harder.
Who this is for
Anyone with a slow WordPress or WooCommerce site who wants to know why before paying to change it.
Stack
Core Web VitalsCloudflareLiteSpeed CacheWooCommerceWordPressCDN
Problems
What this actually solves.
- Nobody knows which layer is at fault
- Hosting, CDN, cache and application each look like the cause from the outside. Separating them is the whole job.
- Optimization plugins stacked on each other
- Two caching plugins and a minifier can contradict one another. More optimization is not more speed.
- A good lab score and a slow site
- Lab numbers and what a real visitor experiences are different measurements. Core Web Vitals are about the second one.
- The CDN was supposed to fix it
- A misconfigured CDN can cost more than no CDN — particularly in front of a store with cart and account pages.
What’s included
- Performance diagnosis and layer attribution
- Hosting response investigation
- CDN and delivery-path investigation (Cloudflare)
- Caching investigation (LiteSpeed Cache and others)
- WooCommerce-specific performance review
- Image optimization and delivery
- CSS and JavaScript weight review
- Third-party script audit
- Core Web Vitals framing — LCP, INP, CLS
- Written, ordered optimization recommendations
Approach
How the work runs.
Reproduce
Establish what is actually slow, on what, and when — before changing anything.
Isolate the layer
Separate hosting, CDN, cache and application so a cause can be attributed rather than assumed.
Review the application
Technical review of the site's own configuration, which is frequently where the weight lives.
Recommend in order
Concrete recommendations, ordered by what actually matters, so the owner can act without guessing.
Quality
What “done well” means here.
- No promised scores
- I do not promise a PageSpeed number. A score is an instrument reading, not the goal, and promising one before diagnosis is a sales tactic rather than an engineering position.
- Lab is not field
- A synthetic test and real-user data answer different questions. Both are useful; they are not interchangeable.
- Diagnosis is deliverable on its own
- Sometimes the correct outcome is a written diagnosis and a recommendation list, not a rebuild. That is a complete engagement.
Evidence
The projects that evidence this.
Every capability claim on this page is backed by delivered work.
Questions
Questions people actually ask.
- Will you guarantee a PageSpeed score of 90+?
- No. Anyone who guarantees a score before looking at the site is guessing. What I will do is attribute the slowness to a layer and tell you, in order, what would move it.
- Is another caching plugin the answer?
- Rarely, and often it makes things worse — two caching layers can contradict each other, and a store's cart and checkout pages must be excluded correctly. Identify the bottleneck first.
- Do you publish before/after numbers from client work?
- Not unless I measured them and can show the source. There are no performance percentages anywhere on this site for that reason.
Contact
Have a site or store that needs to work better?
Tell me what is happening and on which page. A diagnosis is a useful first deliverable on its own.
I read every message myself and reply within one working day — usually with a question or two before anything else, because a scope worth quoting needs them answered.
Available for remote work aligned to EST hours
Mostafa Nouh
Full-Stack Developer & Product Builder
- linkedin.com/in/mostafanoah
- Location
- Egypt · Remote