Access raketa.travel. Ракета. Цифровая платформа для организации командировок и управления расходами

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

raketa.travel

201 ms

raketa.travel

604 ms

unsupported-browser.css

100 ms

gtm.js

60 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that 75% of them (3 requests) were addressed to the original Raketa.travel, 25% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (604 ms) belongs to the original domain Raketa.travel.

Content Size

3.6 kB

After Optimization

1.8 kB

In fact, the total size of Raketa.travel main page is 3.6 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 3.1 kB which makes up the majority of the site volume.

HTML Optimization

-57%

Potential reduce by 1.8 kB

Original 3.1 kB
After minification 2.9 kB
After compression 1.3 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 1.8 kB or 57% of the original size.

CSS Optimization

-12%

Potential reduce by 63 B

Original 519 B
After minification 519 B
After compression 456 B

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Raketa.travel needs all CSS files to be minified and compressed as it can save up to 63 B or 12% of the original size.

Requests Now

After Optimization

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Raketa. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Page is blocked from indexing

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

RU
Language Claimed

RU
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Raketa.travel can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Raketa.travel main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Raketa. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: