Website review, no card needed
mydoorbell.app website review
Visit site (opens in a new tab)Reviewed 7 November 202629 issues · 77 checks
This review found 29 issues worth fixing on mydoorbell.app, 9 of them high impact, across 77 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
77CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
3.6 s · 839 KiBAbout 839 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Use efficient cache lifetimes
2.4 s · 762 KiB19 files are served with short cache lifetimes, so returning visitors download them again (762 KiB).
Render-blocking requests
1.9 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
5 third-party services on the page
5 third-party services load with your homepage (YouTube, Stripe and Other Google APIs/SDKs and others), adding 1.3 MB and 847 ms of main-thread time.
Reduce unused CSS
730 ms · 173 KiBAbout 173 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 730 ms faster on a phone.
YouTube adds 599 ms
599 msYouTube costs a phone 599 ms of main-thread work and 979 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.
Stripe adds 237 ms
237 msStripe costs a phone 237 ms of main-thread work and 300 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.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
242 KiB7 images could be 242 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 186 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 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: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 8.2 s
8.2 sThe first text or image appears after 8.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 8.2 s
8.2 sYour largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “You only need a connection between your smart Doorbird door…”.
Time to Interactive: 11.8 s
11.8 sThe page becomes fully interactive after 11.8 s. Good is under 3.8 s.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 118 ms
118 msScripts block the page for only 118 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.5 g of CO₂ per visit
0.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.52 g of CO₂e: 63.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.9 MB in 42 requests
1.9 MBYour homepage downloads 1.9 MB in 42 requests on a phone: scripts 1.3 MB (9), images 294 KiB (15) and stylesheets 128 KiB (4). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 19 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (22 characters)
Your title is only 22 characters: “Home Page | mydoorbell”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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.
32 internal links, 8 external
The homepage links to 32 pages on mydoorbell.app and 8 external pages.
6 checks passed
Meta description: 121 characters
Your meta description is 121 characters: “Yes, it is possible. You only need a connection between your smart Doorbird doorbell and your Alexa. Here is your chanc…”.
One H1 headline
Your main headline reads: “Alexa as a Doorbell?”.
Canonical URL set
The canonical URL is https://mydoorbell.app/.
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.
XML sitemap found
Your XML sitemap is reachable at https://mydoorbell.app/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://mydoorbell.app/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 (459 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without an H1
https://mydoorbell.app/how-to-get-code, https://mydoorbell.app/ourvision and https://mydoorbell.app/terms-of-service have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://mydoorbell.app/about-us has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 9 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 9 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 9 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
11 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 608 words of copy
The homepage carries about 608 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more”.
8 calls to action
The homepage has 8 calls to action, for example “Sign up”, “Pricing” and “Learn more”.
Social proof on the page
Social proof on the homepage: 18 testimonial or review blocks and 1 customer or partner logo.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Ads (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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies, 1 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.
13 other companies contacted
Loading the homepage contacts 13 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 mydoorbell.app, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- GitHub Pages
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 mydoorbell.app, including 14 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.