Website review, no card needed

earldudley.com logo

earldudley.com website review

Visit site (opens in a new tab)Reviewed 21 November 202639 issues · 77 checks

This review found 39 issues worth fixing on earldudley.com, 16 of them high impact, across 77 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 earldudley.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. earldudley.com at 0.6 s0.6 s
  2. earldudley.com at 1.2 s1.2 s
  3. earldudley.com at 1.8 s1.8 s
  4. earldudley.com at 2.3 s2.3 s
  5. earldudley.com at 2.9 s2.9 s
  6. earldudley.com at 3.5 s3.5 s
  7. earldudley.com at 4.1 s4.1 s
  8. earldudley.com at 4.7 s4.7 s

Speed

8 to fix26
  • Reduce unused JavaScript

    6.1 s · 1.2 MB

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

  • YouTube adds 1.7 s

    1.7 s

    YouTube costs a phone 1.7 s of main-thread work and 2.0 MB 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.

  • Mobile performance score: 26

    26/100

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

  • Main-thread work: 5.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, LiveChat and IPONWEB and others), adding 2.5 MB and 2.1 s of main-thread time.

  • Reduce unused CSS

    450 ms · 112 KiB

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

  • 16 long tasks on the main thread

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

  • LiveChat adds 162 ms

    162 ms

    LiveChat costs a phone 162 ms of main-thread work and 363 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.

  • Improve image delivery

    239 KiB

    15 images could be 239 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    76 KiB

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

  • Legacy JavaScript

    33 KiB

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

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

    7 ms

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

Core Web Vitals

7 to fix31
  • First Contentful Paint: 11.8 s

    11.8 s

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

  • Largest Contentful Paint: 11.8 s

    11.8 s

    Your largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Take Flight with Earl Dudley”.

  • Time to Interactive: 23.1 s

    23.1 s

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

  • Speed Index: 11.8 s

    11.8 s

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

  • Cumulative Layout Shift: 0.266

    0.266

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

  • Total Blocking Time: 647 ms

    647 ms

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

  • 7 images without width and height

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

Images and page weight

2 to fix75
  • Page weight: 3.9 MB in 168 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 168 requests on a phone: scripts 2.4 MB (64), other files 625 KiB (69) and images 480 KiB (22). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    20 KiB

    1 image is downloaded at several times the size a phone draws it, for example Capture_600x600_crop_top.jpg at 600 px wide, shown at 162 px. Resized copies would save about 20 KiB.

  • 5 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (54 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 1.1 g of CO₂ per visit

    1.10 g

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

Accessibility

7 to fixGoogle 8589
  • 9 text elements with low contrast

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

  • Interactive controls must not be nested (3 elements)

    Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

  • 3 tap targets too small

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (1 element)

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

  • Headings skip levels

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

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

6 to fixGoogle 8576
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Earl Dudley, LLC. - Construction, Surveying, and Mapping Instruments”.

  • No structured data

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

  • Meta description is long (308 characters)

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 5 links with vague text

    5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • One H1 headline

    Your <h1> is empty.

  • 112 internal links, 2 external

    The homepage links to 112 pages on earldudley.com and 2 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://earldudley.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://earldudley.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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://earldudley.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix98
  • 2 pages share a meta description

    https://earldudley.com/collections/uav-lidar-ndaa and https://earldudley.com/collections/uav-lidar-standard 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 37 found) and read each the way a search engine does.

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

3 to fixGoogle 7385
  • 5 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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 analytics detected

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

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

    The homepage carries about 425 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Schedule a call/Virtual Demo”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “CONTACT US .cls-1{fill:#231f20} expand”, “CONTACT US” and “Contact Us”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

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.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 cookies, 6 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.

  • 25 other companies contacted

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

Apps on your store

Your storefront loads 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

eventscalendar.co · digitaloceanspaces.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Birmingham

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on earldudley.com, including 15 speed issues, 6 SEO issues and 3 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