Website review, no card needed

steamlogistics.com logo

steamlogistics.com website review

Visit site (opens in a new tab)Reviewed 27 October 202628 issues · 75 checks

This review found 28 issues worth fixing on steamlogistics.com, 8 of them high impact, across 75 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.6 s667 msMay 9Oct 24841 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.2 s
May 16, 20261.2 s
May 23, 20261.5 s
May 30, 20261.4 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.0 s
Jul 4, 20261.0 s
Jul 11, 2026950 ms
Jul 18, 2026907 ms
Jul 25, 2026949 ms
Aug 1, 2026925 ms
Aug 8, 2026948 ms
Aug 15, 2026952 ms
Aug 22, 2026930 ms
Aug 29, 2026912 ms
Sep 5, 2026842 ms
Sep 12, 2026775 ms
Sep 19, 2026855 ms
Sep 26, 2026855 ms
Oct 3, 2026910 ms
Oct 10, 2026971 ms
Oct 17, 2026828 ms
Oct 24, 2026841 ms
Real-visitor tap response (INP)75th percentile, phones
96 ms69 msMay 9Oct 2483 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202688 ms
May 16, 202686 ms
May 23, 202693 ms
May 30, 202692 ms
Jun 6, 202682 ms
Jun 13, 202684 ms
Jun 20, 202678 ms
Jun 27, 202675 ms
Jul 4, 202678 ms
Jul 11, 202684 ms
Jul 18, 202684 ms
Jul 25, 202688 ms
Aug 1, 202684 ms
Aug 8, 202685 ms
Aug 15, 202686 ms
Aug 22, 202690 ms
Aug 29, 202685 ms
Sep 5, 202672 ms
Sep 12, 202675 ms
Sep 19, 202676 ms
Sep 26, 202678 ms
Oct 3, 202683 ms
Oct 10, 202682 ms
Oct 17, 202679 ms
Oct 24, 202683 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of steamlogistics.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. steamlogistics.com at 0.7 s0.7 s
  2. steamlogistics.com at 1.3 s1.3 s
  3. steamlogistics.com at 2.0 s2.0 s
  4. steamlogistics.com at 2.7 s2.7 s
  5. steamlogistics.com at 3.3 s3.3 s
  6. steamlogistics.com at 4.0 s4.0 s
  7. steamlogistics.com at 4.6 s4.6 s
  8. steamlogistics.com at 5.3 s5.3 s

Speed

8 to fix33
  • Render-blocking requests

    8.8 s

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

  • Mobile performance score: 33

    33/100

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

  • Use efficient cache lifetimes

    3.8 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (website-files.com, Google Tag Manager and Google Analytics and others), adding 15.9 MB and 410 ms of main-thread time.

  • website-files.com adds 282 ms

    282 ms

    website-files.com costs a phone 282 ms of main-thread work and 15.7 MB 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.

  • Reduce unused JavaScript

    300 ms · 239 KiB

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

  • 9 long tasks on the main thread

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

  • Main-thread work: 3.3 s

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

  • Reduce unused CSS

    150 ms · 25 KiB

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

  • Improve image delivery

    174 KiB

    1 image could be 174 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify CSS

    150 ms · 5 KiB

    5 KiB could be saved by minifying CSS.

  • Chained critical requests

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

1 checks passed
  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • First Contentful Paint: 9.2 s

    9.2 s

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

  • Largest Contentful Paint: 11.7 s

    11.7 s

    Your largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Modern supply chain solutions for a changing world. Get A Q…”.

  • Time to Interactive: 15.7 s

    15.7 s

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

  • Speed Index: 9.2 s

    9.2 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

    Scripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -7%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.1 s

    1.1 s

    Real visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 363 ms

    363 ms

    Real visitors wait 363 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 31% faster for real visitors

    -31%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.2 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.022

    0.022

    The layout barely moves while loading (CLS 0.022, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 16.2 MB in 51 requests

    16.2 MB

    Your homepage downloads 16.2 MB in 51 requests on a phone: other files 10.0 MB (12), media 3.7 MB (2) and fonts 1.5 MB (8). Under 2 MB keeps phones on slow connections fast.

  • About 4.6 g of CO₂ per visit

    4.61 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9896
  • All page content should be contained by landmarks (6 elements)

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

  • Document should not have more than one banner landmark (1 element)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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

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

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10084
  • Title is short (15 characters)

    Your title is only 15 characters: “Steam Logistics”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is long (183 characters)

    Your meta description is 183 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 30 internal links, 10 external

    The homepage links to 30 pages on steamlogistics.com and 10 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Modern supply chain solutions for a changing world.”.

  • Canonical URL set

    The canonical URL is https://www.steamlogistics.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.steamlogistics.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.steamlogistics.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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (275 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix85
  • 3 pages without a meta description

    https://www.steamlogistics.com/legal/privacy-policy, https://www.steamlogistics.com/legal/terms-of-service and https://www.steamlogistics.com/legal/terms-conditions have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 links to non-canonical URLs

    Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://www.steamlogistics.com/services, whose canonical is //services. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.steamlogistics.com/testimonials and https://www.steamlogistics.com/glossary have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 internal pages checked

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

4 checks passed
  • Linked pages load

    All 11 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute height: Expected length, "auto".”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    10 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • Thin social proof

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

  • No form on the homepage

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

  • No risk reducer

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

  • About 250 words of copy

    The homepage carries about 250 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get A Quote →” and “Learn more.”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us”, “Get a Quote” and “Get A Quote →”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 14 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at steamlogistics.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Analytics
Google Analytics | Google Tag Manager | Hotjar
Hosting
Webflow

Company

Employees
491

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on steamlogistics.com, including 14 speed issues, 3 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25