Website review, no card needed

3dr.com logo

3dr.com website review

Visit site (opens in a new tab)Reviewed 14 November 202633 issues · 78 checks

This review found 33 issues worth fixing on 3dr.com, 8 of them high impact, across 78 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
7.5 s1.5 sMay 23Nov 72.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20264.5 s
May 30, 20264.9 s
Jun 6, 20265.3 s
Jun 13, 20266.2 s
Jun 20, 20266.6 s
Jun 27, 20266.8 s
Jul 4, 20266.7 s
Jul 11, 20266.0 s
Jul 18, 20265.6 s
Jul 25, 20265.3 s
Aug 1, 20264.8 s
Aug 8, 20264.4 s
Aug 15, 20263.9 s
Aug 22, 20263.9 s
Aug 29, 20263.9 s
Sep 5, 20263.4 s
Sep 12, 20263.7 s
Sep 19, 20263.7 s
Sep 26, 20263.4 s
Oct 3, 20263.7 s
Oct 10, 20263.1 s
Oct 17, 20262.2 s
Oct 24, 20262.3 s
Oct 31, 20262.2 s
Nov 7, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
215 ms78 msMay 23Nov 794 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026138 ms
May 30, 2026145 ms
Jun 6, 2026134 ms
Jun 13, 2026173 ms
Jun 20, 2026177 ms
Jun 27, 2026191 ms
Jul 4, 2026199 ms
Jul 11, 2026187 ms
Jul 18, 2026177 ms
Jul 25, 2026179 ms
Aug 1, 2026182 ms
Aug 8, 2026167 ms
Aug 15, 2026148 ms
Aug 22, 2026128 ms
Aug 29, 2026128 ms
Sep 5, 2026151 ms
Sep 12, 2026151 ms
Sep 19, 2026155 ms
Sep 26, 2026140 ms
Oct 3, 2026112 ms
Oct 10, 2026111 ms
Oct 17, 202698 ms
Oct 24, 2026110 ms
Oct 31, 2026102 ms
Nov 7, 202694 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 3dr.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix73
  • Use efficient cache lifetimes

    3.3 s · 1.6 MB

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

  • Mobile performance score: 73

    73/100

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

  • Reduce unused JavaScript

    750 ms · 135 KiB

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

  • Improve image delivery

    650 ms · 124 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Framer CDN, Google Fonts and supabase.co and others), adding 2.5 MB and 510 ms of main-thread time.

  • Framer CDN adds 510 ms

    510 ms

    Framer CDN costs a phone 510 ms of main-thread work and 498 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.1 s

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

  • supabase.co adds 0 ms

    0 ms

    supabase.co costs a phone 0 ms of main-thread work and 1.9 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.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.

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

    41 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 10.9 s

    10.9 s

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

  • Time to Interactive: 10.9 s

    10.9 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 877 ms

    877 ms

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

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

8 checks passed
  • Real-user INP: 105 ms

    105 ms

    Real visitors wait 105 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.

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

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

    -31%

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

  • Largest content (LCP) got 50% faster for real visitors

    -50%

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

  • Cumulative Layout Shift: 0.002

    0.002

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

  • First Contentful Paint: 1.0 s

    1.0 s

    The first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 15 ms

    15 ms

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

Images and page weight

2 to fix75
  • Page weight: 2.6 MB in 58 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 58 requests on a phone: images 2.0 MB (12), scripts 389 KiB (24) and fonts 152 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    124 KiB

    1 image is downloaded at several times the size a phone draws it, for example 3DR_W-t.png at 3,873 px wide, shown at 91 px. Resized copies would save about 124 KiB.

  • 1 image in older formats

    1 image (125 KiB) is 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 0.7 g of CO₂ per visit

    0.75 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.75 g of CO₂e: 89.5 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

6 to fixGoogle 7687
  • Frames without titles

    4 frames have no title, so screen-reader users cannot tell what they contain.

  • 3 text elements with low contrast

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

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

    All page content should be contained by landmarks: 6 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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 23 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 29 WCAG 2.2 A/AA and best-practice rules on the phone render: 23 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9277
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (29 characters)

    Your title is only 29 characters: “3DR || Drone Industry Leaders”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

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

  • 7 internal links, 16 external

    The homepage links to 7 pages on 3dr.com and 16 external pages.

5 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “3DR Inc, is an American company specializing in the design and manufacture of essential electronic systems for unmanned…”.

  • Canonical URL set

    The canonical URL is https://www.3dr.com/.

  • 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://www.3dr.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.3dr.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 (240 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix93
  • 2 pages share a title

    / and https://www.3dr.com/about all use the title “3DR || Drone Industry Leaders”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 internal page checked

    We fetched 1 page linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 1 page 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 1 page 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 1 page that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 13 small tap targets

    13 of 18 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

4 to fix64
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No analytics detected

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

  • Only about 213 words

    The homepage has only about 213 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

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

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us” and “Shop All”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us”, “Shop All” and “Join Discord”.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

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

  • 8 other companies contacted

    Loading the homepage contacts 8 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).

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 3dr.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
Framer
Hosting
Framer

Company

Employees
350
Founded
2009
Headquarters
Berkeley

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on 3dr.com, including 14 speed issues, 4 SEO issues and 4 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