Website performance
Website speed optimisation: investigate slow pages and test improvements
Slow pages make reading, enquiring and buying harder. Gloria investigates the delays affecting important journeys, plans suitable improvements and checks the changes under comparable conditions.
Diagnosis and corrections are quoted according to the causes, access and functions to preserve.
Your project in practice
Example mobile performance review
- Customer task
- Read the menu and find the booking option
- Images
- Deliver appropriate sizes without shifting the surrounding content
- Page behaviour
- Check that menus and buttons respond reliably
- Validation
- Compare the same journey before and after the changes
What it can change
Identify slow customer journeys, investigate causes and measure the changes
Measure the pages used for service enquiries and other key tasks
The review begins with useful business journeys, including mobile use, rather than an isolated score.
Investigate images, scripts, theme behaviour and hosting
Images, scripts, theme behaviour or hosting are examined according to the evidence from your website.
Compare loading measurements and test forms after the changes
Improvements are compared using consistent conditions while the important forms and functions are checked.
In practice
Fix observed loading delays or prepare performance checks before website changes
You notice specific slow pages
Describe the pages and devices affected. We investigate the causes before choosing the corrections.
You are planning changes
We identify the functions to preserve so performance work does not disrupt the customer journey.
The scope
Performance review scope, planned corrections and functional checks
Open the sections below to explore the scope, deliverables and practical requirements.
Understand the experience behind the score
We examine when the main content appears, how the page responds to interaction and whether the layout moves unexpectedly. Available field data is considered alongside tests made under defined conditions.
A laboratory score can highlight useful leads. It does not describe every visitor’s experience or prove the commercial value of a change.
Investigate the source of the delay
- Images and media: dimensions, file size, format and loading.
- Scripts and styles: unnecessary resources and third-party services.
- WordPress: templates, page builders and extensions.
- Server and cache: response behaviour and configuration.
- Page stability: fonts, shifting content and interactive elements.
A full-size photograph used in a small panel can make the browser download far more data than it needs. Choosing an appropriate size and format is a concrete improvement to test against the final layout.
Keep the site working while making it faster
Agreed changes are prepared with a backup and, where needed, a test copy. Cache and loading changes must preserve navigation, forms, consent choices and commercial features.
We do not remove a useful external service solely to improve a score. Its purpose and the consequences of changing it belong in the decision.
Compare like with like
The deliverable records the baseline, completed work and checks on the selected pages. It identifies any remaining limitations, including those tied to third parties or features you need to keep.
Tests are compared under stated conditions. The proposal separates investigation, corrective work and any ongoing monitoring.
Practical guide
Describe the slow action, not just the slow website
A homepage can feel quick while a catalogue, form or basket is frustratingly slow. A returning visitor may also have a different experience from someone opening the site for the first time. Before choosing a remedy, record the URL, action, device and circumstances in which the delay occurs.
Swipe across the table to see every column.
| What you notice | Question to investigate | Useful evidence |
|---|---|---|
| The page stays blank initially | When does the response arrive and visible content appear? | Repeated measurements of the same URL |
| Content appears but a control responds late | What is the browser doing during the action? | A reproducible interaction scenario |
| The layout moves while loading | Which element appears without reserved space? | A recording or capture of the movement |
This connects a performance measure with a customer difficulty. It also helps avoid buying new hosting or installing another optimisation plugin before the cause is understood. The correct response depends on what is actually happening.
Practical guide
Illustrative example: a project gallery delays the enquiry journey
A fictional design studio places a large project gallery before its enquiry link. On a phone, oversized images and an external gallery component delay the page. Removing every image could improve a test result, but would remove evidence customers use to assess the studio's work.
Keep project photos useful while reducing their loading cost
A possible approach is to keep a representative selection, deliver images suited to their display size and defer material that is not needed immediately. The enquiry route must remain visible and functional. Whether this is appropriate depends on the measured cause and how visitors use the gallery, not simply on which setting produces the highest score.
After the change, compare the same page under comparable conditions. Also open images, use the enquiry route and check the mobile layout. This is a fictional design example, not a client case or an expected performance gain. It demonstrates why speed work should preserve the information and actions the visitor came for.
Practical guide
Agree functional checks as well as performance checks
Caching, script changes and plugin replacements can affect forms, baskets and logged-in areas. The scope needs to identify the functions that must continue working and the states in which they should be tested. A faster public page does not establish that every part of the website is safe to release.
When comparing proposals, separate diagnosis, changes, retesting and any later monitoring. The causes found, variety of templates and third-party integrations affect the effort. A hosting change is a separate decision that should be supported by evidence, rather than treated as the automatic answer to any slow page.
- Keep a baseline with the URL, test conditions and device assumptions recorded.
- Retest important functions, including basket and signed-in behaviour where applicable.
- Repeat comparable measurements instead of selecting the best isolated run.
- Where real-user data is available, review it over time without confusing it with a single laboratory test.
If an external service remains a constraint, the report should identify the dependency and available choices. The useful outcome is a documented set of causes addressed, preserved functions and comparable observations. A perfect score or a fixed increase in sales is not a reliable basis for defining the work.
Questions about page builders, hosting changes and performance scores
Can a page-builder website be improved?
Often, but the builder and its modules need to be examined first. Some changes are possible within the current setup; others require a decision about templates.
Do we need a new hosting provider?
Not automatically. We first establish whether the server is contributing to the problem and whether configuration changes may help.
Can you promise a perfect score?
No. The goal is a better, functioning experience under the site’s real constraints, with measurements that explain the result.
Describe the slow pages, actions and devices you want investigated
Send the slow pages and describe the devices or situations in which you notice the problem.
Discuss your project