Website review, no card needed

duromex.com.mx logo

duromex.com.mx website review

Visit site (opens in a new tab)Reviewed 21 October 202645 issues · 92 checks

This review found 45 issues worth fixing on duromex.com.mx, 22 of them high impact, across 92 checks. The most urgent: avoid multiple page redirects. 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

Real-visitor load time (LCP)75th percentile, phones
2.4 s1.4 sMay 2Oct 171.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.8 s
May 9, 20261.5 s
May 16, 20261.6 s
May 23, 20261.7 s
May 30, 20261.8 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jun 27, 20262.0 s
Jul 4, 20261.8 s
Jul 11, 20261.9 s
Jul 18, 20262.0 s
Jul 25, 20262.1 s
Aug 1, 20262.2 s
Aug 8, 20262.1 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.9 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.9 s
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
201 ms123 msMay 2Oct 17183 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026144 ms
May 9, 2026155 ms
May 16, 2026162 ms
May 23, 2026162 ms
May 30, 2026175 ms
Jun 6, 2026192 ms
Jun 13, 2026192 ms
Jun 20, 2026180 ms
Jun 27, 2026161 ms
Jul 4, 2026146 ms
Jul 11, 2026132 ms
Jul 18, 2026138 ms
Jul 25, 2026140 ms
Aug 1, 2026154 ms
Aug 8, 2026151 ms
Aug 15, 2026150 ms
Aug 22, 2026147 ms
Aug 29, 2026140 ms
Sep 5, 2026144 ms
Sep 12, 2026156 ms
Sep 19, 2026163 ms
Sep 26, 2026169 ms
Oct 3, 2026182 ms
Oct 10, 2026190 ms
Oct 17, 2026183 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

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

How it loaded on a phone

  1. duromex.com.mx at 2.0 s2.0 s
  2. duromex.com.mx at 4.0 s4.0 s
  3. duromex.com.mx at 5.9 s5.9 s
  4. duromex.com.mx at 7.9 s7.9 s
  5. duromex.com.mx at 9.9 s9.9 s
  6. duromex.com.mx at 11.9 s11.9 s
  7. duromex.com.mx at 13.9 s13.9 s
  8. duromex.com.mx at 15.8 s15.8 s

Speed

11 to fix22
  • Avoid multiple page redirects

    14.7 s

    The page goes through 1 redirect before it starts loading, costing about 14.7 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    10.8 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.8 s faster on a phone.

  • Use efficient cache lifetimes

    3.1 s · 511 KiB

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

  • Render-blocking requests

    2.4 s

    11 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.

  • Mobile performance score: 22

    22/100

    Your mobile performance score is 22 (desktop: 40). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 5.0 s

    A phone's processor spends 5.0 s on main-thread work while loading, 3.0 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, Hubspot and Shopify and others), adding 1.5 MB and 575 ms of main-thread time.

  • Font display

    350 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).

  • Legacy JavaScript

    300 ms · 18 KiB

    Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 247 ms

    247 ms

    Google Tag Manager costs a phone 247 ms of main-thread work and 524 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.

  • Hubspot adds 180 ms

    180 ms

    Hubspot costs a phone 180 ms of main-thread work and 476 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.

  • Improve image delivery

    250 ms · 39 KiB

    3 images could be 39 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • 16 long tasks on the main thread

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

  • Reduce unused CSS

    11 KiB

    About 11 KiB of CSS is downloaded but never applied on this page.

  • Minify CSS

    6 KiB

    6 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: 5 ms

    5 ms

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

Core Web Vitals

10 to fix100
  • 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.

  • First Contentful Paint: 8.1 s

    8.1 s

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

  • Largest Contentful Paint: 25.5 s

    25.5 s

    Your largest element takes 25.5 s to render on a phone. Google's threshold for “good” is 2.5 s.

  • Speed Index: 19.2 s

    19.2 s

    Visually, the page fills in at 19.2 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 33.3 s

    33.3 s

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

  • Cumulative Layout Shift: 0.846

    0.846

    The layout shifts by 0.846 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) got 25% slower for real visitors

    +25%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 144 ms to 183 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user TTFB: 940 ms

    940 ms

    Real visitors wait 940 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 382 ms

    382 ms

    Scripts block taps and scrolling for 382 ms in total while the page loads. Good is under 200 ms.

  • 14 images without width and height

    14 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) got 10% slower for real visitors

    +10%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

    Real visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 182 ms

    182 ms

    Real visitors wait 182 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.7 s

    1.7 s

    Real visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.

Images and page weight

1 to fix70
  • Page weight: 5.0 MB in 212 requests

    5.0 MB

    Your homepage downloads 5.0 MB in 212 requests on a phone: scripts 3.6 MB (67), fonts 679 KiB (19) and images 428 KiB (55). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.42 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

11 to fixGoogle 7183
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 15 text elements with low contrast

    15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • Orphan list items

    Some list items are not inside a list.

  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 25 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.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h5, h2 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 40 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: 40 passed and 11 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8584
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is short (30 characters)

    Your meta description is only 30 characters: “Solicita más información sobre”. 70 to 160 characters is enough to sell the click.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • One H1 headline

    Your <h1> is empty.

  • 72 internal links, 8 external

    The homepage links to 72 pages on duromex.com.mx and 8 external pages.

5 checks passed
  • Title: 48 characters

    Your title is a healthy 48 characters: “Durotest, tecnología e innovación en iluminación”.

  • Canonical URL set

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

  • 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://durotest.com.mx/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://durotest.com.mx/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix81
  • 1 page points its canonical at the homepage

    https://durotest.com.mx/products/dicroled declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://durotest.com.mx/products/dicroled all use the title “Durotest, tecnología e innovación en iluminación”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages share a meta description

    https://durotest.com.mx/collections/all, https://durotest.com.mx/collections/led, https://durotest.com.mx/collections/tubos-de-led, https://durotest.com.mx/collections/focos-ahorradores-de-led, https://durotest.com.mx/products/dicroled and https://durotest.com.mx/collections/luminarios-de-led and 1 other use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 53 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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 500 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • 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 316 words of copy

    The homepage carries about 316 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Hotjar and HubSpot.

  • Direct contact links

    Visitors can reach you directly: 2 phone links 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

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel (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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies (measured from a US location before any click).

  • 29 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on duromex.com.mx, including 21 speed issues, 4 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

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