sailence.com website review

83 files are served with short cache lifetimes, so returning visitors download them again (17.6 MB).

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.0 s faster on a phone.

37 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.7 s.

About 406 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.7 s faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).

Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

3 images could be 150 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

4 third-party services load with your homepage (YouTube, Google CDN and Other Google APIs/SDKs and others), adding 1.5 MB and 422 ms of main-thread time.

YouTube costs a phone 343 ms of main-thread work and 1,006 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 3.5 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Google CDN costs a phone 71 ms of main-thread work and 349 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

36 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

15 KiB could be saved by minifying CSS.

5 long tasks block the main thread while loading, the longest for 109 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 26.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

Visually, the page fills in at 18.1 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 29.9 s. Good is under 3.8 s.

The first text or image appears after 4.5 s on a phone. Good is under 1.8 s.

1 image have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 19.1 MB in 109 requests on a phone: media 14.3 MB (3), scripts 2.6 MB (43) and images 1.3 MB (13). Under 2 MB keeps phones on slow connections fast.

1 image (65 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 5.41 g of CO₂e: 648.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

8 visible links have no text or label, so screen readers cannot say where they go.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 39 characters: “Sailing for Enterpreneurs and Investors”. 70 to 160 characters is enough to sell the click.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://sailence.com/sitemap.xml, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 11 pages on sailence.com and 0 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://sailence.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

We fetched 5 pages linked from your homepage and read each the way a search engine does.

3 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://sailence.com/' was loaded over HTTPS, but requested an insecure favicon 'http://sai…”.

Chrome logged issues while loading the page (“Mixed content”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 177 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Opening the homepage sets 1 cookie, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.