dat.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and outgo.com and others), adding 1.3 MB and 1.3 s of main-thread time.

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

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

Google Tag Manager costs a phone 440 ms of main-thread work and 548 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.

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

Facebook costs a phone 252 ms of main-thread work and 254 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.

The page has 2,200 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

37 KiB could be saved by minifying JavaScript.

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

14 KiB could be saved by minifying CSS.

10 KiB JavaScript is shipped twice across bundles.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Free factoring for 3 months* when you sign up for DAT Outgo”.

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

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

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

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

15 images have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 4.9 MB in 279 requests on a phone: scripts 2.4 MB (101), other files 988 KiB (81) and images 679 KiB (54). Under 2 MB keeps phones on slow connections fast.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

43 visible links have no text or label, so screen readers cannot say where they go.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

Your title is only 29 characters: “DAT Freight & Analytics - DAT”. Between 30 and 65 characters leaves room to say what you do and for whom.

3 links have no real href, so search engines can't follow them.

The homepage links to 146 pages on dat.com and 31 external pages.

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

/rateview and /network-analytics use the same meta description. A description written for each page earns more clicks.

We fetched 15 pages linked from your homepage (of 37 found) and read each the way a search engine does.

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

6 errors were logged to the browser console while the page loaded, for example “analytics is not defined”.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://instagram.com/datfreight.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

dat.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

dat.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 10 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage carries about 1,417 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 7 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 52 cookies (measured from a US location before any click).

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