The problem to address
Record the URL, device and slow action: opening a page, displaying images, opening a menu or submitting a form. Review the platform, change history and editing access to establish what can be done.
Website speed optimisation
Improve website speed by addressing the cause
Make your business website easier to use on mobile by addressing slow pages and responses across the language versions your customers need.
AT A GLANCE
Find the cause of slow pages, make agreed changes and compare under the same conditions.
- Start with
- Affected URLs, slow actions, device details and access to investigate.
- Deliverable
- Agreed fixes, comparable measurements and checks of the important website functions.
- Agree first
- File sizes, load timings and tool scores are reported as different measures.
What this starting fee covers
- One website, up to 3 page layouts and 50 existing images.
- Baseline measurement and agreed image, resource and loading changes.
- Before/after checks under comparable conditions, plus layout and function checks.
Separate costs / conditions: Hosting changes, code rebuilds and system replacements are separate. No fixed PageSpeed score or load-time guarantee.
Compare service prices →Cost depends on the amount and complexity of the work. A smaller scope may reduce the total; we confirm this after reviewing your requirements. Work fees exclude any applicable taxes; domains, hosting, paid tools/APIs and advertising are separate. The final quote confirms scope, total, taxes and timing before work begins.
Diagnosis
Choose the right pages and checks
Start with pages customers use: the homepage, services, products or an enquiry form. Observed symptoms and available data determine what needs closer investigation.
A baseline with recorded conditions
Record the tool, device, network settings, cache state and measurement time. Repeat measurements where appropriate; an isolated score does not explain the cause or every visitor's experience.
Causes and priorities
Examine images, fonts, frontend code, third-party code and server responses. Separate confirmed issues from hypotheses, prioritising by impact, change risk and available access.
OUR OWN WEBSITE · HISTORICAL EVIDENCE
Smaller files.
What the figures show.
Mắt Rồng Digital: the baseline was recorded on 17 September 2026, with the improvements verified on 18 September 2026. This work was on our own website, not a client project.
FILE-SIZE COMPARISON · BYTES (B)
Header logo image
- Before
- 1 534 822 B
- After
- 10 706 B
A compact separate asset replaced the full layout artwork.
Favicon
- Before
- 1 718 459 B
- After
- 2 754 B
An asset sized for the browser icon.
All 9 declared font files
- Before
- 2 989 728 B
- After
- 1 071 380 B
TTF → WOFF2, preserving glyphs and outlines.
What do these figures establish?
These are historical file sizes, not load times, total page downloads or compressed transfer sizes. Core Web Vitals and PageSpeed measurements were unavailable, so they do not establish a measured speed improvement. The figures do not describe current website speed.
After the changes, the team checked that active HTML/CSS no longer requested the old assets, along with Vietnamese characters, layouts and forms.
Read the finding and verificationImprovements
Make the changes while preserving the experience
Change the necessary assets and settings while preserving important functions.
Images and fonts
Choose formats, dimensions and loading behaviour suited to where assets appear. Check image quality, Vietnamese characters, layout and whether the old resources are still requested.
Frontend code and external connections
Review CSS, JavaScript and third-party resources that may delay content or interaction. Understand dependencies before making changes, then check the agreed menus, forms, tracking and integrations.
Server responses and caching
With suitable access, review server responses, compression and caching rules. Changing content, accounts and form data need appropriate handling; one configuration will not suit every response.
Comparison
A comparison you can inspect
The report records the changes, measurement method and remaining limits. The aim is to improve the experience while keeping the website working correctly.
Before and after under the same conditions
Reuse the recorded URLs, tools and settings for comparison. Distinguish file size, transferred data, timings and tool scores; fewer bytes alone do not establish a measured reduction in load time.
Functional checks after changes
Review mobile layouts, images, text, links and the agreed key flows. Check forms with an approved test destination, and prepare a backup and recovery approach before making changes.
Handover and remaining work
Receive the change list, comparisons and dependencies on hosting, the platform or other providers. The published starting price covers the stated base scope; the final quote follows the pages, causes and access involved. Infrastructure upgrades, paid tools and ongoing maintenance are agreed separately.
HOW WE WORK
Clarity at every step.
Define the problem
Choose URLs and flows to improve, review access and agree what the checks need to establish.
Measure and choose fixes
Record the baseline, measurement conditions and verified causes. Agree the work and recovery approach.
Implement changes
Make approved changes, check dependencies and retain a record so results can be compared with the work.
Remeasure and hand over
Compare under the same conditions, check functionality and explain the findings and data limits.
FAQ
Before we begin.
A few useful answers to help define the right scope.
Do you guarantee a PageSpeed score of 100?
No. Scores depend on the page, test conditions and systems the website needs. We agree the issues, measurement approach and functional checks; a single score is not a promise we make for every project.
How does speed optimisation differ from a website audit?
A broader audit can assess technical SEO, structure, content and usability. This service identifies why selected pages are slow and implements agreed fixes. A diagnosis-only report can be scoped separately if that is what you need.
Can you optimise a site built by another provider?
We can assess it after reviewing the platform, source code, configuration and access. Where a component cannot be edited, the report explains what needs coordination with its manager or provider.
Will I need new hosting or a rebuild?
Not by default. We investigate the cause first. Changes to infrastructure or a rebuild of an affected component need a specific reason, with costs, risks and a plan to preserve data and functionality explained first.
What does the file-size example on this page establish?
The Mắt Rồng Digital example records asset sizes before and after optimisation in September 2026. It establishes that resource changes were implemented, not a measured speed increase, PageSpeed score or Core Web Vitals result.
What should I share for a proposal?
Send the affected URLs, device, specific slow actions and platform if known. You can include existing test results. We discuss the access needed afterwards; do not send passwords through the enquiry form.
LET’S DEFINE THE REQUIREMENTS
Start with the page that feels slow.
Share your website and describe when it feels slow. We will discuss the checks, access and optimisation scope needed.