Website review, no card needed
mjcinc.com website review
Visit site (opens in a new tab)Reviewed 21 October 202631 issues · 78 checks
This review found 31 issues worth fixing on mjcinc.com, 12 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. 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
72C- #92,218 of 118,684 reviewed websitesbeats 19%
- #57,301 of 67,395 online storesbeats 12%
- #1,827 of 2,719 WooCommerce storesbeats 28%
Closest competitors among WooCommerce stores
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
4.0 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.
Render-blocking requests
2.8 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Reduce unused CSS
1.8 s · 388 KiBAbout 388 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 44
44/100Your mobile performance score is 44 (desktop: 80). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
2.3 MB12 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
7 third-party services on the page
7 third-party services load with your homepage (YouTube, Google CDN and Hubspot and others), adding 1.6 MB and 664 ms of main-thread time.
YouTube adds 482 ms
482 msYouTube costs a phone 482 ms of main-thread work and 990 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.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 310 ms. During a long task the page ignores taps.
Google CDN adds 114 ms
114 msGoogle CDN costs a phone 114 ms of main-thread work and 347 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.
Legacy JavaScript
150 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
93 KiB5 files are served with short cache lifetimes, so returning visitors download them again (93 KiB).
Phones get a much slower page than desktops
Desktop scores 80 but mobile only 44. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 20.0 s
20.0 sYour largest element takes 20.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WHO WE ARE Founded in 1989, MJC is a manufacturer of HVAC P…”.
Time to Interactive: 25.7 s
25.7 sThe page becomes fully interactive after 25.7 s. Good is under 3.8 s.
First Contentful Paint: 6.3 s
6.3 sThe first text or image appears after 6.3 s on a phone. Good is under 1.8 s.
Speed Index: 10.0 s
10.0 sVisually, the page fills in at 10.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 485 ms
485 msScripts block taps and scrolling for 485 ms in total while the page loads. Good is under 200 ms.
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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.2 MB in 132 requests
9.2 MBYour homepage downloads 9.2 MB in 132 requests on a phone: images 5.9 MB (27), scripts 2.4 MB (73) and fonts 423 KiB (9). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (119 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 2.6 g of CO₂ per visit
2.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.59 g of CO₂e: 311.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 20 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (8 characters)
Your title is only 8 characters: “MJC, INC”. Between 30 and 65 characters leaves room to say what you do and for whom.
5 H1 headlines
There are 5 <h1> headlines (“WHO WE ARE”, “ADDRESS” and “HOURS”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
39 internal links, 1 external
The homepage links to 39 pages on mjcinc.com and 1 external page.
5 checks passed
Meta description: 78 characters
Your meta description is 78 characters: “MJC is a manufacturer of HVAC Products, modifications, and coatings solutions.”.
Canonical URL set
The canonical URL is https://mjcinc.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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://mjcinc.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
llms.txt published
The site publishes https://mjcinc.com/llms.txt (4 KiB, 20 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://mjcinc.com/product/make-a-payment and https://mjcinc.com/author/mjc have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages with very little text
https://mjcinc.com/products, https://mjcinc.com/capabilities, https://mjcinc.com/product/make-a-payment and https://mjcinc.com/author/mjc 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.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 13 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 13 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
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.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 149 words
The homepage has only about 149 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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LEARN MORE”.
1 call to action
The homepage has 1 call to action, for example “LEARN MORE”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads 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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 1 of them by other companies (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 mjcinc.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
- React
- E-commerce
- WooCommerce
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on mjcinc.com, including 15 speed issues, 4 SEO issues and 4 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.