Tools & Wizards About Us
voyenbus.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

voyenbus.com

VoyenBus | Pasajes de bus online. Buses de media y larga distancia

Page Load Speed

4.4 sec in total

First Response

311 ms

Resources Loaded

3.6 sec

Page Rendered

505 ms

voyenbus.com screenshot

About Website

Visit voyenbus.com now to see the best up-to-date Voyen Bus content for Argentina and also check out these interesting facts you probably never knew about voyenbus.com

Sistema global de compra y venta de pasajes de buses online. Comercialización de pasajes de ómnibus de media y larga distancia. Servicios de buses en América y Europa

Visit voyenbus.com

Key Findings

We analyzed Voyenbus.com page load time and found that the first response time was 311 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

voyenbus.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.222

56/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

voyenbus.com

311 ms

www.voyenbus.com

288 ms

www.voyenbus.com

597 ms

webfont.js

36 ms

main.min.css

447 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 96% of them (68 requests) were addressed to the original Voyenbus.com, 3% (2 requests) were made to Googletagmanager.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Voyenbus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 44.5 kB (2%)

Content Size

1.9 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Voyenbus.com main page is 1.9 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. 55% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 17.4 kB

  • Original 22.9 kB
  • After minification 22.9 kB
  • After compression 5.5 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 17.4 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 23.8 kB

  • Original 1.6 MB
  • After minification 1.5 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. Voyen Bus images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.3 kB

  • Original 252.7 kB
  • After minification 252.7 kB
  • After compression 249.4 kB

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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 57 B

  • Original 51.2 kB
  • After minification 51.2 kB
  • After compression 51.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. Voyenbus.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 32 (47%)

Requests Now

68

After Optimization

36

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

voyenbus.com

voyenbus.com

311 ms

www.voyenbus.com

www.voyenbus.com

288 ms

www.voyenbus.com

www.voyenbus.com

597 ms

webfont.js

webfont.js

36 ms

main.min.css

main.min.css

447 ms

js

js

68 ms

jquery.min.js

jquery.min.js

589 ms

popper.min.js

popper.min.js

436 ms

bootstrap.js

bootstrap.js

585 ms

main.min.js

main.min.js

432 ms

aos.js

aos.js

444 ms

clipboard.min.js

clipboard.min.js

580 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

729 ms

flatpickr.min.js

flatpickr.min.js

621 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

620 ms

ion.rangeSlider.min.js

ion.rangeSlider.min.js

726 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

740 ms

jarallax.min.js

jarallax.min.js

744 ms

jarallax-video.min.js

jarallax-video.min.js

745 ms

jarallax-element.min.js

jarallax-element.min.js

747 ms

jquery.countdown.min.js

jquery.countdown.min.js

869 ms

jquery.smartWizard.min.js

jquery.smartWizard.min.js

872 ms

plyr.polyfilled.min.js

plyr.polyfilled.min.js

1024 ms

prism.js

prism.js

875 ms

scrollMonitor.js

scrollMonitor.js

879 ms

smooth-scroll.polyfills.min.js

smooth-scroll.polyfills.min.js

895 ms

svg-injector.umd.production.js

svg-injector.umd.production.js

1013 ms

twitterFetcher_min.js

twitterFetcher_min.js

1015 ms

typed.min.js

typed.min.js

1019 ms

theme.js

theme.js

1059 ms

js

js

88 ms

voyenbus_logo.svg

voyenbus_logo.svg

609 ms

icon-menu.svg

icon-menu.svg

674 ms

icon-x.svg

icon-x.svg

677 ms

user.svg

user.svg

680 ms

header_02.webp

header_02.webp

828 ms

soluciones_digitales_estrategia_multicanal_01.webp

soluciones_digitales_estrategia_multicanal_01.webp

831 ms

soluciones_digitales_tolpos_01.webp

soluciones_digitales_tolpos_01.webp

841 ms

soluciones_digitales_tolbase_01.webp

soluciones_digitales_tolbase_01.webp

961 ms

soluciones_digitales_tolapi_01.webp

soluciones_digitales_tolapi_01.webp

963 ms

soluciones_digitales_data_01.webp

soluciones_digitales_data_01.webp

965 ms

bandera_argentina.webp

bandera_argentina.webp

970 ms

bandera_brasil.webp

bandera_brasil.webp

975 ms

bandera_chile.webp

bandera_chile.webp

984 ms

bandera_uruguay.webp

bandera_uruguay.webp

1104 ms

bandera_union_europea.webp

bandera_union_europea.webp

1025 ms

bandera_ee_uu_2.webp

bandera_ee_uu_2.webp

1017 ms

bus.svg

bus.svg

1017 ms

edificios.svg

edificios.svg

986 ms

tickets.svg

tickets.svg

994 ms

linkedin.svg

linkedin.svg

1115 ms

twitter.svg

twitter.svg

1011 ms

facebook.svg

facebook.svg

1001 ms

blog.svg

blog.svg

999 ms

secure_site.svg

secure_site.svg

1002 ms

data-fiscal.webp

data-fiscal.webp

1009 ms

certificacion_iso_web.png

certificacion_iso_web.png

1132 ms

icon-arrow-up.svg

icon-arrow-up.svg

1007 ms

header_02.jpg

header_02.jpg

1190 ms

soluciones_digitales_estrategia_multicanal_01.jpg

soluciones_digitales_estrategia_multicanal_01.jpg

912 ms

soluciones_digitales_tolpos_01.jpg

soluciones_digitales_tolpos_01.jpg

918 ms

soluciones_digitales_tolbase_01.jpg

soluciones_digitales_tolbase_01.jpg

926 ms

soluciones_digitales_tolapi_01.jpg

soluciones_digitales_tolapi_01.jpg

1048 ms

soluciones_digitales_data_01.jpg

soluciones_digitales_data_01.jpg

1046 ms

bandera_argentina.png

bandera_argentina.png

1055 ms

bandera_brasil.png

bandera_brasil.png

1061 ms

bandera_chile.png

bandera_chile.png

1069 ms

bandera_uruguay.png

bandera_uruguay.png

1190 ms

bandera_union_europea.png

bandera_union_europea.png

1151 ms

bandera_ee_uu_2.png

bandera_ee_uu_2.png

1157 ms

data-fiscal.jpg

data-fiscal.jpg

1158 ms

Accessibility Review

voyenbus.com accessibility score

79

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

[aria-hidden="true"] elements contain focusable descendents

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

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

Links do not have a discernible name

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

voyenbus.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

voyenbus.com SEO score

97

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

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

voyenbus.com

Open Graph data is detected on the main page of Voyen Bus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: