Website review, no card needed
adhoc.inc website review
Visit site (opens in a new tab)Reviewed 23 October 202634 issues · 82 checks
This review found 34 issues worth fixing on adhoc.inc, 13 of them high impact, across 82 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
72CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.4 s |
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 3.0 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 162 ms |
| May 9, 2026 | 160 ms |
| May 16, 2026 | 152 ms |
| May 23, 2026 | 161 ms |
| May 30, 2026 | 181 ms |
| Jun 13, 2026 | 224 ms |
| Jun 20, 2026 | 237 ms |
| Jun 27, 2026 | 224 ms |
| Jul 4, 2026 | 220 ms |
| Jul 11, 2026 | 231 ms |
| Jul 18, 2026 | 206 ms |
| Jul 25, 2026 | 207 ms |
| Aug 1, 2026 | 203 ms |
| Aug 8, 2026 | 188 ms |
| Aug 15, 2026 | 203 ms |
| Aug 22, 2026 | 204 ms |
| Aug 29, 2026 | 197 ms |
| Sep 5, 2026 | 181 ms |
| Sep 12, 2026 | 186 ms |
| Sep 19, 2026 | 177 ms |
| Sep 26, 2026 | 180 ms |
| Oct 3, 2026 | 181 ms |
| Oct 10, 2026 | 180 ms |
| Oct 17, 2026 | 194 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
Speed
Render-blocking requests
1.6 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Use efficient cache lifetimes
1.1 s · 396 KiB21 files are served with short cache lifetimes, so returning visitors download them again (396 KiB).
Reduce unused CSS
1.1 s · 382 KiBAbout 382 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 26
26/100Your mobile performance score is 26 (desktop: 31). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.8 s
A phone's processor spends 4.8 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
150 ms · 989 KiBAbout 989 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 651 KiB and 778 ms of main-thread time.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 597 ms. During a long task the page ignores taps.
Google Tag Manager adds 412 ms
412 msGoogle Tag Manager costs a phone 412 ms of main-thread work and 362 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.
1,617 HTML elements
The page has 1,617 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
200 ms · 191 KiB11 images could be 191 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Legacy JavaScript
200 ms · 42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Minify CSS
25 KiB25 KiB could be saved by minifying CSS.
Minify JavaScript
13 KiB13 KiB could be saved by minifying JavaScript.
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: 322 ms
322 msYour server sent the HTML in 322 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 9.0 s
9.0 sYour largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “El sistema que integra todos los procesos de tu empresa.”.
Time to Interactive: 24.0 s
24.0 sThe page becomes fully interactive after 24.0 s. Good is under 3.8 s.
First Contentful Paint: 6.2 s
6.2 sThe first text or image appears after 6.2 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.2 s
7.2 sVisually, the page fills in at 7.2 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 250 ms
250 msReal visitors wait 250 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.219
0.219The layout shifts by 0.219 while loading, so content jumps under the reader's thumb. Good is under 0.1.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 162 ms to 194 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 3.8 MB in 69 requests
3.8 MBYour homepage downloads 3.8 MB in 69 requests on a phone: scripts 2.0 MB (16), HTML 711 KiB (1) and images 412 KiB (23). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (105 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 1.1 g of CO₂ per visit
1.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.08 g of CO₂e: 129.1 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
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h4, h1 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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
5 H1 headlines
There are 5 <h1> headlines (“Un sistema, todos los procesos de tu empresa.”, “Un sistema,todos los procesos de tu empresa.” and “Un sistema,todos los procesos de tu empresa.”). One clear main headline is easier for people and search engines.
57 internal links, 0 external
The homepage links to 57 pages on adhoc.inc and 0 external pages.
7 checks passed
Meta description: 94 characters
Your meta description is 94 characters: “Implementamos, capacitamos y te dejamos el sistema listo para operar según tu país y tu rubro.”.
Title: 42 characters
Your title is a healthy 42 characters: “Adhoc | Partner #1 de Odoo a nivel mundial”.
Canonical URL set
The canonical URL is https://www.adhoc.inc/.
Structured data in place
Structured data found: Organization.
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.adhoc.inc/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing 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.
No llms.txt
There is no https://www.adhoc.inc/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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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.
Text is in the HTML
Your server sends the page's text in the HTML (448 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share a title
https://www.adhoc.inc/comercializadoras/materiales-para-contruccion, https://www.adhoc.inc/comercializadoras/equipamientos-para-hogar, https://www.adhoc.inc/comercializadoras/materiales-electricos and https://www.adhoc.inc/manufactura all use the title “Odoo para comercializadoras | descubrí nuestra solución para el rubro”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.adhoc.inc/soluciones/servicios and https://www.adhoc.inc/jobs have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages share a meta description
https://www.adhoc.inc/comercializadoras/materiales-para-contruccion, https://www.adhoc.inc/comercializadoras/equipamientos-para-hogar, https://www.adhoc.inc/comercializadoras/materiales-electricos and https://www.adhoc.inc/manufactura use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.adhoc.inc/education and https://www.adhoc.inc/aboutus-1 have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.
4 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.
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
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
6 of 7 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 538 words of copy
The homepage carries about 538 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Agendar una demo”.
9 calls to action
The homepage has 9 calls to action, for example “Solicitá tu demo ahora”, “Agendar una demo” and “Coordinar demo para ver cómo funciona”.
Social proof on the page
Social proof on the homepage: 14 customer or partner logos and 29 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel, Microsoft Clarity, LinkedIn Insight and Umami.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
21 other companies contacted
Loading the homepage contacts 21 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 adhoc.inc, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Odoo
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on adhoc.inc, including 22 speed issues, 1 SEO issue and 1 conversion gap. 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.