Website review, no card needed
truckmountforums.com website review
Visit site (opens in a new tab)Reviewed 5 November 202636 issues · 75 checks
This review found 36 issues worth fixing on truckmountforums.com, 12 of them high impact, across 75 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
63D- #97,536 of 102,520 reviewed websitesbeats 4%
- #55,713 of 56,980 online storesbeats 2%
- #50,922 of 51,839 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.1 s
2.3 s
3.4 s
4.6 s
5.7 s
6.9 s
8.0 s
9.2 s
Speed
Reduce unused JavaScript
7.1 s · 2.6 MBAbout 2.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.1 s faster on a phone.
Mobile performance score: 27
27/100Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.3 s
A phone's processor spends 8.3 s on main-thread work while loading, 4.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 891 ms. During a long task the page ignores taps.
8 third-party services on the page
8 third-party services load with your homepage (Stripe, Google Tag Manager and Shopify and others), adding 2.6 MB and 604 ms of main-thread time.
Use efficient cache lifetimes
813 KiB10 files are served with short cache lifetimes, so returning visitors download them again (813 KiB).
Improve image delivery
619 KiB26 images could be 619 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Shopify adds 121 ms
121 msShopify costs a phone 121 ms of main-thread work and 1.9 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.
Google Tag Manager adds 211 ms
211 msGoogle Tag Manager costs a phone 211 ms of main-thread work and 374 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.
Reduce unused CSS
176 KiBAbout 176 KiB of CSS is downloaded but never applied on this page.
Render-blocking requests
150 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Minify JavaScript
124 KiB124 KiB could be saved by minifying JavaScript.
Legacy JavaScript
20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need.
Minify CSS
10 KiB10 KiB could be saved by minifying CSS.
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: 50 ms
50 msYour server sent the HTML in 50 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 17.9 s
17.9 sThe first text or image appears after 17.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 17.9 s
17.9 sYour largest element takes 17.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TMF Community is made for Professional cleaning companies w…”.
Speed Index: 22.5 s
22.5 sVisually, the page fills in at 22.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 50.8 s
50.8 sThe page becomes fully interactive after 50.8 s. Good is under 3.8 s.
Total Blocking Time: 2.1 s
2.1 sScripts block taps and scrolling for 2.1 s in total while the page loads. Good is under 200 ms.
31 images without width and height
31 images have no width and height attributes, so the layout jumps as each one loads.
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: 10.2 MB in 305 requests
10.2 MBYour homepage downloads 10.2 MB in 305 requests on a phone: scripts 4.8 MB (129), images 3.3 MB (113) and fonts 965 KiB (10). Under 2 MB keeps phones on slow connections fast.
13 images below the first screen load straight away
13 images further down the page (407 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (216 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.9 g of CO₂ per visit
2.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.88 g of CO₂e: 346.0 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
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 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.
2 checks passed
Every image has alt text
All 65 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 2 failed. 3 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 structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
21 H1 headlines
There are 21 <h1> headlines (“The world's largest online professional carpet cl…”, “Best Pre-Sprays” and “Best Spot Remover”). One clear main headline is easier for people and search engines.
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:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://truckmountforums.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at truckmountforums.com/robots.txt, the first file search crawlers ask for.
Only 4 internal links
The homepage links to only 4 pages on your own site, so visitors and crawlers find few routes into the rest of it.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
1 checks passed
Title: 43 characters
Your title is a healthy 43 characters: “TruckMount Forums #1 Carpet Cleaning Forums”.
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://truckmountforums.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,039 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://truckmountforums.com/help/privacy and https://truckmountforums.com/help/terms have no meta description, so Google writes the search snippet from whatever text it finds.
2 internal pages checked
We fetched 2 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 2 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 2 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
12 distorted images
12 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
8 of 8 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 45 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 1,005 words of copy
The homepage carries about 1,005 words of visible text.
2 checks passed
16 calls to action
The homepage has 16 calls to action, for example “ Download app”, “ Download App” and “Download for iOS”.
Analytics in place
Analytics detected: Google Analytics.
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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
17 cookies set on arrival
17Opening the homepage sets 17 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.
24 other companies contacted
Loading the homepage contacts 24 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 truckmountforums.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
- Webflow
- Framework
- Tailwind CSS
- E-commerce
- Shopify;Shopify Plus;Webflow Ecommerce
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Company
- Headquarters
- Chesapeake
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 truckmountforums.com, including 15 speed issues, 9 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.