Tools & Wizards About Us
whatsail.com screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

whatsail.com

whatsail.com

Page Load Speed

1.9 sec in total

First Response

227 ms

Resources Loaded

1.6 sec

Page Rendered

69 ms

whatsail.com screenshot

About Website

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

Visit whatsail.com

Key Findings

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

Performance Metrics

whatsail.com performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value5.3 s

57/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

whatsail.com

227 ms

bootstrap.min.css

20 ms

1727501614839main.css

67 ms

1727501614839responsive.css

31 ms

all.min.css

39 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Whatsail.com, 5% (2 requests) were made to Stats.dynadot.com and 2% (1 request) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (942 ms) relates to the external source Stats.dynadot.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 11.1 kB (4%)

Content Size

275.7 kB

After Optimization

264.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatsail.com main page is 275.7 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. 75% 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. Javascripts take 145.0 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 7.4 kB

  • Original 10.6 kB
  • After minification 10.6 kB
  • After compression 3.2 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 7.4 kB or 70% of the original size.

Image Optimization

-28%

Potential reduce by 1.4 kB

  • Original 4.8 kB
  • After minification 3.5 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, Whatsail needs image optimization as it can save up to 1.4 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 618 B

  • Original 145.0 kB
  • After minification 145.0 kB
  • After compression 144.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

-1%

Potential reduce by 1.7 kB

  • Original 115.2 kB
  • After minification 115.2 kB
  • After compression 113.5 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. Whatsail.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (84%)

Requests Now

25

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whatsail.com

whatsail.com

227 ms

bootstrap.min.css

bootstrap.min.css

20 ms

1727501614839main.css

1727501614839main.css

67 ms

1727501614839responsive.css

1727501614839responsive.css

31 ms

all.min.css

all.min.css

39 ms

v4-shims.min.css

v4-shims.min.css

65 ms

eyi5ire.css

eyi5ire.css

67 ms

1727501614839cropper.css

1727501614839cropper.css

35 ms

jquery-3.6.3.min.js

jquery-3.6.3.min.js

79 ms

bootstrap.min.js

bootstrap.min.js

66 ms

lazysizes.min.js

lazysizes.min.js

67 ms

js

js

79 ms

popup.css

popup.css

66 ms

switzer.css

switzer.css

67 ms

swansea.css

swansea.css

67 ms

1727501611769forsale-common.css

1727501611769forsale-common.css

78 ms

1727501611769forsale-makeoffer.css

1727501611769forsale-makeoffer.css

68 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

78 ms

1727501611769forsale-makeoffer.js

1727501611769forsale-makeoffer.js

77 ms

highcharts.js

highcharts.js

82 ms

popup.js

popup.js

78 ms

hp_script.js

hp_script.js

215 ms

p.css

p.css

29 ms

matomo.js

matomo.js

114 ms

for-sale-background.webp

for-sale-background.webp

74 ms

navbar-logo-dark-2023.png

navbar-logo-dark-2023.png

17 ms

Switzer-Regular.woff

Switzer-Regular.woff

22 ms

Switzer-Variable.woff

Switzer-Variable.woff

45 ms

Switzer-Medium.woff

Switzer-Medium.woff

21 ms

Switzer-Light.woff

Switzer-Light.woff

22 ms

Switzer-Extralight.woff

Switzer-Extralight.woff

45 ms

Switzer-Thin.woff

Switzer-Thin.woff

55 ms

Switzer-Semibold.woff

Switzer-Semibold.woff

46 ms

Switzer-Extrabold.woff

Switzer-Extrabold.woff

45 ms

Switzer-Black.woff

Switzer-Black.woff

45 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

46 ms

fa-regular-400.ttf

fa-regular-400.ttf

69 ms

fa-brands-400.ttf

fa-brands-400.ttf

69 ms

fa-solid-900.ttf

fa-solid-900.ttf

79 ms

fa-light-300.ttf

fa-light-300.ttf

86 ms

fa-thin-100.ttf

fa-thin-100.ttf

87 ms

matomo.php

matomo.php

942 ms

Accessibility Review

whatsail.com accessibility score

75

Accessibility Issues

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.

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 [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

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

whatsail.com SEO score

77

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

Page is blocked from indexing

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatsail.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Whatsail.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

whatsail.com

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