A website speed test that shows what's slowing your pages and costing you visitors
A slow page makes people wait before they can read or do what they came for.
GET //assets/site.css 380 msSome files may hold up the first view/assets/app.js 520 ms/images/hero.jpg 2.4 MB 910 msAn image may be oversized for its spaceSiteCMD's free website speed test reads your home page and the files it loads from your own domain for likely causes of slow loading, without opening a browser. Hosted scans also open each page in a browser to measure how it loads.
What a scan can flag, and what it can't measure
A scan can flag
- Likely causes of slow loadingThe free test reads your home page and the files it loads from your domain, without a browser.
- How each page loadsHosted scans open each page in a browser and measure it.
What it can't measure
- Every visitor's waitA phone on a slower network can take longer than your computer does.
- One run's exact numbersAds, A/B tests, network routing and your device move them, so compare runs made under the same conditions.
Explore what affects website speed
Speed up your server's response and repeat visits
2 guides
Find the delay before your server starts answering and narrow down its cause.
How to fix
- This needs a change to your site's server, hosting or code.
- Time the page several times and find where the server loses time, such as slow database lookups or calls to other services, then fix that part.
- If you turn on caching, which saves ready-made pages, pages that show a visitor's own details must never be shown to someone else.
- Then run the check again.
Performance
Your server is slow to respond
Your server takes a long time to send even the first byte of a response, delaying everything that has to follow it.
Fix with your agent
# SiteCMD Fix Brief: Your server is slow to respond Site: https://yoursite.com ## What is wrong Your server takes a long time to send even the first byte of a response, delaying everything that has to follow it. ## How to fix Confirm the single SiteCMD sample with several requests under comparable conditions, for example `curl -o /dev/null -s -w 'TTFB: %{time_starttransfer}s\n' https://yourdomain.com`. Trace the measured request through CDN/cache status, origin processing, database queries, and dependency calls and fix the segment that actually consumes time; cache only public or safely keyed responses and never share personalized HTML across users. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Set cache rules that reuse static files while keeping changing pages fresh.
How to fix
- This needs a change to your site's server or CDN settings.
- Set how long browsers may reuse each kind of file: a long time for files that get a new address whenever they change, and a short time for pages and files that can change without one.
- Pages that show a visitor's own account or details must never be saved and shown to other visitors.
- Then run the check again.
Performance
Browsers aren't told how long to keep files
Your server does not tell browsers how long they can safely reuse a response, so they may re-download content that has not changed.
Fix with your agent
# SiteCMD Fix Brief: Browsers aren't told how long to keep files Site: https://yoursite.com ## What is wrong Your server does not tell browsers how long they can safely reuse a response, so they may re-download content that has not changed. ## How to fix Classify each response by whether its URL is content-versioned, public or personalized, and how quickly it must become fresh. Reserve `public, max-age=31536000, immutable` for assets whose URL changes whenever bytes change; give mutable assets and HTML a freshness/revalidation policy, and never cache personalized or authorization-dependent content in a shared cache without a complete safe key and variation design. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Make your pages lighter and show content sooner
3 guides
Choose smaller image files, reserve their space and delay pictures below the fold.
How to fix
- This usually needs a change to your site's code.
- Check which version of the image phones and computers actually download, since our check may have measured the largest one.
- If that version is much bigger than the space it fills, add smaller versions sized for different screens, without lowering quality just to pass the check.
- Reload at several screen sizes and check that your browser downloads an image sized for the space it fills. The free scan may still flag the largest version.
Performance
An image may be oversized for its space
The image version a browser actually selects for this page is unusually large for how small it is shown.
Fix with your agent
# SiteCMD Fix Brief: An image may be oversized for its space Site: https://yoursite.com ## What is wrong The image version a browser actually selects for this page is unusually large for how small it is shown. ## How to fix Inspect the browser's selected candidate and rendered dimensions at representative breakpoints; we may measure the largest srcset candidate, so a response over 300 KB is a review threshold rather than proof that every visitor downloads it. If the selected candidate is oversized for its rendered use, generate appropriate widths with correct `srcset`/`sizes` and compare supported encodings at equivalent visual quality; do not reduce quality solely to cross the band. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Bring useful content into view sooner by changing how CSS, scripts and fonts load.
How to fix
- This needs a change to your site's code.
- Find which style or script files actually hold up the first view of the page, and load the ones that can wait later.
- Check that the page still looks right on a slow connection and with scripts turned off.
- Then run the check again.
Performance
Some files may hold up the first view
Stylesheets or scripts loading in the page head can hold up the very first useful thing a visitor sees.
Fix with your agent
# SiteCMD Fix Brief: Some files may hold up the first view Site: https://yoursite.com ## What is wrong Stylesheets or scripts loading in the page head can hold up the very first useful thing a visitor sees. ## How to fix Record a production Performance trace to identify which stylesheets or parser-blocking scripts actually delay the first useful render; the presence of a head resource alone does not prove it should be deferred. Use `defer` or modules for scripts that can run after parsing, remove unused CSS before considering inlining, keep truly synchronous bootstraps synchronous, and re-test slow-network and no-JavaScript behavior for flashes or missing styles. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Reduce download weight and page complexity by removing code and content you no longer need.
How to fix
- This usually needs a change to your site's code.
- Find what makes the page's main file so big, such as repeated content, data or images written straight into the page, or leftover debugging output, and remove what isn't needed.
- If part of the page isn't essential, it can move to its own page or load later.
- Then run the check again.
Performance
The page's main file is unusually large
The raw page document itself is unusually large, which can slow down how quickly anything starts to appear.
Fix with your agent
# SiteCMD Fix Brief: The page's main file is unusually large Site: https://yoursite.com ## What is wrong The raw page document itself is unusually large, which can slow down how quickly anything starts to appear. ## How to fix Start from the exact fetched HTML document size in the evidence and profile what contributes bytes: rendered content, serialized state, repeated markup, inline styles/scripts/SVG/data URIs, or debug output; the check does not attribute the cause. Remove unintended duplication and debug data first, defer or paginate a section only when it is genuinely non-critical, and treat the 1 MB and 3 MB bands as review thresholds, not universal product budgets. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Speed up slow database queries with the right indexes
1 guide
Index the foreign key columns your lookups and joins depend on.
How to fix
- Confirm the workload with EXPLAIN before adding anything; the referenced key is normally already indexed, and the candidate is the foreign-key column on the referencing (child) table, which PostgreSQL does not create automatically. When the query and data shape justify it, add the child-side index (
@@index([userId])in Prisma,index().on(table.userId)in Drizzle, orCREATE INDEX idx_orders_user_id ON orders(user_id)), then compare the plan and account for the added storage and write cost.
Performance
Linked-record lookups may be slow (missing indexes)
A foreign key column used by a relationship has no index, which can slow down related lookups as the table grows.
Fix with your agent
# SiteCMD Fix Brief: Linked-record lookups may be slow (missing indexes) Site: https://yoursite.com ## What is wrong A foreign key column used by a relationship has no index, which can slow down related lookups as the table grows. ## How to fix Confirm the workload with EXPLAIN before adding anything; the referenced key is normally already indexed, and the candidate is the foreign-key column on the referencing (child) table, which PostgreSQL does not create automatically. When the query and data shape justify it, add the child-side index (`@@index([userId])` in Prisma, `index().on(table.userId)` in Drizzle, or `CREATE INDEX idx_orders_user_id ON orders(user_id)`), then compare the plan and account for the added storage and write cost. ## Acceptance criteria SiteCMD accepts the fix when an authenticated code submission bound to this attempt, from your CI or the SiteCMD CLI, no longer reports the finding. SiteCMD records the result as self-attested. Make the smallest change that fixes the reported risk.
Frequently asked questions
Why is my website slow on mobile?
A phone can spend longer downloading files and processing JavaScript, especially on a slower network or device. A page that feels quick on your computer may still leave mobile visitors waiting.
Why do website speed test results change between runs?
A/B tests, changing ads, network routing, the device you test on and browser extensions can all move the numbers, as Lighthouse's scoring guide explains. Compare runs made under the same conditions before deciding whether a change helped.