Website review, no card needed
chadwellsupply.com website review
Visit site (opens in a new tab)Reviewed 20 November 202655 issues · 96 checks
This review found 55 issues worth fixing on chadwellsupply.com, 23 of them high impact, across 96 checks. The most urgent: use efficient cache lifetimes. 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.0 s |
| Nov 14, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 119 ms |
| Jun 6, 2026 | 116 ms |
| Jun 13, 2026 | 114 ms |
| Jun 20, 2026 | 114 ms |
| Jun 27, 2026 | 111 ms |
| Jul 4, 2026 | 108 ms |
| Jul 11, 2026 | 106 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 107 ms |
| Aug 1, 2026 | 111 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 114 ms |
| Aug 22, 2026 | 115 ms |
| Aug 29, 2026 | 116 ms |
| Sep 5, 2026 | 120 ms |
| Sep 12, 2026 | 125 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 129 ms |
| Oct 3, 2026 | 129 ms |
| Oct 10, 2026 | 130 ms |
| Oct 17, 2026 | 132 ms |
| Oct 24, 2026 | 130 ms |
| Oct 31, 2026 | 131 ms |
| Nov 7, 2026 | 129 ms |
| Nov 14, 2026 | 131 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
8.2 s · 13.4 MB114 files are served with short cache lifetimes, so returning visitors download them again (13.4 MB).
Improve image delivery
4.2 s · 9.8 MB56 images could be 9.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.2 s faster on a phone.
Render-blocking requests
4.2 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Reduce unused JavaScript
1.6 s · 2.0 MBAbout 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Reduce unused CSS
1.9 s · 531 KiBAbout 531 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 25
25/100Your mobile performance score is 25. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, dialpad.com and Cloudflare CDN and others), adding 2.5 MB and 749 ms of main-thread time.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 395 ms. During a long task the page ignores taps.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
Minify JavaScript
350 KiB350 KiB could be saved by minifying JavaScript.
Google Tag Manager adds 278 ms
278 msGoogle Tag Manager costs a phone 278 ms of main-thread work and 336 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.
dialpad.com adds 142 ms
142 msdialpad.com costs a phone 142 ms of main-thread work and 1.2 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.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,010 HTML elements
The page has 2,010 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Cloudflare CDN adds 139 ms
139 msCloudflare CDN costs a phone 139 ms of main-thread work and 357 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.
Google CDN adds 80 ms
80 msGoogle CDN costs a phone 80 ms of main-thread work and 352 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.
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.
Legacy JavaScript
5 KiBPolyfills for old browsers add 5 KiB JavaScript that modern phones do not need.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
Duplicated JavaScript
1 KiB1 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 40 ms
40 msYour server sent the HTML in 40 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 CLS: 0.56
0.56For real visitors the layout shifts by 0.56 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 19.2 s
19.2 sYour largest element takes 19.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Chadwell Supply Difference Next Day Delivery Unforgetta…”.
Speed Index: 20.1 s
20.1 sVisually, the page fills in at 20.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 53.6 s
53.6 sThe page becomes fully interactive after 53.6 s. Good is under 3.8 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.372
0.372The layout shifts by 0.372 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
82 images without width and height
82 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 517 ms
517 msScripts block taps and scrolling for 517 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 119 ms to 131 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 144 ms
144 msReal visitors wait 144 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 15.4 MB in 163 requests
15.4 MBYour homepage downloads 15.4 MB in 163 requests on a phone: images 10.5 MB (75), scripts 4.0 MB (42) and fonts 461 KiB (7). Under 2 MB keeps phones on slow connections fast.
7 images over 500 KB
7 images weigh 6.7 MB together. On a phone connection a single image that size takes seconds.
23 images far larger than shown
7.0 MB23 images are downloaded at several times the size a phone draws them, for example 2026_weatheressentials_slider_1450x450_vf.jpg at 3,021 px wide, shown at 390 px. Resized copies would save about 7.0 MB.
27 images in older formats
27 images (9.4 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.
18 images below the first screen load straight away
18 images further down the page (1.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.4 g of CO₂ per visit
4.37 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.37 g of CO₂e: 524.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
16 buttons without a name
16 buttons have no accessible name, so screen readers announce just “button”.
41 text elements with low contrast
41 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
36 tap targets too small
36 tap targets are too small or too close together to hit reliably with a finger.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
14 images without alt text
14 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (35 elements)
Alternative text of images should not be repeated as text: 35 elements on the page fail this check, rated minor by axe-core.
6 links without text
6 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.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings should not be empty (6 elements)
Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 12 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
516 internal links, 10 external
The homepage links to 516 pages on chadwellsupply.com and 10 external pages.
5 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Shop a wide selection of maintenance, repair, and operations (MRO) products from multifamily's largest privately owned …”.
Title: 57 characters
Your title is a healthy 57 characters: “Chadwell Supply | Multifamily & Apartment Maintenance MRO”.
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.chadwellsupply.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.chadwellsupply.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,652 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages without a title
https://www.chadwellsupply.com/categories/a2l-tools--parts, https://www.chadwellsupply.com/categories/appliance-parts, https://www.chadwellsupply.com/categories/appliance-parts/appliance-tools--paint, https://www.chadwellsupply.com/categories/appliance-parts/bake-elements, https://www.chadwellsupply.com/categories/appliance-parts/broil-element and https://www.chadwellsupply.com/categories/appliance-parts/crisper-drawers--covers and 6 others have no <title>, so Google invents the link text in results.
12 pages without a meta description
https://www.chadwellsupply.com/categories/a2l-tools--parts, https://www.chadwellsupply.com/categories/appliance-parts, https://www.chadwellsupply.com/categories/appliance-parts/appliance-tools--paint, https://www.chadwellsupply.com/categories/appliance-parts/bake-elements, https://www.chadwellsupply.com/categories/appliance-parts/broil-element and https://www.chadwellsupply.com/categories/appliance-parts/crisper-drawers--covers and 6 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 199 found) and read each the way a search engine does.
5 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.
Best practices
29 small tap targets
29 of 109 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “(intermediate value).init is not a function”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 959 words of copy
The homepage carries about 959 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: “Shop Blazer Max Pro” and “Shop Now”.
14 calls to action
The homepage has 14 calls to action, for example “Contact Us”, “Shop the Sale” and “Shop BRK Products”.
3 short forms
3 short forms (3 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 12 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics and Google Tag Manager (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.
22 cookies set on arrival
22Opening the homepage sets 22 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.
26 other companies contacted
Loading the homepage contacts 26 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 chadwellsupply.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Azure
Hiring
- Hiring
- 25 open roles
- Job board
- jazzhr
Company
- Employees
- 2,337
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 55 issues on chadwellsupply.com, including 26 speed issues and 4 SEO issues. 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.