Programmable

Website review, no card needed

dubo.com logo

dubo.com website review

Visit site (opens in a new tab)Reviewed 23 October 202628 issues · 97 checks

This review found 28 issues worth fixing on dubo.com, 6 of them high impact, across 97 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Site score

81B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
3.2 s1.5 sMay 2Oct 172.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.7 s
May 9, 20262.0 s
May 16, 20262.4 s
May 23, 20262.8 s
May 30, 20263.0 s
Jun 6, 20262.8 s
Jun 13, 20262.6 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.7 s
Jul 11, 20262.6 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.6 s
Aug 29, 20262.5 s
Sep 5, 20262.3 s
Sep 12, 20262.5 s
Sep 19, 20262.7 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.7 s
Oct 17, 20262.6 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

www.dubo.com (opens in a new tab)
Live view · interaction off

Speed

5 to fix76

  • Mobile performance score: 76

    76/100

    Your mobile performance score is 76 (desktop: 98). Pages that score under 90 lose visitors before the first paint.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Maps, Other Google APIs/SDKs and sanity.io and others), adding 1.4 MB and 814 ms of main-thread time.

  • Google Maps adds 811 ms

    811 ms

    Google Maps costs a phone 811 ms of main-thread work and 1.3 MB 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.

  • Reduce unused JavaScript

    855 KiB

    About 855 KiB of JavaScript is downloaded but never used on this page.

  • Main-thread work: 3.6 s

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

  • Improve image delivery

    250 ms · 44 KiB

    1 image could be 44 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • 11 long tasks on the main thread

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

  • Use efficient cache lifetimes

    106 KiB

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

  • Legacy JavaScript

    31 KiB

    Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need.

  • Duplicated JavaScript

    15 KiB

    15 KiB JavaScript is shipped twice across bundles.

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

    225 ms

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

Core Web Vitals

8 to fix50

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

  • Time to Interactive: 15.2 s

    15.2 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Largest content (LCP) got 44% slower for real visitors

    +44%

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

  • Largest Contentful Paint: 3.9 s

    3.9 s

    Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Big Results Fair Fees Your Trusted Lawyers Since 1972 Book …”.

  • Total Blocking Time: 352 ms

    352 ms

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Speed Index: 3.9 s

    3.9 s

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

3 checks passed

  • Real-user CLS: 0.05

    0.05

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70

  • Page weight: 6.3 MB in 115 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 115 requests on a phone: other files 2.0 MB (11), media 2.0 MB (1) and scripts 1.8 MB (63). Under 2 MB keeps phones on slow connections fast.

  • About 1.8 g of CO₂ per visit

    1.78 g

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

3 checks passed

  • 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 to fixGoogle 8392

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 15 text elements with low contrast

    15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 4 form fields without a label

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

  • 3 links without text

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

  • Headings skip levels

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

2 checks passed

  • Every image has alt text

    All 44 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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

4 to fixGoogle 10083

  • Canonical points to another host

    Your canonical URL points to dubo-website-p4yr1ypuq-rklar3s-projects.vercel.app, not dubo.com, so Google may credit that host instead.

  • Meta description is long (177 characters)

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

  • Structured data has 1 problem

    Structured data found (LegalService, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://dubo-website-p4yr1ypuq-rklar3s-projects.verce…”.

  • No XML sitemap

    No XML sitemap at https://dubo-website-p4yr1ypuq-rklar3s-projects.vercel.app/sitemap.xml, so Google discovers your pages only by following links.

  • 38 internal links, 24 external

    The homepage links to 38 pages on dubo.com and 24 external pages.

4 checks passed

  • One H1 headline

    Your main headline reads: “Big ResultsFair Fees”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “DuMoulin Boskovich LLP Lawyers | Your Trusted Lawyers Since 1972”.

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

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

  • llms.txt published

    The site publishes /llms.txt (1 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90

  • 5 pages share a title

    /, /payments, /about, /knowledge and /team all use the title “DuMoulin Boskovich LLP Lawyers | Your Trusted Lawyers Since 1972”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    /payments, /about, /knowledge and /team use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

6 checks passed

  • Linked pages load

    All 15 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 15 pages that loaded have a meta description.

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

    20 of 23 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

1 to fix93

  • No Content-Security-Policy

    No Content-Security-Policy header, the main browser-side defence against injected scripts.

  • No clickjacking protection

    Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

  • No X-Content-Type-Options

    X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

6 checks passed

  • Served over HTTPS

    The homepage is served over HTTPS (dubo.com).

  • Valid certificate (40 days left)

    The certificate from Let's Encrypt · YR2 verifies for dubo.com and is valid for another 40 days.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • http:// redirects to https

    http://dubo.com redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

  • All 42 links work

    All 42 links checked from your homepage (22 internal, 20 external) answered without errors; 1 did not answer within 5 s.

Domain and trust

  • DNSSEC is off

    dubo.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

3 checks passed

  • Domain is 29 years old

    29 years

    dubo.com was registered in Apr 1997 through Webnames.ca Inc.. An established domain carries more trust with email providers and search engines.

  • Certificate issuers are restricted

    CAA records allow only sectigo.com, globalsign.com, letsencrypt.org and pki.goog to issue certificates for dubo.com, so a mis-issued certificate from anyone else is refused.

  • Registered until Apr 2029

    dubo.com is registered until Apr 2029.

Content and conversion

1 to fix94

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 1,117 words of visible text.

8 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book Free Consultation”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”, “Book Consultation” and “Book Free Consultation”.

  • 1 short form

    A short form (5 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, a star rating, 1 trust badge and “over 500 clients”.

  • Direct contact links

    Visitors can reach you directly: 8 phone links and 7 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.

Email authentication

90

  • Email authentication score: 90/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed

  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:spf.protection.outlook.com include:_spf.stargate.ca -all”.

  • DKIM signing found

    A DKIM key is published (selector “selector1”), so receivers can verify mail really came from you.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 6 other companies contacted

    Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

Framework
Next.js
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on dubo.com, including 13 speed issues, 4 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