groundtruth.com website review

Your mobile performance score is 98 (desktop: 100). That is in Google's “good” band (90 and up).

A phone's processor spends 0.3 s on main-thread work while loading, 66 ms of it running JavaScript. That is comfortably low.

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

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

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

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

Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

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

Your largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.

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

The page is fully interactive after 2.4 s.

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

Visually, the page fills in at 1.4 s (Speed Index), inside the 3.4 s “good” threshold.

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

Your homepage downloads 278 KiB in 23 requests on a phone: images 134 KiB (17), fonts 75 KiB (4) and HTML 66 KiB (1). That is a lean page.

Every sizeable image is WebP, AVIF or SVG.

Images below the first screen wait until the visitor scrolls to them.

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

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

Your main headline reads: “The easiest way to launch performance ads across every channel.”.

Your title is a healthy 53 characters: “GroundTruth | Launch Performance Ads on Every Channel”.

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

Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

Open Graph tags are complete, so shared links show a title, description and image.

robots.txt is in place and points crawlers to your sitemap.

Your XML sitemap is reachable at https://www.groundtruth.com/sitemap_index.xml.

Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

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

All 15 pages we checked loaded without an error.

Every page we checked has its own title.

Each page we checked has a main headline.

All 15 pages that loaded have a <title>.

No JavaScript errors were logged while the page loaded on a phone.

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

The page declares a mobile viewport.

The homepage is served over HTTPS (groundtruth.com).

The certificate from Let's Encrypt · YE1 verifies for groundtruth.com and is valid for another 89 days.

X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

A Content-Security-Policy is set, the main browser-side defence against injected scripts.

Strict-Transport-Security is set, so browsers always use https.

The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

All 45 links checked from your homepage (40 internal, 5 external) answered without errors; 1 did not answer within 5 s.

groundtruth.com was registered in Oct 1998 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

groundtruth.com is registered until Oct 2027.

On a phone, the first screen shows a clear next step: “Request a demo”.

The homepage has 6 calls to action, for example “Request a demo”, “Learn more” and “Get started”.

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

Analytics detected: Google Tag Manager and Hotjar.

DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:39714994.spf08.hubspotemail.net include:spf.protection.outlook.com include:us._netblocks.mimecast.com in…”.

A DKIM key is published (selector “google”, “k2” and “s1”), so receivers can verify mail really came from you.

No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).