Tools & Wizards About Us
mego.travel screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

mego.travel

Купить дешевые авиабилеты онлайн: цены, поиск и покупка билетов на самолет - Mego.travel

Page Load Speed

2.5 sec in total

First Response

238 ms

Resources Loaded

2.1 sec

Page Rendered

123 ms

mego.travel screenshot

About Website

Click here to check amazing Mego content for Russia. Otherwise, check out these important facts you probably never knew about mego.travel

Mego.travel - надежный сервис по продаже авиабилетов. Низкие цены, удобный поиск, широкая география полетов по всему миру. Гарантия возврата! Купить билет на самолет стало еще проще и надежнее.

Visit mego.travel

Key Findings

We analyzed Mego.travel page load time and found that the first response time was 238 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

mego.travel performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

31/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value11.6 s

5/100

10%

TBT (Total Blocking Time)

Value1,680 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.051

99/100

15%

TTI (Time to Interactive)

Value23.0 s

1/100

10%

Network Requests Diagram

mego.travel

238 ms

mego.travel

507 ms

mego-icons.css

120 ms

vendor.da476dfc.css

477 ms

app.08b6b170.css

459 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 62% of them (21 requests) were addressed to the original Mego.travel, 29% (10 requests) were made to Cdn.mego.travel and 6% (2 requests) were made to Clarity.ms. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Mego.travel.

Page Optimization Overview & Recommendations

Page size can be reduced by 171.6 kB (15%)

Content Size

1.2 MB

After Optimization

980.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Mego.travel main page is 1.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 31.7 kB

  • Original 36.6 kB
  • After minification 35.5 kB
  • After compression 4.9 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 31.7 kB or 87% of the original size.

Image Optimization

-13%

Potential reduce by 139.5 kB

  • Original 1.1 MB
  • After minification 974.6 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Mego needs image optimization as it can save up to 139.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-39%

Potential reduce by 393 B

  • Original 1.0 kB
  • After minification 1.0 kB
  • After compression 612 B

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 393 B or 39% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (41%)

Requests Now

27

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mego. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

mego.travel

mego.travel

238 ms

mego.travel

mego.travel

507 ms

mego-icons.css

mego-icons.css

120 ms

vendor.da476dfc.css

vendor.da476dfc.css

477 ms

app.08b6b170.css

app.08b6b170.css

459 ms

2583.3bef0fec.css

2583.3bef0fec.css

367 ms

6427.c6c861f8.css

6427.c6c861f8.css

391 ms

chunk-common.5550de92.css

chunk-common.5550de92.css

417 ms

vendor.a0f8f122.js

vendor.a0f8f122.js

951 ms

2583.2dade6ae.js

2583.2dade6ae.js

531 ms

6427.a70fae24.js

6427.a70fae24.js

531 ms

chunk-common.fecd4d27.js

chunk-common.fecd4d27.js

771 ms

app.95e8fa98.js

app.95e8fa98.js

1026 ms

cmf5t4tele

cmf5t4tele

43 ms

clarity.js

clarity.js

16 ms

ru.svg

ru.svg

471 ms

am.svg

am.svg

485 ms

az.svg

az.svg

508 ms

by.svg

by.svg

532 ms

kg.svg

kg.svg

583 ms

kz.svg

kz.svg

556 ms

uz.svg

uz.svg

632 ms

tkp-gray.png

tkp-gray.png

658 ms

visa-gray.png

visa-gray.png

684 ms

mastercard-gray.png

mastercard-gray.png

733 ms

home-desktop.png

home-desktop.png

712 ms

mego.svg

mego.svg

147 ms

sprite.sm.svg

sprite.sm.svg

756 ms

Inter-Regular.e89cb199.ttf

Inter-Regular.e89cb199.ttf

703 ms

Inter-Medium.6dcbc9be.ttf

Inter-Medium.6dcbc9be.ttf

717 ms

Inter-Light.eec86646.ttf

Inter-Light.eec86646.ttf

695 ms

Inter-SemiBold.4d56bb21.ttf

Inter-SemiBold.4d56bb21.ttf

790 ms

flUhRq6tzZclQEJ-Vdg-IuiaDsNa.4d73cb90.woff

flUhRq6tzZclQEJ-Vdg-IuiaDsNa.4d73cb90.woff

806 ms

c.gif

c.gif

7 ms

Accessibility Review

mego.travel accessibility score

83

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

mego.travel best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

mego.travel SEO score

100

Search Engine Optimization Advices

Mobile Friendly

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/).

Impact

Issue

High

Document uses legible font sizes

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 Mego.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 Mego.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

mego.travel

Open Graph description is not detected on the main page of Mego. 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: