Website review, no card needed

murphydoor.com logo

murphydoor.com website review

Visit site (opens in a new tab)Reviewed 7 November 202628 issues · 81 checks

This review found 28 issues worth fixing on murphydoor.com, 6 of them high impact, across 81 checks. The most urgent: render-blocking 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
1.5 s1.2 sMay 16Oct 311.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Oct 31, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
176 ms133 msMay 16Oct 31159 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026138 ms
May 23, 2026145 ms
May 30, 2026151 ms
Jun 6, 2026156 ms
Jun 13, 2026161 ms
Jun 20, 2026161 ms
Jun 27, 2026161 ms
Jul 4, 2026156 ms
Jul 11, 2026160 ms
Jul 18, 2026163 ms
Jul 25, 2026166 ms
Aug 1, 2026167 ms
Aug 8, 2026168 ms
Aug 15, 2026164 ms
Aug 22, 2026168 ms
Aug 29, 2026171 ms
Sep 5, 2026171 ms
Sep 12, 2026169 ms
Sep 19, 2026162 ms
Sep 26, 2026158 ms
Oct 3, 2026160 ms
Oct 10, 2026162 ms
Oct 17, 2026163 ms
Oct 24, 2026162 ms
Oct 31, 2026159 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 murphydoor.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix68
  • Render-blocking requests

    1.3 s

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

  • Reduce unused JavaScript

    450 ms · 589 KiB

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

  • Mobile performance score: 68

    68/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, figpii.com and Klaviyo and others), adding 1.5 MB and 702 ms of main-thread time.

  • Main-thread work: 3.8 s

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

  • 2,989 HTML elements

    The page has 2,989 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Google Tag Manager adds 253 ms

    253 ms

    Google Tag Manager costs a phone 253 ms of main-thread work and 350 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 108 ms

    108 ms

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

  • Shopify adds 47 ms

    47 ms

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

  • Use efficient cache lifetimes

    247 KiB

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

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    32 KiB

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

  • Duplicated JavaScript

    15 KiB

    15 KiB JavaScript is shipped twice across bundles.

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

  • Improve image delivery

    4 KiB

    1 image could be 4 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

1 checks passed
  • Server response: 19 ms

    19 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 19.6 s

    19.6 s

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

  • Largest Contentful Paint: 5.3 s

    5.3 s

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

  • Total Blocking Time: 358 ms

    358 ms

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

  • Speed Index: 4.4 s

    4.4 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Tap response (INP) got 13% slower for real visitors

    +13%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 138 ms to 159 ms 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.4 s

    1.4 s

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

  • Real-user INP: 128 ms

    128 ms

    Real visitors wait 128 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.3 s

    1.3 s

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

  • Real-user TTFB: 547 ms

    547 ms

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

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

    -11%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix64
  • Page weight: 6.2 MB in 356 requests

    6.2 MB

    Your homepage downloads 6.2 MB in 356 requests on a phone: media 2.6 MB (1), scripts 1.6 MB (149) and other files 788 KiB (95). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Bookcase_Tennessee_Open_Model_2000x2000_bd982035-52da-4de2-b 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 in older formats

    3 images (208 KiB) are 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 1.8 g of CO₂ per visit

    1.75 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

2 to fixGoogle 9797
  • 26 text elements with low contrast

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

  • 13 links without text

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

2 checks passed
  • Every image has alt text

    All 160 images in the HTML carry an alt attribute.

  • 52 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: 52 passed and 1 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10095
  • Meta description is long (178 characters)

    Your meta description is 178 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 324 internal links, 39 external

    The homepage links to 324 pages on murphydoor.com and 39 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “The Original Hidden Door”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Hidden Doors - Hidden Bookcase Doors – Murphy Door®”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: FAQPage, ItemList, Organization, VideoObject and WebPage.

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

AI search readiness

1 to fix83
  • Parts of the site are closed to 4 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed
  • Organization data: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://murphydoor.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://murphydoor.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://murphydoor.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://murphydoor.com/customer_authentication/redirect and https://murphydoor.com/collections/best-sellers-collection have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://murphydoor.com/collections/hidden-french-doors, https://murphydoor.com/collections/home-organizer-doors and https://murphydoor.com/collections/drink-and-beverage-doors took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    50 of 57 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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 analytics detected

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Call Murphy Door at 888-458-5911” and “Shop Hidden Doors”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Shop By Room”, “Contact Us” and “Shop Hidden Doors”.

  • 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: 313 testimonial or review blocks, 2 customer or partner logos, a star rating and 4 trust badges.

  • Direct contact links

    Visitors can reach you directly: 6 phone links and 4 email links.

  • Phone number on the homepage

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

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, Klaviyo and Meta Pixel 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.

  • 33 cookies set on arrival

    33

    Opening the homepage sets 33 cookies, 2 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.

  • 35 other companies contacted

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

Apps your storefront loads

Figpii Ab Testing Replays · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · Judge Me Reviews · Murphy Door Super App · Pluralcart · Apo Product Options · activatedapps.com · getmulberry.com · amazonaws.com · hubapi.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

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Hiring

Hiring
6 open roles
Job board
careers page

Company

Founded
2012
Headquarters
Ogden

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on murphydoor.com, including 14 speed issues, 1 SEO issue 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