Performance
Find the element causing WordPress layout shift
Find the element causing WordPress layout shift, trace the event in Chrome, separate font and late-content causes, reserve space, and retest mobile.
I'm Hamza Ahmad Aslam, and I diagnose slow WordPress pages by tracing requests through PHP, the database, the network and the browser. I find what is delaying visitors, then test changes against the starting measurements.
From $750
A fixed-price performance diagnosis is $350, credited in full against the fix if you book it within 30 days.
The price is an estimate until the diagnosis. After that the quote is fixed: if the work takes longer, that is my cost. Anything I change that breaks within 30 days, I fix free.
Scope & Deliverables
Profile TTFB, PHP workers and slow database queries
Investigate LCP, INP and CLS using browser traces and available field data
Evaluate persistent object caching against the site’s workload
Review autoloaded options and database cleanup candidates
Remove unnecessary scripts and improve image and font delivery
Review CDN rules, cache exclusions and invalidation
Performance work starts with a baseline. I combine lab diagnostics (Lighthouse, WebPageTest, Chrome DevTools and Query Monitor) with field data from CrUX and Search Console, then map each delay to the server, database, network, or browser main thread.
Audit & profile ──► Diagnose bottlenecks ──► Targeted changes ──► Regression tests ──► Field measurement
TTFB consumes part of the LCP budget, but it is only one component. I measure uncached and cached requests separately, review PHP workers and OPcache, profile slow database queries, inspect autoloaded options, and confirm whether a persistent object cache improves the actual workload. Configuration changes depend on available memory, traffic, and hosting constraints; there is no safe universal PHP-FPM or buffer-pool value.
The LCP element is often a featured image, hero banner, or large text block. I identify it per template, then optimize the measured bottleneck: response time, resource discovery, image dimensions and format, request priority, render-blocking styles, or font delivery.
Common WordPress causes of poor INP include third-party tags, page-builder JavaScript, expensive event handlers, and long main-thread tasks. I profile real interactions, remove unnecessary work, defer non-critical scripts, and split long tasks where the code permits it.
I reserve space for images and embeds, stabilize font rendering, and control dynamically inserted banners or widgets so they do not move content after the page starts rendering.
Every engagement records the starting measurements, the change made, lab results, and field data once enough real visits have accumulated. The interactive calculator below helps plan an LCP and INP budget; it is not a substitute for CrUX data.
As website developer at Half Price Packaging, my performance and infrastructure work contributed to a 10x improvement in site performance while traffic rose 5x, based on PageSpeed Insights and Google Analytics measurements. At Salsoft Technologies, caching and code optimizations took GTmetrix and Lighthouse scores into the top tier.
To find the largest measured bottlenecks on your WordPress site, start with a full performance audit.
Performance budget workshop
Adjust the four phases of LCP and the three phases of INP to see where the budget is being spent. The model turns an abstract score into a practical investigation plan for the server, network, and browser main thread.
Estimated LCP
Largest Contentful Paint
Good
Good up to 2,500 ms · poor above 4,000 ms (the two marks)
Estimated INP
Interaction to Next Paint
Good
Good up to 200 ms · poor above 500 ms (the two marks)
Use the estimate to choose what to profile next, then validate the change with lab traces and 75th-percentile field data. It is a planning aid, not a CrUX score or a performance guarantee.
Open source
Track record
WordPress Developer
Half Price Packaging
Feb 2022 - Mar 2025
I worked as a WordPress Developer at Half Price Packaging from February 2022 to March 2025, full-time for most of that period and part-time from August to November 2023 and August 2024 to March 2025, when I mainly supported Custom Packaging Lane and Custom Stickers Factory. I reworked WordPress admin and theme components, and during my time there site performance improved 10x and traffic rose 5x based on PageSpeed Insights and Google Analytics measurements. I also removed malicious code and hardened the installation.
Web Developer
Salsoft Technologies
May 2021 - Jan 2022
I developed custom WordPress themes, templates and plugins at Salsoft Technologies. Caching and page-load improvements raised GTmetrix and Lighthouse scores. I also tested across browsers and carried out security audits.
Web Developer
Remote Growth Partners (client: Gallery Media Group, New York)
Aug 2023 - Nov 2023
I worked full-time as a Web Developer at Remote Growth Partners from August to November 2023 on a client assignment with Gallery Media Group in New York. I resolved WordPress VIP support tickets, fixed functionality and performance issues, deployed optimized code, and worked with cross-functional teams on new features and code quality.
Website Developer
The Chimera Marketing
Aug 2015 - Mar 2017
I worked full-time, on-site in Lahore as a Website Developer at The Chimera Marketing from August 2015 to March 2017. I developed websites, contributed to interactive media design projects, provided technical analysis, assistance and project management support, and worked on a PepsiCo project.
Technical Insights
Performance
Find the element causing WordPress layout shift
Find the element causing WordPress layout shift, trace the event in Chrome, separate font and late-content causes, reserve space, and retest mobile.
Performance
PageSpeed good, Core Web Vitals failed: read the right data
See why PageSpeed can look good while Core Web Vitals fail, separate lab from field data, check scope and coverage, and choose the right next test.
Performance
Fix INP in WordPress by finding the slow interaction
Fix INP in WordPress by reproducing slow taps and typing, splitting delay into three phases, tracing the long task, and checking field context.
Frequently Asked Questions
The result depends on hosting, the theme, plugins, third-party tags, traffic patterns, and the starting baseline. I establish that baseline first, prioritize the largest measured bottlenecks, and report before-and-after lab and field data rather than promising a fixed percentage.
I use profiling to choose the fix. A caching plugin may help with cacheable pages, while slow queries, heavy JavaScript or blocked requests may need code or configuration changes. Cart, checkout and logged-in flows need separate tests.
Search Console uses rolling real-user data, so changes appear gradually as enough eligible visits are collected. Validation can take about 28 days, but low-traffic URLs or mixed page groups may take longer.
Adjacent engagements
Next step
Send the site URL and the performance problem you are seeing. My first reply will identify the measurements and areas I would review before recommending changes.