Website review, no card needed

detect-inc.com logo

detect-inc.com website review

Visit site (opens in a new tab)Reviewed 18 October 202640 issues · 84 checks

This review found 40 issues worth fixing on detect-inc.com, 18 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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.9 s4.5 sApr 25Oct 105.7 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20264.8 s
May 2, 20264.7 s
May 9, 20264.9 s
May 16, 20265.0 s
May 23, 20264.8 s
May 30, 20265.1 s
Jun 6, 20265.2 s
Jun 13, 20265.3 s
Jun 20, 20265.2 s
Jun 27, 20265.1 s
Jul 4, 20264.9 s
Jul 11, 20265.1 s
Jul 18, 20265.1 s
Jul 25, 20265.1 s
Aug 1, 20265.8 s
Aug 8, 20265.0 s
Aug 15, 20265.0 s
Aug 22, 20265.0 s
Aug 29, 20264.8 s
Sep 5, 20265.4 s
Sep 12, 20265.5 s
Sep 19, 20265.5 s
Sep 26, 20265.6 s
Oct 3, 20265.7 s
Oct 10, 20265.7 s
Real-visitor tap response (INP)75th percentile, phones
156 ms94 msApr 25Oct 10105 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026149 ms
May 2, 2026134 ms
May 9, 2026127 ms
May 16, 2026123 ms
May 23, 2026119 ms
May 30, 2026123 ms
Jun 6, 2026108 ms
Jun 13, 2026113 ms
Jun 20, 2026118 ms
Jun 27, 2026145 ms
Jul 4, 2026109 ms
Jul 11, 2026105 ms
Jul 18, 2026106 ms
Jul 25, 2026101 ms
Aug 1, 2026105 ms
Aug 8, 2026108 ms
Aug 15, 2026107 ms
Aug 22, 2026108 ms
Aug 29, 2026106 ms
Sep 5, 2026105 ms
Sep 12, 2026119 ms
Sep 19, 2026120 ms
Sep 26, 2026119 ms
Oct 3, 2026116 ms
Oct 10, 2026105 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 detect-inc.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. detect-inc.com at 1.4 s1.4 s
  2. detect-inc.com at 2.8 s2.8 s
  3. detect-inc.com at 4.1 s4.1 s
  4. detect-inc.com at 5.5 s5.5 s
  5. detect-inc.com at 6.9 s6.9 s
  6. detect-inc.com at 8.3 s8.3 s
  7. detect-inc.com at 9.7 s9.7 s
  8. detect-inc.com at 11.0 s11.0 s

Speed

9 to fix42
  • Use efficient cache lifetimes

    2.1 s · 5.5 MB

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

  • Reduce unused JavaScript

    5.0 s · 561 KiB

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

  • Render-blocking requests

    3.0 s

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

  • Mobile performance score: 42

    42/100

    Your mobile performance score is 42 (desktop: 77). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google CDN, Google Tag Manager and cdn-cookieyes.com and others), adding 1.1 MB and 585 ms of main-thread time.

  • Google CDN adds 288 ms

    288 ms

    Google CDN costs a phone 288 ms of main-thread work and 739 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.

  • Google Tag Manager adds 229 ms

    229 ms

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

  • Main-thread work: 2.3 s

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

  • 1,983 HTML elements

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

  • Reduce unused CSS

    150 ms · 33 KiB

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

  • 6 long tasks on the main thread

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

  • Improve image delivery

    20 KiB

    1 image could be 20 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Phones get a much slower page than desktops

    Desktop scores 77 but mobile only 42. 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.

1 checks passed
  • Server response: 200 ms

    200 ms

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

Core Web Vitals

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

  • Real-user LCP: 5.6 s

    5.6 s

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

  • Real-user FCP: 4.6 s

    4.6 s

    Real visitors see the first content after 4.6 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: 14.3 s

    14.3 s

    Your largest element takes 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DeTect, Inc specializes in advanced 2D and True3D® radar an…”. Most of its time is element render delay (11.1 s).

  • Speed Index: 13.4 s

    13.4 s

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

  • Time to Interactive: 15.1 s

    15.1 s

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

  • Cumulative Layout Shift: 0.379

    0.379

    The layout shifts by 0.379 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

    +20%

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

  • 28 images without width and height

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

4 checks passed
  • Real-user INP: 93 ms

    93 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Tap response (INP) got 22% faster for real visitors

    -22%

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

  • Total Blocking Time: 74 ms

    74 ms

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

Images and page weight

1 to fix70
  • Page weight: 7.0 MB in 142 requests

    7.0 MB

    Your homepage downloads 7.0 MB in 142 requests on a phone: media 4.6 MB (1), scripts 1.3 MB (39) and images 376 KiB (37). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (24 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.0 g of CO₂ per visit

    1.99 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 8890
  • [role="img"] and [role="image"] elements must have alternative text (7 elements)

    [role="img"] and [role="image"] elements must have alternative text: 7 elements on the page fail this check, rated serious by axe-core.

  • 6 text elements with low contrast

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

  • 3 tap targets too small

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 2 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor 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 33 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 4 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
  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 147 internal links, 14 external

    The homepage links to 147 pages on detect-inc.com and 14 external pages.

8 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “DeTect designs bird and drone detection radar systems with True3D™ technology for aviation safety, wind energy and secu…”.

  • One H1 headline

    Your main headline reads: “DeTect® Bird and Drone Detection Radar Technologies”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Bird and Drone Detection Radar Systems | DeTect, Inc.”.

  • Canonical URL set

    The canonical URL is https://detect-inc.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://detect-inc.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,420 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix76
  • 2 pages share a title

    https://detect-inc.com/aircraft-detection-lighting-systems and https://detect-inc.com/aircraft-detection-lighting-system all use the title “Aircraft Detection Lighting System (ADLS) | DeTect”. 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://detect-inc.com/events has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://detect-inc.com/aircraft-detection-lighting-systems and https://detect-inc.com/aircraft-detection-lighting-system use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://detect-inc.com/beyond-line-of-sight-bvlos, whose canonical is https://detect-inc.com/beyond-line-of-sight-bvlos-old. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://detect-inc.com/contact has 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 20 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

2 to fixGoogle 9687
  • 4 small tap targets

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

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 932 words of copy

    The homepage carries about 932 words of visible text.

4 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact DeTect”, “Contact” and “Contact us”.

  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: 22 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

  • 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). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 9 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 detect-inc.com, 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 | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on detect-inc.com, including 20 speed issues, 1 SEO issue and 2 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