Website review, no card needed
jcnewman.com website review
Visit site (opens in a new tab)Reviewed 19 October 202620 issues · 73 checks
This review found 20 issues worth fixing on jcnewman.com, 7 of them high impact, across 73 checks. The most urgent: improve image delivery. 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
85B- #12,775 of 93,505 reviewed websitesbeats 82%
- #7,724 of 49,968 online storesbeats 79%
- #133 of 2,210 WooCommerce storesbeats 92%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.6 s |
| May 2, 2026 | 1.6 s |
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 82 ms |
| May 2, 2026 | 83 ms |
| May 9, 2026 | 81 ms |
| May 16, 2026 | 82 ms |
| May 23, 2026 | 82 ms |
| May 30, 2026 | 82 ms |
| Jun 6, 2026 | 83 ms |
| Jun 13, 2026 | 85 ms |
| Jun 20, 2026 | 83 ms |
| Jun 27, 2026 | 85 ms |
| Jul 4, 2026 | 86 ms |
| Jul 11, 2026 | 86 ms |
| Jul 18, 2026 | 86 ms |
| Jul 25, 2026 | 86 ms |
| Aug 1, 2026 | 86 ms |
| Aug 8, 2026 | 87 ms |
| Aug 15, 2026 | 87 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 87 ms |
| Sep 5, 2026 | 86 ms |
| Sep 12, 2026 | 80 ms |
| Sep 19, 2026 | 79 ms |
| Sep 26, 2026 | 75 ms |
| Oct 3, 2026 | 72 ms |
| Oct 10, 2026 | 71 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
Improve image delivery
2.9 s · 858 KiB9 images could be 858 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.
Render-blocking requests
1.9 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 68
68/100Your mobile performance score is 68 (desktop: 92). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
730 ms · 135 KiBAbout 135 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 730 ms faster on a phone.
Reduce unused CSS
450 ms · 47 KiBAbout 47 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 176 ms
176 msGoogle Tag Manager costs a phone 176 ms of main-thread work and 340 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.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, jQuery CDN and cdn-cookieyes.com and others), adding 543 KiB and 217 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 117 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Use efficient cache lifetimes
6 KiB2 files are served with short cache lifetimes, so returning visitors download them again (6 KiB).
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.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 283 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.3 s
12.3 sYour largest element takes 12.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 12.4 s
12.4 sThe page becomes fully interactive after 12.4 s. Good is under 3.8 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 71 ms
71 msReal visitors wait 71 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.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 348 ms
348 msReal visitors wait 348 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 82 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 37% faster for real visitors
-37%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 79 ms
79 msScripts block the page for only 79 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 14.3 MB in 68 requests
14.3 MBYour homepage downloads 14.3 MB in 68 requests on a phone: media 12.3 MB (2), images 1.3 MB (14) and scripts 460 KiB (21). Under 2 MB keeps phones on slow connections fast.
8 images below the first screen load straight away
8 images further down the page (787 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images in older formats
3 images (147 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.
About 4.0 g of CO₂ per visit
4.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.05 g of CO₂e: 485.6 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
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 11 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 1 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (73 characters)
Your title is 73 characters, so Google will cut it off around 60: “America’s Oldest Family-Owned Premium Cigar Maker | J.C. Newman Cigar Co.”.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
68 internal links, 11 external
The homepage links to 68 pages on jcnewman.com and 11 external pages.
7 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Founded in 1895, J.C. Newman Cigar Co. is America’s oldest family-owned premium cigar co. Our HQ remains the El Reloj c…”.
One H1 headline
Your main headline reads: “AMERICA’S OLDEST FAMILY-OWNED PREMIUM CIGAR MAKER”.
Canonical URL set
The canonical URL is https://www.jcnewman.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, OnlineStore, 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.jcnewman.com/sitemap_index.xml.
AI search readiness
4 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, sameAs (social profiles) and description; logo and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (365 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.jcnewman.com/llms.txt (5 KiB, 44 links), a plain-text guide to the site for AI tools.
Other pages
1 page slow to respond
https://www.jcnewman.com/store took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 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
2 small tap targets
2 of 9 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 “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 281 words of copy
The homepage carries about 281 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Personal Reserve”, “Shop Now” and “Contact Us”.
1 short form
A short form (4 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 jcnewman.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
- E-commerce
- WooCommerce
- 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 20 issues on jcnewman.com, including 10 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.