sdsd.com website review

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

15 images could be 933 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.7 s faster on a phone.

About 409 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.

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

Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

5 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.0 MB and 458 ms of main-thread time.

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

Google CDN costs a phone 298 ms of main-thread work and 736 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.

About 47 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

8 long tasks block the main thread while loading, the longest for 93 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.

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

Your largest element takes 22.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Every company faces unique challenges, that's why our solut…”.

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

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

The layout shifts by 0.156 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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 6.1 MB in 320 requests on a phone: media 2.6 MB (1), images 1.8 MB (27) and scripts 1.0 MB (27). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example iso-9001-2015-certifications-services.jpg at 1,000 px wide, shown at 113 px. Resized copies would save about 124 KiB.

2 images (366 KiB) are 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.

2 images further down the page (163 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your title is 70 characters, so Google will cut it off around 60: “SDSD - Maritime Fleet Management Software - Marine ERP - Ship Managers”.

There are 2 <h1> headlines (“Maritime technology solutions for” and “better decisions and commercial outcomes”). One clear main headline is easier for people and search engines.

Structured data found (BreadcrumbList, FAQPage, ImageObject and Organization) but with 8 problems, for example “SoftwareApplication: no offers (price) block”.

The homepage links to 88 pages on sdsd.com and 3 external pages.

https://www.sdsd.com/operational-efficiency-solutions, https://www.sdsd.com/safety-solutions, https://www.sdsd.com/esg-environmental-solutions, https://www.sdsd.com/people-crew-solutions, https://www.sdsd.com/digital-innovation-bespoke-development and https://www.sdsd.com/ship-broking-and-charterers-solutions have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://www.sdsd.com/' was loaded over HTTPS, but requested an insecure font 'http://staggi…”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage carries about 387 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 5 cookies (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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.