Website review, no card needed
grupohitec.com website review
Visit site (opens in a new tab)Reviewed 27 October 202647 issues · 92 checks
This review found 47 issues worth fixing on grupohitec.com, 22 of them high impact, across 92 checks. The most urgent: improve image delivery. 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
61DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.2 s |
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 180 ms |
| May 16, 2026 | 171 ms |
| May 23, 2026 | 166 ms |
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 160 ms |
| Jun 13, 2026 | 161 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 155 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 152 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 151 ms |
| Aug 1, 2026 | 148 ms |
| Aug 8, 2026 | 149 ms |
| Aug 15, 2026 | 153 ms |
| Aug 22, 2026 | 161 ms |
| Aug 29, 2026 | 166 ms |
| Sep 5, 2026 | 171 ms |
| Sep 12, 2026 | 168 ms |
| Sep 19, 2026 | 238 ms |
| Sep 26, 2026 | 283 ms |
| Oct 3, 2026 | 281 ms |
| Oct 10, 2026 | 278 ms |
| Oct 17, 2026 | 266 ms |
| Oct 24, 2026 | 259 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
How it loaded on a phone
0.6 s
1.3 s
1.9 s
2.5 s
3.2 s
3.8 s
4.5 s
5.1 s
Speed
Improve image delivery
41.5 s · 8.0 MB20 images could be 8.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 41.5 s faster on a phone.
Use efficient cache lifetimes
7.2 s · 1.8 MB109 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).
Reduce unused JavaScript
3.0 s · 999 KiBAbout 999 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Render-blocking requests
1.1 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 14
14/100Your mobile performance score is 14 (desktop: 42). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Hubspot and others), adding 2.2 MB and 1.9 s of main-thread time.
Google Tag Manager adds 897 ms
897 msGoogle Tag Manager costs a phone 897 ms of main-thread work and 1.0 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.
Hubspot adds 267 ms
267 msHubspot costs a phone 267 ms of main-thread work and 505 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.
Facebook adds 279 ms
279 msFacebook costs a phone 279 ms of main-thread work and 316 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 215 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 36 KiBPolyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 23 KiBAbout 23 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
130 ms · 2 KiB2 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Phones get a much slower page than desktops
Desktop scores 42 but mobile only 14. 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: 8 ms
8 msYour server sent the HTML in 8 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.
Real-user CLS: 0.59
0.59For real visitors the layout shifts by 0.59 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 59.1 s
59.1 sYour largest element takes 59.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Contamos con más de 300 modelos de máquinas herramienta par…”.
Speed Index: 17.6 s
17.6 sVisually, the page fills in at 17.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 63.4 s
63.4 sThe page becomes fully interactive after 63.4 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.
Cumulative Layout Shift: 0.402
0.402The layout shifts by 0.402 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Real-user INP: 225 ms
225 msReal visitors wait 225 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 50% slower for real visitors
+50%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 180 ms to 259 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
51 images without width and height
51 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.2 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 552 ms
552 msReal visitors wait 552 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 12.4 MB in 184 requests
12.4 MBYour homepage downloads 12.4 MB in 184 requests on a phone: images 9.7 MB (79), scripts 2.3 MB (45) and fonts 294 KiB (8). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
formatos-sitio-web-mobil.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
13 images far larger than shown
455 KiB13 images are downloaded at several times the size a phone draws them, for example formatos-sitio-web-mobil.png at 1,200 px wide, shown at 360 px. Resized copies would save about 455 KiB.
6 images below the first screen load straight away
6 images further down the page (418 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.5 g of CO₂ per visit
3.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.51 g of CO₂e: 420.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
37 images without alt text
37 images have no alt text, which hurts accessibility and image search.
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.
21 links without text
21 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Máquinas CNC” and “Soluciones para el tipo de industria que necesita…”). 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 crawlers can't follow
1 link has no real href, so search engines can't follow it.
159 internal links, 22 external
The homepage links to 159 pages on grupohitec.com and 22 external pages.
5 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “Descubre el catálogo más completo de máquinas CNC en México. Escala tu producción con marcas globales y equipos de alta…”.
Title: 55 characters
Your title is a healthy 55 characters: “Venta de máquinas CNC en MX, CO, EC y CR | Grupo Hi-Tec”.
Canonical URL set
The canonical URL is https://www.grupohitec.com/es/.
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.grupohitec.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.
Parts of the site are closed to 6 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
No llms.txt
There is no https://www.grupohitec.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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (1,338 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://www.grupohitec.com/es/maquinas/centro-de-torneado-horizontal and https://www.grupohitec.com/es/maquinas-grandes have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.grupohitec.com/en has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.grupohitec.com/es/maquinas/centros-de-maquinado-para-de-grafito took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 121 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
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
22 small tap targets
22 of 96 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 428 ()”.
5 low-resolution images
5 images are served at too low a resolution for sharp phone screens.
1 checks passed
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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,197 words of copy
The homepage carries about 1,197 words of visible text.
4 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Hotjar, HubSpot, LinkedIn Insight and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 3 mores (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.
22 cookies set on arrival
22Opening the homepage sets 22 cookies (measured from a US location before any click).
40 other companies contacted
Loading the homepage contacts 40 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 grupohitec.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
- HubSpot CMS
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- HubSpot
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on grupohitec.com, including 21 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.