WPHost in Uzbekistan: WordPress Prices and Limits

Who WPHost may suit

This profile is based on published offers and documentation. No new hosting benchmark or support test was performed for this translation.

Plans, prices and renewals

Prices retain the market, currency and billing period described in the French source. Translation does not update a commercial quote. Confirm the final price, taxes and options before ordering.

Languages and support

Website and documentation

Russian, Uzbek and English.

Control panel

cPanel and AHOST subscriber area. Private-interface languages must be confirmed.

Support

Russian, Uzbek and English advertised. Continuous ticket availability according to the provider.

WPHost for WordPress in Uzbekistan

WPHost publishes five WordPress packages with prices in Uzbek soums and servers advertised in Tashkent. The first tier provides one site and 1 GB storage. The table also gives memory, cores, file count and a simultaneous-task limit. Staging and optimization are advertised across the range. Domain email is explicitly excluded. A project must therefore budget for it if it wants to receive messages on its own domain.

This profile follows a small organization in Tashkent publishing information and receiving registration requests. It wants to measure optimization’s effect without disrupting form use. A local check simulates script dependencies and compares several loading orders. The case prepares a staging acceptance test and helps decide when to retain or adjust an acceleration setting. Exercise data is fictional. Capacity and prices come from official pages consulted for the Uzbek market.

Monthly payments, annual payment and renewal

The WordPress table displays four terms in Uzbek soums. The plan presentation reports the total for the cycle, including when the page shows a monthly equivalent. The Russian, Uzbek and English versions consulted directly agree on amounts and discounts of 4%, 7% and 15% for three, six and twelve months. The commercial PDF available from the documents page still displays a 5% annual discount and 786,600 UZS for Start. This discrepancy warrants requesting the first-cycle amount on the invoice. For Start, the current table displays 703,800 UZS for twelve months. The difference from the PDF proposal is 82,800 UZS.

For Start, twelve monthly payments total 828,000 UZS. The displayed annual total is 124,200 UZS lower. The next cycle’s amount and whether hosting taxes are included or added still require invoice confirmation. The domain table explicitly states VAT-inclusive prices, including .uz renewal at 27,000 UZS per year. It advertises a free first year for eligible extensions with hosting. The WordPress contract and domain should each be priced on their own line.

Public documentation describes card, local-service and bank-transfer payments. It states that businesses can obtain contractual documents and an invoice. SUVAN NET’s public offer provides for advance payment and rates current when service is supplied. Before paying for a year, request a document stating the exact amount, currency, cycle, tax treatment, next due date and termination procedure. Terms for free migration, a bonus or a free domain may depend on the case.

Resources by package and WordPress limits

The first package includes one site and 1 GB disk. The second increases to three sites and 5 GB. Memory, cores and file limits also rise by tier. The table separately states site count and simultaneous tasks. The task limit is a hosting measure. One visit can request several operations and several visits can receive the same cached page. The ceiling therefore does not indicate a number of readers supported at a given instant.

For an existing WordPress site, measure files, media generated from originals and the database. Add space that a working copy may require. The table does not specify how staging and available copies count against storage. An association mainly publishing text may start with a small footprint, then have different needs after adding photos and documents. Publishing can be spread over time. Nevertheless, the next quarter’s budget should include the production site and planned operations on its copy.

Documentation reserves this range for WordPress and explicitly excludes domain mailboxes. A site displaying a form does not resolve reception or team-mailbox availability. For an organization already using an email service, retain a separate quote line and check the accounts administering its domain. The project should also distinguish site transactional email from work mailboxes. Ask how site sending can connect to the chosen email provider and which limits apply to that workflow.

Languages, assistance and location

The site offers public pages in Russian, Uzbek and English. WPHost also advertises technical assistance in those three languages and continuous ticket availability. Commercial pages and the FAQ display different initial-response times. Ask for the contract’s applicable time and urgent-incident channel. Always-accessible support does not guarantee resolution when the team wants to publish. For acceptance testing, record request time and response time to obtain a case-specific measurement.

Navigation separates cPanel from the AHOST subscriber area. The footer identifies WPHost as a SUVAN NET brand. All three pricing-table versions link to those interfaces. Languages actually offered on private screens have not been tested. If people read different languages, request demonstrations of the workflows they will own. The WordPress publisher, domain administrator and payer may need three distinct accesses. Have recovery procedures recorded for each.

WPHost locates its servers in Tashkent and mentions local TAS-IX interconnection in the FAQ. It also presents Cloudflare’s content distribution network. For a project targeting Uzbek readers, distinguish the site location, public-asset delivery point and external services. Provider-published latency figures do not measure the project’s form. Test the current version from a phone and connection used by the target audience, then compare with the optimized copy.

Backups, staging and acceleration

The table, FAQ and home page present weekly backups. The FAQ and home page give about one month’s retention. The features-page illustration refers to three months. Retention therefore needs confirmation for the proposed package. Clarify the number of accessible points and file/database export. For an important publication, identify the latest copy actually available. An example screen can illustrate a procedure without committing to a retention period.

The provider advertises staging and copying the site to a temporary address. Before using it, ask whether this copy consumes storage or a site slot. Protect access and replace recipients with test addresses. Define the scope of a production deployment. A cache-setting change and full database replacement have different effects on registrations received between testing and publishing. Check public indexing after cutover if the team changed visibility settings on the copy.

WPHost highlights AccelerateWP, caching and minification. A setting changing when a script runs can affect a form depending on a library or validation loaded earlier. Record a baseline before optimization. Then test one configuration at a time and observe a valid submission and an expected error. A loading-metric improvement must accompany verification of the actual workflow. If an old file still seems in use, compare staging results with caches serving the public.

AI and site automation

WPHost presents an integrated AI tool for creating a site or proposing its structure. Public pages consulted do not specify credits, generation languages, additional cost, model used or prompt retention per package. The package table presents hosting resources and features. The project can request an assistant demonstration and a description of export capabilities. The domain catalogue separately offers extensions such as .ai, which concern name registration.

For an initial brochure site, provide the assistant only a public example, such as a business name and expected sections. Then check page hierarchy, headings, links and contact details. A page targeting Uzbek and Russian-speaking readers deserves review of every version actually published, especially personal names, addresses and error labels. The site administrator must retain the ability to correct text and change structure after initial creation. Also ask what happens if assistant access changes at renewal.

The creation assistant and acceleration setting are documented separately. For the Tashkent team, the initial structure can be tested in staging with a simple form and fictional recipients. The administrator keeps a list of scripts actually required for the workflow. If a generated page uses an external component, identify its origin and data it may receive. The acceptance test below concerns JavaScript dependencies. It can be rerun regardless of where page content originated.

Local exercise: check an optimized form’s loading

Deferring a script can leave the form visible while preventing its initialization. — Illustration by BlogPasCher.Open full-size illustration ↗

A fictional registration-request form has three scripts. The foundation initializes the page. Validation prepares field checks. The form then installs its submission action. The local script executes these stages in three orders, then checks two submissions, including one with an empty field. This models a common dependency. It prepares acceptance testing after optimization that defers a script. Tested scripts belong to the exercise and come from neither WPHost nor a WordPress plugin.

Extract the profile’s archive. In the extracted folder, run this command.

The baseline loads the foundation, validation and form in that order. The overly broad configuration postpones validation until after form initialization. The adjusted configuration keeps the dependency in the correct order while executing a decorative element after the form. The check requires rejection for the empty field and a recorded submission for the completed field. It also flags a dependency missing at initialization.

Remove validation from the adjusted configuration to trigger failure. On the real copy, open the page as a visitor, reload with caching enabled, then check both workflows in the browser. If the empty field is accepted, the displayed time saving does not justify the configuration. If the button remains blocked, identify the first required file that did not execute. Compare the unoptimized version with the targeted setting, then record the result and how to restore the setting.

node EXERCICE-WPHOST-UZ.cjs

Which package to choose and what to clarify

Start provides an entry point for a single site whose files and database fit the available space. The budget must include the working copy if it counts against quota, plus a separate email service when needed. Blogger is the first tier advertising multiple sites and 5 GB capacity. Business, Shop and Agency also increase memory, cores and simultaneous tasks. Record values relevant to the project before choosing a tier. A cache setting can be tried and evaluated on a copy using workflow criteria independent of site count.

Request a first-order amount citing the selected table and term. The difference between the PDF and the three current tables warrants written confirmation, especially for annual payment. Clarify renewal price and method, tax treatment, domain costs, storage charged to staging and backup retention. If the AI assistant matters to the choice, include its access level, languages, rights to created content and next-cycle cost.

The Tashkent team can decide to retain an optimization setting by comparing two runs of the same form. It records script order, expected error and fictional submission result. The site owner then validates the workflow on the version to publish. Keep the name of the file or setting that restores previous behavior. If the temporary copy and production load scripts differently, repeat verification on pages actually served to visitors before opening registration.

Prepare your site

• Noindex after WordPress staging: make the right pages indexable
• Invisible WordPress change: find and clear the right cache
• Contact Form 7 keeps loading after submission
• Download the form-dependency exercise