Blog
Practice, not advice
Breakdowns of things we measured ourselves on live sites: technical SEO, development, integrations and ads. No promises of rankings or percentages.
Breakdowns of things we measured ourselves on live sites: technical SEO, development, integrations and ads. No promises of rankings or percentages.
Found 25 articles
Thousands of products carrying the supplier's description, and the same text sitting in dozens of competitors. Here is how a bulk AI rewrite works and what it does not do.
We built LEO Chat as a bot that not only answers but also shows which scenario a paid order came after. Here is the mechanism, its limit and our own measurements.
The seller's cabinet says «N of M uploaded», the validator awards a hundred points, and it is unclear what is wrong. A run of 21 third-party feeds and 88,991 products on 5 September 2026: the structure is almost always intact, yet one feed breaks none of Rozetka's mandatory elements.
Our daily impressions in August swung from 55 to 579, while the weekly totals rose steadily: 421 → 858 → 2,127 → 2,250. A breakdown of our own data and the five-step method we use to separate movement in search from a fault on the site.
A checkout with a free-text address field works as long as the manager phones every buyer and creates the waybill in the carrier's cabinet himself. A breakdown of what a working integration looks like through the buyer's eyes and the manager's, what breaks most often, and how to check your own checkout in two minutes.
A wholesale store looks like a retail one with different prices, yet it diverges in six places: customer groups, pack multiplicity, list ordering, invoices, exchange with the accounting system and catalogue picking. Plus what measuring seven wholesale catalogues on 31 July 2026 showed.
«How long does it take» is a separate question on 162 of our service pages. The public ranges in working days: an OpenCart store 25–45, a landing page 7–18, wholesale 30–55. Seven stages of a store project, why the lower bound is rarely reached, and what stretches the timeline.
On 7 and 8 August 2026 we measured live online stores and service sites from the outside: canonicals, sitemaps, structured data, first response time, PHP version. This is not a bad market — it is the baseline every new store competes against.
The question «how much does a store cost» is a question about scope. On 31 July 2026 we took technical readings from 24 live shops on a single engine: catalogues from 76 cards to 116,841 URLs, first server response from 126 ms to a second and a half. A breakdown of the five cost multipliers on those numbers.
On 8 August 2026 we opened the product pages of thirty live online stores and looked at them not as a shopper but as a crawler. Product markup was present in ten of them, specifications in four. A breakdown of what follows from that.
Our site has been in search for exactly one month. On 2 September 2026 we ran it through our own audit checklist: 5,656 impressions, 41 clicks, 562 URLs walked. A breakdown of all twelve checks, with commands you can repeat on your own site.
Search Console reports 5,226 external links and, right beside it, the five sites that produce them. A breakdown of our own profile: why link count is the worst metric, what to read instead, and how to pull the same data for free.
The server supports brotli, everything is enabled in the settings, and the check reports «compression is on». Meanwhile the user's browser receives a page twice as heavy, every single time. A breakdown of our own case with before and after measurements.
The crawler diligently walked hundreds of addresses the site itself had marked «do not index», and never once visited two pages from the main menu. A breakdown of our own indexing report and the checks worth running on your site.
Language versions can exist, carry hreflang and have a switcher — and still every internal link returns the reader to the default language. A breakdown of our own mistake, with before and after figures and a way to check your own site.
What is the delay, what is removed from it by the distributed network, and what remains in place. Our TTFB measurements on live sites and checks done in half an hour at the terminal.
Where code generation saves time, where it fails imperceptibly, and analysis of a defect that we found in our own project during technical measurement.
A PWA is a manifest, service worker, and HTTPS on top of your site. What's changing technically, where the bottom line is, iOS limitations, and why a non-prerendered SPA can cost you search traffic.
Three different projects are hidden behind the word "AI". We analyze the mechanisms that really work in the shop, their limits and checks that are done without a contractor - with examples from our technical measurements.
TTFB, LCP, and INP are different numbers and are treated differently. Our external measurements of live sites 31/07-01/08/2026, reasons for lost seconds and commands to repeat the test yourself.
Headless is a decision about where content lives and who is responsible for displaying it. What does separation provide, what new task does it add, and when a monolithic CMS remains a smarter choice.
Turbopack, default fetch caching, async params, and what actually gets to the visitor. Plus four commands for checking your own project.
Tokens, components, composition — and commands in the terminal, which show whether the system is really used, or if it exists only in mockups.
Where did the figure "50% of voice searches" come from and why it will not be here. As assistant agents read the site, what our measurements showed and what checks you will do yourself in the evening.
Sitemap, duplicates, speed, markup, hreflang, HTTPS, analytics. Each test comes with an example of a real defect from our measurements and a command for the terminal.
Where code generation saves time, where it fails imperceptibly, and analysis of a defect that we found in our own project during technical measurement.
Turbopack, default fetch caching, async params, and what actually gets to the visitor. Plus four commands for checking your own project.
Tokens, components, composition — and commands in the terminal, which show whether the system is really used, or if it exists only in mockups.