Paid diagnosis for slow, unstable or bloated AI-built websites
AI Website Performance Audit
Find the real loading, responsiveness and layout problems before spending money on random plugins, hosting changes or cosmetic speed scores.
Evidence before optimisation. Priority fixes. Implementation quoted separately.
A score is useful evidence, but it is not the diagnosis
AI-built websites can feel quick in an early preview and slow down as real images, scripts, tracking, fonts, plugins and content are added. Performance problems can also come from hosting, third-party services, repeated components or code that does unnecessary work in the browser.
The audit identifies the bottlenecks affecting the agreed pages and journeys. Google’s current Core Web Vitals cover loading, responsiveness and visual stability through Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. Those metrics are useful, but the work still needs to connect measured symptoms to causes and practical fixes.
Running a public speed test can help qualify the enquiry. Investigating templates, code, assets, hosting, third parties and real causes is paid audit work.
Lab tests, field data and human experience answer different questions
A single test captures one device, network and moment. Real-user data, where available, reflects a wider range of visits. Neither replaces checking the page itself, the business-critical journey and the technical work that creates the delay.
Measurements can show
- When important content becomes visible
- How quickly the page responds to interaction
- Whether content shifts while loading
- Which assets, scripts or requests consume time
- Differences between mobile and desktop conditions
Diagnosis must establish
- Which bottlenecks are under your control
- Whether the problem is page-specific or site-wide
- Which third-party tools are commercially necessary
- Whether hosting, code, content or design should change
- Which fixes are likely to produce useful improvement without breaking the site
The audit follows the slow journey from browser to server and back
The exact checks depend on the platform and symptoms. The aim is to identify the small number of changes that matter rather than recommending every possible optimisation technique.
Images, fonts and page assets
I review oversized media, formats, loading behaviour, font choices and assets that delay useful content or consume unnecessary bandwidth.
Scripts and third parties
I identify tracking, widgets, libraries and integrations that block rendering, duplicate work or add significant cost to important pages.
Templates, plugins and code
I inspect repeated components, builder overhead, plugin behaviour and selected code paths that create avoidable browser or server work.
Hosting, caching and delivery
I review relevant server response, caching, compression, CDN and hosting constraints where the available access and evidence support it.
Performance work can involve trade-offs. Removing a useful feature purely to improve a score may be poor business advice, while keeping an unnecessary script because it is familiar may also be poor value.
Use a performance audit when you need causes and priorities, not another generic report
The service is designed for websites where speed, responsiveness or visual stability is affecting usability, trust, search foundations or the ability to maintain the site.
A good fit
- Mobile pages feel much slower than the preview suggested
- Core Web Vitals or other tests show recurring weaknesses
- The site has accumulated scripts, plugins or repeated components
- A key landing page becomes unstable or slow under real content
- Previous optimisation plugins have not solved the underlying issue
- You need to decide whether hosting, code or page design should change
Another service may be better
- The main issue is broken functionality rather than speed
- You need a pre-launch check across forms, SEO and tracking
- The codebase itself needs maintainability or security review
- The website has broad connected problems with no confirmed cause
- The current platform is so limited that repair-versus-rebuild is the real decision
Where performance is only one symptom in a wider failing build, I will recommend the broader paid audit rather than isolating the speed score from the rest of the website.
The evidence should be measurements and reproducible behaviour, not a dramatic testimonial
I do not have a published AI-builder performance case study and I will not invent one. The audit stands on the evidence collected from the website and my wider experience building and improving commercial sites.
The projects below are broader website and SEO evidence, not AI performance case studies. They show the practical value of combining technical work with content, structure and the customer journey.
Jet Washing Farnham
A new local business needed a website planned around real services and search intent, with a clear route from discovery to enquiry.
LAN Support
A restrictive website was rebuilt on a flexible WordPress structure so useful pages could be added and the customer journey could be improved.
For more background, read about my experience. I will describe uncertainty plainly and will not replace missing proof with an invented quote.
The audit moves from symptom to cause before recommending changes
A successful implementation should be validated against the same pages and conditions used to establish the baseline, while recognising that real-user performance can vary.
Price depends on the templates, platform and depth of investigation
A single slow landing page can be a focused audit. A website with several templates, custom code, ecommerce, multiple third parties and uncertain hosting needs a wider scope.
You receive the pages, devices, tests, access, deliverable and price before the investigation starts. The audit does not include unlimited rounds of optimisation or a promise to achieve a particular score.
Included when named in scope
- Baseline measurements for the agreed pages and conditions
- Investigation of likely asset, script, code and hosting causes
- Practical Core Web Vitals and mobile findings
- Prioritised recommendations with trade-offs explained
- A separate implementation and re-test route where appropriate
Not included automatically
- Guaranteed scores or search rankings
- Automatic removal of every third-party tool
- Code, hosting or design changes within the audit fee
- Unlimited testing across every page and device
- Control over external services, networks or visitor hardware
- Third-party hosting, CDN, licence or specialist costs
Performance can be improved without chasing perfection. The target should be a faster, more stable customer experience and a maintainable website, not a screenshot of one favourable test.
Frequently Asked Questions
What are Core Web Vitals?
They are Google’s current page-experience metrics for loading, responsiveness and visual stability: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. They are useful signals, but they do not explain every cause or business impact.
Will you guarantee a 100 performance score?
No. Scores vary by tool, device, network and page conditions. The audit identifies practical bottlenecks and priorities rather than promising a particular number that may not reflect real visitors.
Do you use PageSpeed Insights?
It can be one source of evidence, alongside browser tools, request analysis, available real-user data and direct testing of the important pages. No single tool is treated as the complete diagnosis.
Can hosting be the cause of poor performance?
Yes, but it is only one possible cause. Slow server response, weak caching or delivery can matter, while oversized images, third-party scripts and page code may remain slow even on better hosting.
Is fixing the performance included?
No. The audit provides the baseline, causes and priority actions. Implementation is a separate paid phase so that you can approve the changes and trade-offs after seeing the evidence.
Can you improve mobile performance without changing the design?
Sometimes. Asset loading, scripts, caching and code may be improved without a visible redesign. In other cases, heavy layouts, animations or third-party features need to change to produce a meaningful result.
Will faster pages improve rankings or conversions?
A better experience can support users and SEO foundations, but I do not guarantee rankings, traffic or enquiries. Results also depend on content, demand, competition, offer quality and the rest of the customer journey.
What happens after the fixes are made?
The agreed pages should be re-tested against the baseline and checked for visual or functional regressions. Field data, where available, may take time to reflect changes and can vary with real users.
Related AI website services
These pages cover the related parts of the AI website service family.
For broader search work on an established website, see monthly SEO services and AI SEO services.
Find the bottleneck before paying for random optimisation
Tell me which pages feel slow, what platform is involved and what testing has already been done. I will define the pages, evidence, access and price before the audit starts.
Prefer to write it down? Send a quick enquiry.