Tangensys • Plan, deliver, measure
Website speed optimisation
Investigate the slow templates and interactions first. A single score from one test is not enough to understand how real visitors experience the site.
The work to plan together
A scope shaped around this requirement.
- Speed auditScope
- Image, script and font optimisationReview
- Caching and hosting adviceCheck
- VisitorArrives on a phone or desktop
- NavigationFinds the right page quickly
- Form or integrationEnquiry, booking or order
- Your teamReceives it in the right place
In short
What does Website speed optimisation involve?
Website speed optimisation makes pages load and respond faster, improving Core Web Vitals, user experience and conversion.
When Website speed optimisation is a useful fit
Slow WordPress and Shopify sites
Identify the scripts, images and templates causing delays before replacing the whole site.
Sites failing Core Web Vitals
Compare real-user evidence with repeatable lab checks to prioritise useful improvements.
Stores losing mobile shoppers
Test product browsing and checkout on mobile so performance changes preserve essential functions.
Problems worth addressing first
Use these situations to identify the work that deserves attention before expanding the scope.
- Pages take seconds to load on mobile
- Images and scripts are heavy
- Third-party apps slow the site
A practical example
If a product page loads slowly, inspect the hero image, app scripts and review widget before changing hosting or removing useful buying information.
This is an illustrative scenario to explain the approach, not a claimed client project.
The work we can include
The final quote identifies the deliverables, quantities, approvals and exclusions. Select the work that serves your goal rather than assuming every item is required.
- Speed audit
- Image, script and font optimisation
- Caching and hosting advice
- Before-and-after measurements
Where we usually begin
Hosting restrictions and third-party scripts can limit improvements. We agree the pages, changes and measurement conditions; no fixed score is guaranteed.
Practical detail
Read a speed result with its test conditions
An illustrative product page may feel slow because its hero image blocks useful content. Review the specific page and device before changing the entire site.
| Part of the work | Example output | How to review it |
|---|---|---|
| Lab baseline | Page URL, tool, mobile profile and repeated runs | Compare the same conditions; do not select only the best score. |
| Observed issue | Oversized first image or a blocking script | The finding points to a resource and its effect on the useful page content. |
| Proposed change | Resize/compress the image or defer a nonessential script | The change preserves the important visual or business function. |
| Validation | Repeated lab checks plus available field data | Separate a controlled improvement from real-user measurements that update over time. |
Field data describes actual usage when available; lab data helps diagnose a controlled test. Neither a single score nor an isolated before/after test proves ranking or revenue changes.
Find the bottleneck on representative journeys
Speed work should start with the pages customers actually use. A homepage score cannot describe every product, service or checkout journey. Review device and connection conditions, page templates and the assets or scripts contributing to the delay.
Separate page-level issues from hosting, application and third-party dependencies. Large images, excessive script work and slow server responses need different fixes. Removing a useful feature to improve a score may create a worse customer experience.
Compare before and after using the same test conditions and available real-user information. Record what changed and any remaining limitations. One laboratory score is a diagnostic observation, not a guarantee that every visitor or all search outcomes will improve.
Free technical review
Start with a clear scope and a practical next step.
Tell us what you want to improve and share the relevant website or project details. We will review the starting point, recommend a suitable scope and provide a custom quote.
The initial review is free. Delivery, third-party charges and ongoing support are quoted separately.
Process
How the work is delivered
Review the starting point
Review the current setup, examples of the problem and the information needed to agree the work.
Agree scope and sign-off
Discovery covers existing code, users, data and external systems. We turn the main workflow into sign-off checks, then agree milestones and responsibilities.
Deliver and review
Changes are reviewed on a test environment before release. Handover includes agreed documentation, access and a maintenance route; ongoing support is separately defined.
Hand over the next steps
Review the agreed outputs together. Confirm what your team maintains and what needs a separate ongoing arrangement.
What progress should mean
Measures that match the work
Use comparable before-and-after tests and available real-user data. Track loading, interaction and layout stability alongside whether important features still work.
A record of delivery
See what was completed, reviewed and still dependent on access or approvals. Project delivery and business results are reported separately.
Clear limits in the data
We explain what can be verified and where a result is only an estimate. Contact clicks, conversations and sales are different actions.
Scope and responsibilities
You keep ownership of your business accounts and approved deliverables under the agreed contract. Any third-party licences, subscriptions or usage fees are identified before you commit.
Will removing plugins always make a website faster?
No. Review which code actually affects the page and what the plugin does. An unused dependency may be removable, while another provides essential functionality. Test the relevant journey after changes rather than treating plugin count as the performance measure.
What if there is no field data for our page?
Use repeatable lab diagnostics and practical device checks, then review available site-level or later field data with its limitations.
Will a higher speed score guarantee better rankings?
No. Faster useful pages support usability, but relevance, competition, technical access and many other factors also affect search performance.
Will speed improve rankings?
Speed improvements support usability. Rankings and conversion changes depend on several factors, so neither is guaranteed.
How is Website speed optimisation priced?
We quote against your goals, current setup and agreed scope. The quote separates delivery from third-party costs and ongoing support. You receive a custom quote within 2 working days.
How long does the work take?
The timeline follows the size of the agreed scope, access, content and approvals. We confirm milestones in the quote; a simple change and a full implementation need different schedules.
How will we communicate?
Your point of contact agrees a review rhythm with you. We use email, WhatsApp and scheduled calls, with decisions and scope changes recorded clearly.
What do you need to get started?
Share your current website or system, your main goal and examples of what is not working. We then agree the access and information needed for discovery.
Is everything included in the free review?
No. The free initial review helps define the next step. Detailed research, design, implementation and ongoing support are included only when stated in your quote.
Explore the related services
Let’s agree the right next step.
Tell us your goals and current setup. We’ll recommend a practical starting point and provide a custom quote.
Custom quote within 2 working days