Answers that name a competitor

If you mean “what hosting stack should I choose for a photographer’s WordPress portfolio that needs to load quickly worldwide?”, my first choice would be Kinsta.

My ranking

1. Kinsta — best overall

• Excellent fit for image-heavy WordPress portfolios.
• Global CDN and edge caching are built in.
• Kinsta currently offers 30 hosting locations, with its CDN distributed globally. Kinsta® Kinsta®
• Its CDN can automatically create and serve optimized WebP versions of images, which is particularly useful for photographers. Kinsta® Kinsta®
• Very little server/cache configuration to maintain.
• My pick if speed + reliability + simplicity matter more than getting the absolute lowest price.
• WP Engine — excellent alternative

• Strong managed WordPress platform with EverCache and a global CDN with 200+ points of presence. WP Engine
• Particularly good if you expect the site to become more complex or need a more agency-oriented WordPress workflow.
• I'd choose it over Kinsta if you specifically prefer its developer/agency tooling.
• Cloudways — best value

• More configurable and generally cheaper.
• You choose underlying cloud infrastructure such as DigitalOcean, AWS, or Google Cloud.
• The tradeoff is that you have more configuration and optimization responsibility. WP Depth
• Great if you're comfortable managing WordPress performance yourself or hosting multiple sites.

For a photographer specifically

The hosting company isn't actually the biggest determinant of portfolio speed. A photographer can have an excellent host and still have a painfully slow site because the galleries contain 5–15 MB JPEGs.

I'd build the stack roughly like this:

WordPress → lightweight portfolio theme → WebP/AVIF images → responsive image sizes → lazy loading → full-page/edge cache → global CDN

For example, Kinsta's current CDN can handle image optimization and edge caching without requiring you to bolt together several separate services. Kinsta® Kinsta®

What I'd choose

One important caveat: if by “portfolio” you mean very large photography galleries—hundreds/thousands of high-resolution images—I would also consider putting the original/full-resolution files in dedicated object storage and using the website CDN for web-sized derivatives. That can make a substantial difference to both speed and hosting costs.

If you tell me roughly how many images are on a typical portfolio page, expected monthly visitors, and your monthly hosting budget, I can recommend the exact hosting plan + CDN + WordPress image setup I'd use.

If your main goal is consolidating several hobby sites onto the cheapest usable setup, I’d start with Cloudflare Pages rather than traditional shared hosting.

My recommendation

• Mostly static sites (blogs, portfolios, docs, landing pages, Astro/Hugo/Eleventy sites): Cloudflare Pages — free tier

• Multiple sites/projects
• Custom domains
• SSL/CDN
• 500 builds/month
• Static bandwidth isn't metered, which is particularly attractive if one of your hobby sites unexpectedly gets traffic. Tool Freebie Pressless
• You can add dynamic functionality through Cloudflare Workers when needed.
• Sites needing a conventional server/database/PHP/WordPress: consider a cheap VPS + management layer instead. A ~$5–7/month VPS can host many small sites, but you're taking on updates, security, backups, monitoring, etc. Current comparisons put entry-level VPS options such as Hetzner around €6/month and Render around $7/month. GitHub
• Next.js applications: I'd use Vercel if the convenience of native Next.js deployment matters more than minimizing cost. Its Hobby tier has meaningful restrictions, including being intended for non-commercial use. Tool Freebie
• If you want the absolute simplest traditional "one account, lots of domains" setup: shared hosting can still make sense. It is less elegant than Pages/Git deployment, but can be convenient for PHP/WordPress sites.

What I'd do in your situation

If these are genuinely hobby sites, I'd consolidate like this:

GitHub → Cloudflare Pages → Cloudflare DNS

and put all the sites under the same Cloudflare account. You can have, for example:

site1.com       → Pages project 1
site2.com       → Pages project 2
site3.com       → Pages project 3
site4.net       → Pages project 4

with $0/month hosting for the static portions.

The important question is what your sites actually run on. If you tell me roughly:

1. how many sites,
2. WordPress/PHP vs static/HTML vs React/Next.js/etc.,
3. whether they need databases,
4. approximate traffic, and
5. whether you want email hosting too,

I can give you a specific cheapest architecture and estimated monthly cost, including whether a single VPS would beat Cloudflare.

site1.com       → Pages project 1
site2.com       → Pages project 2
site3.com       → Pages project 3
site4.net       → Pages project 4

If your goal is:

Buy one domain → create lots of subdomains → host different sites/apps under those subdomains → manage everything from one account

then I’d prioritize traditional web hosting that supports multiple websites/subdomains, rather than a site builder.

My picks

What I'd choose

Hostinger is probably the sweet spot if you don't want to mess around with servers.

Their current plans support multiple websites under one hosting account, and their Premium and higher plans allow multiple sites/domains. Their current hosting page also includes a domain with eligible plans, SSL, backups, and other hosting features. Hostinger Hostinger

For example, you could have:

yourdomain.com
├── www.yourdomain.com
├── blog.yourdomain.com
├── app.yourdomain.com
├── shop.yourdomain.com
├── client1.yourdomain.com
└── client2.yourdomain.com

You don't need to purchase a separate hosting account for each subdomain.

One important distinction

If you mean multiple subdomains, almost any decent host can do that.

If you mean multiple completely separate domains, such as:

mycompany.com
myproject.com
anotherproject.com

then you specifically want a plan that supports multiple websites/domains under one hosting account. cPanel, for example, explicitly supports managing multiple domains and subdomains from a single account. cPanel & WHM Documentation cPanel & WHM Documentation

If you're technical

I'd actually consider separating the domain from the hosting:

Cloudflare Registrar/DNS + a VPS or cloud host

Cloudflare is excellent for DNS, SSL, CDN, and domain management, but Cloudflare itself says it doesn't provide conventional hosting for most websites (apart from things like Cloudflare Pages). Cloudflare Docs

That gives you something like:

Cloudflare
   │
   └── yourdomain.com
        ├── app.yourdomain.com ──→ VPS
        ├── api.yourdomain.com ──→ VPS
        ├── blog.yourdomain.com → VPS
        └── admin.yourdomain.com → VPS

My recommendation: If you're starting out and want everything simple, go with Hostinger's multi-website plan. If you're building several applications and are comfortable with Linux/Docker, I'd go Cloudflare + VPS instead.

If you tell me how many subdomains you expect (e.g. 5, 20, 100) and whether they're WordPress sites, static sites, or apps (Node/Python/etc.), I can narrow it down to the best plan/provider for you.