Website review, no card needed
badgermurphy.com website review
Visit site (opens in a new tab)Reviewed 5 November 202632 issues · 95 checks
This review found 32 issues worth fixing on badgermurphy.com, 10 of them high impact, across 95 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
76C- #49,801 of 82,915 reviewed websitesbeats 35%
- #28,533 of 41,463 online storesbeats 27%
- #892 of 2,118 WooCommerce storesbeats 52%
Closest competitors among WooCommerce stores
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
3.3 s42 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.
Reduce unused CSS
900 ms · 210 KiBAbout 210 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
650 ms · 112 KiB4 images could be 112 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
Reduce unused JavaScript
300 ms · 401 KiBAbout 401 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
550 ms · 81 KiB78 files are served with short cache lifetimes, so returning visitors download them again (81 KiB).
Google CDN adds 360 ms
360 msGoogle CDN costs a phone 360 ms of main-thread work and 736 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.
5 third-party services on the page
5 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Unpkg and others), adding 988 KiB and 414 ms of main-thread time.
Legacy JavaScript
200 ms · 49 KiBPolyfills for old browsers add 49 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Minify JavaScript
150 ms · 37 KiB37 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 12 KiB12 KiB could be saved by minifying CSS.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 119 ms. During a long task the page ignores taps.
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: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 905 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.8 s
6.8 sYour largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Badger Murphy is Chicagoland's brand name, full line food s…”.
Time to Interactive: 11.3 s
11.3 sThe page becomes fully interactive after 11.3 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 121 ms
121 msScripts block the page for only 121 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 2.1 MB in 100 requests
2.1 MBYour homepage downloads 2.1 MB in 100 requests on a phone: scripts 1,022 KiB (45), other files 354 KiB (4) and images 312 KiB (7). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.60 g of CO₂e: 72.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 4 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 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
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (13 characters)
Your title is only 13 characters: “Badger Murphy”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
20 internal links, 0 external
The homepage links to 20 pages on badgermurphy.com and 0 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.badgermurphy.com/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.badgermurphy.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 /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.
1 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.
Other pages
6 pages without a meta description
/company, /history, /products, /request-quote, /contact and /job-application have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages with very little text
/request-quote and /contact have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
6 internal pages checked
We fetched 6 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 6 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 6 pages that loaded have a <title>.
Best practices
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
http:// does not redirect
http://badgermurphy.com does not redirect to https, so some visitors land on the insecure version.
No Content-Security-Policy
No Content-Security-Policy header, the main browser-side defence against injected scripts.
No clickjacking protection
Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.
Short HSTS lifetime
HSTS is set, but max-age is 180 days; one year is the recommended minimum.
No X-Content-Type-Options
X-Content-Type-Options: nosniff is missing, so browsers may guess file types.
2 redirects before the homepage
Opening https://badgermurphy.com goes through 2 redirects before the homepage loads.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
4 checks passed
Served over HTTPS
The homepage is served over HTTPS (badgermurphy.com).
Valid certificate (62 days left)
The certificate from Let's Encrypt · YE2 verifies for badgermurphy.com and is valid for another 62 days.
HTTP/2
The server speaks HTTP/2, so browsers load many files over one connection.
All 14 links work
All 14 links checked from your homepage (14 internal, 0 external) answered without errors.
Domain and trust
Domain expires in 4 days
badgermurphy.com is registered until Nov 2026. If it lapses, the site and its email stop working and someone else can buy the name. Renew it, and turn on auto-renew.
No CAA record
badgermurphy.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
badgermurphy.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
1 checks passed
Domain is 25 years old
25 yearsbadgermurphy.com was registered in Nov 2000 through NameSilo, LLC. An established domain carries more trust with email providers and search engines.
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.
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.
Thin social proof
Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 106 words
The homepage has only about 106 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
3 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Request a Quote”, “Contact” and “Contact submenu”.
1 short form
A short form (1 field at most) is right on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Email authentication
DMARC is monitor-only (p=none)
DMARC is set to p=none, so mail pretending to be badgermurphy.com is still delivered. Add a report address, check the reports, then move to quarantine.
Email authentication score: 75/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
2 checks passed
SPF with a strict ending (-all)
An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 mx a include:mailanyone.net include:spf.protection.outlook.com ip4:50.31.1.187 ip4:209.142.65.57 -all”.
DKIM signing found
A DKIM key is published (selector “selector1”, “selector2” and “default”), so receivers can verify mail really came from you.
Privacy and tracking
10 cookies set on arrival
10Opening the homepage sets 10 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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Upkeep, stack and company
- It runs WordPress 6.9.11; the current release is 7.1.4.
- 1 plugin is behind its latest release.woocommerce 10.6.2 → 11.2.2
Stack
- CMS
- WordPress 6.9.11
- Framework
- jQuery
- E-commerce
- WooCommerce
- Hosting
- Scala Hosting LLC
Company
- Headquarters
- Chicago
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on badgermurphy.com, including 11 speed issues, 4 SEO issues and 5 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.