Optimization & Caching: frequently asked questions

This article is part of the Spark Rack Performance & Reliability knowledgebase and covers Optimization & Caching. These frequently asked questions cover the decisions and failure patterns customers most often encounter. Each answer includes the practical next step rather than a one-line definition.

The relevant customer area is Application configuration, PHP settings, browser diagnostics, database behavior, and caching layers. It is used to manage website optimization and caching, including page generation, assets, images, compression, browser caches, application caches, personalized pages, database queries, and third-party calls. Controls can differ by product, lifecycle status, account permission, domain state, payment method, or service configuration. When an action is not shown, confirm eligibility and permission instead of following an unrelated workaround.

Before you begin

• Record a representative performance or availability baseline
• Collect timestamps, status codes, usage, and logs
• Know recent deployments, traffic changes, and scheduled jobs
• Create a backup before changing cache or application behavior
• Check the Status Center before changing production
• Identify the exact item associated with website optimization and caching and confirm its current status.
• Write down the expected result and the current value before changing anything.
• Plan a rollback or recovery path for any action that can affect access, billing, data, routing, delivery, or availability.

Frequently asked questions

Why can I see an item but not change it?

Visibility and change permission can be separate. The product, lifecycle state, owner policy, or delegated user permission may limit the action. Confirm the selected item and ask the account owner to review permissions.

Why did the portal save my value but the result has not changed?

The saved value may still require provisioning, cache expiration, external approval, client refresh, or a dependent setting. Check status indicators and run an independent end-to-end test.

Should I submit the form again when nothing appears to happen?

No. Wait for the action to complete, check for a modal or notice, refresh the item, and review whether the first request succeeded. Duplicate submissions can create conflicting or repeated work.

Can a contact manage the account?

A contact and an account user serve different purposes. Interactive access requires an invited user with the appropriate permissions; a contact may only receive selected notices.

What should I record before making a change?

Record the exact item, current value, reason, expected result, dependencies, approver, time, and rollback method. Do not capture unredacted passwords, recovery codes, or payment data.

How do I know whether the issue is local or service-wide?

Test another device or network, compare another user or item, and review the Status Center. A problem isolated to one browser, user, or client usually requires a different investigation from a broad outage.

When should I roll back?

Roll back when written success criteria are not met by the planned deadline, impact exceeds the approved scope, security is uncertain, or the change causes an unrelated critical failure.

What should I send to support?

Send the target identifier, expected and actual result, exact error, timeline, recent changes, safe evidence, and completed tests. Never send active secrets in ordinary ticket text.

Detailed operating procedure

Use this sequence as the baseline workflow for Optimization & Caching. Some steps may be informational when the selected product does not expose that exact control, but the verification and recordkeeping principles still apply.

1. Separate backend response time from asset loading and browser rendering
2. Measure page size, request count, slow resources, errors, and resource use
3. Optimize images, static assets, database work, and third-party calls
4. Cache only pages that do not contain private, personalized, cart, account, or form data
5. Review storage growth, overlapping scheduled jobs, backups, imports, bots, and abusive traffic
6. Change one layer at a time and compare the same test
7. Document sustained requirements before upgrading a service plan
8. Confirm that dependent settings still point to the intended destination and that no older value is overriding the new one.
9. Observe the result long enough to catch delayed processing, caching, queued work, or an intermittent failure.
10. Update internal documentation with the final value, date, owner, result, and any scheduled follow-up.

Verification checklist

• Repeated controlled tests improve
• Personalized pages and forms remain correct
• Usage returns to normal after corrective action
• Scheduled tasks do not overlap
• The service remains available across multiple checks
• The selected account item, identifier, domain, invoice, user, or service matches the original request.
• The portal no longer shows a pending or failed action unless delayed processing is expected and documented.
• An independent customer-side test produces the expected result.
• Related billing, security, notification, routing, and renewal settings remain correct.
• The previous value and rollback information are retained until the change is proven stable.

Common failure patterns

Use the symptom to narrow the investigation. Do not apply every possible fix at once.

• One browser refresh is treated as a benchmark
• Private account pages are cached
• A runaway task is hidden by a plan upgrade
• Backups fill the account
• A cron job starts before the previous run ends
• The correct value was saved on the wrong item, environment, domain, mailbox, record, user, or billing account.
• A dependent setting, external provider, cache, client, or application continues to use an older value.
• The item is pending, suspended, expired, unpaid, cancelled, locked, or otherwise not eligible for the requested action.
• The change completed, but verification reused an authenticated session or cached result that hid the actual behavior.
• A temporary error was treated as permanent and followed by multiple conflicting edits.

Security, privacy, and data handling

• Use a unique password stored in a reputable password manager and enable two-factor authentication for every account user who can access it.
• Give each person an individual account user instead of sharing the owner login. Remove access promptly when responsibilities change.
• Do not send passwords, two-factor recovery codes, full payment-card data, private keys, API secrets, or unredacted identity documents in a normal support reply.
• Review unexpected sign-in notices, permission changes, domain changes, payment changes, and credential resets as possible security events.
• After an access-related incident, rotate affected credentials, review delegated users and contacts, verify domains and DNS, and document the recovery actions.
• Limit access to website optimization and caching to people who need it and review that access when responsibilities change.
• Before sharing evidence involving page generation, assets, images, compression, browser caches, application caches, personalized pages, database queries, and third-party calls, redact information that is not required to diagnose the issue.

When to contact Spark Rack

Contact Spark Rack when the account shows a failed or inconsistent provider-side action, the required control is missing despite confirmed eligibility and permission, data restoration or protected logs are required, an unauthorized change is suspected, or the problem remains after a controlled rollback and independent verification.

• The account email address and the exact service, domain, invoice, ticket, or other item involved
• The page and section used, including the tab or subtab, without copying session tokens from the address bar
• The expected result and the actual result in separate sentences
• The approximate time of the last successful use and the first failure, including the time zone
• The exact error text, response code, bounce text, or visible status
• The changes made immediately before the issue, including old and new values when known
• The devices, browsers, networks, applications, or external tools used to reproduce the issue
• The troubleshooting steps already completed and the result of each step

Closeout and ongoing care

After Optimization & Caching is working, record the final state and remove any temporary access, files, forwarding paths, test records, or broad permissions that were created for the work. Review related expiration dates, renewal settings, payment status, contacts, and alerts so a future administrative event does not recreate the problem.

Keep the support history, change record, and safe verification evidence for as long as they are operationally useful. Periodic review is especially important after staff changes, migrations, major application updates, domain renewals, payment-method changes, or security incidents.