Website review, no card needed

cdainteriors.com logo

cdainteriors.com website review

Visit site (opens in a new tab)Reviewed 22 October 202623 issues · 74 checks

This review found 23 issues worth fixing on cdainteriors.com, 6 of them high impact, across 74 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

Full-page screenshot of cdainteriors.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix66
  • Reduce unused JavaScript

    1.2 s · 195 KiB

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

  • Render-blocking requests

    1.2 s

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

  • Improve image delivery

    750 ms · 907 KiB

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

  • Mobile performance score: 66

    66/100

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

  • Use efficient cache lifetimes

    600 ms · 183 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, YouTube and Fathom Analytics and others), adding 1.5 MB and 242 ms of main-thread time.

  • Google Tag Manager adds 233 ms

    233 ms

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

  • digitaloceanspaces.com adds 0 ms

    0 ms

    digitaloceanspaces.com costs a phone 0 ms of main-thread work and 1.1 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.

  • 3 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 98 but mobile only 66. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 227 ms of it running JavaScript. That is comfortably low.

  • Server response: 15 ms

    15 ms

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 8.1 s

    8.1 s

    Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “CD Website Landscape Landing page”.

  • Time to Interactive: 8.1 s

    8.1 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • 3 images without width and height

    3 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: 116 ms

    116 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix90
  • 1 image far larger than shown

    92 KiB

    1 image is downloaded at several times the size a phone draws it, for example Hermiston.png at 426 px wide, shown at 69 px. Resized copies would save about 92 KiB.

  • 6 images in older formats

    6 images (386 KiB) 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 below the first screen load straight away

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

  • About 0.5 g of CO₂ per visit

    0.47 g

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

1 checks passed
  • Page weight: 1.7 MB in 38 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 38 requests on a phone: images 1.1 MB (14), scripts 453 KiB (9) and fonts 90 KiB (3). That is a lean page.

Accessibility

3 to fixGoogle 8895
  • 8 buttons without a name

    8 buttons have no accessible name, so screen readers announce just “button”.

  • 7 tap targets too small

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 4 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10093
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Contract Design | Total Workplace Solutions for the Inland NW and…”.

  • 79 internal links, 12 external

    The homepage links to 79 pages on cdainteriors.com and 12 external pages.

7 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Providing modern workplace solutions with furnishings, professional planning, design, installation and project manageme…”.

  • One H1 headline

    Your main headline reads: “Contract Design”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, LocalBusiness and WebSite.

  • 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://cdcollective.com/sitemaps-1-sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://cdcollective.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.

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

Other pages

2 to fix90
  • 4 pages share a title

    /, https://cdcollective.com/products, https://cdcollective.com/markets and https://cdcollective.com/projects all use the title “Contract Design | Total Workplace Solutions for the Inland NW and…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages share a meta description

    https://cdcollective.com/products, https://cdcollective.com/markets and https://cdcollective.com/projects 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 49 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 10093
  • 5 small tap targets

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

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

1 to fix94
  • Thin social proof

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

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

    The homepage carries about 872 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: “Contact”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact” and “Join Our Team”.

  • 2 short forms

    2 short forms (7 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Fathom and Umami.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

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

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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 11 other companies contacted

    Loading the homepage contacts 11 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 cdainteriors.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager | Fathom

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on cdainteriors.com, including 13 speed issues, 1 SEO issue 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