Website review, no card needed

nwpipe.com logo

nwpipe.com website review

Visit site (opens in a new tab)Reviewed 3 November 202633 issues · 80 checks

This review found 33 issues worth fixing on nwpipe.com, 10 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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

Real-visitor load time (LCP)75th percentile, phones
4.1 s3.0 sMay 16Oct 313.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.7 s
May 23, 20263.8 s
May 30, 20263.8 s
Jun 6, 20263.9 s
Jun 13, 20263.9 s
Jun 20, 20263.9 s
Jun 27, 20263.7 s
Jul 4, 20263.9 s
Jul 11, 20263.8 s
Jul 18, 20263.5 s
Jul 25, 20263.5 s
Aug 1, 20263.1 s
Aug 8, 20263.3 s
Aug 15, 20263.5 s
Aug 22, 20263.5 s
Aug 29, 20263.6 s
Sep 5, 20263.5 s
Sep 12, 20263.5 s
Sep 19, 20263.5 s
Sep 26, 20263.4 s
Oct 3, 20263.3 s
Oct 10, 20263.1 s
Oct 17, 20263.2 s
Oct 24, 20263.2 s
Oct 31, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
89 ms71 msMay 16Oct 3178 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202680 ms
May 23, 202681 ms
May 30, 202683 ms
Jun 6, 202687 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202683 ms
Jul 4, 202680 ms
Jul 11, 202682 ms
Jul 18, 202683 ms
Jul 25, 202680 ms
Aug 1, 202679 ms
Aug 8, 202679 ms
Aug 15, 202678 ms
Aug 22, 202680 ms
Aug 29, 202679 ms
Sep 5, 202681 ms
Sep 12, 202681 ms
Sep 19, 202673 ms
Sep 26, 202678 ms
Oct 3, 202681 ms
Oct 10, 202678 ms
Oct 17, 202678 ms
Oct 24, 202678 ms
Oct 31, 202678 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of nwpipe.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nwpipe.com at 0.5 s0.5 s
  2. nwpipe.com at 1.0 s1.0 s
  3. nwpipe.com at 1.6 s1.6 s
  4. nwpipe.com at 2.1 s2.1 s
  5. nwpipe.com at 2.6 s2.6 s
  6. nwpipe.com at 3.1 s3.1 s
  7. nwpipe.com at 3.7 s3.7 s
  8. nwpipe.com at 4.2 s4.2 s

Speed

9 to fix53
  • Reduce unused JavaScript

    3.9 s · 457 KiB

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

  • Improve image delivery

    550 ms · 1.0 MB

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

  • Use efficient cache lifetimes

    900 ms · 181 KiB

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

  • Mobile performance score: 53

    53/100

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

  • 8 third-party services on the page

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

  • Render-blocking requests

    400 ms

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.

  • Google CDN adds 311 ms

    311 ms

    Google CDN costs a phone 311 ms of main-thread work and 734 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.

  • Legacy JavaScript

    300 ms · 48 KiB

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

  • Reduce unused CSS

    300 ms · 48 KiB

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

  • 7 long tasks on the main thread

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

  • Font display

    100 ms

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

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

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 18.1 s

    18.1 s

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

  • First Contentful Paint: 6.6 s

    6.6 s

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

  • Time to Interactive: 18.5 s

    18.5 s

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

  • Speed Index: 8.3 s

    8.3 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Total Blocking Time: 245 ms

    245 ms

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

6 checks passed
  • Real-user INP: 83 ms

    83 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 419 ms

    419 ms

    Real visitors wait 419 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix68
  • Page weight: 3.7 MB in 82 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 82 requests on a phone: images 1.8 MB (27), scripts 1.2 MB (22) and other files 366 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (594 KiB) 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.

  • 9 images below the first screen load straight away

    9 images further down the page (397 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    1.04 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

4 to fixGoogle 8694
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • 2 links without text

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

  • 1 form field without a label

    1 form field has 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.

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • Meta description is long (259 characters)

    Your meta description is 259 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 3 links with vague text

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

  • 103 internal links, 22 external

    The homepage links to 103 pages on nwpipe.com and 22 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “A Legacy Grounded in Water”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Engineered Pipe Systems - Northwest Pipe Company”.

  • Canonical URL set

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

  • Structured data in place

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

  • Open Graph tags complete

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

  • 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.nwpipe.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 10 pages without a meta description

    https://www.nwpipe.com/products/engineered-steel-water-pipe/infrashield-joint-system-grsp, https://www.nwpipe.com/products/trenchless-pipe, https://www.nwpipe.com/products/trenchless-pipe/steel-pipe-for-curved-microtunneling, https://www.nwpipe.com/products/trenchless-pipe/permalok-hdd-pipe, https://www.nwpipe.com/products/trenchless-pipe/concrete-jacking-pipe and https://www.nwpipe.com/products/lined-sanitary-sewer-systems and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

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

Best practices

2 to fixGoogle 9687
  • 6 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'value')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

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

  • No form on the homepage

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

  • 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 560 words of copy

    The homepage carries about 560 words of visible text.

2 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Contact Us”, “Register Now” and “Learn More”.

  • Analytics in place

    Analytics detected: Google Analytics and HubSpot.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 34 other companies contacted

    Loading the homepage contacts 34 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 nwpipe.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
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Cloudflare

Hiring

Hiring
16 open roles
Job board
careers page

Company

Employees
1,197

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on nwpipe.com, including 17 speed issues, 2 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