Website review, no card needed
murphybeddepot.com website review
Visit site (opens in a new tab)Reviewed 9 November 202632 issues · 87 checks
This review found 32 issues worth fixing on murphybeddepot.com, 11 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
86B- #11,189 of 113,333 reviewed websitesbeats 86%
- #6,969 of 65,304 online storesbeats 85%
- #6,763 of 59,725 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 752 ms |
| May 30, 2026 | 738 ms |
| Jun 6, 2026 | 742 ms |
| Jun 13, 2026 | 796 ms |
| Jun 20, 2026 | 821 ms |
| Jun 27, 2026 | 852 ms |
| Jul 4, 2026 | 865 ms |
| Jul 11, 2026 | 847 ms |
| Jul 18, 2026 | 850 ms |
| Jul 25, 2026 | 835 ms |
| Aug 1, 2026 | 833 ms |
| Aug 8, 2026 | 829 ms |
| Aug 15, 2026 | 810 ms |
| Aug 22, 2026 | 824 ms |
| Aug 29, 2026 | 830 ms |
| Sep 5, 2026 | 847 ms |
| Sep 12, 2026 | 859 ms |
| Sep 19, 2026 | 854 ms |
| Sep 26, 2026 | 840 ms |
| Oct 3, 2026 | 805 ms |
| Oct 10, 2026 | 764 ms |
| Oct 17, 2026 | 794 ms |
| Oct 24, 2026 | 916 ms |
| Oct 31, 2026 | 1.1 s |
| Nov 7, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 139 ms |
| May 30, 2026 | 140 ms |
| Jun 6, 2026 | 141 ms |
| Jun 13, 2026 | 145 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 145 ms |
| Jul 18, 2026 | 145 ms |
| Jul 25, 2026 | 145 ms |
| Aug 1, 2026 | 146 ms |
| Aug 8, 2026 | 152 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 162 ms |
| Aug 29, 2026 | 165 ms |
| Sep 5, 2026 | 170 ms |
| Sep 12, 2026 | 173 ms |
| Sep 19, 2026 | 177 ms |
| Sep 26, 2026 | 178 ms |
| Oct 3, 2026 | 179 ms |
| Oct 10, 2026 | 184 ms |
| Oct 17, 2026 | 188 ms |
| Oct 24, 2026 | 187 ms |
| Oct 31, 2026 | 180 ms |
| Nov 7, 2026 | 172 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.5 s · 527 KiBAbout 527 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 367 KiB18 files are served with short cache lifetimes, so returning visitors download them again (367 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Shopify and others), adding 1.8 MB and 933 ms of main-thread time.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
500 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Google Tag Manager adds 432 ms
432 msGoogle Tag Manager costs a phone 432 ms of main-thread work and 652 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.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 118 ms
118 msShopify costs a phone 118 ms of main-thread work and 462 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.
Reduce unused CSS
150 ms · 49 KiBAbout 49 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 145 ms. During a long task the page ignores taps.
Improve image delivery
55 KiB3 images could be 55 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
54 KiBPolyfills for old browsers add 54 KiB JavaScript that modern phones do not need.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.0 s
15.0 sYour largest element takes 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 20.6 s
20.6 sThe page becomes fully interactive after 20.6 s. Good is under 3.8 s.
Speed Index: 6.1 s
6.1 sVisually, the page fills in at 6.1 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 139 ms to 172 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 71% slower for real visitors
+71%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.8 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 327 ms
327 msScripts block taps and scrolling for 327 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
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 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 164 ms
164 msReal visitors wait 164 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 520 ms
520 msReal visitors wait 520 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 3.3 MB in 249 requests
3.3 MBYour homepage downloads 3.3 MB in 249 requests on a phone: scripts 1.8 MB (147), images 1,019 KiB (24) and other files 186 KiB (56). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
33 KiB1 image is downloaded at several times the size a phone draws it, for example image_17.png at 1,200 px wide, shown at 308 px. Resized copies would save about 33 KiB.
1 image in older formats
1 image (31 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 0.9 g of CO₂ per visit
0.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 111.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Certain ARIA roles must be contained by particular parents (3 elements)
Certain ARIA roles must be contained by particular parents: 3 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
5 images without alt text
5 images have 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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 10 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
70 internal links, 1 external
The homepage links to 70 pages on murphybeddepot.com and 1 external page.
7 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Shop Murphy beds, wall beds, library beds, and cabinet beds with fast U.S. shipping and expert support. Find your perfe…”.
Title: 59 characters
Your title is a healthy 59 characters: “Murphy Beds & Wall Beds for Small Spaces | Murphy Bed Depot”.
Canonical URL set
The canonical URL is https://murphybeddepot.com/.
Structured data in place
Structured data found: FAQPage, 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://murphybeddepot.com/sitemap.xml.
AI search readiness
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,938 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://murphybeddepot.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages share a meta description
https://murphybeddepot.com/collections/murphy-bed-systems/library, https://murphybeddepot.com/collections/murphy-bed-systems/panel and https://murphybeddepot.com/collections/murphy-bed-systems use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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
4 small tap targets
4 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 896 words of copy
The homepage carries about 896 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP COMPLETE BED SYSTEMS” and “SHOP IN-STOCK COLLECTION”.
7 calls to action
The homepage has 7 calls to action, for example “SHOP COMPLETE BED SYSTEMS”, “SHOP FAST-TRACK COLLECTION” and “SHOP IN-STOCK COLLECTION”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks and “OVER 60,000 CUSTOMERS”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
41 cookies set on arrival
41Opening the homepage sets 41 cookies, 2 of them by other companies (measured from a US location before any click).
46 other companies contacted
Loading the homepage contacts 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 murphybeddepot.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 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Spark Tools For Inbox · Attentive · Easyban · Klaviyo Email Marketing Sms · Uppromote Affiliate · Microsoft Clarity · Page Speed Optimizer · Affliate By Secomapp · Simple Bundle · Back In Stock · Apo Product Options · w3apps.co · cloudfront.net · herokuapp.com · attn.tv · archive-digger.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
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Saint Augustine
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on murphybeddepot.com, including 15 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.