Website review, no card needed
zmodo.com website review
Visit site (opens in a new tab)Reviewed 19 October 202635 issues · 75 checks
This review found 35 issues worth fixing on zmodo.com, 9 of them high impact, across 75 checks. The most urgent: fails Core Web Vitals for real visitors. 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
72CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.5 s |
| May 9, 2026 | 1.4 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 74 ms |
| May 9, 2026 | 74 ms |
| Aug 15, 2026 | 77 ms |
| Aug 22, 2026 | 77 ms |
| Aug 29, 2026 | 77 ms |
| Oct 10, 2026 | 103 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
Mobile performance score: 59
59/100Your mobile performance score is 59 (desktop: 72). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
632 KiB9 images could be 632 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
150 ms · 26 KiBAbout 26 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
100 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 203 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user CLS: 0.80
0.80For real visitors the layout shifts by 0.80 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.806
0.806The layout shifts by 0.806 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 4.7 s
4.7 sYour largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 74 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 4.9 s
4.9 sThe page becomes fully interactive after 4.9 s. Good is under 3.8 s.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 96 ms
96 msReal visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 459 ms
459 msReal visitors wait 459 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 2.3 s
2.3 sVisually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 0.8 s
0.8 sThe first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 8 ms
8 msScripts block the page for only 8 ms while loading. Good is under 200 ms.
Images and page weight
10 images in older formats
10 images (1.4 MB) 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.
3 images far larger than shown
319 KiB3 images are downloaded at several times the size a phone draws them, for example 1001H.jpg at 1,348 px wide, shown at 390 px. Resized copies would save about 319 KiB.
About 0.5 g of CO₂ per visit
0.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.46 g of CO₂e: 55.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.6 MB in 60 requests
1.6 MBYour homepage downloads 1.6 MB in 60 requests on a phone: images 1.4 MB (26), scripts 199 KiB (11) and other files 21 KiB (19). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
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.
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.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (73 characters)
Your title is 73 characters, so Google will cut it off around 60: “Zmodo - A Global Provider of Security Camera Systems & Smart Home Devices”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://zmodo.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at zmodo.com/robots.txt, the first file search crawlers ask for.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
37 internal links, 19 external
The homepage links to 37 pages on zmodo.com and 19 external pages.
1 checks passed
Meta description: 130 characters
Your meta description is 130 characters: “Zmodo offers smart home security cameras, video doorbells, and smart home devices. Shop indoor cameras, outdoor cameras…”.
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://zmodo.com/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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (167 words), so crawlers that don't run JavaScript still read it.
Other pages
3 linked pages are broken
Your homepage links to https://zmodo.com/1080p-outdoor-wifi-camera, https://zmodo.com/google-assistant and https://zmodo.com/amazon-alexa, which answer with an error. Visitors hit a dead end and search engines drop them.
11 pages share a title
/, https://zmodo.com/store, https://zmodo.com/cloud, https://zmodo.com/rma, https://zmodo.com/1080p-indoor-wifi-camera and https://zmodo.com/reviewers-program and 5 others all use the title “Zmodo - A Global Provider of Security Camera Systems & Smart Home Dev…”. Search engines can't tell which page to show for a search, so each competes with the others.
10 pages share a meta description
https://zmodo.com/store, https://zmodo.com/cloud, https://zmodo.com/rma, https://zmodo.com/1080p-indoor-wifi-camera, https://zmodo.com/reviewers-program and https://zmodo.com/about and 4 others use the same meta description. A description written for each page earns more clicks.
7 pages without an H1
https://zmodo.com/store, https://zmodo.com/cloud, https://zmodo.com/rma, https://zmodo.com/reviewers-program, https://zmodo.com/legal and https://zmodo.com/privacy-policy and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://zmodo.com/contact 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.
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
4 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 11 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
19 small tap targets
19 of 38 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
7 distorted images
7 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 183 words
The homepage has only about 183 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More”.
4 calls to action
The homepage has 4 calls to action, for example “Learn More” and “Contact”.
Privacy and tracking
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 zmodo.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
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 zmodo.com, including 9 speed issues, 8 SEO issues and 4 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.