Website review, no card needed
ajmadison.com website review
Visit site (opens in a new tab)Reviewed 21 October 202636 issues · 85 checks
This review found 36 issues worth fixing on ajmadison.com, 16 of them high impact, across 85 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.9 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 166 ms |
| May 9, 2026 | 166 ms |
| May 16, 2026 | 163 ms |
| May 23, 2026 | 163 ms |
| May 30, 2026 | 164 ms |
| Jun 6, 2026 | 169 ms |
| Jun 13, 2026 | 171 ms |
| Jun 20, 2026 | 172 ms |
| Jun 27, 2026 | 173 ms |
| Jul 4, 2026 | 175 ms |
| Jul 11, 2026 | 175 ms |
| Jul 18, 2026 | 175 ms |
| Jul 25, 2026 | 178 ms |
| Aug 1, 2026 | 179 ms |
| Aug 8, 2026 | 185 ms |
| Aug 15, 2026 | 188 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 193 ms |
| Sep 5, 2026 | 191 ms |
| Sep 12, 2026 | 188 ms |
| Sep 19, 2026 | 188 ms |
| Sep 26, 2026 | 191 ms |
| Oct 3, 2026 | 195 ms |
| Oct 10, 2026 | 196 ms |
| Oct 17, 2026 | 196 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
1.0 s · 667 KiB15 files are served with short cache lifetimes, so returning visitors download them again (667 KiB).
Render-blocking requests
1.4 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 43
43/100Your mobile performance score is 43 (desktop: 61). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.7 s
A phone's processor spends 5.7 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
3.1 MB23 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
630 ms · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 630 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (px-cloud.net, Facebook and Clarity and others), adding 911 KiB and 653 ms of main-thread time.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 274 ms. During a long task the page ignores taps.
px-cloud.net adds 222 ms
222 mspx-cloud.net costs a phone 222 ms of main-thread work and 385 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.
2,414 HTML elements
The page has 2,414 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
260 ms · 52 KiBAbout 52 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 260 ms faster on a phone.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Legacy JavaScript
64 KiBPolyfills for old browsers add 64 KiB JavaScript that modern phones do not need.
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: 108 ms
108 msYour server sent the HTML in 108 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.
Time to Interactive: 27.7 s
27.7 sThe page becomes fully interactive after 27.7 s. Good is under 3.8 s.
Largest Contentful Paint: 6.4 s
6.4 sYour largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Promo Sale”.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Real-user INP: 231 ms
231 msReal visitors wait 231 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 886 ms
886 msReal visitors wait 886 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
23 images without width and height
23 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 166 ms to 196 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.5 MB in 224 requests
7.5 MBYour homepage downloads 7.5 MB in 224 requests on a phone: images 3.3 MB (68), scripts 2.5 MB (54) and media 966 KiB (1). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
wm4000hba_dlex4000b_dlgx4001b~side-by-side5f3c1cd73df782.348 weighs 1.8 MB. On a phone connection a single image that size takes seconds.
4 images far larger than shown
2.1 MB4 images are downloaded at several times the size a phone draws them, for example wm4000hba_dlex4000b_dlgx4001b~side-by-side5f3c1cd73df782.348 at 6,336 px wide, shown at 117 px. Resized copies would save about 2.1 MB.
An image on the first screen is lazy-loaded
c92f2748570af411bcd81e5cfdebbbdb9ee8fcec-1560x2076.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 2.1 g of CO₂ per visit
2.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.11 g of CO₂e: 253.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
1 link without text
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.
Elements with visible text labels do not have matching accessible names. (27 elements).
2 checks passed
Every image has alt text
All 222 images in the HTML carry an alt attribute.
16 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 17 WCAG 2.2 A/AA and best-practice rules on the phone render: 16 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (10 characters)
Your title is only 10 characters: “AJ Madison”. Between 30 and 65 characters leaves room to say what you do and for whom.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
277 internal links, 15 external
The homepage links to 277 pages on ajmadison.com and 15 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Shop Home & Kitchen Appliances”.
Structured data in place
Structured data found: Organization.
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.ajmadison.com/sitemapindex.xml.
AI search readiness
No llms.txt
There is no https://www.ajmadison.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,993 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without a meta description
https://www.ajmadison.com/showroom/new-york, https://www.ajmadison.com/showroom/miami, https://www.ajmadison.com/showroom/atlanta and https://www.ajmadison.com/showroom/washington-dc 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 153 found) and read each the way a search engine does.
6 checks passed
Linked pages load
4 pages of 15 loaded without an error (the rest turned automated requests away).
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 4 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5577446&tm=gtm002&Ver=2&mid=376fa095-63ed-4f23-98c5-575454d14b1d&bo=1&sid=7e1d2ea0cd3611f19aad2523aa96e12e&vid=7e1d5710cd3611f1af1875455fd2acdf&vids=1&msclkid=N>m_ta.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
76 of 82 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
About 2,836 words of copy
The homepage carries about 2,836 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Order Status” and “Join Pro”.
11 calls to action
The homepage has 11 calls to action, for example “Call Us800-570-3355”, “Order Status” and “Shop”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 15 trust badges and “over 150 brands”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel, Microsoft Ads and Microsoft Clarity and 1 more (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.
32 cookies set on arrival
32Opening the homepage sets 32 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.
42 other companies contacted
Loading the homepage contacts 42 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 ajmadison.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
- Next.js
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on ajmadison.com, including 19 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.