Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

jollysailing.com

Jolly Sailing & Dolphin Cruise | Pensacola Bay Cruises

Page Load Speed

6.7 sec in total

First Response

48 ms

Resources Loaded

4.8 sec

Page Rendered

1.9 sec

About Website

Visit jollysailing.com now to see the best up-to-date Jolly Sailing content and also check out these interesting facts you probably never knew about jollysailing.com

Come see dolphins play on a Pensacola Beach dolphin cruise in Pensacola Bay with Jolly Sailing and Dolphin Cruise, a family-owned company. Book now!

Visit jollysailing.com

Key Findings

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

Performance Metrics

jollysailing.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value25.1 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value5,130 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.073

96/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

jollysailing.com

48 ms

jollysailing.com

383 ms

gtm.js

65 ms

131 ms

jolly_sailing_dolphin_cruise_logo.png

168 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 63% of them (17 requests) were addressed to the original Jollysailing.com, 15% (4 requests) were made to Dipr2nuwo661l.cloudfront.net and 11% (3 requests) were made to Fareharbor.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Jollysailing.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 194.7 kB (3%)

Content Size

5.8 MB

After Optimization

5.6 MB

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

HTML Optimization

-85%

Potential reduce by 149.5 kB

  • Original 176.3 kB
  • After minification 154.6 kB
  • After compression 26.8 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 21.7 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 149.5 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 916 B

  • Original 4.7 MB
  • After minification 4.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. Jolly Sailing images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 40.3 kB

  • Original 841.9 kB
  • After minification 841.9 kB
  • After compression 801.6 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

-9%

Potential reduce by 4.1 kB

  • Original 43.1 kB
  • After minification 43.1 kB
  • After compression 39.1 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. Jollysailing.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (28%)

Requests Now

25

After Optimization

18

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

Accessibility Review

jollysailing.com accessibility score

94

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

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

jollysailing.com best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

jollysailing.com SEO score

84

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

Links do not have descriptive text

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

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