Skip to content

Services

Performance Optimization & Maintenance

Large catalogs, heavy customisation and growing traffic can slow a store down. We profile where time is actually spent, fix the causes, and can stay on to maintain the platform afterwards.

diagnostics · concept-supply.example

Request waterfall · /safety-ppe

Relative time →
  • Document/safety-ppe
  • Imagecategory-banner.webp
  • Imageproduct thumbnails
  • API/api/prices
  • Databaseprice list lookup

Potential bottleneck: the price API waits on a database lookup before the page can show prices. Measure again after changes.

Maintenance queue

Example
  1. Review image delivery (pending)Check sizes and formats
  2. Inspect slow query (in progress)Price list lookup
  3. Check scheduled tasks (pending)Overlap with peak hours

Cache path

  1. Request for category page
  2. CachedServed from cacheOriginApp + database
Concept performance diagnostics and maintenance workflow — illustrative content.

Where this helps

Situations that typically lead businesses to this kind of work.

  • Category, search or checkout pages load slowly.
  • Admin screens time out on large catalogs.
  • Scheduled tasks or imports affect storefront responsiveness.
  • There is no one responsible for updates, monitoring and small fixes.

Capabilities

What we deliver

  • Profiling

    Request, query and memory profiling to find the real bottlenecks.

  • Database tuning

    Index review, query optimisation and Entity Framework Core usage fixes.

  • Caching strategy

    Review of nopCommerce cache configuration and distributed cache options.

  • Front-end performance

    Image handling, bundling and render improvements for Core Web Vitals.

  • Hosting review

    Recommendations for IIS, Linux, container or Azure hosting configurations.

  • Ongoing maintenance

    Security patches, dependency updates, monitoring and small enhancements.

Running an older release? Newer versions run on newer .NET runtimes. See the version paths in how to upgrade nopCommerce to 4.90 or 5.0.

Checking the server first? Our guide to nopCommerce hosting requirements covers .NET 10, IIS, Linux, Docker and running several servers.

Thinking about Redis? Our Redis caching guide explains the cache options and why Redis rarely speeds up a single server.

Approach

How we approach it

  1. 01

    Measure first

    We establish a baseline on representative pages before changing anything.

  2. 02

    Fix by impact

    Changes are prioritised by measured effect, not guesswork.

  3. 03

    Verify and report

    Each change is measured against the baseline and documented.

Platform

nopCommerce versions we support

We build for and support nopCommerce 4.50 to 5.00. Each release runs on a specific .NET version, which sets the hosting a store needs and how much work an upgrade involves.

Stores on 4.40 or later upgrade the database automatically when the new release first starts. Plugins and the theme still need builds for the target version.

Planning a move between versions? Read our nopCommerce upgrade guide.

nopCommerce versions and the .NET runtime each one needs
nopCommerce.NET runtimeNotes
4.50.NET 6
4.60.NET 7
4.70.NET 8
4.80.NET 9
4.90.NET 9Previous release line, latest patch 4.90.8
5.00.NET 10Current release, 27 October 2026

Checked against the nopCommerce source code and release notes on 27 October 2026. Sources: nopCommerce releases on GitHub, Official upgrade documentation.

Related

Ready to plan your nopCommerce project?

Tell us about your storefront, ordering workflows or integrations by email, phone or WhatsApp. An outline is enough to start.