Website review, no card needed
willoughby-ind.com website review
Visit site (opens in a new tab)Reviewed 23 October 202626 issues · 81 checks
This review found 26 issues worth fixing on willoughby-ind.com, 11 of them high impact, across 81 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.4 s |
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 4.2 s |
| Jul 18, 2026 | 4.6 s |
| Jul 25, 2026 | 4.2 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 4.5 s |
| Sep 12, 2026 | 5.2 s |
| Sep 19, 2026 | 5.0 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 75 ms |
| May 9, 2026 | 77 ms |
| May 16, 2026 | 78 ms |
| May 23, 2026 | 80 ms |
| May 30, 2026 | 79 ms |
| Jun 6, 2026 | 72 ms |
| Jun 13, 2026 | 71 ms |
| Jun 20, 2026 | 77 ms |
| Jun 27, 2026 | 77 ms |
| Jul 4, 2026 | 80 ms |
| Jul 11, 2026 | 96 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 155 ms |
| Aug 29, 2026 | 132 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 110 ms |
| Sep 19, 2026 | 109 ms |
| Sep 26, 2026 | 127 ms |
| Oct 3, 2026 | 113 ms |
| Oct 10, 2026 | 112 ms |
| Oct 17, 2026 | 100 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
How it loaded on a phone
0.5 s
1.0 s
1.5 s
2.0 s
2.5 s
2.9 s
3.4 s
3.9 s
Speed
Render-blocking requests
2.6 s29 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Mobile performance score: 50
50/100Your mobile performance score is 50 (desktop: 97). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
600 ms · 100 KiB6 files are served with short cache lifetimes, so returning visitors download them again (100 KiB).
Reduce unused JavaScript
450 ms · 61 KiBAbout 61 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
2,992 HTML elements
The page has 2,992 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Hubspot and Google CDN and others), adding 509 KiB and 394 ms of main-thread time.
Legacy JavaScript
150 ms · 13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 158 ms. During a long task the page ignores taps.
Reduce unused CSS
11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 97 but mobile only 50. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify JavaScript
8 KiB8 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 58 ms
58 msYour server sent the HTML in 58 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.7 s
2.7 sReal visitors wait 2.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 10.0 s
10.0 sYour largest element takes 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PLUMBING FIXTURES FOR DEMANDING FACILITIES Built for durabi…”.
Time to Interactive: 10.0 s
10.0 sThe page becomes fully interactive after 10.0 s. Good is under 3.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 39% slower for real visitors
+39%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 75 ms to 100 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 176% slower for real visitors
+176%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.4 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 449 ms
449 msScripts block taps and scrolling for 449 ms in total while the page loads. Good is under 200 ms.
3 checks passed
Real-user INP: 103 ms
103 msReal visitors wait 103 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.3 g of CO₂ per visit
0.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.29 g of CO₂e: 34.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.0 MB in 112 requests
1.0 MBYour homepage downloads 1.0 MB in 112 requests on a phone: scripts 602 KiB (47), fonts 135 KiB (7) and stylesheets 121 KiB (36). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h5, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 4 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (71 characters)
Your title is 71 characters, so Google will cut it off around 60: “American-Made Stainless Steel Plumbing Fixtures | Willoughby Industries”.
2 H1 headlines
There are 2 <h1> headlines (“Plumbing Fixtures for Demanding Facilities” and “Search Products, Resources, and More”). One clear main headline is easier for people and search engines.
Meta description is long (170 characters)
Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
219 internal links, 16 external
The homepage links to 219 pages on willoughby-ind.com and 16 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://willoughby-ind.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://willoughby-ind.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://willoughby-ind.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 (1,334 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages slow to respond
https://willoughby-ind.com/products/accessories, https://willoughby-ind.com/products/combination-units, https://willoughby-ind.com/products/handwashing and https://willoughby-ind.com/products/hydration took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 68 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
12 of 13 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 539 words of copy
The homepage carries about 539 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT”.
9 calls to action
The homepage has 9 calls to action, for example “Contact”, “Download Catalog” and “Buy Direct on wsf‑usa.com”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics and HubSpot.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (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.
10 cookies set on arrival
10Opening the homepage sets 10 cookies (measured from a US location before any click).
18 other companies contacted
Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 willoughby-ind.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on willoughby-ind.com, including 17 speed issues, 4 SEO issues and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.