Website review, no card needed

cam-do.com logo

cam-do.com website review

Visit site (opens in a new tab)Reviewed 9 November 202637 issues · 85 checks

This review found 37 issues worth fixing on cam-do.com, 11 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. 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
2.7 s2.1 sMay 23Nov 72.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.4 s
May 30, 20262.5 s
Jun 6, 20262.4 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.4 s
Jul 4, 20262.5 s
Jul 11, 20262.4 s
Jul 18, 20262.2 s
Jul 25, 20262.4 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.3 s
Oct 24, 20262.2 s
Oct 31, 20262.3 s
Nov 7, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
322 ms195 msMay 23Nov 7272 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026217 ms
May 30, 2026217 ms
Jun 6, 2026222 ms
Jun 13, 2026228 ms
Jun 20, 2026228 ms
Jun 27, 2026226 ms
Jul 4, 2026217 ms
Jul 11, 2026212 ms
Jul 18, 2026210 ms
Jul 25, 2026214 ms
Aug 1, 2026217 ms
Aug 8, 2026241 ms
Aug 15, 2026230 ms
Aug 22, 2026230 ms
Aug 29, 2026237 ms
Sep 5, 2026230 ms
Sep 12, 2026247 ms
Sep 19, 2026257 ms
Sep 26, 2026262 ms
Oct 3, 2026284 ms
Oct 10, 2026284 ms
Oct 17, 2026284 ms
Oct 24, 2026307 ms
Oct 31, 2026269 ms
Nov 7, 2026272 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 cam-do.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix53
  • Reduce unused JavaScript

    2.4 s · 634 KiB

    About 634 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Use efficient cache lifetimes

    1.2 s · 455 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.4 MB and 1.3 s of main-thread time.

  • Mobile performance score: 53

    53/100

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

  • Google Tag Manager adds 785 ms

    785 ms

    Google Tag Manager costs a phone 785 ms of main-thread work and 847 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.

  • Render-blocking requests

    450 ms

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Main-thread work: 3.4 s

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

  • 13 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 26 KiB

    Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 23 KiB

    About 23 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.

  • Improve image delivery

    98 KiB

    3 images could be 98 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

  • 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: 5 ms

    5 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Largest Contentful Paint: 17.8 s

    17.8 s

    Your largest element takes 17.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AI-Powered Construction Time Lapse & Jobsite Monitoring ✓ P…”.

  • Time to Interactive: 21.2 s

    21.2 s

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

  • Speed Index: 5.9 s

    5.9 s

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

  • Real-user INP: 272 ms

    272 ms

    Real visitors wait 272 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

    +25%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 217 ms to 272 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 584 ms

    584 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 16 images without width and height

    16 images have no width and height attributes, so the layout jumps as each one loads.

6 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 554 ms

    554 ms

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

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

    -10%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.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

3 to fix60
  • 1 image over 500 KB

    stride-logo.svg weighs 733 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.9 MB in 214 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 214 requests on a phone: scripts 1.6 MB (67), images 1.4 MB (34) and other files 750 KiB (102). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    118 KiB

    1 image is downloaded at several times the size a phone draws it, for example stride_instagram-photo.jpg at 2,794 px wide, shown at 374 px. Resized copies would save about 118 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (283 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (142 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 1.1 g of CO₂ per visit

    1.11 g

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

Accessibility

4 to fixGoogle 8394
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 20 images without alt text

    20 images have no alt text, which hurts accessibility and image search.

  • 4 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

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

SEO

5 to fixGoogle 7780
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Explore Cam-Do | Innovative Time-Lapse Solutions for Every Industry”.

  • Meta description is long (166 characters)

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

  • Structured data has 5 problems

    Structured data found (BreadcrumbList, Organization, Service and Store) but with 5 problems, for example “WebSite: potentialAction.target is not an absolute URL ("https://cam-do.com/search?q={search_term_string}")”.

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

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • 47 internal links, 15 external

    The homepage links to 47 pages on cam-do.com and 15 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “AI-Powered Construction Time Lapse & Jobsite Monitoring”.

  • Canonical URL set

    The canonical URL is https://cam-do.com/.

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

AI search readiness

100
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 (703 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://cam-do.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

6 to fix52
  • 1 linked page is broken

    Your homepage links to https://cam-do.com/pages/contech-finder, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages share a title

    https://cam-do.com/pages/cloudx-time-lapse-platform and https://cam-do.com/pages/stride-cloudx-pillar all use the title “Explore Our CloudX Time-Lapse Platform | Cam-Do”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://cam-do.com/pages/securelens-announcement has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://cam-do.com/pages/cloudx-time-lapse-platform and https://cam-do.com/pages/stride-cloudx-pillar use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://cam-do.com/pages/stride-cloudx-pillar, whose canonical is https://cam-do.com/pages/cloudx-time-lapse-platform. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://cam-do.com/pages/resources and https://cam-do.com/pages/securelens-announcement have 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 25 found) and read each the way a search engine does.

2 checks passed
  • 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 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: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    7 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix86
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 568 words of visible text.

6 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Get Quote”, “Learn More” and “Book a Demo”.

  • 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: 6 testimonial or review blocks, 2 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 cookies, 6 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: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 cam-do.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 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Gorgias Live Chat Helpdesk · Seo Manager Venntov · elfsight.com · orderlogicapp.com · hubapi.com · 9gtb.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
Hosting
Shopify

Company

Headquarters
Vancouver

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on cam-do.com, including 17 speed issues, 5 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

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