rsms.com website review

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

16 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.5 s faster on a phone.

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

Your mobile performance score is 65 (desktop: 85). Pages that score under 90 lose visitors before the first paint.

About 269 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 280 ms faster on a phone.

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

Google Maps costs a phone 249 ms of main-thread work and 478 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.

4 third-party services load with your homepage (Google Maps, JSDelivr CDN and Other Google APIs/SDKs and others), adding 584 KiB and 253 ms of main-thread time.

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

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

Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

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.

5 KiB could be saved by minifying CSS.

Your largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welcome To Red Sea Marine Services LLC”.

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 90 ms to 80 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 16.6 MB in 69 requests on a phone: media 12.5 MB (1), images 3.3 MB (39) and scripts 547 KiB (17). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.4 MB together. On a phone connection a single image that size takes seconds.

9 images (2.8 MB) 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.

8 images further down the page (2.0 MB) 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 4.71 g of CO₂e: 565.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

21 buttons have no accessible name, so screen readers announce just “button”.

19 tap targets are too small or too close together to hit reliably with a finger.

Links must have discernible text: 12 elements on the page fail this check, rated serious by axe-core.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Some lists contain elements other than list items, which screen readers announce wrongly.

9 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.

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

Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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 http://rsms.com/sitemap.xml, so Google discovers your pages only by following links.

4 links have no real href, so search engines can't follow them.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 39 pages on rsms.com and 1 external page.

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://rsms.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.

https://rsms.com/reach-us, https://rsms.com/vision-mission-principle, https://rsms.com/hsseq-policy, https://rsms.com/our-management-team, https://rsms.com/managing-directors-desk and https://rsms.com/ship-management and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://rsms.com/reach-us, https://rsms.com/vision-mission-principle, https://rsms.com/hsseq-policy, https://rsms.com/our-management-team, https://rsms.com/managing-directors-desk and https://rsms.com/ship-management and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://rsms.com/our-operating-area and https://rsms.com/our-partners have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

4 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is served at too low a resolution for sharp phone screens.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

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 472 words of visible text.

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