Website review, no card needed

dormeo-na.com logo

dormeo-na.com website review

Visit site (opens in a new tab)Reviewed 6 November 202639 issues · 84 checks

This review found 39 issues worth fixing on dormeo-na.com, 18 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
3.8 s2.5 sMay 16Oct 312.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.0 s
May 23, 20263.1 s
May 30, 20263.2 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20263.3 s
Jul 4, 20263.5 s
Jul 11, 20263.6 s
Jul 18, 20263.6 s
Jul 25, 20263.7 s
Aug 1, 20263.6 s
Aug 8, 20263.4 s
Aug 15, 20263.4 s
Aug 22, 20263.4 s
Aug 29, 20263.4 s
Sep 5, 20263.4 s
Sep 12, 20263.3 s
Sep 19, 20263.2 s
Sep 26, 20263.1 s
Oct 3, 20263.1 s
Oct 10, 20263.1 s
Oct 17, 20263.0 s
Oct 24, 20262.9 s
Oct 31, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
371 ms283 msMay 16Oct 31294 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026293 ms
May 23, 2026316 ms
May 30, 2026326 ms
Jun 6, 2026332 ms
Jun 13, 2026344 ms
Jun 20, 2026344 ms
Jun 27, 2026360 ms
Jul 4, 2026361 ms
Jul 11, 2026343 ms
Jul 18, 2026335 ms
Jul 25, 2026326 ms
Aug 1, 2026330 ms
Aug 8, 2026342 ms
Aug 15, 2026345 ms
Aug 22, 2026345 ms
Aug 29, 2026338 ms
Sep 5, 2026333 ms
Sep 12, 2026327 ms
Sep 19, 2026319 ms
Sep 26, 2026321 ms
Oct 3, 2026322 ms
Oct 10, 2026325 ms
Oct 17, 2026326 ms
Oct 24, 2026315 ms
Oct 31, 2026294 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 dormeo-na.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix49
  • Reduce unused JavaScript

    3.0 s · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

  • Use efficient cache lifetimes

    1.9 s · 964 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 49

    49/100

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

  • Main-thread work: 7.0 s

    A phone's processor spends 7.0 s on main-thread work while loading, 3.7 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 (iubenda, Affirm and rebuyengine.com and others), adding 1.8 MB and 1.8 s of main-thread time.

  • iubenda adds 976 ms

    976 ms

    iubenda costs a phone 976 ms of main-thread work and 141 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.

  • Improve image delivery

    350 ms · 419 KiB

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

  • Affirm adds 255 ms

    255 ms

    Affirm costs a phone 255 ms of main-thread work and 172 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.

  • rebuyengine.com adds 183 ms

    183 ms

    rebuyengine.com costs a phone 183 ms of main-thread work and 682 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.

  • emotivecdn.io adds 117 ms

    117 ms

    emotivecdn.io costs a phone 117 ms of main-thread work and 384 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.

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    81 KiB

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

  • Reduce unused CSS

    39 KiB

    About 39 KiB of CSS is downloaded but never applied on this page.

  • Minify CSS

    6 KiB

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

  • Forced reflow

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

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

10 to fix33
  • Fails Core Web Vitals for real visitors

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

  • Largest Contentful Paint: 19.1 s

    19.1 s

    Your largest element takes 19.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Video Player”.

  • Time to Interactive: 28.3 s

    28.3 s

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

  • Speed Index: 7.3 s

    7.3 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user INP: 203 ms

    203 ms

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Total Blocking Time: 541 ms

    541 ms

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

  • 11 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

3 checks passed
  • 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 TTFB: 453 ms

    453 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 24.7 MB in 534 requests

    24.7 MB

    Your homepage downloads 24.7 MB in 534 requests on a phone: media 19.5 MB (5), scripts 2.2 MB (98) and other files 1.6 MB (370). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    61 KiB

    2 images are downloaded at several times the size a phone draws them, for example 30cardtrial.png at 1,442 px wide, shown at 390 px. Resized copies would save about 61 KiB.

  • 4 images below the first screen load straight away

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

  • About 7.0 g of CO₂ per visit

    6.99 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

6 to fixGoogle 9390
  • 6 tap targets too small

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

  • 5 text elements with low contrast

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • 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 (1 element)

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Dormeo USA Official Site | Better Sleep with Octaspring® Technology”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 86 internal links, 9 external

    The homepage links to 86 pages on dormeo-na.com and 9 external pages.

7 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Dormeo® improves sleep with our mattresses, toppers, and pillows featuring our Patented Aerospace Octaspring® technolog…”.

  • One H1 headline

    Your main headline reads: “Dormeo North America LLC”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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.

  • No llms.txt

    There is no https://www.dormeousa.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 (1,103 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.dormeousa.com/products/the-essential-mattress-topper-by-dormeo%C2%AE%EF%B8%8F-usa, whose canonical is https://www.dormeousa.com/products/the-essential-mattress-topper-by-dormeo%c2%ae%ef%b8%8f-usa. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.dormeousa.com/collections/mattress-toppers has 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 30 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 6 pages that loaded have a meta description.

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

Best practices

3 to fixGoogle 9671
  • 3 broken images

    3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343135116&Ver=2&mid=eead63dc-5bf0-4bb5-a493-0dcac37c4e97&bo=3&sid=9cfb61d0d9bd11f1acaff7ec21ac74b0&vid=9cfb8c00d9bd11f1869c4b97f3acd078&vids=1&msclkid=N&pi=918639831&l.

  • 4 small tap targets

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

  • 6 JavaScript errors while loading

    6 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

2 to fix79
  • No social proof

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

  • No analytics detected

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

  • About 581 words of copy

    The homepage carries about 581 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact Us”, “Shop The Premium Mattress Topper” and “Shop the toppers”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 3 mores (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

  • 50 cookies set on arrival

    50

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

  • 78 other companies contacted

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

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) loads with the page.

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 dormeo-na.com, 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 19 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geo Pro Geolocation · P9nl2c6l2 Opensend · Dormeo Usa X Retention · Cmp Insert Code · Gorgias Live Chat Helpdesk · Aimerce First Party Pixel · Triplewhale · Klaviyo Email Marketing Sms · Easylocation · Shopify App Template Php · Applovin Shop Integration · emotivecdn.io · nmgassets.com · shareasale.com · popt.in · trustpilot.com · rebuyengine.com · 9gtb.com · paytomorrow.com

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
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on dormeo-na.com, including 21 speed issues, 2 SEO issues and 2 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