Website review, no card needed
hiddendoorkits.com website review
Visit site (opens in a new tab)Reviewed 8 November 202629 issues · 81 checks
This review found 29 issues worth fixing on hiddendoorkits.com, 11 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
83B- #28,214 of 124,214 reviewed websitesbeats 72%
- #18,453 of 69,818 online storesbeats 67%
- #17,866 of 63,496 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 138 ms |
| May 23, 2026 | 145 ms |
| May 30, 2026 | 151 ms |
| Jun 6, 2026 | 156 ms |
| Jun 13, 2026 | 161 ms |
| Jun 20, 2026 | 161 ms |
| Jun 27, 2026 | 161 ms |
| Jul 4, 2026 | 156 ms |
| Jul 11, 2026 | 160 ms |
| Jul 18, 2026 | 163 ms |
| Jul 25, 2026 | 166 ms |
| Aug 1, 2026 | 167 ms |
| Aug 8, 2026 | 168 ms |
| Aug 15, 2026 | 164 ms |
| Aug 22, 2026 | 168 ms |
| Aug 29, 2026 | 171 ms |
| Sep 5, 2026 | 171 ms |
| Sep 12, 2026 | 169 ms |
| Sep 19, 2026 | 162 ms |
| Sep 26, 2026 | 158 ms |
| Oct 3, 2026 | 160 ms |
| Oct 10, 2026 | 162 ms |
| Oct 17, 2026 | 163 ms |
| Oct 24, 2026 | 162 ms |
| Oct 31, 2026 | 159 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
Speed
Render-blocking requests
1.3 s29 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 41
41/100Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 1.8 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 (Google Tag Manager, figpii.com and Klaviyo and others), adding 1.5 MB and 940 ms of main-thread time.
Reduce unused JavaScript
450 ms · 589 KiBAbout 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.
Google Tag Manager adds 342 ms
342 msGoogle Tag Manager costs a phone 342 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.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 324 ms. During a long task the page ignores taps.
2,989 HTML elements
The page has 2,989 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 122 ms
122 msKlaviyo costs a phone 122 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 64 ms
64 msShopify costs a phone 64 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
246 KiB16 files are served with short cache lifetimes, so returning visitors download them again (246 KiB).
Legacy JavaScript
32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
15 KiB15 KiB JavaScript is shipped twice across bundles.
Improve image delivery
6 KiB1 image could be 6 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 18 ms
18 msYour server sent the HTML in 18 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 19.9 s
19.9 sThe page becomes fully interactive after 19.9 s. Good is under 3.8 s.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Cumulative Layout Shift: 0.283
0.283The layout shifts by 0.283 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 650 ms
650 msScripts block taps and scrolling for 650 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.6 s
4.6 sVisually, the page fills in at 4.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe 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).
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.4 s
1.4 sReal 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 msReal 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.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 538 ms
538 msReal visitors wait 538 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).
Images and page weight
Page weight: 6.2 MB in 375 requests
6.2 MBYour homepage downloads 6.2 MB in 375 requests on a phone: media 2.6 MB (1), scripts 1.6 MB (149) and other files 836 KiB (114). 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.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.77 g of CO₂e: 212.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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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
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 hiddendoorkits.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
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
1 linked page is broken
Your homepage links to https://murphydoor.com/customer_authentication/redirect, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without an H1
https://murphydoor.com/collections/best-sellers-collection 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 131 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 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 14 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=27000580&tm=gtm002&Ver=2&mid=f8f545c3-0224-4cc7-bfa0-1d43664eb3d6&bo=1&sid=c3bf2bb0db7611f18a930fb334076b90&vid=c3bf4a00db7611f1ae9e6f6139ea6887&vids=1&msclkid=N&pi=91.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
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
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,111 words of copy
The homepage carries about 1,111 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
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 6 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.
37 cookies set on arrival
37Opening the homepage sets 37 cookies, 3 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.
54 other companies contacted
Loading the homepage contacts 54 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 hiddendoorkits.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on hiddendoorkits.com, including 16 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.