FAQs

No. The planners do not request a page, scan resources or observe visitors. They organise your entered information and, where relevant, calculate a simple scenario. A result cannot establish the actual speed of your website.

No account or payment is required for any of the six planners. Results are generated in the page without a sign-up gate or an email requirement.

No. The public tools have no connection workflow and ask for no credentials. Installing the website plugin lets the owner publish these pages; it does not give a visitor’s planner access to another WordPress installation.

The supplied plugin keeps planner entries in the current browser page and sends no planner payload to a server. It does not use persistent browser storage. Leaving, reloading or resetting the page clears the active plan. Your browser may independently remember form values, and other site components have their own behaviour.

Yes. Build a result, then select Download text or Print plan. The browser creates the text file locally, and its print dialog can usually save a PDF. Share the saved file yourself after checking it for sensitive details. There is no public share link or server-side saved plan.

The estimator uses an additive model of transfer time, network rounds, server response and device processing. Real browsers overlap work, and networks and devices vary. It is neither a live test nor a Core Web Vitals result.

No. A name or count is not a benchmark or a security finding. The planner creates an inventory review process and repeats counts you supplied. Confirm purpose, dependencies and page coverage on a staging copy.

No. They are planning tools, not optimisation agents. You or an authorised maintainer must perform any changes using appropriate software and access. Use backups and staging rather than experimenting directly on important live workflows.

Optional blank fields are left out of the result. Entered text is placed in text nodes, not interpreted as HTML. A typed tag remains visible text. Numeric fields use bounded values, and related counts are checked before a result is built.

The supplied plugin adds neither analytics nor planner cookies, and it does not use localStorage or sessionStorage. WordPress, the host, theme or separately installed services may set cookies or log page requests. The operator must check those additions and update notices where needed.

There is no universal number. Image needs depend on dimensions, subject and quality. Cache settings depend on changing and personalised content, provider behaviour and purge rules. Use the plans to write assumptions, then verify them with representative pages and your own workflow.

No. The tools do not forecast rankings, revenue, speed scores or seconds saved. Better planning can make work clearer, but actual outcomes depend on implementation and conditions the tools do not observe.

Have a usable backup and rollback process, work in staging, record your own baseline, and check forms, navigation, accounts and checkout after changes. Change one thing at a time so a regression is easier to trace.

Use the Contact page for the operator’s configured public email and reporting guidance. Do not include admin credentials or customer information. If no email is published, this plugin does not provide an alternative server-side submission channel.