Book a call
Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

WordPress and WooCommerce performance optimization for a live site that loads slowly

We find out why a WordPress site or WooCommerce store is slow before changing anything. The pages that matter are measured first, and each delay is traced to its source: the theme, a plugin, an image or script, the cache setup or the server. Fixes are then made on a staging copy in small groups. After each group, the same tests run again, and on a store, the cart, checkout and customer accounts are tested as well.

A few clients we’ve worked with

99Legal / Kremenchuker Law GroupAstraZenecaCoxitDiet vs DiseaseFlorida seal — Regional Counsel projectMetroplex HomebuyersNasdaq Private MarketOffice of Criminal Conflict and Civil Regional Counsel, Second Region of Florida — Ita M. NeymotinPolaclubThe Farm Soho

What we do

Norml diagnoses and fixes speed problems on an existing WordPress site or WooCommerce store. The work covers a baseline on representative pages, a report of what slows them down, the fixes you approve, and the same tests repeated on the live site after release.

What WordPress and WooCommerce performance work covers

Each part below is used only where the baseline shows it is needed, so the work stays limited to the causes the measurements find.

Solution
Websites
Platforms
WordPress, WooCommerce
  • A baseline you can repeatWe pick representative pages for each template, such as the home page and a blog post, and on a store a product, category, cart and checkout page. Each page is tested several times with the same device and connection settings, and the median is recorded for loading speed, layout shift and script blocking time. Field data from real Chrome visitors, including the Core Web Vitals, is recorded separately where Google has enough of it for the site.
    01
  • Causes traced before any fixFor each slow page we work out where the time goes: server response, the theme and page builder, plugins that load code on every page, images, fonts, scripts and third-party tags. The report puts the proposed fixes in order of how much of the delay they address and notes what else each one could affect.
    02
  • Images, fonts, scripts and tagsImages are resized to the size they are shown at, saved in modern formats and given fixed dimensions so the layout does not jump, and the main image at the top of a page loads first. Unused font weights are dropped. Scripts are deferred or delayed one setting at a time, because these settings can break menus, sliders, forms or checkout. Third-party tags that are deprecated but still firing are removed with your approval.
    03
  • One owner for each cache layerYour hosting, a caching plugin, a CDN and an object cache can all cache the same site. We list which layer does what and leave each kind of caching to one tool, so two tools are not caching or minifying the same files. An object cache is switched on only when the server provides one and it is confirmed to work.
    04
  • Store pages that must stay dynamicOn a WooCommerce store, product and category pages are measured separately, because they load different scripts and database queries than content pages. Cart, checkout and account pages stay out of the page cache. Before any cache change reaches the live store, adding to cart, coupons, checkout and signed-in customer sessions are tested on the staging copy.
    05
  • Database and scheduled tasksWordPress loads some stored settings on every request, and removed plugins can leave data behind. We measure these and the scheduled tasks first, then clean only data that can be traced to a specific plugin, after a backup we have confirmed can be restored. WP-Cron is moved to a server cron job only when that job is set up and confirmed to run.
    06
  • Content added during the workWhen prepared posts or pages need to go into the site, we add them after the baseline is recorded, so their effect on speed shows up in the measurements. Each post is checked against its source text and images, changed addresses get redirects, and the post template joins the pages we test.
    07
  • Layout and checkout checksBefore and after each group of changes, every representative template is compared in screenshots at desktop and mobile widths, and menus, forms and sliders are clicked through. On a store, the same checks include a test order for each payment and shipping method. A change that alters how a page looks or works is reversed or brought to you for a decision.
    08
Josiah BallCo-Founder & CEO, HOMEEC

“Norml Studio's professionalism and responsiveness were impressive.”

Clutch review
Lucas SeyhunCEO, The Farm Soho

“They were proactive in suggesting improvements we hadn't considered.”

Clutch review
Gaius CooperDirector, Streamline Pump Solutions

“They delivered what they said they would, on time.”

Clutch review
Emma EstefaClient Success Manager, Metroplex Homebuyers

“They focused on how to make our daily operations easier, not just on building features for the sake of it.”

Clutch review
Bret MillerManager, Door Knock Pro

“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”

Clutch review
Saima AhmedFounder, GoPetZen

“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”

Clutch review

What we need to start

  • Access in each person's nameAccounts for the WordPress admin, the hosting account or server, any CDN and the code repository, created for each person on our team, so you can see who changed what and remove access at any time.
    01
  • A staging copyAn existing staging site, or permission to create one with your current host or in a separate environment.
    02
  • The pages and paths that matterYour most visited pages, any page that feels slow, the purchase paths on a store and any earlier speed report. Read access to Search Console and analytics lets us compare lab results with real visits.
    03
  • Licenses for paid pluginsLicense keys for the theme, the caching plugin and other paid plugins, or access to the account they were bought under, so settings can be changed and updates applied.
    04
  • Payment test mode for a storeTest-mode access to your payment gateway, so checkout can be tested on the staging copy without charging a real card.
    05
  • Content to add, if anyThe prepared posts and their images, plus a list of any old addresses that must redirect to new ones.
    06
  • One person who decidesA named person who approves fixes, decides on trade-offs such as removing a widget, and agrees release times.
    07

How the work runs

  1. [Measure the pages that matter]

    We agree the representative pages and test settings with you, then record the baseline on the live site before anything changes.

    Step 01
  2. [Report the causes]

    You get the report of what slows each page down, with the proposed fixes in order. You choose which fixes go ahead.

    Step 02
  3. [Change a staging copy]

    Approved fixes are made on the staging copy in small groups, each with a recorded way to undo it. On a store copy, payments run in test mode and customer emails are turned off.

    Step 03
  4. [Repeat the tests]

    After each group, the baseline tests and the layout and checkout checks run again before the next group starts.

    Step 04
  5. [Release and measure again]

    After a fresh backup, the changes go live at an agreed time and the caches are cleared. The baseline tests then run on the live site.

    Step 05
  6. [Hand over the results]

    The report shows the results before and after, each change and how to undo it, and what still limits speed, such as hosting or scripts you decide to keep. It also lists the tests, so anyone can repeat them after future updates.

    Step 06

The people who do this work.

Meet the whole team

No account layer between you and them. These are the Norml specialists this work runs through.

Max Tymoshyn, founder of Norml Studio

Let's chat

“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”

Max TymoshynFounder & Architect

From the Norml blog.

Questions about WordPress and WooCommerce performance

Can you promise a speed score or a load time?
No. Results depend on your hosting, theme, plugins and the scripts your business needs, so we do not promise a number. You get the same tests run before and after the work, with the median results and the changes made in between.
Will you remove features or scripts to make pages faster?
Not without your decision. When a slider, video, chat widget or tracking tag costs loading time, the report shows how much and what depends on it. The options can include loading it later or only on the pages that use it.
Can a WooCommerce store be cached without breaking carts or checkout?
Yes, if the cache excludes what has to stay current. Cart, checkout and account pages are left out of it, and so are shoppers with items in their cart and signed-in customers where the caching tool supports that. New cache rules reach the live store only after the store checks pass on the staging copy.
Will you replace our theme or page builder?
Not as part of this work. We work within the current theme and builder and reduce what they load where the measurements show a cost. If the builder itself turns out to be the main cause, the report shows the evidence, and rebuilding on a custom theme is scoped as a separate project.
Do we have to change hosting?
Not necessarily. Server response time is part of the baseline, so the report shows whether the hosting limits the result. If it does, we set out the options, such as different server settings or a different plan. Moving the site to another host is separate work.
Our site runs on a server we manage ourselves. Do you need access to it?
Only for changes made on the server, such as compression, browser caching rules, PHP settings or an object cache. Theme and plugin changes need WordPress and code access only. Before any server change, we agree who maintains it afterwards.
Search Console reports poor Core Web Vitals for our site. When will that change?
Not immediately. That report uses data from real Chrome users' visits over the previous 28 days, so changes on the site show up in it gradually. It groups similar pages and shows a group only when there is enough data for it. Our lab tests show the effect of each change right away. We report the two kinds of data separately, so a lab result is never presented as what real visitors experience.
Will faster pages improve our search rankings?
Page experience is one of many things Google takes into account, so a speed improvement does not establish a ranking change. We report the speed measurements and do not forecast rankings.
Can we order only the diagnosis?
Yes. The baseline and the report of causes can be agreed on their own. Your team or another developer can then make the fixes, and we can run the same tests afterwards to check the result.
How do we keep the site fast after the work ends?
Plugin updates, new tags and heavy content can slow pages down again. Because the report lists the tests, they can be re-run after updates or a large batch of content, and the same checks can become part of a monthly maintenance plan.
What falls outside this work?
A redesign or theme rebuild, a move to another host, administration of the server itself and SEO campaigns are scoped separately. If the slowdown comes from malicious code on a hacked site, cleanup starts with its own investigation. Hosting, plugin licenses and CDN fees stay outside the agreement unless it names them.

See more of our WordPress work

Each case study covers the starting point, what we built and what changed after launch.

See all case studies