Website review, no card needed

steigen.com.sg logo

steigen.com.sg website review

Visit site (opens in a new tab)Reviewed 12 November 202625 issues · 79 checks

This review found 25 issues worth fixing on steigen.com.sg, 8 of them high impact, across 79 checks. The most urgent: page weight: 21.9 MB in 314 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
3.9 s399 msMay 23Nov 7857 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.3 s
May 30, 20263.4 s
Jun 6, 20263.5 s
Jun 13, 20263.4 s
Jun 20, 20262.7 s
Jun 27, 20261.8 s
Jul 4, 20261.1 s
Jul 11, 2026818 ms
Jul 18, 2026800 ms
Jul 25, 2026798 ms
Aug 1, 2026811 ms
Aug 8, 2026818 ms
Aug 15, 2026855 ms
Aug 22, 2026911 ms
Aug 29, 2026941 ms
Sep 5, 2026938 ms
Sep 12, 2026927 ms
Sep 19, 2026896 ms
Sep 26, 2026891 ms
Oct 3, 2026899 ms
Oct 10, 2026892 ms
Oct 17, 2026909 ms
Oct 24, 2026882 ms
Oct 31, 2026867 ms
Nov 7, 2026857 ms
Real-visitor tap response (INP)75th percentile, phones
135 ms101 msMay 23Nov 7118 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026124 ms
May 30, 2026123 ms
Jun 6, 2026121 ms
Jun 13, 2026121 ms
Jun 20, 2026115 ms
Jun 27, 2026113 ms
Jul 4, 2026111 ms
Jul 11, 2026108 ms
Jul 18, 2026112 ms
Jul 25, 2026108 ms
Aug 1, 2026108 ms
Aug 8, 2026105 ms
Aug 15, 2026112 ms
Aug 22, 2026121 ms
Aug 29, 2026128 ms
Sep 5, 2026131 ms
Sep 12, 2026130 ms
Sep 19, 2026126 ms
Sep 26, 2026121 ms
Oct 3, 2026121 ms
Oct 10, 2026120 ms
Oct 17, 2026121 ms
Oct 24, 2026123 ms
Oct 31, 2026121 ms
Nov 7, 2026118 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 steigen.com.sg (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. steigen.com.sg at 0.4 s0.4 s
  2. steigen.com.sg at 0.8 s0.8 s
  3. steigen.com.sg at 1.1 s1.1 s
  4. steigen.com.sg at 1.5 s1.5 s
  5. steigen.com.sg at 1.9 s1.9 s
  6. steigen.com.sg at 2.3 s2.3 s
  7. steigen.com.sg at 2.6 s2.6 s
  8. steigen.com.sg at 3.0 s3.0 s

Speed

3 to fix80
  • Main-thread work: 8.3 s

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

  • Mobile performance score: 80

    80/100

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

  • Render-blocking requests

    800 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Clarity and Shopify), adding 157 KiB and 271 ms of main-thread time.

  • Reduce unused JavaScript

    210 ms · 56 KiB

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

  • 2 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    20 ms · 24 KiB

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

  • Minify JavaScript

    20 ms · 19 KiB

    19 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    15 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (15 KiB).

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

  • Forced reflow

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

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 4.9 s

    4.9 s

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

  • Time to Interactive: 5.8 s

    5.8 s

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

  • Speed Index: 4.0 s

    4.0 s

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

  • Tap response (INP) held steady for real visitors

    -3%

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

10 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.0 s

    1.0 s

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

  • Real-user INP: 89 ms

    89 ms

    Real visitors wait 89 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • 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: 362 ms

    362 ms

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

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

    -74%

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 7 ms

    7 ms

    Scripts block the page for only 7 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix69
  • Page weight: 21.9 MB in 314 requests

    21.9 MB

    Your homepage downloads 21.9 MB in 314 requests on a phone: media 19.8 MB (8), other files 1.3 MB (238) and images 329 KiB (22). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Frame_1000007571.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 3 images below the first screen load straight away

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

  • About 6.2 g of CO₂ per visit

    6.22 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8892
  • 3 tap targets too small

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

  • 2 text elements with low contrast

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

  • 12 images without alt text

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

  • 12 links without text

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

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

2 to fixGoogle 8595
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links with vague text

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

  • 59 internal links, 14 external

    The homepage links to 59 pages on steigen.com.sg and 14 external pages.

7 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Steigen is an automatic laundry system designed by German engineers for Singapore homes, with Halo AI or Solar heat dry…”.

  • One H1 headline

    Your main headline reads: “Steigen Singapore”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Automated Laundry System & Smart Laundry Rack | Steigen”.

  • Canonical URL set

    The canonical URL is https://www.steigen.com.sg/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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.steigen.com.sg/sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • llms.txt published

    The site publishes https://www.steigen.com.sg/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 4 pages without a meta description

    https://www.steigen.com.sg/pages/comparison, https://www.steigen.com.sg/policies/privacy-policy, https://www.steigen.com.sg/policies/refund-policy and https://www.steigen.com.sg/policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://www.steigen.com.sg/pages/steigen-halo, https://www.steigen.com.sg/pages/steigen-solar, https://www.steigen.com.sg/pages/about, https://www.steigen.com.sg/pages/user-account, https://www.steigen.com.sg/pages/user-order and https://www.steigen.com.sg/pages/technician-admin and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.steigen.com.sg/pages/technician-admin has 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.

  • 13 internal pages checked

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

5 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 4 small tap targets

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

  • 2 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix70
  • No call to action on the first screen

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

  • No social proof

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

  • Local business without LocalBusiness data

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

  • Only about 148 words

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

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

6 checks passed
  • 14 calls to action

    The homepage has 14 calls to action, for example “Learn More”, “Buy” and “Buy Now”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 steigen.com.sg, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

Microsoft Clarity

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Singapore

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on steigen.com.sg, including 6 speed issues, 2 SEO issues and 4 conversion gaps. 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