Methodology
How HostingSelectPro reaches a verdict
HostingSelectPro is designed to slow down premature migration decisions. The report weighs hosting signals against website implementation signals and reduces confidence when important data is unavailable.
Evidence groups
Signals stay separated
Reports separate server delivery, website efficiency, real user experience, and technical configuration. A verdict should come from the pattern across groups, not from a single slow metric.
Verdict labels
Four outcomes, no overreach
Host likely means server-side delivery evidence is strong. Website likely means page implementation is the clearer bottleneck. Mixed means both sides need attention. Insufficient evidence means the report cannot responsibly choose.
Confidence
Agreement raises confidence
Confidence rises when multiple independent signals agree and falls when field data, origin detail, or repeat checks are unavailable.
CDN-hidden origins
Observed network is not origin identity
When a CDN is visible, the report names the observed network and avoids claiming to know the origin host. The correct wording is direct: observed network is visible, origin hosting provider is hidden by CDN.
Edge probe limits
Preliminary checks stay preliminary
The live Edge response probe is a preliminary check from one Cloudflare edge execution. It records reachability, manual redirects, response-header timing, HTTPS use, HTML detection, and public cache or delivery clues. It is not a global TTFB measurement, browser performance test, real-user experience report, or origin hosting provider lookup.
For HTML responses, the probe inspects at most 128 KiB. A runtime may deliver a larger stream chunk, but HostingSelectPro counts only inspected bytes up to the cap and cancels once the cap is reached. The report labels this as the inspection cap being reached, not as proof that the remote body was definitely larger.
The probe does not force cache-bypass request headers such as no-cache. Cache clues are treated as observations of ordinary behavior for the requested route, not as a complete cache audit.