What this check examines
Public delivery signals that often get confused with hosting.
Delivery means what happens before the browser starts rendering the page: redirects, HTTPS, response headers, cache clues and the first edge response observation.
Preliminary hosting delivery check
Is your web host really the problem?
Enter your website to inspect redirects, HTTPS, caching and edge response. Get a clear preliminary report before you migrate or upgrade your hosting.
Redirect path
Shows how many URL hops happen before the final page, because extra redirects can add delay.
HTTPS configuration
Checks whether the final page uses HTTPS and whether a redirect downgraded from HTTPS to HTTP.
Cache and compression signals
Reads public headers such as cache status, cache-control and content-encoding when available.
Edge response observation
Records how long one Cloudflare edge check waited for response headers from the public page.
What this check does not measure yet
A preliminary delivery check is not a full speed audit.
A slow page can come from the browser, scripts, images, third-party tags, or the origin server. This check only covers the public delivery layer listed above.
Browser rendering
It does not measure how long the page takes to paint, become interactive, or run JavaScript.
Core Web Vitals or PageSpeed
It does not run Lighthouse, PageSpeed, or Core Web Vitals checks.
Real-user or global origin performance
It does not use visitor field data or test the origin host from many regions.
Three possible result types
The report should tell you what the delivery check can support.
Redirects, HTTPS and public cache or compression clues do not show an obvious delivery problem in this check.
The report found something concrete to review, such as too many redirects, an HTTPS issue or weak cache signals.
The check does not have enough information to blame hosting. You may need browser performance or repeat tests.
Why this is different
It answers a narrower question first.
Generic speed tests are useful, but they mix many causes into one score. HostingSelectPro starts with delivery clues so you can decide whether the first response path deserves attention before you spend money.
Redirect and HTTPS path
- HostingSelectPro
- Shown as delivery evidence
- Generic speed test
- Often folded into a broader score
Cache and compression clues
- HostingSelectPro
- Listed with source labels
- Generic speed test
- May be mixed with page advice
Provider recommendation
- HostingSelectPro
- No hosting recommendations
- Generic speed test
- Depends on the tool
Browser and Core Web Vitals
- HostingSelectPro
- Not measured in this check
- Generic speed test
- Often included
| Question | HostingSelectPro | Generic speed test |
|---|---|---|
| Redirect and HTTPS path | Shown as delivery evidence | Often folded into a broader score |
| Cache and compression clues | Listed with source labels | May be mixed with page advice |
| Provider recommendation | No hosting recommendations | Depends on the tool |
| Browser and Core Web Vitals | Not measured in this check | Often included |
True Hosting Cost Calculator
Know the renewal cost before you upgrade.
Compare due today, one-year cost, four-year cost, eight-year cost and add-ons before choosing a hosting plan.
Methodology
Every metric needs a source and a limit.
The report labels where each observation came from and states what the check cannot prove. A single edge response observation is a clue, not a final hosting verdict.
Read methodologyFAQ
Common questions before checking a site
Can this prove hosting is the cause?
No. It can show delivery clues that need attention, but one edge check cannot prove global origin hosting performance.
Does it identify my hosting provider?
No. If a CDN is visible, the report may show the observed delivery network, but it does not claim to know the origin host.
Will the probe change my website?
No. It requests public response headers and a capped amount of HTML without logging in or changing files.