Website review, no card needed

dadco.net logo

dadco.net website review

Visit site (opens in a new tab)Reviewed 22 October 202635 issues · 69 checks

This review found 35 issues worth fixing on dadco.net, 14 of them high impact, across 69 checks. The most urgent: improve image delivery. 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
5.2 s3.3 sMay 2Oct 173.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.5 s
May 9, 20263.6 s
May 16, 20263.7 s
May 23, 20264.1 s
May 30, 20264.2 s
Jun 6, 20264.2 s
Jun 13, 20264.8 s
Jun 20, 20265.0 s
Jun 27, 20264.5 s
Jul 4, 20264.2 s
Jul 11, 20263.8 s
Jul 18, 20263.5 s
Jul 25, 20263.7 s
Aug 1, 20263.9 s
Aug 8, 20264.0 s
Aug 15, 20264.2 s
Aug 22, 20264.0 s
Aug 29, 20263.9 s
Sep 5, 20263.7 s
Sep 12, 20263.6 s
Sep 19, 20263.7 s
Sep 26, 20263.7 s
Oct 3, 20264.1 s
Oct 10, 20264.1 s
Oct 17, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
508 ms67 msMay 2Oct 17196 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026175 ms
May 9, 2026137 ms
May 16, 2026151 ms
May 23, 2026183 ms
May 30, 2026216 ms
Jun 6, 2026245 ms
Jun 13, 2026167 ms
Jun 20, 2026185 ms
Jun 27, 2026146 ms
Jul 4, 2026381 ms
Jul 11, 2026457 ms
Jul 18, 2026381 ms
Jul 25, 2026381 ms
Aug 1, 2026230 ms
Aug 8, 2026135 ms
Aug 15, 2026118 ms
Aug 22, 2026184 ms
Aug 29, 2026160 ms
Sep 5, 2026188 ms
Sep 12, 2026174 ms
Sep 19, 2026125 ms
Sep 26, 2026139 ms
Oct 3, 2026139 ms
Oct 10, 2026131 ms
Oct 17, 2026196 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 dadco.net (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dadco.net at 0.7 s0.7 s
  2. dadco.net at 1.3 s1.3 s
  3. dadco.net at 2.0 s2.0 s
  4. dadco.net at 2.7 s2.7 s
  5. dadco.net at 3.4 s3.4 s
  6. dadco.net at 4.0 s4.0 s
  7. dadco.net at 4.7 s4.7 s
  8. dadco.net at 5.4 s5.4 s

Speed

11 to fix50
  • Improve image delivery

    3.9 s · 962 KiB

    8 images could be 962 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.9 s faster on a phone.

  • Use efficient cache lifetimes

    2.6 s · 862 KiB

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

  • Render-blocking requests

    1.9 s

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

  • Reduce unused JavaScript

    1.2 s · 413 KiB

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

  • amcharts.com adds 1.3 s

    1.3 s

    amcharts.com costs a phone 1.3 s of main-thread work and 380 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 6 third-party services on the page

    6 third-party services load with your homepage (amcharts.com, Google Tag Manager and Usercentrics CMP and others), adding 774 KiB and 1.5 s of main-thread time.

  • Mobile performance score: 50

    50/100

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

  • Reduce unused CSS

    600 ms · 78 KiB

    About 78 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • 6 long tasks on the main thread

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

  • Main-thread work: 3.0 s

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

  • 1,686 HTML elements

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

  • Legacy JavaScript

    200 ms · 40 KiB

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

  • Minify JavaScript

    13 KiB

    13 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: 11 ms

    11 ms

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

Core Web Vitals

11 to fix33
  • 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.42

    0.42

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Real-user TTFB: 2.7 s

    2.7 s

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

  • Largest Contentful Paint: 10.5 s

    10.5 s

    Your largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Image”.

  • Time to Interactive: 14.5 s

    14.5 s

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

  • Speed Index: 7.2 s

    7.2 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Total Blocking Time: 558 ms

    558 ms

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +5%

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

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

    +11%

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

2 checks passed
  • Real-user INP: 176 ms

    176 ms

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

  • Cumulative Layout Shift: 0.024

    0.024

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

Images and page weight

1 to fix50
  • Page weight: 2.8 MB in 70 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 70 requests on a phone: images 1.3 MB (23), scripts 897 KiB (21) and fonts 507 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.80 g

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

Accessibility

3 to fix90
  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (1 element).

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links do not have a discernible name

    Links do not have a discernible name (1 element).

1 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

SEO

3 to fixGoogle 9283
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 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 X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 70 internal links, 6 external

    The homepage links to 70 pages on dadco.net and 6 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Outstanding Quality, Service & Technical Support”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Dadco – Outstanding Quality, Service & Technical Support”.

  • Canonical URL set

    The canonical URL is https://www.dadco.net/.

  • 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://www.dadco.net/wp-sitemap.xml.

AI search readiness

1 to fix83
  • 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://www.dadco.net/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.

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

Other pages

2 to fix88
  • 4 pages share a title

    /, https://www.dadco.net/zh-hans, https://www.dadco.net/de and https://www.dadco.net/ja all use the title “Dadco – Outstanding Quality, Service & Technical Support”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.dadco.net/zh-hans, https://www.dadco.net/de and https://www.dadco.net/ja have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages with very little text

    https://www.dadco.net/zh-hans and https://www.dadco.net/ja have 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 45 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    3 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 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 3 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9288
  • 2 console errors

    2 errors were logged to the browser console during Google's test (“Access to script at 'https://embed.tawk.to/663a562407f59932ab3d0350/1ht9u103n' from origin 'https:/…”).

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • 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 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 302 words of copy

    The homepage carries about 302 words of visible text.

4 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “REQUEST A QUOTE”, “Contact Us” and “Contact Us Menu”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

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 dadco.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics

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 dadco.net, including 22 speed issues, 3 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