Loading Report View…
0/ 100
jolooch.net Website Audit Report
jolooch.net scored 72 out of 100 in this SavageAudit website audit covering Performance, SEO, Design, Copy, User Experience, and Conversion. The report uses captured website evidence to explain what is working, what is limiting the experience, and which improvements deserve attention first.
“A marketplace built for trust keeps hiding the receipt.”
For a construction marketplace, this site talks like it’s introducing itself to the courtroom, then forgets to bring the witness. The tools are there, but the actual proof, next step, and human handshake are missing from the stage.
https://jolooch.net/
TECHNICAL SUMMARY
Performance is mostly solid, but the site still leaves money on the table with a 3.2 s LCP, 880 ms of render-blocking savings, 129 KiB of unused JavaScript, and a 693 KiB payload. The bigger problem is business execution: copy is thin at 50 words, there are 0 CTA elements and 0 contact paths, social proof is just 1 element, and the UX has 2 broken assets plus 1 CSP console error — which means discoverability is decent, but trust and browsing-to-lead conversion are getting kneecapped. Fix the primary CTA/contact path first, then clean up the broken assets and social metadata so the site can actually sell the listings instead of merely existing.
Where It Burns
6 categoriesWebsite Audit Findings for jolooch.net
SavageAudit identified 36 visible findings and recommendations across 6 audit categories. Each section below combines the category score with observed evidence and prioritized fixes.
9401 PERFORMANCELCP 3.2 s9002 SEOSEO score 100/1007403 DESIGNFont families 124804 COPYWord count 508605 UXBroken assets 21506 CONVERSIONCTA count 0
01
PERFORMANCE AUDIT
94
LCP3.2 sRender-blocking savings880 msUnused JavaScript129 KiBTotal byte weight693 KiB
- 🔥Your LCP is 3.2 s, which is fast enough for a meeting invite and slow enough to make a contractor refresh.
💀
Solid server, but the page still drags a suitcase of avoidable delay across the job site.
- →Compress the hero images and switch them to WebP or AVIF.LCP: 3.2 sImpact: highEffort: medium
Why this matters
The LCP is above the good threshold, so the hero content is taking too long to land and delaying the first meaningful impression.
- →Defer non-critical JavaScript and cut back render-blocking resources.TBT: 120 msImpact: highEffort: medium
Why this matters
Even with a decent total blocking time, the page still has 880 ms of avoidable blocking work that is wasting perceived speed.
- →Enable CDN caching and serve static assets with long cache TTLs.FCP: 2.0 sImpact: mediumEffort: low
Why this matters
The first contentful paint is acceptable but not snappy, and caching is the cheapest way to stop the same assets from re-entering the job site every visit.
02
SEO AUDIT
90
SEO score100/100Open Graph imageMissingSocial titlesMisalignedHeading skiph1→h3
- 🔥Your Open Graph image is missing, so social shares show up dressed like a default placeholder in a hard hat.
💀
Search can read it, but social and structure are making the site look less deliberate than the business deserves.
- →Add an llms.txt or ai.txt file with priority URLs, core docs, and support paths.AI Hints: MissingImpact: mediumEffort: medium
Why this matters
AI crawler guidance is absent, so the site is missing a cheap way to steer citation and discovery toward the pages that matter most.
- →Add Organization or WebSite schema with sameAs links to official brand profiles.Entity Graph: MissingImpact: mediumEffort: medium
Why this matters
The brand lacks connected entity signals, which weakens how clearly search systems can validate the marketplace as a legitimate organization.
- →Add an og:image meta tag for a polished appearance when shared on social media.Open Graph Image: MissingImpact: mediumEffort: low
Why this matters
Without an OG image, link previews lose visual identity and the site looks like it forgot to bring its own name badge.
03
DESIGN AUDIT
74
Font families12Heading count8Heading skiph1→h3Images3
- 🔥You’ve got 12 font families on one page, which is less a design system and more a typeface group chat.
💀
The page looks organized until the typography and heading structure start freelancing off-script.
- →Reduce font families from 12 to 2-3 for visual consistency.Font Families: 12Impact: mediumEffort: low
Why this matters
Twelve font families create visual drift, which is especially bad on a trust-heavy marketplace where consistency should do the heavy lifting.
- →Add supporting imagery so the layout feels intentional, not empty.Images: 3Impact: mediumEffort: medium
Why this matters
With only 3 images, the page lacks enough visual proof to make a heavy-machinery marketplace feel grounded in real listings.
- →Test spacing and alignment across mobile and desktop breakpoints.Viewport: PresentImpact: lowEffort: medium
Why this matters
Viewport support exists, but that only proves the page can respond; it does not prove the layout survives real devices without awkward alignment.
04
COPY AUDIT
48
Word count50Sentence count31Social proof1CTA count0
- 🔥Fifty words on a marketplace homepage is not copy, it’s a legal disclaimer with ambitions.
💀
The page says almost nothing, proves even less, and gives the user nowhere to go.
- →Tighten the headline to state the value in one sentence.H1 Count: 1Impact: mediumEffort: low
Why this matters
The homepage has only one main headline, so it needs to carry the entire value proposition for contractors deciding whether to trust the platform.
- →Break the copy into skimmable bullets and shorter sentences.Avg Words/Sentence: 2Impact: lowEffort: medium
Why this matters
The current structure is too thin to scan quickly, and better chunking would make the listing value easier to digest on first pass.
- →Add a clear CTA — there are none right now.CTA Count: 0Impact: highEffort: low
Why this matters
With zero CTAs, the page offers information but no instruction, which is a terrible trade for a transactional marketplace.
05
UX AUDITUSER EXPERIENCE AUDIT
86
Broken assets2Console errors1NavAbsentButtons6
- 🔥Two broken assets — the reCAPTCHA script and a Firestore fetch — means the interface is tripping over its own shoelaces in public.
💀
Users can see the site, but the broken parts and missing wayfinding keep trying to sabotage the visit.
- →Repair failed asset URLs and deployment paths so scripts, images, and stylesheets load cleanly.Broken Assets: 2Impact: highEffort: medium
Why this matters
Both the reCAPTCHA script and the Firestore fetch are failing, so key interactions are already starting from a broken state.
- →Fix client-side JavaScript errors so interactions do not fail silently in production.JS Errors: 1Impact: highEffort: medium
Why this matters
The CSP violation means the browser is rejecting a script load, which can break user-facing functionality without any graceful recovery.
- →Ensure consistent navigation and footer links across all pages.Nav/Footer: No nav / FooterImpact: mediumEffort: medium
Why this matters
Without navigation, users have fewer paths to explore listings, verify credibility, or recover when they land on the wrong page.
06
CONVERSION AUDIT
15
CTA count0Contact elements0Social proof1Word count50
- 🔥CTA count is 0, which is the digital equivalent of opening a store and never unlocking the door.
💀
The site wants browsing behavior, but the conversion path is missing the signposts, the door handle, and the receptionist.
- →Add a primary CTA above the fold that matches the core offer.CTA Count: 0Impact: highEffort: low
Why this matters
A transactional marketplace cannot convert if the first screen gives no obvious action for browsing listings or contacting a vendor.
- →Offer a low-friction contact option such as a form, chat, or visible email.Contact Path: MissingImpact: highEffort: medium
Why this matters
Construction and equipment users need fast trust confirmation, and a missing contact path forces them to leave instead of inquire.
- →Place social proof or trust signals near the CTA.Social Proof: 1Impact: mediumEffort: low
Why this matters
With only one proof point, trust needs to be visible right where the user is deciding whether to browse or bounce.
Audit overview
jolooch.net Audit Summary
Performance is mostly solid, but the site still leaves money on the table with a 3.2 s LCP, 880 ms of render-blocking savings, 129 KiB of unused JavaScript, and a 693 KiB payload. The bigger problem is business execution: copy is thin at 50 words, there are 0 CTA elements and 0 contact paths, social proof is just 1 element, and the UX has 2 broken assets plus 1 CSP console error — which means discoverability is decent, but trust and browsing-to-lead conversion are getting kneecapped. Fix the primary CTA/contact path first, then clean up the broken assets and social metadata so the site can actually sell the listings instead of merely existing.
Based on the category scores in this report, Performance is the strongest area while Conversion has the most room for improvement.
How SavageAudit Evaluated jolooch.net
SavageAudit evaluated the public website at https://jolooch.net/ across performance, technical SEO, design, copy, user experience, and conversion signals. Scores and recommendations reflect the website evidence available when this audit was generated on July 5, 2026.
Similar Website Audit Reports
Compare this result with other public SavageAudit reports that received a similar overall website score.