Retain usable content and systems, and allocate the budget to areas that need improvement.
Responsive Website Upgrades
Is your phone cluttered with swiping left and right, menus bunched together, or products and forms difficult to navigate? First, perform a site check on your old website, then choose to reuse the layout, rebuild the front end, or completely redesign it.
These are DFocus planning budgets, not a market-price survey or a fixed package offer. Prices are in TWD and exclude tax. Your written quote depends on the source code, software versions, features, licenses, and acceptance criteria. Last updated: October 26, 2026.
First, distinguish between the three types of projects to avoid comparing prices based on different content.
The existing website will be retained, but adjusted to RWD.
Retain the main visuals, content, and existing functions, and modify the layout, images, menus, and operation presentation; suitable for old websites with complete source code and maintainable backend.
Keep the Back End. Redesign the Front End.
Reorganize the visuals, navigation, and mobile interface to give the existing website a fresh browsing experience; first, confirm the compatibility and integration scope between the front-end and back-end.
Full Redesign or System Rebuild
When adjustments are needed to technology, data structure, management processes, or essential functions, the front-end, back-end, and data engineering should be evaluated separately, rather than treating it as a simple responsive web design (RWD) add-on.
Responsive Upgrade Plans & Planning Budgets
Page count is a reference point for scale; the key factors are the independent layout and the actual amount of work done. Pricing methods differ between websites using shared layouts and those where each page is handcrafted.
Basic RWD Upgrade
TWD 28,000–48,000
A small website that uses existing visuals and programming.
A scale of 5–10 content pages and up to 3 independent layouts is recommended.
The style of the homepage is retained, but the text, images, and column arrangement of the agreed-upon inner pages are adjusted.
The original menu has been changed to a collapsible navigation menu that can be folded up on mobile phones, with images that adapt to different screen sizes and prevent unexpected overflow.
The front and back ends are still maintainable, and the existing URLs, titles, and indexing settings are retained.
This does not include a completely new brand visual identity, logo/banner creation, backend reconstruction, membership features, or new modules.
The old site can still use the backend, but it needs a new visual identity and navigation.
A scale of 15–50 content pages and 6–10 independent layouts is recommended.
A completely new homepage visual, inner page design guidelines, and responsive layout.
Reorganize the product/service display and form front-end interface, and plan basic interactive effects.
Reuse the existing compatible backend, check the original URL and necessary SEO structure, and test existing functions.
This is a visual and front-end redesign, not just a simple CSS modification; necessary back-end interfaces, new features, and asset creation need to be listed separately.
Content architecture, brand design, and necessary front-end and back-end integration are all organized together.
Approximately 8–15 front-end layouts are provided for reference; content and data volume will be assessed separately.
Website architecture analysis, brand new UI/UX and responsive front end.
Confirm the necessary backend adjustments or model rebuilds item by item, and handle the data transfer within the agreed scope.
Plan 301 redirects for URLs that need to be changed, and complete front-end and back-end integration and acceptance testing.
"Overall redesign" does not mean that all programs and data are rewritten indefinitely; backend modules, data entries and migration methods must be agreed upon item by item.
Existing shopping websites, membership/matching platforms, and business integration systems
Individual assessments are conducted based on transaction processes, role permissions, databases, and external APIs.
The project is separated into front-end RWD, back-end system, database, and API, and then connected.
Confirm the retention, adjustment, and regression testing of existing processes such as membership, orders, and payment.
List the security testing, deployment, and data transfer tasks as required.
This level serves as the starting point for discussions on redesigning existing systems, not as the fixed total price for building a new, fully customized system.
The project duration, number of proposals and revisions, data processing volume, warranty period, and tax amount will be confirmed in the formal quote. Server, domain, third-party paid services, and programming work exceeding the agreed scope will be listed separately.
The quote should include not only the website address, but also the individual website design and the actual project details.
For example, a website may have 123 URLs, but only 6 templates for the homepage, company introduction, services, product list, product details, and contact page. Sharing a template for product pages does not mean creating a new layout for each page. If each content page is an independent static HTML page, then a separate estimate of page-by-page adjustments is required.
How are project costs composed?
Total project cost = basic engineering + independent version construction + existing function adjustment + data processing + environmental and testing work.
The official list should specify the number of versions, the number of pages of content, the functional flow, the number of data entries, and the scope of design and modifications, avoiding the use of "the entire site's RWD" to encompass unlimited work.
Items that usually require additional confirmation
New logo, banner, product photography, copywriting, and multilingual content.
Add new features such as membership, shopping cart, reservation, payment, CRM/ERP, etc., or integrate them.
Backend rewrite, database reconstruction, large-scale migration, host or PHP/framework upgrade.
Advanced performance, SEO/GEO strategy, content management, vulnerability scanning and patching.
Assess First. Then Decide What to Keep, Redesign, or Rebuild.
Technical conditions and evaluation direction of old websites
Current situation
Priority assessment
HTML/CSS is modifiable, and the backend functions normally.
Assess basic upgrades and business upgrades, while retaining the brand and existing functions.
The front-end structure is messy, but the back-end is still usable.
When assessing business upgrades and redesigns, first confirm the interdependence between the front-end and back-end systems.
Missing source code or unclear original permission to modify the original software
First, we will assess the scope of modifications, without directly promising an upgrade to the existing website.
Old PHP/ASP/framework or special hosting environment
Additionally, assess maintainability, version compatibility, and the scope of updates required.
Tight coupling between front-end and back-end
Evaluate the redesign and overall revision, and list the necessary system adjustments.
There are members, orders, payments, or APIs.
Separate integration and regression testing will be conducted, and e-commerce and special system redesigns will be evaluated as necessary.
Reference price for old site technical inventory: TWD 3,000–10,000 (excluding tax). Price will be determined based on source code, testing environment, and system size; larger sites or those with incomplete data will be confirmed in your quote separately. Whether this price can be offset against the project cost and the amount offset will be agreed upon in the quote.
What We Test Before Sign-Off
The page width is sampled at 320, 375, 390, 768, 1024, and 1440 pixels, and reasonable scaling is allowed within the agreed support range.
General text, images, and main blocks do not have unexpected horizontal scrolling; wide tables can use independent horizontal scrolling areas according to their specifications.
The mobile menu can be toggled on and off, the connection is correct, and the switching works normally when zooming back to the desktop.
Text does not overlap or get cropped, images maintain a reasonable aspect ratio, and buttons and forms are touch-sensitive.
The existing functions are working properly, and the applicable processes such as membership, forms, and transactions have completed regression testing.
The mobile and desktop versions retain the agreed-upon main content, URLs, titles, and necessary index information.
Test within the specified browser and page range, and deliver backups, test records, and basic response arrangements.
The defect correction shall be provided in accordance with the contract, and the warranty period and scope shall be specified in the contract.
RWD upgrades improve the mobile reading and operating experience, laying a better foundation for subsequent SEO/GEO. For further enhancement of search visibility and AI content understanding, performance optimization, content curation, and continuous SEO/GEO can be implemented; performance metrics and cybersecurity testing will be subject to separate acceptance testing and environment arrangements.
Example quote: 35 content pages, using 6 different templates.
Assuming that existing manufacturing websites can be modified, products are maintained by the existing backend, no new functions are added, and no new brand visuals are required, the assessment is based on the company's upgrade direction; although there are 35 URLs, the actual focus is on 6 templates and operating procedures.
The prices shown are for illustrative purposes only and are not fixed prices for every website.
Engineering Project
Tax-exclusive amount
Architecture and compatibility review
TWD 6,000
Front-end shared components and basic settings
TWD 12,000
6 template adjustmentsTWD , 7,000 each
TWD 42,000
Mobile menu and existing interactive adjustments
TWD 6,000
Cross-device and functional regression testing
TWD 8,000
Total Project
TWD 74,000 (excluding tax)
The example is limited to the template and agreed-upon functions mentioned above, excluding database migration, backend rewriting, new visual design, and unidentified defects. Inventory and testing already included in the total project cost will not be charged again.
Before collaborating, confirm these six things.
Inventory: Provides the old website URL, availability of source code, hosting environment, and existing issues.
Define the scope: specify the layout, content, retained functions, new work to be added, and excluded items.
Confirm the quote: Confirm the amount, tax type, timeline, number of revisions, delivery documents, and warranty item by item.
Handling changes: When encountering authorization, compatibility, or existing defects, first confirm the impact, additional costs, and timelines before proceeding.
Test and Deployment: First, back up the data and test it in the agreed environment, then deploy and go live according to the deployment and response schedule.
Acceptance and handover: Complete the acceptance process by comparing with the construction and testing checklist; confirm subsequent maintenance and new requirements separately.
FAQs about Upgrading Old Websites (RWD)
Can an old website always be directly converted to RWD?
Not necessarily. First, you need to confirm the source code, modify the license, check the hosting environment, and ensure the compatibility between the front-end and back-end. If the front-end is modifiable and the back-end is maintainable, it's more suitable to continue using it. If the source code is missing, components cannot be modified, or the old environment can no longer be maintained, first take stock, then evaluate whether to remake or rebuild.
Is the RWD upgrade charged based on the number of URLs or the number of versions?
The assessment is primarily based on the independent template and the actual workload, with separate content organization and data processing outlined. For example, if a large number of products share a single details template, each product URL should not be treated as a completely new template; if they are independent static HTML files, then page-by-page construction must be estimated.
Are the number of pages and page layouts for each plan a fixed package?
No. The number of pages is a reference for scale; the formal quote will list the actual layout, content pages, functions, and acceptance scope. Even with the same number of URLs, differences in source code, design complexity, and interactive flow may result in different workloads.
Does an RWD upgrade include redesigning the website or rebuilding the backend?
Basic upgrades and business upgrades will primarily retain the existing style and functions; redesign includes agreed-upon visuals and front-end redesign; overall redesigns, e-commerce redesigns, and redesigns of special systems will require further evaluation of back-end and system integration according to specifications. Whether the logo, materials, copywriting, new features, and database projects are included must be confirmed in writing.
If a website has members, shopping carts, or payments, how will a redesign be inspected?
First, confirm the agreed roles and key processes, and then check the applicability of login, query, form, order placement, and payment status in the test environment. Testing of transactions, permissions, third-party integration, and data transfer needs to be listed separately for each project, and should not be limited to screen acceptance.
Does changing it to RWD include high scores in GEO, SEO, or PageSpeed?
Not equivalent. RWD projects will retain important content, URLs, and necessary relay data within their scope; advanced performance, SEO/GEO content optimization, and ongoing maintenance will be listed separately. Search visibility and AI citations are evaluated over time; they depend on content, technical conditions, competition, and the search platform.
How much does a technical inventory of an old site cost? Can it be offset against the implementation cost?
Technical inventory reference price: TWD 3,000–10,000 (excluding tax), depending on source code, testing environment, and system size; prices for large websites or those with incomplete data will be confirmed in your quote separately. Whether a credit is applicable, the credit amount, and applicable conditions will be confirmed in the quote; automatic credit is not preset.
Can RWD upgrades be commissioned even across different counties and cities?
We’re based in Sanchong, New Taipei City, Taiwan. We work with businesses in Taipei, New Taipei, and other parts of Taiwan, with experience serving clients as far south as Tainan. Most discovery meetings, project reviews, and training can be handled remotely. On-site meetings for contracts, handoff, or additional guidance are arranged when needed. Contact Welson at +886 918 508 509 or welson@ecmd.com.tw; LINE ID: WELSON-LEE. Consultation hours are 1–8 p.m. Taiwan time (UTC+8).
Does the price include taxes, hosting, SSL, and subsequent maintenance?
The prices listed on this page are in New Taiwan dollars (TWD) excluding tax. Hosting, domain, SSL, third-party services, maintenance, and work exceeding the scope of the work order need to be confirmed item by item; not all costs are included in the RWD project. For subsequent maintenance, please refer to the website maintenance and security solutions.
Let's discuss suitable upgrade methods, using the old website URL as a reference.
You can first choose the option that interests you, and then Welson will assist you in confirming the scope of construction and the formal quote.
Please provide your existing website, main issues, source code availability, desired features to retain, budget, and estimated timeframe. First, assess how much of the functionality can be retained before deciding on the upgrade plan.
Based in Sanchong District, New Taipei City, we provide convenient consultation services to businesses in Taipei and New Taipei City, as well as remote services remotely. We already have experience serving Tainan. Necessary contract signing, handoff and training, or on-site explanations will be coordinated separately.
