Tools & Wizards About Us
horariodebus.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 87

    SEO

    Google-friendlier than
    66% of websites

horariodebus.com

Mexican, Caribbean, Central and South American, India and Balearic Islands bus schedule

Page Load Speed

3.5 sec in total

First Response

368 ms

Resources Loaded

2.9 sec

Page Rendered

212 ms

horariodebus.com screenshot

About Website

Welcome to horariodebus.com homepage info - get ready to check Horariode Bus best content right away, or after learning these important things about horariodebus.com

Online schedule for bus, train, ferry and boat connections in South and Central America, Mexico, the Caribbean and the Balearic Islands. Portal of public transport for travelers and local mobility.

Visit horariodebus.com

Key Findings

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

Performance Metrics

horariodebus.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

19/100

25%

SI (Speed Index)

Value45.1 s

0/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

horariodebus.com

368 ms

horariodebus.com

716 ms

choice.js

23 ms

bootstrap.min.css

338 ms

metisMenu.min.css

350 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 83% of them (64 requests) were addressed to the original Horariodebus.com, 4% (3 requests) were made to S7.addthis.com and 3% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (865 ms) belongs to the original domain Horariodebus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 452.2 kB (66%)

Content Size

690.0 kB

After Optimization

237.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Horariodebus.com main page is 690.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 200.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 117.3 kB

  • Original 147.8 kB
  • After minification 143.2 kB
  • After compression 30.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 117.3 kB or 79% of the original size.

Image Optimization

-70%

Potential reduce by 139.3 kB

  • Original 200.1 kB
  • After minification 60.7 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, Horariode Bus needs image optimization as it can save up to 139.3 kB or 70% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-34%

Potential reduce by 61.3 kB

  • Original 178.2 kB
  • After minification 176.9 kB
  • After compression 116.9 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 61.3 kB or 34% of the original size.

CSS Optimization

-82%

Potential reduce by 134.3 kB

  • Original 163.9 kB
  • After minification 161.5 kB
  • After compression 29.6 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. Horariodebus.com needs all CSS files to be minified and compressed as it can save up to 134.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (53%)

Requests Now

73

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Horariode 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 15 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

horariodebus.com

horariodebus.com

368 ms

horariodebus.com

horariodebus.com

716 ms

choice.js

choice.js

23 ms

bootstrap.min.css

bootstrap.min.css

338 ms

metisMenu.min.css

metisMenu.min.css

350 ms

sb-admin-2.css

sb-admin-2.css

351 ms

font-awesome.min.css

font-awesome.min.css

455 ms

footer.css

footer.css

367 ms

ads.css

ads.css

351 ms

hdb.css

hdb.css

441 ms

plusone.js

plusone.js

153 ms

befrei.js

befrei.js

451 ms

wh.js

wh.js

517 ms

adsbygoogle.js

adsbygoogle.js

178 ms

jquery.min.js

jquery.min.js

711 ms

bootstrap.min.js

bootstrap.min.js

716 ms

metisMenu.min.js

metisMenu.min.js

698 ms

sb-admin-2.js

sb-admin-2.js

706 ms

addthis_widget.js

addthis_widget.js

165 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

220 ms

hda16.png

hda16.png

772 ms

hf16.png

hf16.png

175 ms

ht16.png

ht16.png

165 ms

tm16.png

tm16.png

162 ms

fla_bb.gif

fla_bb.gif

168 ms

fla_bz.gif

fla_bz.gif

408 ms

fla_bm.gif

fla_bm.gif

426 ms

fla_ky.gif

fla_ky.gif

400 ms

fla_cr.gif

fla_cr.gif

410 ms

fla_cu.gif

fla_cu.gif

411 ms

fla_do.gif

fla_do.gif

413 ms

fla_ec.gif

fla_ec.gif

419 ms

fla_sv.gif

fla_sv.gif

419 ms

fla_gf.gif

fla_gf.gif

418 ms

fla_gp.gif

fla_gp.gif

417 ms

fla_gt.gif

fla_gt.gif

419 ms

fla_hn.gif

fla_hn.gif

420 ms

fla_in.gif

fla_in.gif

460 ms

fla_mx.gif

fla_mx.gif

459 ms

fla_ni.gif

fla_ni.gif

459 ms

fla_pa.gif

fla_pa.gif

459 ms

fla_pe.gif

fla_pe.gif

458 ms

fla_sanandres.gif

fla_sanandres.gif

458 ms

fla_es.gif

fla_es.gif

731 ms

fla_sr.gif

fla_sr.gif

728 ms

fla_ve.gif

fla_ve.gif

730 ms

bus_logo2.gif

bus_logo2.gif

728 ms

Flag_of_Barbados.png

Flag_of_Barbados.png

725 ms

Flag_of_Belize.png

Flag_of_Belize.png

728 ms

Flag_of_Bermuda.png

Flag_of_Bermuda.png

731 ms

Flag_of_the_Cayman_Islands.png

Flag_of_the_Cayman_Islands.png

730 ms

Flag_of_CostaRica.png

Flag_of_CostaRica.png

720 ms

Flag_of_Cuba.png

Flag_of_Cuba.png

622 ms

Flag_of_the_Dominican_Republic.png

Flag_of_the_Dominican_Republic.png

616 ms

Flag_of_Ecuador.png

Flag_of_Ecuador.png

613 ms

Flag_of_El_Salvador.png

Flag_of_El_Salvador.png

717 ms

Flag_of_French_Guyana.png

Flag_of_French_Guyana.png

715 ms

Flag_of_Guadeloupe.png

Flag_of_Guadeloupe.png

715 ms

Flag_of_Guatemala.png

Flag_of_Guatemala.png

711 ms

Flag_of_Honduras.png

Flag_of_Honduras.png

707 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

865 ms

zrt_lookup.html

zrt_lookup.html

88 ms

Flag_of_India.png

Flag_of_India.png

567 ms

Flag_of_Mexico.png

Flag_of_Mexico.png

550 ms

Flag_of_Nicaragua.png

Flag_of_Nicaragua.png

558 ms

Flag_of_Panama.png

Flag_of_Panama.png

549 ms

Flag_of_Peru.png

Flag_of_Peru.png

550 ms

Flag_of_San_Andres.png

Flag_of_San_Andres.png

802 ms

Flag_of_Spain.png

Flag_of_Spain.png

803 ms

Flag_of_Suriname.png

Flag_of_Suriname.png

803 ms

Flag_of_Venezuela.png

Flag_of_Venezuela.png

803 ms

show_ads_impl.js

show_ads_impl.js

99 ms

moatframe.js

moatframe.js

249 ms

_ate.track.config_resp

_ate.track.config_resp

318 ms

300lo.json

300lo.json

500 ms

sh.f48a1a04fe8dbf021b4cda1d.html

sh.f48a1a04fe8dbf021b4cda1d.html

68 ms

layers.fa6cd1947ce26e890d3d.js

layers.fa6cd1947ce26e890d3d.js

32 ms

Accessibility Review

horariodebus.com accessibility score

96

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

Links do not have a discernible name

Best Practices

horariodebus.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

horariodebus.com SEO score

87

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

horariodebus.com

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