Speed
Make the server answer before visitors give up
Your server takes too long to start sending the page, so visitors wait at a blank screen with no sign that anything is happening.
Why it matters
There are two delays between a click and a page: the wait for the server to begin replying, and the time the browser then spends drawing it. This is the first one, and it is the one that feels worst. Nothing appears on screen during it, so a visitor has no feedback at all and simply leaves. Because your server is slow rather than the visitor connection, the same wait applies to everyone.
How you would notice it
- Pages hang for a second or more before any content appears.
- The same pages feel slow even on a fast office connection.
- A hosting dashboard reports slow response times or a high percentage of server time.
What to do
Stage 1
- Measure it from your side first, so you can tell whether a change helped. The Siege Test reports this number for your site.
Test a page you have never visited in that browser. A page already saved on your own machine will look instant, which tells you nothing about what a first time visitor experiences.
https://noblemarketglobal.com/audit/Stage 2
- If your site is behind a CDN or platform host, turn on page caching. This is the single largest improvement available for most small sites, and it needs no code.
Look for a setting named Caching, Cache Level, or Page Rules. Serving the stored copy means the visitor never waits for your server to build the page at all.
- If pages are built from a database, check the slow query log in your hosting panel and add an index for any query that appears there repeatedly.
A missing database index is the usual cause of a page that is fast when you test it alone and slow once several people are on the site at once.
- If the server still cannot answer quickly, the fix is a better host rather than more code. Shared hosting with no caching layer will stay slow regardless of what you optimise.
How to check it worked
Confirm it worked
Run the Siege Test once, make one change, wait for it to be live, then run it again. The server response number should drop. If it does not move at all after a caching change, the change is not actually applied, so confirm the setting saved.