Let's find out what's slowing your website down
Slow loading can be caused by images, scripts, the server or several factors at once. A speed test score alone doesn't tell us what to fix first.
Open the website on your phone and note which page loads most slowly and whether the issue affects the whole website.
Let's see what's making your website hard to use on a phone
The issue could be the layout, readability, a form or a single element. The scope of the fixes depends on where visitors run into trouble; a full rebuild isn't always necessary.
On your phone, try to find the most important information and use one of the contact options. Note where you run into difficulty.
First, let's find out what stopped working
An error might affect just one feature, or it might block inquiries and sales. Without checking the symptoms, I can't reliably identify the cause or scope of the repair.
Note the page address, the error message and the action that triggers it. If a form or checkout doesn't work, treat it as urgent.
Let's work out what's ready and what's missing
With an unfinished project, the first step is to separate working parts from missing ones and decide what's essential for launch. Only then can we estimate the time and cost to finish it.
List three things the website needs before it can go live, and gather access to the project, hosting and domain.
Let's make everyday website changes easier
Difficult editing doesn't always mean you need a new website. The problem might be how fields were set up, permissions or the lack of clear instructions. It's worth starting with the tasks you do most often.
Note the three content changes you make most often and exactly what makes them difficult.
Let's start with the information your customers need
Out-of-date opening hours, prices or service descriptions can mislead customers. Fixing one page will help for a while, but it's also worth deciding who will review the content and when.
Check your contact details, opening hours and most-visited service pages. Note anything that needs an urgent update.
Let's plan regular website updates
When no one is responsible for technical updates, it's easy to put them off for months. First, we need to see what needs changing and how to make overdue updates safely, then establish a regular routine.
Check when the website software was last updated and who has access. Before making overdue changes, make sure you have a current backup.
First, let's define what your website needs to do now
When your services or the way you attract customers change, your existing website may no longer support the business. The decision to improve it or build a new one should come from your goals, not just the age of the website.
Write down what visitors should do on the website and what they currently can't easily find or do.
First, let's see what is worth automating
Repeated questions might call for better website content, a simpler way to get in touch or an automated reply. AI only makes sense once we know which questions it should handle and where the answers will come from.
Gather the five questions customers ask most often and check whether the answers are already easy to find on your website.
Where to start
Let's find out what's slowing your website down
Slow loading can be caused by images, scripts, the server or several factors at once. A speed test score alone doesn't tell us what to fix first.
Open the website on your phone and note which page loads most slowly and whether the issue affects the whole website.
- server response time and Core Web Vitals
- images, scripts and resources that block loading
- website and cache configuration
- identify the elements with the biggest impact on speed
- fix the causes that are worth addressing
- compare measurements from before and after the changes
A possible first step
You can start with an audit
I'll measure the speed of the most important pages and identify the elements that slow them down most.
You'll get a list of fixes ranked by their impact on speed, along with an estimated time and cost for each.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an auditLet's see what's making your website hard to use on a phone
The issue could be the layout, readability, a form or a single element. The scope of the fixes depends on where visitors run into trouble; a full rebuild isn't always necessary.
On your phone, try to find the most important information and use one of the contact options. Note where you run into difficulty.
- layout and readability of the most important pages
- whether the menu, buttons and forms work
- whether a targeted fix can solve the problem
- remove obstacles to using the website on a phone
- work out what layout changes are needed
- test the fixes at different screen sizes
A possible first step
You can start with an audit
I'll test the most important things visitors need to do on a phone and identify where the layout or features get in their way.
You'll get a plan for mobile fixes that distinguishes small changes from a larger rebuild, with time and cost estimates.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an auditFirst, let's find out what stopped working
An error might affect just one feature, or it might block inquiries and sales. Without checking the symptoms, I can't reliably identify the cause or scope of the repair.
Note the page address, the error message and the action that triggers it. If a form or checkout doesn't work, treat it as urgent.
- which features are unavailable and since when
- whether the error can be reproduced and what the logs show
- how the problem affects customer inquiries and sales
- restore the most important features
- fix the identified cause of the error
- check that the repair hasn't disrupted other parts of the website
A possible first step
You can start with an audit
I'll investigate the reported error and its effect on key website features.
You'll get an explanation of possible causes, repair priorities and an estimated time and cost to restore functionality.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an auditLet's work out what's ready and what's missing
With an unfinished project, the first step is to separate working parts from missing ones and decide what's essential for launch. Only then can we estimate the time and cost to finish it.
List three things the website needs before it can go live, and gather access to the project, hosting and domain.
- what already works and can be kept
- what content, features or access are missing
- the work needed for a safe launch
- put together a plan to finish the website, in the right order
- use the completed parts if they make sense
- get the website ready to launch and check that it works
A possible first step
You can start with an audit
I'll check what already works, what's missing for launch and which parts of the project are worth keeping.
You'll get a plan to finish the website, with the order of work and an estimated time and cost to launch.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an auditLet's make everyday website changes easier
Difficult editing doesn't always mean you need a new website. The problem might be how fields were set up, permissions or the lack of clear instructions. It's worth starting with the tasks you do most often.
Note the three content changes you make most often and exactly what makes them difficult.
- how the most important content is edited
- permissions and limits of the current system
- which changes can be made easier without a rebuild
- make the most common elements easier to edit
- organize the fields and screens you use
- show you how to make changes safely
A possible first step
You can start with an audit
I'll go through your most common content changes and show what's making editing difficult and what can be simplified without a rebuild.
You'll get suggestions for improving editing, from small fixes to bigger changes, with time and cost estimates.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an auditLet's start with the information your customers need
Out-of-date opening hours, prices or service descriptions can mislead customers. Fixing one page will help for a while, but it's also worth deciding who will review the content and when.
Check your contact details, opening hours and most-visited service pages. Note anything that needs an urgent update.
- which information is out of date or inconsistent
- how often your services change and who approves content
- whether the current editing process makes updates easy
- organize the content you identify and correct the most important information
- set up a simple process for requesting changes
- help plan regular website reviews
A possible first step
You can start with an audit
I'll review the information that matters most to customers, identify outdated or inconsistent content and suggest a way to check it regularly.
You'll get a prioritized list of content to update and a plan to organize it, with estimated time and cost.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an auditLet's plan regular website updates
When no one is responsible for technical updates, it's easy to put them off for months. First, we need to see what needs changing and how to make overdue updates safely, then establish a regular routine.
Check when the website software was last updated and who has access. Before making overdue changes, make sure you have a current backup.
- which parts of the website need updating
- whether a backup is made before changes
- how the website is checked after an update
- prioritize and carry out overdue updates
- check key features after the changes
- take over regular updates and website checks
A possible first step
You can start with an audit
I'll check the state of the website software, overdue updates and how changes are protected with a backup.
You'll get a plan for overdue updates and ongoing care, with the order of work and time and cost estimates.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an auditFirst, let's define what your website needs to do now
When your services or the way you attract customers change, your existing website may no longer support the business. The decision to improve it or build a new one should come from your goals, not just the age of the website.
Write down what visitors should do on the website and what they currently can't easily find or do.
- business goals and the needs of your main audiences
- which content and features still do their job
- what can stay and what needs to change
- propose a structure that supports your new goals
- compare the scope of updating and rebuilding the website
- implement the option chosen based on that assessment
A possible first step
You can start with an audit
I'll assess how well the current website supports your new business goals and compare updating it with building a new one.
You'll get a comparison of both options, including the scope, estimated time and cost of each.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an auditFirst, let's see what is worth automating
Repeated questions might call for better website content, a simpler way to get in touch or an automated reply. AI only makes sense once we know which questions it should handle and where the answers will come from.
Gather the five questions customers ask most often and check whether the answers are already easy to find on your website.
- the number and types of repeated questions
- the quality of answer sources and access to data
- when a human needs to be involved in the answer
- assess whether better content is enough or AI would help
- design a limited scope for automation
- test the answers against real questions
A possible first step
You can start with an audit
I'll review the most common customer questions and the sources of their answers to see whether better content is enough or automation is worthwhile.
You'll get an assessment of whether automation makes sense and a proposed solution with an estimated scope, timeline and cost.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an audit- server response time and Core Web Vitals
- images, scripts and resources that block loading
- website and cache configuration
- identify the elements with the biggest impact on speed
- fix the causes that are worth addressing
- compare measurements from before and after the changes
A possible first step
You can start with an audit
I'll measure the speed of the most important pages and identify the elements that slow them down most.
You'll get a list of fixes ranked by their impact on speed, along with an estimated time and cost for each.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an audit- layout and readability of the most important pages
- whether the menu, buttons and forms work
- whether a targeted fix can solve the problem
- remove obstacles to using the website on a phone
- work out what layout changes are needed
- test the fixes at different screen sizes
A possible first step
You can start with an audit
I'll test the most important things visitors need to do on a phone and identify where the layout or features get in their way.
You'll get a plan for mobile fixes that distinguishes small changes from a larger rebuild, with time and cost estimates.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an audit- which features are unavailable and since when
- whether the error can be reproduced and what the logs show
- how the problem affects customer inquiries and sales
- restore the most important features
- fix the identified cause of the error
- check that the repair hasn't disrupted other parts of the website
A possible first step
You can start with an audit
I'll investigate the reported error and its effect on key website features.
You'll get an explanation of possible causes, repair priorities and an estimated time and cost to restore functionality.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an audit- what already works and can be kept
- what content, features or access are missing
- the work needed for a safe launch
- put together a plan to finish the website, in the right order
- use the completed parts if they make sense
- get the website ready to launch and check that it works
A possible first step
You can start with an audit
I'll check what already works, what's missing for launch and which parts of the project are worth keeping.
You'll get a plan to finish the website, with the order of work and an estimated time and cost to launch.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an audit- how the most important content is edited
- permissions and limits of the current system
- which changes can be made easier without a rebuild
- make the most common elements easier to edit
- organize the fields and screens you use
- show you how to make changes safely
A possible first step
You can start with an audit
I'll go through your most common content changes and show what's making editing difficult and what can be simplified without a rebuild.
You'll get suggestions for improving editing, from small fixes to bigger changes, with time and cost estimates.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an audit- which information is out of date or inconsistent
- how often your services change and who approves content
- whether the current editing process makes updates easy
- organize the content you identify and correct the most important information
- set up a simple process for requesting changes
- help plan regular website reviews
A possible first step
You can start with an audit
I'll review the information that matters most to customers, identify outdated or inconsistent content and suggest a way to check it regularly.
You'll get a prioritized list of content to update and a plan to organize it, with estimated time and cost.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an audit- which parts of the website need updating
- whether a backup is made before changes
- how the website is checked after an update
- prioritize and carry out overdue updates
- check key features after the changes
- take over regular updates and website checks
A possible first step
You can start with an audit
I'll check the state of the website software, overdue updates and how changes are protected with a backup.
You'll get a plan for overdue updates and ongoing care, with the order of work and time and cost estimates.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an audit- business goals and the needs of your main audiences
- which content and features still do their job
- what can stay and what needs to change
- propose a structure that supports your new goals
- compare the scope of updating and rebuilding the website
- implement the option chosen based on that assessment
A possible first step
You can start with an audit
I'll assess how well the current website supports your new business goals and compare updating it with building a new one.
You'll get a comparison of both options, including the scope, estimated time and cost of each.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an audit- the number and types of repeated questions
- the quality of answer sources and access to data
- when a human needs to be involved in the answer
- assess whether better content is enough or AI would help
- design a limited scope for automation
- test the answers against real questions
A possible first step
You can start with an audit
I'll review the most common customer questions and the sources of their answers to see whether better content is enough or automation is worthwhile.
You'll get an assessment of whether automation makes sense and a proposed solution with an estimated scope, timeline and cost.
Once you've received the audit, you can decide whether to ask me to do the follow-up work.
Ask about an auditSend me your website address and tell me which pages feel slowest. That's enough to start a conversation about what to check.
Send me your website address and an example of a page or element that causes trouble on a phone. If you can, include a screenshot.
Send me your website address, a description of the error and when it started. If it blocks a form or orders, mention that in your message.
Tell me what stage the project is at, what's left to do and whether you have access to the files and hosting. You don't need a complete specification.
Send me your website address and two or three examples of content that's difficult to change. We can use those to decide what to check.
Send me your website address and point out what's out of date. If there are many changes, a few examples are enough to begin with.
Send me your website address and tell me when its software was last updated and who looks after it now. If you don't know, we can start there too.
Tell me what your business does and what your current website no longer helps you achieve. You don't need to prepare a specification.
Tell me which questions customers ask most often and how your team answers them today. That will help us assess whether automation makes sense.
If either problem stops customers from using your website or contacting your business, deal with that one first. In your message, describe both problems and include your website address. I'll help you decide what to tackle next and in what order.
