targetsms.tech website review

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.

3 images could be 165 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.

About 210 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

12 files are served with short cache lifetimes, so returning visitors download them again (84 KiB).

The page has 1,835 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 39 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

6 third-party services load with your homepage (Google Tag Manager, Yandex Metrica and Google Analytics and others), adding 301 KiB and 152 ms of main-thread time.

3 long tasks block the main thread while loading, the longest for 92 ms. During a long task the page ignores taps.

Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Сервис СМС-рассылки сообщений для бизнеса”. Most of its time is element render delay (2.7 s).

Visually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 2.6 s on a phone. Good is under 1.8 s.

The page becomes fully interactive after 5.0 s. Good is under 3.8 s.

15 images have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 image is downloaded at several times the size a phone draws it, for example slide11.jpg at 1,070 px wide, shown at 330 px. Resized copies would save about 16 KiB.

2 images (279 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image further down the page (169 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 0.28 g of CO₂e: 33.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

All page content should be contained by landmarks: 82 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

15 visible links have no text or label, so screen readers cannot say where they go.

4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (4 elements).

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

Google's crawler is blocked from indexing this page.

Your canonical URL points to targetsms.ru, not targetsms.tech, so Google may credit that host instead.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 77 pages on targetsms.tech and 28 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

/uslugi, /sms-rassylka, /avtorizatsiya-po-sms, /pozdravleniya-s-prazdnikami-i-dnyami-rozhdeniya, /email-rassylka and /partnerskaya-programma and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/tarify has no <h1> headline, so visitors and search engines get no clear main topic.

/avtorizatsiya-po-sms, /pozdravleniya-s-prazdnikami-i-dnyami-rozhdeniya, /email-rassylka, /sms-rassylka-megafon, /sms-rassylka-mts and /sms-rassylka-tele2 and 4 others took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 70 found) and read each the way a search engine does.

Large scripts ship without source maps.

Social proof on the homepage: 32 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 91 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Yandex Metrica (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 8 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.