ADS Moldova: updates from 11 September 2026

On 11 September 2026, we worked on how visitors understand ADS Moldova services, compare projects and read information on a phone. The updates focused on pages already in use: the calculator, service pages, portfolio and blog. Their shared purpose was to reduce the effort needed to find an answer and start a useful conversation about a project.

This journal explains that day's changes and the reasons behind them. Some improvements continued on 12 September, and we identify those connections where relevant. Published on 12 September, the article documents the previous day's work. It is neither a promise of future features nor a report of commercial results we have not measured.

A calculator that makes costs easier to understand

We simplified the price calculator and improved the connection between the quick selection on the home page and the full calculator. Visitors can start with a service, adjust options and continue with the same selection. Someone who has already begun outlining a project should not have to repeat those decisions when opening the dedicated page.

We paid particular attention to separating initial costs from recurring charges. A website, a campaign and monthly management do not share the same payment structure. Combining them into a difficult total can create the wrong expectations. The update makes the estimate a clearer starting point for a conversation, with options and conditions that are easier to follow.

We checked changes to selections, service removal, reset behaviour and returning after a page reload. The message prepared for an enquiry should reflect the current choice. The calculator provides an indicative estimate; project details are discussed before a final quotation, especially when integrations or requirements cannot be described adequately by a single option in a form.

A more coherent presentation of design and identity

We brought together the presentation of web design, branding and visual identity where separate offers were overlapping. For a client, internal service names matter less than deliverables: how the website looks, which visual rules are provided and how that identity can support future materials. The Web Design page explains those connections in a clearer context.

This reorganization does not mean that every order automatically includes every possible asset. It helps visitors find the appropriate service and identify the questions they need to ask. A business with an existing logo may need usage rules and a web interface, for example, while a new business may need to establish its overall visual direction first.

Service illustrations with a calmer visual hierarchy

We replaced crowded compositions across several service presentations with more orderly illustrations. The updated system keeps the brand character while giving interfaces, titles and relevant service elements more room. Instead of numerous decorative objects competing for attention, each image has a main idea and a limited set of supporting components. This makes the message easier to recognize.

We prepared Romanian, Russian and English versions and checked their framing on phones. These visuals help visitors quickly distinguish a website service from an application or an automation. Conceptual illustrations remain different from screenshots of real projects. An interface drawing is not presented as evidence that a particular campaign ran or that a particular result was achieved.

Portfolio examples tied to the actual contribution

We reviewed project recommendations displayed on service pages. The fact that a company has a website does not demonstrate that its project included TikTok Ads, local SEO or SMM management. We removed associations without a relevant documented contribution and described retained examples more precisely, such as the development of a landing page intended to support a campaign.

In the portfolio, visitors can explore projects independently of the service page that brought them there. On a service page, the selection should answer a narrower question: which part of this project illustrates the offer? This rule makes recommendations more useful and reduces the chance that an attractive image suggests a promise unsupported by the accompanying case study.

A more compact portfolio introduction

We reduced heading sizes and the amount of introductory text in the portfolio. Lengthy explanations about the page's internal organization were taking up too much of the first screen, particularly on mobile. Most visitors come here to see projects, understand their context and open examples that resemble the kind of work they are considering for their own business.

Filters and counts remain close to the content they control. We retained the distinction between active and completed projects without filling the beginning of the page with a large explanatory panel. The exact selection in the home page's Live section was refined later, on 12 September, and is described in the journal covering that day's updates.

More substantial case studies without padding

After an initial simplification, the case studies had become too short to explain decisions behind the projects. We expanded each study with roughly 500 relevant words, focusing on context, contribution, implemented structure and the reasons for particular choices. Length was a working reference, rather than a reason to repeat the same paragraphs under different headings.

Readers can examine Karma Numbers for the relationship between a website, content and application access, then explore BB Fliesen for a different type of web presence. Each article needs to explain its own project. We do not automatically transfer features, campaigns or results between clients merely to fill a shared editorial structure or produce a longer page.

PageSpeed: comparable screenshots and access to detail

We rebuilt the section presenting PageSpeed checks. The mobile screenshot was too small relative to the desktop version, while surrounding text made the presentation busier. The reports can now be selected through dedicated controls and opened at their original resolution. The purpose is to make the information inspectable on a phone instead of asking visitors to interpret an unreadable thumbnail.

We removed wording that suggested a website could simply be declared “100% ready for Google.” Saved screenshots are examples of checks performed at a particular moment, and results can vary. The values are presented in context. A laboratory score is not turned into a ranking guarantee or a promise that applies automatically to every new website we build.

A simpler template offer and PWA explanation

The free website template banner received a simpler composition, a short explanation and a clear action. On mobile, the elements move into a single column rather than squeezing a desktop poster into a narrow space. Visitors can understand what they may request and where to continue, without decorative forms that look functional but do not actually receive information.

We also simplified the explanation of the PWA available on request in relevant offers. The central information appears directly, supported by a browser-to-phone illustration. For technical context, MDN's guide to making PWAs installable explains why installation depends on browser and platform. A concise service presentation should preserve those real distinctions rather than imply identical behaviour on every device.

Better balanced headings on long pages

We reduced excessively large headings in the AI services presentation and compacted the home page's tools section. A large heading can suit a particular setting, but repeating that scale throughout a page pushes useful information well below the first screen. The effect becomes more pronounced on a phone, where a heading may wrap across several lines before the explanation begins.

We worked towards a steadier relationship between headings, descriptions and buttons. This stage prioritized clarity and space; on 12 September, we restored colour accents to icons and actions. Those directions complement each other. An interface can retain personality without making every card compete equally for attention or forcing visitors to work out which element is most important.

The mobile blog: search and categories in a useful space

On the blog index, the introduction and categories occupied too much space on mobile. A long collection of labels pushed articles far down the page, while text sizes made scanning difficult. We compacted the presentation and reorganized filtering so that the search field, selected category and resulting articles could be understood as parts of the same activity.

The purpose is practical: someone looking for automation, e-commerce or an SEO guide should reach relevant reading quickly. The principles in web.dev's responsive design guide support adapting a composition to available space. For our implementation, that means checking the working page in a browser, rather than merely shrinking a desktop screenshot until it fits a phone display.

Thematic covers and a clearer editorial direction

We prepared thematic covers for published articles, following the visual direction of our practical Figma guide. Each topic has an appropriate composition: search and catalogue elements for a marketplace, interfaces for websites, messages for automation or settings for consent. The purpose is to make the subject recognizable before opening an article, without placing crowded titles over generic images.

The article rewrite intended to improve reading was also authored on 11 September; final publication of that stage continued on 12 September. The texts received specific sections, relevant examples and direct sources. Articles temporarily withdrawn stayed outside the public collection. Expanding a library should not mix available material with pages that are still being reviewed or are not ready for readers.

Checking the changes and deciding what comes next

Alongside visual presentation, we checked Romanian, Russian and English pages, navigation links and mobile behaviour. The SEO audit examined relationships between published pages, the sitemap and metadata. Whether a page is published and accessible for discovery can be checked. Its actual inclusion in a search engine's results is a separate process, and the two should not be treated as interchangeable outcomes.

For a business planning its own website, this day's lesson is the order of priorities: the offer should be understandable, examples should be relevant and information should be readable on a phone. Start with the website creation service and the projects supporting its presentation, then identify which integrations and materials your particular situation requires before moving towards a detailed quotation.

The continuation appears in the 12 September update journal, covering language-specific URLs, AI chat, cookie preferences and later corrections. Together, the two articles document the evolution of one website: more precise information, easier access and fewer obstacles between a visitor's initial interest and an enquiry that describes what they actually need from a project.