Tools & Wizards About Us
roneeyshuttle.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

roneeyshuttle.com

Shuttle service in Central America | Roneey Shuttle

Page Load Speed

1.5 sec in total

First Response

112 ms

Resources Loaded

1.1 sec

Page Rendered

316 ms

roneeyshuttle.com screenshot

About Website

Click here to check amazing Roneey Shuttle content. Otherwise, check out these important facts you probably never knew about roneeyshuttle.com

ferry dock to utila, ronney shuttle, honduras shuttle, shuttle to honduras, crental america

Visit roneeyshuttle.com

Key Findings

We analyzed Roneeyshuttle.com page load time and found that the first response time was 112 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

roneeyshuttle.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value1.008

2/100

15%

TTI (Time to Interactive)

Value6.6 s

57/100

10%

Network Requests Diagram

roneeyshuttle.com

112 ms

www.roneeyshuttle.com

233 ms

critical.css

64 ms

js

51 ms

bootstrap.css

111 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 98% of them (60 requests) were addressed to the original Roneeyshuttle.com, 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (396 ms) belongs to the original domain Roneeyshuttle.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 198.3 kB (12%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 28.8 kB

  • Original 33.8 kB
  • After minification 25.4 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. This page needs HTML code to be minified as it can gain 8.4 kB, which is 25% 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 28.8 kB or 85% of the original size.

Image Optimization

-11%

Potential reduce by 168.7 kB

  • Original 1.5 MB
  • After minification 1.4 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. Obviously, Roneey Shuttle needs image optimization as it can save up to 168.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 429 B

  • Original 53.5 kB
  • After minification 53.5 kB
  • After compression 53.1 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

-1%

Potential reduce by 299 B

  • Original 29.0 kB
  • After minification 29.0 kB
  • After compression 28.7 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. Roneeyshuttle.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (36%)

Requests Now

28

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

roneeyshuttle.com

roneeyshuttle.com

112 ms

www.roneeyshuttle.com

www.roneeyshuttle.com

233 ms

critical.css

critical.css

64 ms

js

js

51 ms

bootstrap.css

bootstrap.css

111 ms

RoneeyStyle.css

RoneeyStyle.css

154 ms

fonts_site.css

fonts_site.css

155 ms

aos.css

aos.css

156 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

166 ms

bootstrap.min.js

bootstrap.min.js

155 ms

home.js

home.js

179 ms

aos.js

aos.js

229 ms

parallax-background.min.js

parallax-background.min.js

285 ms

modernizr-2.8.3.min.js

modernizr-2.8.3.min.js

229 ms

logo_mediano.png

logo_mediano.png

220 ms

logo_pequenio.png

logo_pequenio.png

221 ms

leon_wp.jpg

leon_wp.jpg

246 ms

antigua.jpg

antigua.jpg

291 ms

utila_wp.jpg

utila_wp.jpg

344 ms

yojoalake_wp.jpg

yojoalake_wp.jpg

293 ms

laceiba2_wp.jpg

laceiba2_wp.jpg

393 ms

tb_honduras.jpg

tb_honduras.jpg

236 ms

tb_guatemala.jpg

tb_guatemala.jpg

249 ms

tb_elsalvador.jpg

tb_elsalvador.jpg

300 ms

tb_nicaragua.jpg

tb_nicaragua.jpg

300 ms

contact_wp.jpg

contact_wp.jpg

343 ms

whatsapp.png

whatsapp.png

345 ms

mail.png

mail.png

351 ms

call.png

call.png

351 ms

wp.png

wp.png

396 ms

MrDafoe-Regular.woff

MrDafoe-Regular.woff

170 ms

MrDafoe-Regular.woff

MrDafoe-Regular.woff

177 ms

Raleway-Light.woff

Raleway-Light.woff

177 ms

Raleway-Light.woff

Raleway-Light.woff

178 ms

Raleway-ExtraLight.woff

Raleway-ExtraLight.woff

219 ms

Raleway-ExtraLight.woff

Raleway-ExtraLight.woff

227 ms

Raleway-Thin.woff

Raleway-Thin.woff

226 ms

Raleway-Thin.woff

Raleway-Thin.woff

227 ms

Raleway.woff

Raleway.woff

240 ms

Raleway.woff

Raleway.woff

239 ms

Raleway-Medium.woff

Raleway-Medium.woff

271 ms

Raleway-Medium.woff

Raleway-Medium.woff

284 ms

Raleway-SemiBold.woff

Raleway-SemiBold.woff

285 ms

Raleway-SemiBold.woff

Raleway-SemiBold.woff

284 ms

Raleway-Bold.woff

Raleway-Bold.woff

285 ms

Raleway-Bold.woff

Raleway-Bold.woff

286 ms

Raleway-ExtraBold.woff

Raleway-ExtraBold.woff

322 ms

Raleway-ExtraBold.woff

Raleway-ExtraBold.woff

331 ms

Raleway-Heavy.woff

Raleway-Heavy.woff

331 ms

Raleway-Heavy.woff

Raleway-Heavy.woff

330 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

344 ms

MrDafoe-Regular.ttf

MrDafoe-Regular.ttf

150 ms

Raleway-Light.ttf

Raleway-Light.ttf

182 ms

Raleway-ExtraLight.ttf

Raleway-ExtraLight.ttf

143 ms

Raleway-Thin.ttf

Raleway-Thin.ttf

142 ms

Raleway.ttf

Raleway.ttf

137 ms

Raleway-Medium.ttf

Raleway-Medium.ttf

78 ms

Raleway-SemiBold.ttf

Raleway-SemiBold.ttf

78 ms

Raleway-Bold.ttf

Raleway-Bold.ttf

117 ms

Raleway-ExtraBold.ttf

Raleway-ExtraBold.ttf

84 ms

Raleway-Heavy.ttf

Raleway-Heavy.ttf

84 ms

Accessibility Review

roneeyshuttle.com accessibility score

59

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 input fields do not have accessible names

High

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible 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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

roneeyshuttle.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

roneeyshuttle.com SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Roneeyshuttle.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 Roneeyshuttle.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

roneeyshuttle.com

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