Website review, no card needed

dudum.com logo

dudum.com website review

Visit site (opens in a new tab)Reviewed 18 November 202634 issues · 90 checks

This review found 34 issues worth fixing on dudum.com, 11 of them high impact, across 90 checks. The most urgent: page weight: 47.1 MB in 189 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
3.0 s2.0 sSep 5Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
Sep 5, 20262.3 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.3 s
Oct 3, 20262.5 s
Oct 10, 20262.6 s
Oct 31, 20262.9 s
Nov 7, 20262.5 s
Nov 14, 20262.3 s

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 dudum.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix61
  • Use efficient cache lifetimes

    750 ms · 30.7 MB

    131 files are served with short cache lifetimes, so returning visitors download them again (30.7 MB).

  • Reduce unused JavaScript

    900 ms · 523 KiB

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

  • Mobile performance score: 61

    61/100

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

  • Render-blocking requests

    650 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and luxurypresence.com and others), adding 1.5 MB and 439 ms of main-thread time.

  • 2,704 HTML elements

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

  • 3 long tasks on the main thread

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

  • Main-thread work: 2.3 s

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

  • Google Tag Manager adds 178 ms

    178 ms

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

  • luxurypresence.com adds 73 ms

    73 ms

    luxurypresence.com costs a phone 73 ms of main-thread work and 524 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.

  • Other Google APIs/SDKs adds 62 ms

    62 ms

    Other Google APIs/SDKs costs a phone 62 ms of main-thread work and 344 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.

  • Improve image delivery

    150 ms · 131 KiB

    4 images could be 131 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    50 ms · 42 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Reduce unused CSS

    35 KiB

    About 35 KiB of CSS is downloaded but never applied on this page.

  • Duplicated JavaScript

    26 KiB

    26 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    6 KiB

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 62 ms

    62 ms

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

Core Web Vitals

6 to fix100
  • 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: 13.2 s

    13.2 s

    Your largest element takes 13.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “POWER OF COMMITMENT”.

  • Time to Interactive: 19.6 s

    19.6 s

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

  • Speed Index: 8.5 s

    8.5 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user TTFB: 892 ms

    892 ms

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

6 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 103 ms

    103 ms

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

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

    1.4 s

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

  • Total Blocking Time: 135 ms

    135 ms

    Scripts block the page for only 135 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.011

    0.011

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

Images and page weight

4 to fix25
  • Page weight: 47.1 MB in 189 requests

    47.1 MB

    Your homepage downloads 47.1 MB in 189 requests on a phone: images 45.4 MB (129), scripts 1.4 MB (29) and HTML 146 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 40 images far larger than shown

    20.7 MB

    40 images are downloaded at several times the size a phone draws them, for example -4296494589925829139.jpg at 3,072 px wide, shown at 288 px. Resized copies would save about 20.7 MB.

  • 25 images over 500 KB

    25 images weigh 19.0 MB together. On a phone connection a single image that size takes seconds.

  • 40 images in older formats

    40 images (24.6 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.

  • About 13.4 g of CO₂ per visit

    13.36 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

5 to fixGoogle 9293
  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • All page content should be contained by landmarks (27 elements)

    All page content should be contained by landmarks: 27 elements on the page fail this check, rated moderate by axe-core.

  • 7 form fields without a label

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

  • 5 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 104 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 42 links with vague text

    42 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 153 internal links, 14 external

    The homepage links to 153 pages on dudum.com and 14 external pages.

8 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Discover Dudum Real Estate Group, your East Bay experts in buying, selling, and renting homes. Explore listings and con…”.

  • One H1 headline

    Your main headline reads: “Power of Commitment”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Dudum Real Estate Group | East Bay CA Homes & Agents”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: RealEstateAgent.

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

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    41%

    The HTML your server sends has 2,289 of the 5,525 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

3 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: 5 of 6 facts

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

  • llms.txt published

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

Other pages

100
  • 1 page with very little text

    https://dudum.com/home-search/listings 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.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 9687
  • 2 small tap targets

    2 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix80
  • 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.

  • Thin social proof

    Social proof on the homepage: 25 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 9-field form

    Your longest form asks for 9 fields (6 required). Every extra field lowers completion.

  • No map or directions link

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

  • About 5,525 words of copy

    The homepage carries about 5,525 words of visible text.

7 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Buy Your Home”, “Join Us” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Umami and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 7 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (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.

  • 24 other companies contacted

    Loading the homepage contacts 24 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 dudum.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
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on dudum.com, including 17 speed issues, 1 SEO issue and 3 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