Measured website & server performance support

Website Performance Optimization From Browser to Database

Find and reduce slow TTFB, poor Core Web Vitals, overloaded PHP workers, slow database queries, cache misses, heavy WordPress execution, Cloudflare mistakes, and slow ecommerce workflows.

You do not need to host with usThis is a paid engineering service, open to anyone. We work on your systems wherever they run — another hosting provider, your own server, or a client's account.
Request Performance SupportSee the investigation process
  • Baseline before optimisation
  • Dynamic and personalised paths protected
  • Changes measured against the same test
  • No universal speed-score guarantees

Send the affected URLs, locations or devices, when the slowdown occurs, business impact, recent changes, available monitoring or test results, hosting plan, traffic pattern, and whether logged-in or checkout users are affected.

evidence-console controlled scope
$ profile request --browser-to-origin
01
Browser experienceLCP, INP, CLS, assets, main thread
02
Network and edgeDNS, TLS, cache, CDN, geography
03
Application runtimePHP, WordPress, APIs, external calls
04
Origin resourcesDatabase, CPU, memory, disk, workers
MethodEvidence first
ChangesApproved only
OutputVerified report
Slow TTFBEdge, origin, runtime, and query timing
Core Web VitalsLCP, INP, CLS, and rendering evidence
Backend bottlenecksPHP workers, queries, jobs, and storage
Ecommerce speedCart, checkout, account, and API paths
Performance work with a baseline

A faster synthetic score is not enough if production gets slower.

Performance varies by URL, cache state, geography, device, login state, traffic, data size, and business workflow. We define the slow experience, measure the same path, and protect correctness while changing it.

Production remains yoursOptimisation does not justify caching private responses, hiding errors, disabling required security, or making untested production changes. Business correctness and recoverability remain part of the acceptance criteria.
01

Define the affected experience

We distinguish first visit, repeat visit, logged-in use, wp-admin, product, search, cart, checkout, API, cron, and traffic-spike behaviour.

02

Record a comparable baseline

URL, device, region, cache state, data state, test method, server timing, and workload conditions are kept consistent where practical.

03

Profile the slow layer

Browser work, assets, network, Cloudflare, web server, PHP, WordPress, database, storage, and external services are separated.

04

Protect dynamic content

Sessions, carts, checkout, accounts, admin pages, APIs, webhooks, and personalised responses are excluded from unsafe caching.

05

Verify impact and side effects

Speed, errors, content freshness, functionality, resource use, and the real business workflow are checked after changes.

Performance problems we solve

Frontend experience, application execution, and origin capacity

We investigate the component that owns the delay instead of applying a generic optimisation checklist to every website.

01

Core Web Vitals and frontend

Identify rendering, interaction, layout, asset, and third-party work that affects real browser experience.

  • Largest Contentful Paint (LCP)
  • Interaction to Next Paint (INP)
  • Cumulative Layout Shift (CLS)
  • Images, fonts, CSS, and JavaScript
  • Third-party scripts and tag load
02

Network, CDN and caching

Reduce avoidable distance and repeat work while preserving personalised and time-sensitive responses.

  • DNS, TLS, and connection timing
  • Cloudflare cache behaviour
  • Page and object caching
  • Cache misses and purge strategy
  • Compression and asset delivery
03

WordPress, PHP and application

Profile server-side execution where themes, plugins, APIs, jobs, or worker capacity delay the response.

  • Slow WordPress and wp-admin
  • PHP-FPM worker saturation
  • Plugin and theme execution
  • Cron, queues, and external APIs
  • Memory and error pressure
04

Database and server resources

Investigate query, storage, CPU, memory, concurrency, and service constraints behind slow or unstable requests.

  • Slow MySQL / MariaDB queries
  • Locks and database contention
  • CPU, RAM, disk, and inode pressure
  • Web-server concurrency
  • Traffic spikes and capacity limits
Revenue-path performance

Optimise ecommerce without caching carts, customers, or payment responses incorrectly.

We can profile product, search, cart, checkout, account, AJAX, REST API, payment callback, order, email, and scheduled-action paths separately so speed changes preserve transaction correctness.

Controlled troubleshooting

Measure, isolate, change, and compare

We establish the slow path and baseline, profile the responsible layer, apply an approved focused change, then compare performance and functionality under equivalent conditions.

  1. 01

    Describe the symptoms

    Tell us which pages are slow, for which visitors, and what the impact is. Send a PageSpeed or field-data report if you have one—you do not need to diagnose the performance problem.

  2. 02

    Confirm the investigation scope

    We agree which templates and journeys matter—home, category, product, checkout—and the access needed to profile them without changing live behaviour.

  3. 03

    Trace where the time goes

    We separate server time from browser time: PHP-FPM and MySQL profiling, cache hit ratio, and Core Web Vitals field data, so effort goes where the milliseconds are.

  4. 04

    Review findings and proposal

    You receive a ranked list—slow queries, missing cache rules, oversized assets, third-party scripts—with expected gain per item, the risk, and a quote where needed.

  5. 05

    Approve, optimise, and verify

    After approval we apply the changes, then re-measure TTFB, LCP, and CLS on the same pages so the improvement is proven rather than assumed.

Clear approval boundary. Investigation and repair are separated where applicable. Broader changes, added scope, and material risk are explained before you authorise the work.

Start a scoped request
Anonymised performance case pattern

The homepage was fast, but checkout stalled during busy periods

Cached public pages scored well while uncached customer requests slowed or timed out under modest concurrency.

Root causeA scheduled background task and slow order queries consumed PHP workers and database capacity, while the public-page cache hid the origin pressure from superficial tests.
  • Cached and uncached paths were measured separately.
  • PHP-FPM saturation, task timing, and slow queries were correlated.
  • The job schedule and query path were improved without caching checkout.
  • A controlled transaction and concurrent uncached requests were retested.
performance-profile.logdiagnostic record

homepagecache=HIT ttfb=84ms

checkoutcache=BYPASS ttfb=4.8s

php-fpmmax children reached

databaseorder query and job overlap

changeschedule isolated; query reduced

verifycheckout correct; latency stable

Uncached transaction path stabilisedNo cart or checkout response cached
Engagement options

Fix one bottleneck or build a prioritised performance plan

Choose focused troubleshooting for a defined slow path, or request a broader review across representative pages, devices, cache states, and backend resources.

Focused investigation

Performance Troubleshooting

For a slow page, high TTFB, traffic incident, wp-admin delay, checkout bottleneck, or resource problem.

Best for
  • Affected-path baseline
  • Layer-by-layer profiling
  • Focused optimisation or repair
  • Equivalent-condition verification
Request performance help
Structured assessment

Website Performance Review

For businesses that need a prioritised plan spanning browser experience, delivery, application, and origin capacity.

Best for
  • Representative URL and workflow set
  • Core Web Vitals and TTFB
  • Cache, PHP, and database review
  • Prioritised findings and trade-offs
Discuss a performance review
Why Hostaccent

Performance troubleshooting needs visibility across every layer

Hostaccent works with Linux, web servers, PHP-FPM, databases, WordPress, ecommerce, DNS, SSL, and Cloudflare. We can trace a slow browser experience into the origin instead of treating optimisation as a plugin installation task.

Browser-to-database analysis
WordPress and ecommerce context
Server-capacity troubleshooting
Measured changes without score guarantees
Performance layers and toolsCommon platforms and layers
Core Web VitalsWordPressWooCommercePHP-FPMMySQL / MariaDBApacheNginxLiteSpeedRedis / Object CacheCloudflarePage CacheBrowser AssetsLinux ResourcesApplication Logs

Results depend on the application, hosting resources, code, third-party services, user location, device, traffic, data, cache state, and access available. Hostaccent does not guarantee a specific score, ranking, load time, or business outcome for every test condition.

The Hostaccent support ecosystem

One technical partner. Ten specialist paths.

A slow page rarely has one cause: TTFB can come from PHP execution, an unindexed query, a cache that never warms, or render-blocking assets long after the server has replied. Explore every specialist service without losing the wider production context.

Not sure which service matches?Tell us which page is slow and for whom—we will start where the time is actually spent.
Request technical support
Questions before access

Scope, credentials, approval, and practical expectations

These answers explain how the investigation works before you share access or approve a production change.

Ask about your environment
01Do I need to buy hosting from HostAccent to use this service?

No. This is a paid service and the site can be hosted anywhere. We profile whatever stack it runs on — another provider's shared hosting, a VPS, or a managed platform — and report where the time is actually spent. Where a hosting limit is genuinely the ceiling, we show the evidence instead of simply recommending a move.

02Can you improve Core Web Vitals?

We can investigate LCP, INP, CLS, rendering, images, fonts, CSS, JavaScript, third-party scripts, network delivery, server response, and application behaviour. The achievable result depends on the site, content, code, platform, and third parties.

03Can you fix a slow WordPress website or wp-admin?

Yes. We can separate frontend and admin paths and inspect plugins, themes, PHP workers, memory, database queries, cron, object cache, page cache, external APIs, storage, and server resources.

04Can you reduce slow TTFB?

Yes. We measure DNS, connection, TLS, edge cache, origin connection, web server, PHP, application, database, and external dependencies to determine which part owns the delay before optimising it.

05Will you install a caching plugin?

Only when it fits the diagnosed problem and application. A plugin alone cannot fix every bottleneck, and unsafe caching can break sessions, carts, accounts, admin pages, APIs, webhooks, or personalised content.

06Can you optimise WooCommerce checkout performance?

Yes. We can profile product, search, cart, checkout, account, AJAX, scheduled actions, PHP, database, cache bypass, and payment-related paths. Transaction correctness is verified alongside speed.

07Can you tune PHP-FPM, Nginx, Apache, or MySQL?

Yes, when authorised server access and evidence are available. We assess workload, concurrency, resources, configuration inheritance, query behaviour, application limits, and neighbouring-service impact before changing server settings.

08Can Cloudflare make the website faster?

Cloudflare can improve delivery for suitable content, but cache rules, origin behaviour, geography, dynamic paths, assets, and the application must be considered. It cannot make every uncached database or application request fast by itself.

09Do you guarantee a 100 PageSpeed score?

No. Scores vary by test, device, network, content, third-party scripts, and platform. We focus on evidence-backed improvements to representative user experiences and explain remaining constraints and trade-offs.

10What information should I send?

Provide affected URLs and workflows, device or location patterns, when slowdown occurs, test or monitoring results, hosting plan, traffic, recent changes, logged-in or ecommerce impact, and any relevant errors. Avoid sharing secrets in the problem description.

11Can you optimise a website hosted outside Hostaccent?

Yes. We can support authorised websites and compatible servers at third-party providers. Limited logs, shared-hosting restrictions, closed platforms, code ownership, or unavailable server access may limit the optimisations possible.

Send the symptoms, not a guess

Slow TTFB, poor Core Web Vitals, or an overloaded transaction path?

Send the affected URLs, workflows, conditions, and available evidence. We can measure the browser-to-origin path, isolate the responsible layer, and propose improvements that preserve production correctness.

Request Performance SupportAsk About a Performance ReviewNo broader changes before scope and approval