Website review, no card needed

originmattress.com.my logo

originmattress.com.my website review

Visit site (opens in a new tab)Reviewed 8 November 202637 issues · 84 checks

This review found 37 issues worth fixing on originmattress.com.my, 11 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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.8 s1.3 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.5 s
Aug 8, 20261.4 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.5 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
190 ms166 msMay 16Oct 31186 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026169 ms
May 23, 2026175 ms
May 30, 2026174 ms
Jun 6, 2026179 ms
Jun 13, 2026182 ms
Jun 20, 2026179 ms
Jun 27, 2026186 ms
Jul 4, 2026187 ms
Jul 11, 2026187 ms
Jul 18, 2026185 ms
Jul 25, 2026179 ms
Aug 1, 2026178 ms
Aug 8, 2026179 ms
Aug 15, 2026178 ms
Aug 22, 2026178 ms
Aug 29, 2026174 ms
Sep 5, 2026170 ms
Sep 12, 2026170 ms
Sep 19, 2026173 ms
Sep 26, 2026178 ms
Oct 3, 2026180 ms
Oct 10, 2026185 ms
Oct 17, 2026187 ms
Oct 24, 2026186 ms
Oct 31, 2026186 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 originmattress.com.my (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. originmattress.com.my at 0.9 s0.9 s
  2. originmattress.com.my at 1.7 s1.7 s
  3. originmattress.com.my at 2.6 s2.6 s
  4. originmattress.com.my at 3.4 s3.4 s
  5. originmattress.com.my at 4.3 s4.3 s
  6. originmattress.com.my at 5.1 s5.1 s
  7. originmattress.com.my at 6.0 s6.0 s
  8. originmattress.com.my at 6.8 s6.8 s

Speed

11 to fix59
  • Reduce unused JavaScript

    2.7 s · 617 KiB

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

  • Main-thread work: 4.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, monkcommerce.app and Klaviyo and others), adding 2.3 MB and 1.4 s of main-thread time.

  • Mobile performance score: 59

    59/100

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

  • Improve image delivery

    550 ms · 404 KiB

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

  • Shopify adds 785 ms

    785 ms

    Shopify costs a phone 785 ms of main-thread work and 1.1 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.

  • Use efficient cache lifetimes

    550 ms · 192 KiB

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

  • Render-blocking requests

    700 ms

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

  • Legacy JavaScript

    300 ms · 66 KiB

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

  • monkcommerce.app adds 179 ms

    179 ms

    monkcommerce.app costs a phone 179 ms of main-thread work and 550 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.

  • Klaviyo adds 174 ms

    174 ms

    Klaviyo costs a phone 174 ms of main-thread work and 309 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.

  • 6 long tasks on the main thread

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

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

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

    11 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 18.6 s

    18.6 s

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

  • Speed Index: 12.4 s

    12.4 s

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

  • Time to Interactive: 18.8 s

    18.8 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

8 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.7 s

    1.7 s

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

  • Real-user INP: 170 ms

    170 ms

    Real visitors wait 170 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: 1.5 s

    1.5 s

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

  • Real-user TTFB: 795 ms

    795 ms

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

  • Total Blocking Time: 147 ms

    147 ms

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

  • Cumulative Layout Shift: 0.033

    0.033

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

Images and page weight

3 to fix53
  • Page weight: 10.3 MB in 325 requests

    10.3 MB

    Your homepage downloads 10.3 MB in 325 requests on a phone: media 6.5 MB (1), scripts 1.6 MB (126) and images 925 KiB (36). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    M_120-Night_c98a9e90-0e92-4e6f-90cd-379cd08272a6.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).

  • 1 image far larger than shown

    154 KiB

    1 image is downloaded at several times the size a phone draws it, for example 741869bb-f054-457a-aa5e-b3c503b1148b.jpeg at 2,000 px wide, shown at 195 px. Resized copies would save about 154 KiB.

  • 1 image in older formats

    1 image (168 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.

  • About 2.9 g of CO₂ per visit

    2.92 g

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

Accessibility

6 to fixGoogle 8791
  • 17 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

  • 1 form field without a label

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

  • Headings skip levels

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

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

4 to fixGoogle 8575
  • No meta description

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

  • Title is long (76 characters)

    Your title is 76 characters, so Google will cut it off around 60: “Origin Mattress Malaysia | Best Mattress in Malaysia – Origin Sleep Malaysia”.

  • No social preview image

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

  • One H1 headline

    Your <h1> is empty.

  • 46 internal links, 10 external

    The homepage links to 46 pages on originmattress.com.my and 10 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://originmattress.com.my/.

  • Structured data in place

    Structured data found: 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://originmattress.com.my/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

3 to fix88
  • 7 pages without a meta description

    https://originmattress.com.my/pages/trial, https://originmattress.com.my/pages/faq, https://originmattress.com.my/pages/instalments, https://originmattress.com.my/pages/reviews, https://originmattress.com.my/pages/media and https://originmattress.com.my/pages/origin-awards and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://originmattress.com.my/products/origin-hybrid-mattress, https://originmattress.com.my/products/origin-snow-tencel-bedding-set and https://originmattress.com.my/products/origin-arctic-cool-mattress-protector use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://originmattress.com.my/pages/trial, https://originmattress.com.my/pages/faq, https://originmattress.com.my/pages/instalments, https://originmattress.com.my/pages/reviews and https://originmattress.com.my/pages/origin-awards have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

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

Best practices

3 to fixGoogle 7785
  • 2 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

  • 5 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • No analytics detected

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 307 words of copy

    The homepage carries about 307 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Mattresses” and “Join Now & Save”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us” and “Shop Mattresses”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and 3 trust badges.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies, 1 of them by other companies (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.

  • 39 other companies contacted

    Loading the homepage contacts 39 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 originmattress.com.my, 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 17 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Eg Auto Add To Cart · Sales Popup Autoketing Pop · Pagefly Ai Page Builder · Timesact Pre Order · Vo Product Options · Rt Facebook Messenger Chat · Simprosys Google Shopping Feed · Shopback Growth Tools · Judge Me Reviews · Monk Free Gift With Purchase · herokuapp.com · cfjump.com · apaylater.com · metorik.com · provesrc.com · socialsnowball.io

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

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on originmattress.com.my, including 16 speed issues, 4 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