pegast.ru website review

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.0 s faster on a phone.

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

Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

12 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

8 third-party services load with your homepage (yandex.ru, jivo.ru and Yandex CDN and others), adding 2.2 MB and 879 ms of main-thread time.

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

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

yandex.ru costs a phone 329 ms of main-thread work and 888 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 2.9 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

jivo.ru costs a phone 184 ms of main-thread work and 366 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Yandex CDN costs a phone 125 ms of main-thread work and 697 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Polyfills for old browsers add 42 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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 25.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Попробуйте обновить страницу через несколько минут”.

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

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

Real visitors wait 255 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

The layout shifts by 0.232 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Scripts block taps and scrolling for 520 ms in total while the page loads. Good is under 200 ms.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 190 ms to 178 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.6 MB in 199 requests on a phone: scripts 3.8 MB (102), images 2.2 MB (35) and HTML 185 KiB (3). Under 2 MB keeps phones on slow connections fast.

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

98 elements use ARIA attributes their role does not allow, which confuses screen readers.

5 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 4 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.

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

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

Your title is 246 characters, so Google will cut it off around 60: “Официальный сайт туроператора ПЕГАС Туристик. Туры и отдых в Турции, России, Вьетнаме, Та…”.

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

There are 2 <h1> headlines (“Лучшие туры” and “Популярные направления”). One clear main headline is easier for people and search engines.

Your meta description is 188 characters; Google truncates after about 160, so the end of your pitch is cut.

Open Graph is missing og:title, so shared links fall back to guesses.

The homepage links to 122 pages on pegast.ru and 12 external pages.

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 https://pegast.ru/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.

https://pegast.ru/offices is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://pegast.ru/offices, https://pegast.ru/pegasselect, https://pegast.ru/how-to-buy, https://pegast.ru/how-to-pay, https://pegast.ru/help and https://pegast.ru/about-company and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://pegast.ru/News/pegas-golf, https://pegast.ru/News/early-booking-turkey-2027, https://pegast.ru/news/zarubezhnye-napravleniya-winter-26-27 and https://pegast.ru/news/russia-leisure-and-excursions-winter-26-27 use the same meta description. A description written for each page earns more clicks.

https://pegast.ru/offices, https://pegast.ru/pegasselect, https://pegast.ru/about-company/insurance and https://pegast.ru/about-company/graphics-materials have no <h1> headline, so visitors and search engines get no clear main topic.

https://pegast.ru/pegasselect, https://pegast.ru/how-to-buy, https://pegast.ru/how-to-pay, https://pegast.ru/help, https://pegast.ru/about-company and https://pegast.ru/about-company/personal-data and 7 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

9 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Requests the geolocation permission on page load.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 1 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.

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.