• Technical SEO · gzip / brotli

Mobile speed: the site can be seen from a smartphone, and so can the search engine

Optimizing the site's mobile speed is not about working with a separate version, but with what actually reaches the phone: the weight of the document, compression on the server, images and other people's scripts. First, we measure the mobile return on three types of pages, then we remove one by one what costs the smartphone the most. The spread is multiple: in its own measurement on 07/31/2026, the main markup weighed 103.2 KB in one store and 295.7 KB in the second. The second reason to do this is indexing: search reads the mobile version, so the discrepancy with the desktop version costs more than just visitors.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
What do we measure?
document weight, compression, images, viewport and third-party scripts on three types of pages
Price
after a free audit
Guarantee
30
days after project sign-off
What do we measure?
document weight, compression, images, viewport and third-party scripts on three types of pages
Scattering of the marking weight in its own dimension
103.2–295.7
KB at three stores, 07/31/2026
The first answer is on the same sites
440.7, 524.8
and 547.2 ms
Upper limit on images
66
out of 69 pictures (96%) are delayed in loading
Term of works
9–20
business days, depending on what we find
Before the estimate
free mobile return measurement, 2-3 working days
What we do not promise
specific values ​​in the field data - they are not controlled by any contractor
Process steps

Transparent stages with approval at every step

Total duration:5–18 days

  1. Measurement of mobile return

    2-3 working days

    Main, category, card: first response, full load, markup weight before and after compression, inventory of images and third-party scripts, viewport status. The output is a list of reasons in order of influence.

  2. Server: compression and protocol

    1 working day

    gzip or brotli, headers, HTTP/2. The cheapest profit for the time spent: the appearance of the site does not change, and the difference is visible in the same measurement on the same day.

  3. Image

    1-4 working days

    Delayed loading everywhere except the first screen, modern formats, sizes for mobile container instead of desktop originals. Separately, we check whether the quality of the photo of the product has not been affected - the limit here is commercial, not technical.

  4. Viewport and mobile content parity

    1-2 working days

    We remove scaling blocking, compare the server's response to the mobile and desktop agent by text, links, and markup. Disagreements are listed in a list: some are treated with a template, some are treated with a decision about what remains on the phone.

  5. Revision of third-party scripts

    1-3 working days

    A list of what is loaded on the page, with the price of each item over time. The decision "to leave or remove" is yours; after disconnection, we check that the chat, analytics and the order button are alive.

  6. A template that gives the phone too much

    2-6 working days

    It is not always necessary - it is this stage that keeps the upper limit of the term. Here we stop hiding blocks with styles and start not giving them to mobile at all. It follows a separate line of the estimate so that it is clear what you are paying for.

  7. Re-measurement and document

    1 working day

    Same pages, same methods, same number of attempts. Comparison before and after for each point and a short instruction on how not to lose the result in six months.

Technologies & integrations

What we build on and what it connects to

Stack

  • gzip / brotli — compression of the response on the server. The cheapest item on the list; on already compressed files, in particular JPEG and WebP, it does nothing
  • HTTP/2 — parallel requests in a single connection. It does not reduce the number of requests: a hundred images remain a hundred images
  • WebP / AVIF — the profit is proportional to the number of photos; you can't see it on a website with a dozen pictures
  • loading="lazy" — delayed loading of everything except the first screen. In the upper images, it is harmful: it delays what a person sees immediately
  • Responsive layout — one document for all screens. The price of the solution: hidden by the styles, the phone's browser still downloaded
  • Lighthouse in mobile profile and network-restricted DevTools - a laboratory, not your visitors: treated as a cause, not a diagnosis
  • PageSpeed ​​Insights - This is where the owner and ad contractor look. Field data appears there only with sufficient traffic and with a delay

Integrations

  • Google Search Console
  • GA4
  • Google Tag Manager
  • Cloudflare
What's included

Complete list of work and what you get as a result

  • Measurement of mobile return to work on the main, in the category and in the card — three numbers with which in two weeks there will be something to compare
  • Compression of the response on the server, gzip or brotli, with header verification: times fewer bytes are sent over the network to the phone, and the site does not change externally
  • Protocol Validation - HTTP/2 parallelizes requests in a single connection, and this is more noticeable on a long-response mobile network than on cable
  • Markup weight reduction: cleaning up unused and reducing duplicate blocks so that the phone browser starts drawing earlier
  • Images: modern formats, delayed loading, sizes for mobile screens instead of desktop originals
  • A correct viewport without blocking zoom is both a convenience for a person with poor eyesight and a removed remark in accessibility checks
  • Porting third-party scripts so that they don't block the first run of content, with a list of how much each costs
  • Reconciliation of mobile and desktop response: same text, same links, same markup - the basis of mobile indexing
  • Re-measurement using the same methods and a document with the difference for each item
  • The rule for your team to follow: added a new script or block — measure and compare with the number in the document
When this service isn't right

What's not included — so there are no surprises at delivery

  • Development of a separate mobile version or application
  • Redesign of the interface
  • Optimizing third-party widgets you're not ready to turn off
  • Promise specific metric values ​​in field data - these depend on the devices of your visitors
Who it's for

Situations where this service delivers results

Scenario 1 of 4

Most of the visits come from the phone, and the page was made on a wide screen

The layout was drawn on 27 inches, it is viewed on six. On mobile, network time is added to server time, so each extra kilobyte costs longer than on cable. In the three stores we measured, the first response was kept in a narrow corridor of 440.7–547.2 ms, and the markup weight differed almost three times: 103.2 vs. 295.7 KB. The difference is the theme and the set of modules, not the hosting.

We'll review your situation in a free audit
Responsive layout versus separate mobile site

How this option differs from the alternative

A separate mobile version on a subdomainOur approach
What the search seestwo documents, and it is the mobile one that goes into the index — any incompleteness of it becomes an incompleteness in the indexone document, there is nowhere to part with the desktop
Content updateis corrected twice or synchronized by a script that also breaksdone once
Addressesthe second address, redirect by device and canonical, which must be kept in the correct yearsone address per page
The price of a new sectiontwo jobs instead of one, and the discrepancy accumulates imperceptiblyappears on all screens at once
A weak pointversion is lighter by design, but lives a separate life from the main sitethe phone's browser also loads what is hidden by styles
Free audit

Free measurement of what a smartphone receives

Mobile speed is not a separate version of the site, but how many bytes and how much time a person gets from a phone on a network that is worse than the office Internet. We measure it from the outside and show the numbers.

What we measure

  1. Document weight and compressionHow much does a page weigh raw and how much - compressed. In the three stores we measured, the raw markup of the main one diverged almost threefold: 103.2, 252.6, and 295.7 KB.
  2. First answer and full downloadSeparately for the main, category and card. These three numbers often diverge more than the owner expects.
  3. Mobile viewportWhether it is set at all and whether finger zooming is blocked is the last and accessibility note.
  4. ImageQuantity, formats, delayed download. Measured landmark from above: 66 out of 69 pictures, i.e. 96%, in one of the shops.
  5. Third-party scriptsChats, widgets, pixels — they cost more on mobile than on desktop.
  6. Compression on the serverWhether gzip or brotli is enabled and whether HTTP/2 is working. This is the cheapest part of the work with the greatest effect.

What you get

  • Mobile return figures for three types of pages with measurement date.
  • Distribution of page weight by components: markup, images, scripts.
  • List of edits from the cheapest to the most expensive.
  • Conversation for 30 minutes on the document.

Timeline: 2-3 working days

Why is it free

Because in half the cases, turning on compression and correct images gives the greatest effect - it's inexpensive, and we'll say it instead of selling a month of work.

What's next

Next is a list of works with the amount and term. If the numbers are already good, let's say it straight: in our sample there are sites where mobile speed is not a problem.

Short form: your contact and site URL

Did not find your case?

Describe how it works on your side — we will tell you whether “Mobile site speed” fits and what it means in your situation. No brief and no call: one question, one answer.

Contract and paperwork

We work officially

Contract, act and invoice — for every project, not just large ones.

Trusted by6 brands

Trusted by: Kvant Energy, GYPSUN, Naturel Cosmetics, Pancer Protection, LUGI, BeeTech

Terms fixed in writing8 points

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

We sign NDAs on request. After completing the work, we delete our access to your services ourselves.

What affects the price

Why two seemingly identical tasks are priced differently

  • What will the measurement show?Compression and images close in a few days. The theme that gives the phone a desktop layout entirely is weeks. That's why we don't call the forks to measure: it would coincide with reality only by chance.
  • Server access levelYou have the right to edit the configuration - compression, protocol and headers are closed in one day. There is none - we act through the hoster and rely on what the tariff allows.
  • How many images and where do they come from?Seventy pictures in a template is one edit. The catalog, where the manager pours originals from the camera every week, also requires a rule for the future, otherwise the weight will return in a quarter.
  • Who disposes of third-party scriptsRemove the counter - a minute. Agree with the marketer and the advertising contractor, which five of the twelve remain, a separate week of the calendar, and it is also on time.
  • How different is the template for mobileA theme where the mobile view is styled on top of the same document is cheap only in appearance: the phone's browser loaded everything hidden anyway. Separating "hide" and "do not give" is the most expensive part of the job.
  • Number of page types and language versionsEach unique pattern and each language branch is a separate measurement before and after. In the measured store of heating equipment, there are two such branches, uk and ru with the correct x-default, that is, the check is doubled.
Cases

Tasks and results in numbers — all metrics measured by us

a niche store of dental materials with a content part

Task
Keep the page light while combining the catalog with content materials for a professional audience.
Solution
A compact theme without unnecessary modules by Cloudflare; the catalog is limited to the actual assortment, the site map is compiled as an index of four files.
Result
Measured on 07/31/2026: Main markup weight 103.2KB — second lightest page among 16 sites we measured, first response 440.7ms, full load 543.1ms. The catalog of 96 products and 21 categories gives exactly 123 addresses in the site map without a single duplicate. A defect was found: there are no analytics counters on the site - zero mentions of the tag manager, gtag and GA, that is, conversions are not measured here at all.

online store of garden tools for private buyers

Task
Check how ready the page is for mobile traffic.
Solution
Measurement of markup weight and response time, count of delayed loading images, mobile viewport and protocol verification.
Result
Measurement 07/31/2026: 252.6KB markup, first response 547.2ms, full load 676.7ms, HTTP/2, viewport set. Images are done correctly: 66 out of 69 tags have delayed loading, that's 96%. At the same time, defects other than speed were found - the site map gives 200 with an empty body, there is no block of structured data and no h1 tag on the main page, and the names of the carriers are presented as pictures without textual descriptions, so neither search nor screen readers see them.

online retail store of heating equipment, catalog of about 3.5 thousand items

Task
Evaluate the mobile performance of a medium-sized directory with two language versions.
Solution
Measuring the first response and full load, checking the weight of markup, viewport and language versions on the live directory.
Result
Measured on 07/31/2026: first response 524.8ms, full load 662.7ms with a markup weight of 295.7KB and a catalog of 3,565 cards. The mobile viewport is set, the language versions are uk and ru with the correct x-default. The bottleneck was not speed: the sitemap returns 200 with an empty body, and there are no structured data blocks at all - the page loads fine, but search sees it worse than it could.
What we need from you

We can't start without this — best to prepare in advance

  1. Site address and list of pages where mobile traffic comes from.
  2. Access to templates and to the server: compression and headers are done there, not in the admin.
  3. Analytics data on the share of mobile visitors - it is better to calculate the impact on your number, not on the industry average.
  4. Widget solution: Some of the weight cannot be removed without touching other people's scripts.
  5. One person from your side who can say "turn off" in a day.
  6. The list of language versions that are really advancing: you need to measure before and after each one separately.
If something is missing — let us know, we'll help you gather it or do it as a separate task.
FAQ

Most frequently asked questions — with concrete answers

Why is mobile speed more important than desktop speed?

For two reasons, and they are different in nature. The first is technical: the search indexes the site according to the mobile version, that is, what the smartphone sees, and what the search engine sees — hidden or underloaded on the phone does not exist for the index. The second is arithmetic: the majority of search and social traffic comes from phones, where network latency is added to server latency. Check your GA4 for exact share, not industry reviews: B2B is not the same as retail.

Do you need a separate mobile version?

No, and we refuse when asked. A separate mobile site is two documents that someone has to keep the same, the second address, the redirect by device and the canonical, which sooner or later gets confused. For mobile indexing, the discrepancy between them is downright harmful. The right way is adaptive layout: one document, different presentation. We will also mention its minus: what is hidden by styles on the phone, the browser still downloaded, so "hide" and "do not show" are different things, and we work with the second one.

What gives the most at the least cost?

Server-side response and image compression. Both points do not change the appearance of the site and do not require reworking of the theme: compression is enabled in the configuration, delayed loading is an attribute in the template. Our own measurements show how well this works: the garden tool store's 66 out of 69 images take a while to load, and the dental supply store's main markup weighs in at 103.2 KB — the second lightest page of the 16 sites we measured. The most expensive item, the theme, goes last and not always at all.

How do you check that the mobile version is serving the same content?

We request the page twice, with a desktop and mobile agent, and compare the answers: text, links, headers, blocks of structured data. There are two types of disagreement. The first part of the content comes via a script, and it is not in the initial response. The second — the template deliberately gives the mobile a truncated set of blocks. Both are visible only when comparing the answers: everything looks normal on the phone screen. At the same time, little things are caught that break the understanding of the page. In the measured garden tool store, the names of the carriers on the delivery page are presented as pictures without a text description, so neither search nor a screen reader reads them.

Does the locked zoom get in the way?

Yes, and both sides at once. You forbid a person with poor eyesight to zoom in on the text with his fingers - this is not a theoretical, but a daily inconvenience. Accessibility checks record such a parameter as a defect, and it ends up in reports that are then read by your partners. This is fixed by one line in the template: the viewport remains, the zooming ban is removed. Separately, it is worth mentioning the limit: in the three stores we measured, the viewport was set everywhere, and this is a necessary minimum, not a proof of convenience. Whether it's easy to checkout with your thumb is checked only in live sessions.

We have B2B and buyers sitting at computers - do we need it?

Maybe not, and we'll say it straight. In B2B, the share of desktop is usually significantly higher, mobile speed is not the first priority there, and it is more honest to admit this than to sell work as universal. Two remarks still remain. Indexing follows the mobile version in the same way, so the shortened mobile template is visible even with a desktop audience. And the share is worth looking at in your own GA4: with suppliers whose customers are looking for the right position simply in the shop or on the object, it is not at all what the owner expects.

How long does the work take?

9–20 working days. The lower limit is when the case is closed by the server and images: measurement 2-3 days, compression and protocol a day, images a day or two. The top is held by the theme. If she gives the same blocks to the phone as to the desktop, and hides half of them with styles, it has to be disassembled - that's 2-6 days in a separate line of the estimate. We deliberately put cheap edits first so that the effect is visible in the second week, and not after everything is finished.

When will the result be visible in Search Console?

Not immediately and not completely. In our measurements, the difference is visible on the same day: the same pages, the same methods, the same number of attempts. The field data that Search Console looks at is collected from real devices, updated with a delay of weeks, and its value also depends on which phones and networks you are accessing from - no contractor manages this, so we do not promise a specific number in the report. And separately about orders: you can see a change in them only where there is analytics. There are none in the measured dental supply store, so any acceleration there will show up in our numbers and nowhere else.

Demo

Your catalogue on a phone screen

This is how your store can look on a phone: a collection banner, popular products and a cart one tap away. Tap “Add to cart” and the counter in the header updates, just like in a real store.

  • Collection bannerThe first screen shows what is new, not a logo.
  • Product cardsPhoto, price and a button — no extra page to open.
  • One-tap cartThe counter in the header updates instantly, like in a real store.
Stores in the portfolio
This is a demo interface, not a client's store. Live projects are in the portfolio.
SHOP
New collectionAutumn / WinterExplore
PopularAll products ›
  • Essentials Hoodie1 290 ₴
  • Urban Backpack1 490 ₴
  • Classic Cap690 ₴
  • Basic Tee590 ₴
  • Street Sneakers2 390 ₴
  • Active Shorts890 ₴

Submit your site address and tell us which pages are getting mobile traffic.

In response, there are numbers of mobile returns for three types of pages, a breakdown of weight by component, and a list of edits from the cheapest to the most expensive. If it turns out that you are fine with mobile speed, we will write that way: there are such sites in our sample.

From measured casesMeasured on 07/31/2026: Main markup weight 103.2KB

View cases
  • Reply within 2 hours
  • No commitment
  • We work under a contract

There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.