dnow.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Hubspot and Clarity and others), adding 8.0 MB and 721 ms of main-thread time.

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

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

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

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

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

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

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

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

Desktop scores 100 but mobile only 43. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

5 KiB could be saved by minifying CSS.

Your largest element takes 50.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DNOW + MRC Global Creating a premier solutions provider to …”.

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

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

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

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

1 image 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' tap response (inp) went from 78 ms to 76 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.2 MB in 85 requests on a phone: images 7.9 MB (24), fonts 764 KiB (9) and scripts 399 KiB (21). Under 2 MB keeps phones on slow connections fast.

4 images weigh 7.6 MB together. On a phone connection a single image that size takes seconds.

4 images (7.6 MB) are 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.

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

3 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

Main landmark should not be contained in another landmark: 3 elements on the page fail this check, rated moderate by axe-core.

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.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 29 characters: “DNOW | Official Site Homepage”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 167 pages on dnow.com and 35 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.

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

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

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

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

The homepage carries about 833 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 Analytics, Google Tag Manager, HubSpot and Microsoft Clarity (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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