Website review, no card needed

getthedataguy.com logo

getthedataguy.com website review

Visit site (opens in a new tab)Reviewed 7 November 202637 issues · 77 checks

This review found 37 issues worth fixing on getthedataguy.com, 15 of them high impact, across 77 checks. The most urgent: render-blocking requests. 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 getthedataguy.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix40
  • Render-blocking requests

    7.2 s

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

  • Reduce unused JavaScript

    5.4 s · 781 KiB

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

  • Use efficient cache lifetimes

    1.5 s · 335 KiB

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

  • Mobile performance score: 40

    40/100

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

  • Improve image delivery

    50 ms · 1.8 MB

    4 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Squarespace, Google CDN and Google Tag Manager and others), adding 4.3 MB and 1.2 s of main-thread time.

  • Squarespace adds 589 ms

    589 ms

    Squarespace costs a phone 589 ms of main-thread work and 1,001 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.

  • Reduce unused CSS

    450 ms · 88 KiB

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

  • Google CDN adds 443 ms

    443 ms

    Google CDN costs a phone 443 ms of main-thread work and 736 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.9 s

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

  • squarespace-cdn.com adds 0 ms

    0 ms

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

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 36 KiB

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

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

    43 ms

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

Core Web Vitals

6 to fix47
  • First Contentful Paint: 12.2 s

    12.2 s

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

  • Largest Contentful Paint: 17.8 s

    17.8 s

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

  • Time to Interactive: 20.5 s

    20.5 s

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

  • Speed Index: 12.2 s

    12.2 s

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

  • Cumulative Layout Shift: 0.257

    0.257

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

  • 9 images without width and height

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

1 checks passed
  • Total Blocking Time: 167 ms

    167 ms

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

Images and page weight

4 to fix28
  • Page weight: 4.8 MB in 95 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 95 requests on a phone: images 2.1 MB (20), scripts 1.8 MB (49) and other files 467 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Screenshot+2023-02-28+at+10.49.11+AM.png weighs 1.8 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    899 KiB

    1 image is downloaded at several times the size a phone draws it, for example Screenshot+2023-02-28+at+10.49.11+AM.png at 1,472 px wide, shown at 350 px. Resized copies would save about 899 KiB.

  • 5 images below the first screen load straight away

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

  • About 1.4 g of CO₂ per visit

    1.36 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 9496
  • 24 text elements with low contrast

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

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 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 18 images in the HTML carry an alt attribute.

  • 43 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: 43 passed and 3 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 9274
  • No meta description

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

  • Title is short (12 characters)

    Your title is only 12 characters: “The Data Guy”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 4 H1 headlines

    There are 4 <h1> headlines (“”, “Now Servicing All Your Data Needs” and “CONTracting Services Provided”). One clear main headline is easier for people and search engines.

  • Structured data has 2 problems

    Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5a08de81d74cffe4d8a…”.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 30 internal links, 3 external

    The homepage links to 30 pages on getthedataguy.com and 3 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.getthedataguy.com/.

  • 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.getthedataguy.com/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing name, url, logo and description. 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://www.getthedataguy.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,345 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 6 pages share a title

    https://www.getthedataguy.com/services-1/l0xj2m6xmvmvq2lonc099q67ydlse0, https://www.getthedataguy.com/services-1/analytics, https://www.getthedataguy.com/services-1/c7stw3w3siudm77yec4bhklafsolnf, https://www.getthedataguy.com/services-1/2018/8/29/data-systems-integration, https://www.getthedataguy.com/services-1/warehousing and https://www.getthedataguy.com/services-1/scraping all use the title “services — The Data Guy”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://www.getthedataguy.com/contact-me, https://www.getthedataguy.com/revenue-operations, https://www.getthedataguy.com/services-1/l0xj2m6xmvmvq2lonc099q67ydlse0, https://www.getthedataguy.com/analytics, https://www.getthedataguy.com/services-1/analytics and https://www.getthedataguy.com/admin-as-a-service and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 links to non-canonical URLs

    Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.getthedataguy.com/services-1/l0xj2m6xmvmvq2lonc099q67ydlse0, whose canonical is https://www.getthedataguy.com/services-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page with very little text

    https://www.getthedataguy.com/contact-me has 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.

  • 13 internal pages checked

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

4 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

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

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/sitecss/5a08de81d74cffe4d8a12048/63/5a590d6e24a6942…”.

2 checks passed
  • Tap targets are thumb-sized

    10 of 10 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

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

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

  • About 456 words of copy

    The homepage carries about 456 words of visible text.

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Me”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • 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
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (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.

  • 10 other companies contacted

    Loading the homepage contacts 10 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 getthedataguy.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
Squarespace
Analytics
Google Analytics
Hosting
Squarespace

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on getthedataguy.com, including 17 speed issues, 4 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