Project summary · Online publishing
Website Performance Engineering for an Online Publisher
Salt worked on an online publisher’s website performance, addressing code, assets, caching, content delivery, and infrastructure constraints.
Discuss a similar projectThe starting point
The business problem.
Slow access to content and website performance issues affected the publishing experience. The work needed to consider both page delivery and the infrastructure behind it.
Salt’s contribution
What the work covered.
The published implementation includes a performance audit, code and database query optimization, caching, CDN integration, image compression, lazy loading, asset minification, and infrastructure work.
Inside the delivery
The work in practical terms.
Explore the scope and implementation details relevant to a similar engagement.
Project detail
How the work
comes together.
Reducing page-delivery overhead
Image compression, lazy loading, and JavaScript and CSS minification addressed asset delivery. Code, query, and caching work addressed additional sources of server requests and response overhead.
Considering traffic and infrastructure
The project also addressed infrastructure and load distribution. This is relevant to publishers assessing both the weight of individual pages and how the site behaves as traffic changes.
Delivery scope
What the engagement covered.
The project addressed website performance at the asset, application, database, and infrastructure levels.
For your project
Start with the scope.
A similar engagement starts by identifying the workflow, existing system, and responsibilities your team needs help with. The proposal should define the deliverables, dependencies, and acceptance criteria for your situation.
Explore ways to work with SaltApply the experience
Explore relevant expertise.
Build on relevant experience
Working through a similar challenge?
Tell us about your users, existing systems, and the change you need. We’ll help define an appropriate scope for your project.