Website review, no card needed

maquinter.com.mx logo

maquinter.com.mx website review

Visit site (opens in a new tab)Reviewed 24 October 202621 issues · 70 checks

This review found 21 issues worth fixing on maquinter.com.mx, 8 of them high impact, across 70 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of maquinter.com.mx (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. maquinter.com.mx at 0.4 s0.4 s
  2. maquinter.com.mx at 0.8 s0.8 s
  3. maquinter.com.mx at 1.1 s1.1 s
  4. maquinter.com.mx at 1.5 s1.5 s
  5. maquinter.com.mx at 1.9 s1.9 s
  6. maquinter.com.mx at 2.3 s2.3 s
  7. maquinter.com.mx at 2.6 s2.6 s
  8. maquinter.com.mx at 3.0 s3.0 s

Speed

2 to fix90
  • Render-blocking requests

    1.9 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.9 s.

  • Improve image delivery

    8.1 MB

    17 images could be 8.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    200 KiB

    3 files are served with short cache lifetimes, so returning visitors download them again (200 KiB).

  • 2 third-party services on the page

    2 third-party services load with your homepage (Facebook and Google Fonts), adding 311 KiB and 146 ms of main-thread time.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 109 ms. During a long task the page ignores taps.

  • Reduce unused JavaScript

    77 KiB

    About 77 KiB of JavaScript is downloaded but never used on this page.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

  • 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.

3 checks passed
  • Mobile performance score: 90

    90/100

    Your mobile performance score is 90 (desktop: 75). That is in Google's “good” band (90 and up).

  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 138 ms of it running JavaScript. That is comfortably low.

  • Server response: 21 ms

    21 ms

    Your server sent the HTML in 21 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix93
  • First Contentful Paint: 2.9 s

    2.9 s

    The first text or image appears after 2.9 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 2.9 s

    2.9 s

    Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Distribuidor líder de las marcas más confiables del mundo. …”.

  • Time to Interactive: 4.6 s

    4.6 s

    The page becomes fully interactive after 4.6 s. Good is under 3.8 s.

  • 4 images without width and height

    4 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.

3 checks passed
  • Speed Index: 2.9 s

    2.9 s

    Visually, the page fills in at 2.9 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.011

    0.011

    The layout barely moves while loading (CLS 0.011, good is under 0.1).

  • Total Blocking Time: 46 ms

    46 ms

    Scripts block the page for only 46 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 11.6 MB in 35 requests

    11.6 MB

    Your homepage downloads 11.6 MB in 35 requests on a phone: images 11.3 MB (27), scripts 226 KiB (2) and fonts 82 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 10 images over 500 KB

    10 images weigh 7.0 MB together. On a phone connection a single image that size takes seconds.

  • 12 images far larger than shown

    6.8 MB

    12 images are downloaded at several times the size a phone draws them, for example ars-21.jpg at 1,920 px wide, shown at 65 px. Resized copies would save about 6.8 MB.

  • 13 images in older formats

    13 images (7.8 MB) 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.

  • 13 images below the first screen load straight away

    13 images further down the page (7.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.3 g of CO₂ per visit

    3.29 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.29 g of CO₂e: 395.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

2 to fixGoogle 9696
  • 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.

  • All page content should be contained by landmarks (63 elements)

    All page content should be contained by landmarks: 63 elements on the page fail this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 31 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 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

1 to fixGoogle 10099
  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 65 internal links, 19 external

    The homepage links to 65 pages on maquinter.com.mx and 19 external pages.

8 checks passed
  • Meta description: 114 characters

    Your meta description is 114 characters: “MAQUINTER · 75 años distribuyendo maquinaria pesada en México. AMMANN, DIECI, PETTIBONE, INDECO, CAMS, ROBUST, HD.”.

  • One H1 headline

    Your main headline reads: “Maquinaria que Mueve México.”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “MAQUINTER — La maquinaria que mueve México · desde 1951”.

  • Canonical URL set

    The canonical URL is https://maquinter.com.mx/.

  • Structured data in place

    Structured data found: LocalBusiness and 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://maquinter.com.mx/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://maquinter.com.mx/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.

3 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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,226 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 13 links to non-canonical URLs

    Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://maquinter.com.mx/marcas, whose canonical is https://maquinter.com.mx/marcas.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 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.

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • 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

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute preserveAspectRatio: Unrecognized enumerated value, "xMidYEnd meet".”.

2 checks passed
  • Tap targets are thumb-sized

    26 of 28 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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.

  • About 1,011 words of copy

    The homepage carries about 1,011 words of visible text.

3 checks passed
  • Analytics in place

    Analytics detected: Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Meta Pixel (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.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 maquinter.com.mx, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Netlify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on maquinter.com.mx, including 6 speed issues, 1 SEO issue 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25