Mikro Yazılım Destek is the site of an ERP partner — standing right on a threshold: V16 support is ending, and the homepage countdown ticks the remaining business days live. The site’s job is to carry urgency without panic language: "A plan is cheaper than a rush."
APPROACH
The content and SEO infrastructure is built on Astro; the page opens in 23 requests at a 361 KB cold load — a decision-stage manager’s patience is not measured but simply never tested. A migration guide, sector-specific breakdowns, and price transparency that says "don’t decide before seeing the numbers"; ProfessionalService and FAQPage in the schema layer.
RESULT
0.53 sload time on desktop
0.49 sload time on a phone
124URLs
MEASURED: 2026-11-16
LCP 532 ms · CLS 0.001 · TTFB 200 ms
HTTP/2 · 124 URL sitemap
llms.txt ✓ · 23 req · 361 KB
0.53 sload time on desktop
A plan is cheaper than a rush.
— mikroyazilimdestek.com
MEASURED
16
November
Monday · 2026
LOAD, FRAME BY FRAME
Opens in 0.53 seconds.
468 ms
501 ms
535 ms
785 ms
Frames from an animation-free recording; time from the case ledger (cold load, 1440×900, median of 5 runs).
Mikro Yazılım Destek is an ERP partner whose site looks at a date on the calendar: the end of V16 support. The homepage title tag already names the V17 migration. The reader is a business that has not yet made its migration decision.
Strategy
The site conveys urgency through numbers: the remaining business days are computed from the calendar, the price list states the package fees openly and the migration guide has a page of its own. The content puts the information a decision needs on the table before the decision is due.
CLOSE-UP
The crops are real regions of the live site; each caption is the section’s own heading.
03Mikro’nun bittiği yerde başlayan yazılımmikroyazilimdestek.com/
04Mikro fiyat listesi 2026 · Jump, Fly, Run ve Müşavir bedelleri, KDV hariç · Asena Bilgisayar, İstanbul Rakamları saklamıyoruz.mikroyazilimdestek.com/fiyat-listesi/
Structure
The homepage carries the live database flow, the product selector and the integrations; the price list and the migration guide have pages of their own. The site speaks Turkish only, and its sitemap holds 124 URLs.
ARCHITECTURE
The lines are measured layout: we read container width and section rhythm from the live page and draw nothing by hand.
mikroyazilimdestek.com1440px
MATERIAL
Barlow Condensed · 600 · 92px
Headline typography — we measure the specimen line from the live page’s computed style.
Measured palette: the page’s three most frequent neutrals plus its saturated accents.
MOBILE
Three real 390 px frames; the alt text is the page’s own title.
05Mikro Yazılım Destek
06Mikro fiyat listesi 2026
07Mikro V16→V17 Geçiş Rehberi
Lessons
For a reader on the eve of a decision, speed is an argument in itself: a page that opens in 23 requests and 361 KB has an LCP of 532 ms. It is the lightest of the cases.
Cold-load measurement dated November 16, 2026: Largest Contentful Paint 532 milliseconds, Time to First Byte 200 milliseconds, layout shift 0.001. 361 kilobytes transferred in total, in 23 requests. These two numbers are the ones that matter: of the cases, this page downloads the fewest bytes.
The way to make few requests usually runs through removing something, not adding it. Third-party scripts, embedded widgets, external font hosts and analytics layers quietly inflate the request count; each one means a separate DNS lookup, a separate connection setup and a separate wait. We have written up which resource blocks what separately.
One language, narrow scope
The site runs in a single language and its sitemap carries 124 URLs. Staying monolingual is a deliberate scope decision: for a dealership and support service whose audience is domestic, a second language raises maintenance costs without paying them back. What would be wrong is staying monolingual without ever having made the decision.
When the scope is narrow, investment in the structure layer pays back more. The pages carry six types of structured data — Organization, LocalBusiness, ProfessionalService, WebSite, WebPage and FAQPage — and an llms.txt file is set up separately for model crawlers. For a small site this is a few hours of work, but it lets search and answer engines classify the page correctly.
A closed item
One item in this case had been left open: in the coverage report, the URL for a high-intent search term returned 404. The finding was recorded; the page has since gone live and the item is closed. A measurement is only useful if it reports what it finds — and says so again once the item is closed.
How few requests stay few
23 requests means that everything a page needs to open — document, styles, scripts, fonts, images — fits into that many files. For comparison: adding an embedded map, a chat tool and an analytics layer can double this number on its own, and every new domain brings a separate DNS lookup and TLS handshake.
We do not claim that none of those tools is necessary; before adding any of them, we measure its cost and question its return. Tools added without measurement pile up, nobody removes them, and a year later no one can tell why the page got slow. We have written up how the budget is set up separately.
One language is a decision
Being multilingual is not always right. A second language means content to translate, a second version to keep updated and an hreflang set that can break. For a service whose audience is in a single country that cost goes unrewarded, and a half-finished translation is worse than none: the user finds a page in their own language, and its content turns out to be incomplete or out of date.
When deciding, we asked "should we go multilingual" in a more concrete form: "which pages will really be kept up to date in a second language". Since the answer was not clear, we kept the site in one language and recorded that decision. We explain how multilingual content is managed separately.
What 124 URLs say
A small site is not at a disadvantage in search visibility. Authority comes from pages that genuinely answer a question. If each of the 124 URLs serves a specific service, product or question, that is stronger than three hundred pages repeating the same topic in different words.
The most common mistake on a small site is inflating the page count artificially — a separate page for every district, a separate URL for every keyword variant. The result is measurable: pages that copy each other compete for the same query, and the engine cannot tell which one to show. We have written up what a canonical address is for and crawl budget separately.
The figures in this case come from the cold-load measurement dated November 16, 2026, and its method is on record: real Chrome, 1440×900, no cache, Largest Contentful Paint the median of 5 runs. As the site changes, we renew the measurement and write it with the new date; the old value stays in the repository history, because a measurement with two dates shows the direction of change.
Source
The site is live and its address is open on this page; the measurement can be repeated with the browser’s own tools. The request count and transfer size are visible directly in the network tab. These two values are the most honest measures of what the page really downloads.