WordPress Speed Optimization and Performance Improvement

// Who is WordPress speed optimization for?

WordPress speed optimization is for businesses whose site loads slowly and who can see it costing visitors or Google rankings. Slowness rarely has a single cause: uncompressed images, unnecessary plugins and an uncached server work together, and until each is measured separately nobody knows which one dominates. If any of the following sounds familiar, you are on the right page.

• PageSpeed Insights scores below 50 on mobile
• The home page takes more than 4 seconds to open and product pages are slower still
• Search Console's Core Web Vitals report shows red pages
• Ad traffic arrives but visitors leave before the page has loaded

We use the same measurement method on brochure sites, blogs and WooCommerce stores; on stores the cart and checkout pages are handled separately.

// What is included and what is not

Speed work is a one-off project; for ongoing monitoring it attaches to the monthly maintenance plan. The table below lists what the one-off project includes and what stays outside, line by line. We write the exclusions up front so there are no surprises at the quote stage and the boundaries are clear from the start.

If the slowness comes from the server itself, the measurement shows it and we propose a migration as a separate step; the measurement does not lie.

// How does it work and how long does it take?

The process has four steps and takes 2 to 4 business days in total for a typical site. Measurement is done on day one and the expected improvement is written into the quote as a number. The work is done on a copy of the site and pushed live in one go at a low-traffic hour; visitors see no downtime and a backup is taken before the switch.

// How is the price determined?

Three variables set the price: number of pages and images, plugin density and whether e-commerce is involved. A 20-page brochure site and a 2,000-product store do not carry the same image-processing load, so we quote from the measurement rather than a fixed list. The first measurement is free, its report is shared, and the quote is fixed once it is done.

The quote states a target score; if the target is not reached, the difference is not charged. Server-side slowness is flagged and a migration is quoted separately. Customers on the maintenance plan get speed work at a reduced rate.

// Results we have delivered

The three cases below represent different bottlenecks and typical outcomes of speed work. We do not share client names without permission, so sector and scale are given instead; scores are mobile PageSpeed Insights measurements taken on the same page, with the same method, 7 days after the work. You receive the same before/after table.

• Furniture store, 600 products — 4 MB product images were converted to WebP; mobile score rose from 31 to 78 and LCP fell from 6.2 seconds to 2.1 seconds
• Law firm, 25 pages — 6 of 14 plugins were removed and caching set up; page weight fell 62% and the score went from 44 to 91
• News site — Ad and social scripts were deferred; INP dropped from 480 milliseconds to 140 milliseconds

Installing a speed plugin is not speed work. Every improvement made without measuring what is slow is a guess, and sometimes it makes the site slower.

// The team behind the work

The work is carried out by Caner Zep Çelik, founder of Zep Bilisim. As founder and technical consultant he has worked on WordPress infrastructure, server configuration and search visibility since 2020 and has been involved in more than 100 projects. He does the measurement and the server tuning himself and does not outsource the work.

The before/after report is written by the same person at Zep Bilisim: which bottleneck was found, what was done and which number moved from where to where. It also lets you track the improvement in Search Console.

// When is it not needed?

On a site with a mobile score above 85 and a green Core Web Vitals report, speed work is unnecessary; we say so plainly in the first measurement and do not sell it. If the slowness is only in the admin panel it does not affect visitors and is usually solved with a smaller adjustment, often a single plugin setting.

If the theme itself is badly coded, optimization has limited effect; replacing the theme is cheaper and we say so explicitly in the measurement report.

For ongoing monitoring see WordPress maintenance and updates, and for server-caused slowness see site migration. Errors and conflicts found during speed work are handled under technical support and troubleshooting. Google's Core Web Vitals guide explains the three metrics, their thresholds and how they are measured.

// Frequently Asked Questions