Website review, no card needed

traektoria.ru logo

traektoria.ru website review

Visit site (opens in a new tab)Reviewed 19 October 202653 issues · 80 checks

This review found 53 issues worth fixing on traektoria.ru, 23 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.1 s2.6 sApr 25Oct 103.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.9 s
May 2, 20262.8 s
May 9, 20262.7 s
May 16, 20262.7 s
May 23, 20262.6 s
May 30, 20262.7 s
Jun 6, 20262.8 s
Jun 13, 20262.9 s
Jun 20, 20263.0 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.0 s
Jul 18, 20263.1 s
Jul 25, 20263.0 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20262.8 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
216 ms188 msApr 25Oct 10199 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026213 ms
May 2, 2026209 ms
May 9, 2026205 ms
May 16, 2026199 ms
May 23, 2026198 ms
May 30, 2026200 ms
Jun 6, 2026200 ms
Jun 13, 2026205 ms
Jun 20, 2026207 ms
Jun 27, 2026207 ms
Jul 4, 2026209 ms
Jul 11, 2026207 ms
Jul 18, 2026206 ms
Jul 25, 2026204 ms
Aug 1, 2026200 ms
Aug 8, 2026197 ms
Aug 15, 2026193 ms
Aug 22, 2026191 ms
Aug 29, 2026193 ms
Sep 5, 2026196 ms
Sep 12, 2026199 ms
Sep 19, 2026204 ms
Sep 26, 2026204 ms
Oct 3, 2026201 ms
Oct 10, 2026199 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of traektoria.ru (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. traektoria.ru at 1.0 s1.0 s
  2. traektoria.ru at 2.0 s2.0 s
  3. traektoria.ru at 2.9 s2.9 s
  4. traektoria.ru at 3.9 s3.9 s
  5. traektoria.ru at 4.9 s4.9 s
  6. traektoria.ru at 5.9 s5.9 s
  7. traektoria.ru at 6.8 s6.8 s
  8. traektoria.ru at 7.8 s7.8 s

Speed

12 to fix21
  • Use efficient cache lifetimes

    3.1 s · 1.9 MB

    56 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).

  • Reduce unused JavaScript

    3.4 s · 741 KiB

    About 741 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.4 s faster on a phone.

  • Mobile performance score: 21

    21/100

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

  • Main-thread work: 4.3 s

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

  • Improve image delivery

    600 ms · 3.5 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (diginetica.net, mango-office.ru and Google Tag Manager and others), adding 2.4 MB and 1.6 s of main-thread time.

  • Render-blocking requests

    750 ms

    9 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • mango-office.ru adds 587 ms

    587 ms

    mango-office.ru costs a phone 587 ms of main-thread work and 1.5 MB 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.

  • diginetica.net adds 655 ms

    655 ms

    diginetica.net costs a phone 655 ms of main-thread work and 393 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.

  • 14 long tasks on the main thread

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

  • Reduce unused CSS

    341 KiB

    About 341 KiB of CSS is downloaded but never applied on this page.

  • Google Tag Manager adds 229 ms

    229 ms

    Google Tag Manager costs a phone 229 ms of main-thread work and 309 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.

  • Minify CSS

    225 KiB

    225 KiB could be saved by minifying CSS.

  • Font display

    200 ms

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

  • Minify JavaScript

    150 ms · 32 KiB

    32 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    10 KiB

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

  • Chained critical requests

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

1 checks passed
  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 15.8 s

    15.8 s

    Your largest element takes 15.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 26.7 s

    26.7 s

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

  • Speed Index: 10.5 s

    10.5 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Cumulative Layout Shift: 0.282

    0.282

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

  • Real-user LCP: 3.2 s

    3.2 s

    Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.23

    0.23

    For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.9 s

    1.9 s

    Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

  • 21 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

2 checks passed
  • Real-user INP: 194 ms

    194 ms

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

  • Real-user TTFB: 619 ms

    619 ms

    Real visitors wait 619 ms for your server to start answering (75th percentile). Good is under 800 ms.

Images and page weight

6 to fix19
  • Page weight: 8.2 MB in 170 requests

    8.2 MB

    Your homepage downloads 8.2 MB in 170 requests on a phone: images 4.8 MB (55), scripts 3.2 MB (65) and fonts 93 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 15 images far larger than shown

    2.9 MB

    15 images are downloaded at several times the size a phone draws them, for example 494nkh3z3t3l6735l0il27alydld1dks.jpg at 1,500 px wide, shown at 219 px. Resized copies would save about 2.9 MB.

  • 1 image over 500 KB

    494nkh3z3t3l6735l0il27alydld1dks.jpg weighs 581 KiB. On a phone connection a single image that size takes seconds.

  • 15 images in older formats

    15 images (3.9 MB) 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.

  • 10 images below the first screen load straight away

    10 images further down the page (2.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    89hbnwb0qzjex14padtwzaqxyj457p2w.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 2.3 g of CO₂ per visit

    2.32 g

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

Accessibility

9 to fixGoogle 7383
  • Images must have alternative text (10 elements)

    Images must have alternative text: 10 elements on the page fail this check, rated critical by axe-core.

  • 5 buttons without a name

    5 buttons have no accessible name, so screen readers announce just “button”.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • All page content should be contained by landmarks (70 elements)

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

  • No main landmark

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

  • 3 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 33 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 9270
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (115 characters)

    Your title is 115 characters, so Google will cut it off around 60: “Интернет-магазин Траектория – продажа сноубордов, лонгбордов, вейкбордов, одежды, обуви и…”.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

3 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Купить сноуборды, лонгборды, скейтборды и аксессуары с доставкой по Москве, Санкт-Петербургу, России и СНГ можно в мага…”.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.traektoria.ru/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.traektoria.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.

1 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    36 of 41 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • No call to action on the first screen

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

  • No calls to action

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 138 words

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

  • No form on the homepage

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

  • No risk reducer

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 20 cookies set on arrival

    20

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

  • No consent tool detected

    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.

  • 18 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at traektoria.ru, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on traektoria.ru, including 23 speed issues, 6 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25