◇独立。 詳細情報 インフラ第一号

方法論 · レジリエンス

WordPressのホスティング: compare Hostinger and SiteGround plans

A dated offer snapshot, cash commitments, backup limits and a checklist matched to your WordPress workload.

Content site workload with editorial media database cache and integrations

Choose WordPressのホスティング from the work the site must perform, not from the largest advertised discount. An editorial site with cached pages, a membership area and a shop accepting orders have different recovery and resource needs. This documentary comparison uses Hostinger and SiteGround as concrete examples. We have not measured their speed, contacted their support as test customers or placed an order. The objective is a shortlist you can verify, not a universal winner.

Write the requirements before selecting a plan

Count the sites, administrators and applications you actually operate. Record the size of uploads and the database, the busiest interactive journey, background jobs and the amount of recent work you can afford to lose. A monthly visitor estimate does not reveal how much server work each request creates. Ask whether important requests can be cached and whether a failed form would be noticed.

For a fictional two-person editorial team, the main needs might be safe updates, recoverable articles and images, and a working contact channel. For a shop, orders created since the last backup may matter more than the cost of storage. These are different acceptance tests even when both sites run WordPress. Decide who will perform a restoration before buying a package that advertises backups.

A dated offer snapshot, not a live quotation

The following entries were observed on the suppliers’ English pages on 26 September 2026. Amounts are the displayed dollar prices, with billing periods stated explicitly. Hostinger’s page says prices exclude VAT; confirm applicable taxes, currency and eligibility at checkout for both suppliers. The monthly equivalents below do not mean monthly billing. Offers and plan names can change by market.

Hostinger Premium
US$2.99/month equivalent over 48 months, US$143.52 upfront; renewal displayed at US$10.99/month. The page lists 3 websites, 20 GB SSD and weekly backups.
Hostinger Unlimited
US$3.99/month equivalent over 48 months, US$191.52 upfront; renewal displayed at US$16.99/month. The page lists 50 GB NVMe and daily backups.
Hostinger Cloud Startup
US$7.99/month equivalent over 48 months, US$383.52 upfront; renewal displayed at US$25.99/month. The page lists 100 GB NVMe and daily/on-demand backups.
SiteGround StartUp
US$2.99/month displayed, prepaid for 12 months; renewal displayed at US$17.99/month. The page lists one website, 10 GB storage and backups. GrowBig separately lists staging and on-demand backups.

比較する cash commitments rather than matching headline numbers

The two starting offers above both display 2.99 per month but require different commitments. For SiteGround’s displayed twelve-month offer, 2.99 × 12 gives 35.88 before any added items or taxes; Hostinger’s stated 143.52 covers forty-eight months. This calculation compares initial cash, not value, performance or identical service. A four-year commitment may be unsuitable for an unproven project even if its monthly equivalent is attractive.

Build a second estimate for renewal using the actual term offered at checkout. Add domains, mailboxes, paid extensions, restoration assistance and operator time where these are not included for the full period. Do not assume an introductory email or domain benefit renews free. Save the applicable terms and invoice privately, and record the cancellation conditions before committing.

Match backup and staging arrangements to the workflow

A weekly backup schedule can leave more recently changed content outside the last copy than a daily schedule. Neither label proves that the copy can be restored completely. Check retention, which files and databases are covered, where copies are held and whether individual restores cost extra. Keep a protected independent backup strategy proportionate to the site.

Staging is useful when an update can affect forms or payments, but it is not automatically a safe copy of production. Use fictional data when possible, restrict access and prevent test emails or transactions from reaching real people. Test the entire update and rollback procedure, not only the button that creates the environment.

Conditions that would change the shortlist

  • If no one can administer the server, do not choose a self-managed VPS merely for larger resource figures.
  • If the team cannot justify four years of commitment, compare shorter billing terms explicitly rather than extrapolating the promotional equivalent.
  • If daily content changes are valuable, check whether the backup schedule and restore process meet that exposure.
  • If several independent sites need separate access or recovery, test the account boundaries instead of assuming that a large site allowance creates isolation.

Shortlist the least complex service that satisfies the documented constraints. Before paying, verify one representative installation, its permitted workload and the support boundary through the provider’s official materials or a clearly scoped question. A supplier’s marketing uptime or speed claim is not a measurement of your own site.

Documentation checked: 26 September 2026. References: Hostinger “Web hosting”; SiteGround “Hosting for WordPress”; WordPress “Backups”. Prices are historical observations requiring rechecking, not affiliate offers. No hands-on performance result is claimed.

Plan the next step