Website review, no card needed

dynastymattress.com logo

dynastymattress.com website review

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

This review found 35 issues worth fixing on dynastymattress.com, 13 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
2.0 s1.3 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.5 s
Jun 6, 20261.6 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.6 s
Jul 4, 20261.5 s
Jul 11, 20261.7 s
Jul 18, 20261.8 s
Jul 25, 20262.0 s
Aug 1, 20261.8 s
Aug 8, 20261.7 s
Aug 15, 20261.6 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.3 s
Sep 26, 20261.4 s
Oct 17, 20261.7 s
Oct 24, 20261.6 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
105 ms94 msMay 16Sep 595 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202696 ms
May 23, 202696 ms
May 30, 202697 ms
Jun 6, 202697 ms
Jun 13, 2026104 ms
Jun 20, 2026104 ms
Jun 27, 2026104 ms
Jul 4, 2026104 ms
Jul 11, 202696 ms
Jul 18, 202696 ms
Jul 25, 202697 ms
Aug 1, 202696 ms
Aug 15, 202697 ms
Sep 5, 202695 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 dynastymattress.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dynastymattress.com at 0.9 s0.9 s
  2. dynastymattress.com at 1.8 s1.8 s
  3. dynastymattress.com at 2.7 s2.7 s
  4. dynastymattress.com at 3.5 s3.5 s
  5. dynastymattress.com at 4.4 s4.4 s
  6. dynastymattress.com at 5.3 s5.3 s
  7. dynastymattress.com at 6.2 s6.2 s
  8. dynastymattress.com at 7.1 s7.1 s

Speed

9 to fix62
  • Reduce unused JavaScript

    3.3 s · 606 KiB

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

  • Use efficient cache lifetimes

    1.3 s · 285 KiB

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

  • Main-thread work: 4.0 s

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

  • Reduce unused CSS

    990 ms · 184 KiB

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

  • Mobile performance score: 62

    62/100

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

  • Render-blocking requests

    950 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Yotpo, Shopify and jQuery CDN and others), adding 1.1 MB and 807 ms of main-thread time.

  • Minify CSS

    390 ms · 6 KiB

    6 KiB could be saved by minifying CSS.

  • Shopify adds 151 ms

    151 ms

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

  • Minify JavaScript

    130 ms · 90 KiB

    90 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    202 KiB

    6 images could be 202 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    150 ms · 43 KiB

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

  • 8 long tasks on the main thread

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

  • Duplicated JavaScript

    100 ms · 11 KiB

    11 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.

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

    5 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 14.9 s

    14.9 s

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

  • Time to Interactive: 16.6 s

    16.6 s

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

  • Speed Index: 7.5 s

    7.5 s

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

  • 39 images without width and height

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 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 96 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +2%

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

6 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 CLS: 0.01

    0.01

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Total Blocking Time: 199 ms

    199 ms

    Scripts block the page for only 199 ms while loading. Good is under 200 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 fix75
  • Page weight: 3.8 MB in 354 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 354 requests on a phone: scripts 1.4 MB (94), other files 1.2 MB (162) and images 1,001 KiB (76). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    111 KiB

    1 image is downloaded at several times the size a phone draws it, for example Variation_1_Mobile_8d077a76-55e0-45c0-9e70-1eb86b44e830.png at 2,397 px wide, shown at 390 px. Resized copies would save about 111 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (38 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.07 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.07 g of CO₂e: 128.1 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

9 to fixGoogle 7588
  • 9 buttons without a name

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

  • 21 text elements with low contrast

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

  • Malformed lists

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

  • ARIA input fields must have an accessible name (3 elements)

    ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

  • 6 images without alt text

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 13 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 9 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 7780
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (74 characters)

    Your title is 74 characters, so Google will cut it off around 60: “Buy Quality Online Mattresses | Gel Memory Foam Mattress – DynastyMattress”.

  • 9 links crawlers can't follow

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

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

  • 107 internal links, 4 external

    The homepage links to 107 pages on dynastymattress.com and 4 external pages.

6 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Buy the best quality mattresses online from Dynasty mattress. Check out high end, luxurious & affordable mattresses. Fr…”.

  • Canonical URL set

    The canonical URL is https://dynastymattress.com/.

  • Structured data in place

    Structured data found: 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://dynastymattress.com/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 (1,650 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://dynastymattress.com/pages/compare-bases-beds-brands-1 has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://dynastymattress.com/collections/gel-memory-foam-mattresses, https://dynastymattress.com/collections/base-frames and https://dynastymattress.com/collections/sofa-mattresses 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 32 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 11 small tap targets

    11 of 31 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 “Unexpected token 'function'”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • 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.

  • 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 1,057 words of copy

    The homepage carries about 1,057 words of visible text.

4 checks passed
  • 22 calls to action

    The homepage has 22 calls to action, for example “Shop”, “Track Your Order!” and “Contact Us”.

  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 9 testimonial or review blocks, 18 customer or partner logos, a star rating and 5 trust badges.

  • Analytics in place

    Analytics detected: Microsoft Clarity and Hotjar.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 mores (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.

  • 27 cookies set on arrival

    27

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

  • 41 other companies contacted

    Loading the homepage contacts 41 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 dynastymattress.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 13 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Delm · Discount In Cart · Hs Slide Cart Drawer · autoketing.org · salessquad.co.uk · herokuapp.com · amazonaws.com · retention.com · gorgias.chat · cloudfront.net · klaviyo.com · ryviu.com · 9gtb.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

  • The footer still says © 2024.

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Hotjar | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
City of Industry

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on dynastymattress.com, including 14 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