jonesknowsdata.com website review

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

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

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

2 third-party services load with your homepage (WordPress Site Stats and WordPress), adding 4.4 MB and 1 ms of main-thread time.

WordPress costs a phone 0 ms of main-thread work and 4.4 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.

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

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

About 14 KiB of CSS is downloaded but never applied on this page.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

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.

Your homepage downloads 4.7 MB in 45 requests on a phone: images 4.4 MB (10), scripts 129 KiB (13) and stylesheets 44 KiB (17). Under 2 MB keeps phones on slow connections fast.

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

1 image is downloaded at several times the size a phone draws it, for example jkdlogo.png at 390 px wide, shown at 54 px. Resized copies would save about 47 KiB.

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

2 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: 7 elements on the page fail this check, rated moderate by axe-core.

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

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 23 characters: “Home - Jones Knows Data”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Strategic Revenue Operations & Data Consulting” and “About Our Company”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 29 pages on jonesknowsdata.com and 3 external pages.

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.

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

/ and https://jonesknowsdata.com/home all use the title “Home - Jones Knows Data”. Search engines can't tell which page to show for a search, so each competes with the others.

https://jonesknowsdata.com/home, https://jonesknowsdata.com/about, https://jonesknowsdata.com/blog, https://jonesknowsdata.com/contact, https://jonesknowsdata.com/gallery and https://jonesknowsdata.com/where-to-buy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://jonesknowsdata.com/blog, https://jonesknowsdata.com/contact and https://jonesknowsdata.com/gallery 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.

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

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 ()”.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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.

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