Tools & Wizards About Us
vr.by screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

vr.by

Турагентство

Page Load Speed

5.2 sec in total

First Response

396 ms

Resources Loaded

4.2 sec

Page Rendered

604 ms

vr.by screenshot

About Website

Visit vr.by now to see the best up-to-date Vr content for Belarus and also check out these interesting facts you probably never knew about vr.by

Visit vr.by

Key Findings

We analyzed Vr.by page load time and found that the first response time was 396 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

vr.by performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value10.2 s

9/100

10%

TBT (Total Blocking Time)

Value2,180 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.474

18/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

vr.by

396 ms

vr.by

729 ms

style.css

120 ms

style.css

239 ms

daterangepicker.css

356 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 78% of them (78 requests) were addressed to the original Vr.by, 4% (4 requests) were made to Cdn-ru.bitrix24.by and 4% (4 requests) were made to Vrlines.bitrix24.by. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Vr.by.

Page Optimization Overview & Recommendations

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

Content Size

4.8 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vr.by main page is 4.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 218.0 kB

  • Original 277.7 kB
  • After minification 244.1 kB
  • After compression 59.6 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. This page needs HTML code to be minified as it can gain 33.5 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 218.0 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 171.1 kB

  • Original 2.8 MB
  • After minification 2.7 MB

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. Vr images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 224.0 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.1 MB

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 224.0 kB or 17% of the original size.

CSS Optimization

-35%

Potential reduce by 113.4 kB

  • Original 320.6 kB
  • After minification 259.2 kB
  • After compression 207.2 kB

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. Vr.by needs all CSS files to be minified and compressed as it can save up to 113.4 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (49%)

Requests Now

91

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vr.by

vr.by

396 ms

vr.by

vr.by

729 ms

style.css

style.css

120 ms

style.css

style.css

239 ms

daterangepicker.css

daterangepicker.css

356 ms

style.css

style.css

356 ms

style.css

style.css

357 ms

style.css

style.css

361 ms

style.css

style.css

363 ms

style.css

style.css

365 ms

bootstrap.min.css

bootstrap.min.css

25 ms

reset.css

reset.css

472 ms

plugins.css

plugins.css

592 ms

style.css

style.css

601 ms

style.css

style.css

478 ms

core.js

core.js

872 ms

vue.bundle.js

vue.bundle.js

866 ms

jquery.min2.js

jquery.min2.js

862 ms

daterangepicker.min.js

daterangepicker.min.js

657 ms

script.js

script.js

861 ms

script.js

script.js

863 ms

script.js

script.js

864 ms

moment.min.js

moment.min.js

866 ms

daterangepicker.js

daterangepicker.js

867 ms

script.js

script.js

867 ms

js

js

65 ms

bootstrap.js

bootstrap.js

868 ms

plugins.js

plugins.js

1092 ms

scripts.js

scripts.js

953 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

954 ms

js

js

72 ms

map-single.js

map-single.js

953 ms

all.minify.js

all.minify.js

1318 ms

loader_29.js

loader_29.js

621 ms

main-hp.jpg

main-hp.jpg

501 ms

logo.png

logo.png

323 ms

f1c9dz0qohvpiur63xe29hscjuarmzc3.jpg

f1c9dz0qohvpiur63xe29hscjuarmzc3.jpg

922 ms

2x673bwoq14n7yshm79g05j1c0l51wkl.png

2x673bwoq14n7yshm79g05j1c0l51wkl.png

414 ms

7rary7qbsvwdqkm9y1wrawpzun8f74bj.png

7rary7qbsvwdqkm9y1wrawpzun8f74bj.png

417 ms

eu6lqkmbmw21d3ug1hdcpfv44bylmnz4.png

eu6lqkmbmw21d3ug1hdcpfv44bylmnz4.png

484 ms

0gudoxtmtr6xwn6ba0yz10fccrq2764k.png

0gudoxtmtr6xwn6ba0yz10fccrq2764k.png

532 ms

570whe7anssyjbd9ww5h4232ixgp8xyl.jpeg

570whe7anssyjbd9ww5h4232ixgp8xyl.jpeg

655 ms

y2ubnav1246zu2uffnlq3vwjh0fauyip.jpeg

y2ubnav1246zu2uffnlq3vwjh0fauyip.jpeg

564 ms

ccj9rtfmncx4vkld3umxsg7douoi3hbm.jpeg

ccj9rtfmncx4vkld3umxsg7douoi3hbm.jpeg

566 ms

o9gg8udaoo8smmz8c44gj5dvq4exgwvd.jpeg

o9gg8udaoo8smmz8c44gj5dvq4exgwvd.jpeg

651 ms

oairkr7qll96hywb7el5a0xglo8daii5.jpeg

oairkr7qll96hywb7el5a0xglo8daii5.jpeg

719 ms

qdn55bkxkx759b6giy08b4zlir9rtiov.jpeg

qdn55bkxkx759b6giy08b4zlir9rtiov.jpeg

720 ms

8n7dtdwb8h6w2o9399kdd5nmg4sas67c.jpg

8n7dtdwb8h6w2o9399kdd5nmg4sas67c.jpg

1008 ms

ssy9i3q3mwlahpz0swk7b2psh4rvxj53.jpeg

ssy9i3q3mwlahpz0swk7b2psh4rvxj53.jpeg

921 ms

sxl9u92ncw1gxebuelzlz84l702ix3po.jpg

sxl9u92ncw1gxebuelzlz84l702ix3po.jpg

918 ms

dhv6ykhau3t7o1273p2qynjieyxr5v2o.jpg

dhv6ykhau3t7o1273p2qynjieyxr5v2o.jpg

919 ms

whcp51nquxp1ie1t3c0nprkyx42scpps.jpg

whcp51nquxp1ie1t3c0nprkyx42scpps.jpg

917 ms

geysso0522t6zsm4zqg915jz5n4o0ub5.jpeg

geysso0522t6zsm4zqg915jz5n4o0ub5.jpeg

921 ms

jbub5b1264vxns3xpndj7cgu25jjl8oj.jpg

jbub5b1264vxns3xpndj7cgu25jjl8oj.jpg

947 ms

6nsnhbf9scbsi44712rcejo5fqjmhfax.jpeg

6nsnhbf9scbsi44712rcejo5fqjmhfax.jpeg

946 ms

izp20d55hybaxxldyf2szgap1i9rfvti.jpeg

izp20d55hybaxxldyf2szgap1i9rfvti.jpeg

793 ms

oyyvtvcxl6bbzlu7zbm970u15q8hfkdw.jpeg

oyyvtvcxl6bbzlu7zbm970u15q8hfkdw.jpeg

808 ms

ttsi9qb1odun0365n45r57519x1981wo.jpg

ttsi9qb1odun0365n45r57519x1981wo.jpg

823 ms

city7.png

city7.png

852 ms

7x4tre1x19oldf509jhj5mrz9sd6hwkr.jpg

7x4tre1x19oldf509jhj5mrz9sd6hwkr.jpg

844 ms

ckdly7482u3pi6hwe1fix13djea443kz.jpg

ckdly7482u3pi6hwe1fix13djea443kz.jpg

1135 ms

75lbjcrpy2g3kg9t77x2mf8qd9htdbjt.jpeg

75lbjcrpy2g3kg9t77x2mf8qd9htdbjt.jpeg

913 ms

jhmpeic4m8ygorxc7lea54ev8foyloek.jpg

jhmpeic4m8ygorxc7lea54ev8foyloek.jpg

921 ms

g93skm7udb147ygarngtmk05xlgmaaqv.jpeg

g93skm7udb147ygarngtmk05xlgmaaqv.jpeg

936 ms

2r9b363isvvaxbblw7i2am8ejt38ghhd.jpg

2r9b363isvvaxbblw7i2am8ejt38ghhd.jpg

960 ms

loader_4_5erglq.js

loader_4_5erglq.js

1128 ms

51nc7onpdrcwoaldyimit8oggwynw0gv.jpg

51nc7onpdrcwoaldyimit8oggwynw0gv.jpg

934 ms

ba.js

ba.js

289 ms

gtm.js

gtm.js

67 ms

rtrg

rtrg

621 ms

fbevents.js

fbevents.js

31 ms

tag.js

tag.js

924 ms

7wr02mub3om0fqrcl4y4epj5hpe2k2z3.jpg

7wr02mub3om0fqrcl4y4epj5hpe2k2z3.jpg

1047 ms

zd18ex17qjg5hi1nib77r23hv32hio05.jpg

zd18ex17qjg5hi1nib77r23hv32hio05.jpg

1048 ms

fa-regular-400.woff

fa-regular-400.woff

1048 ms

color.css

color.css

1031 ms

magnific-popup.css

magnific-popup.css

951 ms

fa-light-300.woff

fa-light-300.woff

995 ms

fa-solid-900.woff

fa-solid-900.woff

931 ms

viber.png

viber.png

929 ms

instagram.png

instagram.png

881 ms

facebook.png

facebook.png

921 ms

vk.png

vk.png

919 ms

polyfill.js

polyfill.js

328 ms

alfapay.png

alfapay.png

836 ms

logo_travelsoft.jpeg

logo_travelsoft.jpeg

832 ms

bx_stat

bx_stat

273 ms

jquery.arcticmodal.css

jquery.arcticmodal.css

774 ms

jquery.arcticmodal.js

jquery.arcticmodal.js

793 ms

recall-face.jpg

recall-face.jpg

747 ms

app.js

app.js

254 ms

528 ms

app.bundle.min.css

app.bundle.min.css

559 ms

app.bundle.min.js

app.bundle.min.js

1053 ms

call.tracker.js

call.tracker.js

163 ms

styles.min.css

styles.min.css

919 ms

script.min.js

script.min.js

1003 ms

advert.gif

advert.gif

526 ms

sync_cookie_image_decide

sync_cookie_image_decide

147 ms

sync_cookie_image_decide

sync_cookie_image_decide

141 ms

Accessibility Review

vr.by accessibility score

69

Accessibility Issues

ARIA

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.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

vr.by best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

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

vr.by SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vr.by can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Vr.by 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

vr.by

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