Website review, no card needed

proquimia.com logo

proquimia.com website review

Visit site (opens in a new tab)Reviewed 1 November 202644 issues · 88 checks

This review found 44 issues worth fixing on proquimia.com, 17 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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
3.6 s2.5 sMay 9Oct 243.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.7 s
May 16, 20262.7 s
May 23, 20262.7 s
May 30, 20262.6 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.9 s
Jul 4, 20263.2 s
Jul 11, 20263.4 s
Jul 18, 20263.5 s
Jul 25, 20263.4 s
Aug 1, 20263.3 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.2 s
Aug 29, 20263.1 s
Sep 5, 20263.0 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20263.0 s
Oct 24, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
214 ms116 msMay 9Oct 24142 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026203 ms
May 16, 2026203 ms
May 23, 2026197 ms
May 30, 2026181 ms
Jun 6, 2026183 ms
Jun 13, 2026184 ms
Jun 20, 2026184 ms
Jun 27, 2026180 ms
Jul 4, 2026166 ms
Jul 11, 2026146 ms
Jul 18, 2026141 ms
Jul 25, 2026140 ms
Aug 1, 2026131 ms
Aug 8, 2026130 ms
Aug 15, 2026129 ms
Aug 22, 2026128 ms
Aug 29, 2026127 ms
Sep 5, 2026128 ms
Sep 12, 2026131 ms
Sep 19, 2026130 ms
Sep 26, 2026131 ms
Oct 3, 2026135 ms
Oct 10, 2026132 ms
Oct 17, 2026136 ms
Oct 24, 2026142 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 proquimia.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. proquimia.com at 0.8 s0.8 s
  2. proquimia.com at 1.6 s1.6 s
  3. proquimia.com at 2.4 s2.4 s
  4. proquimia.com at 3.2 s3.2 s
  5. proquimia.com at 4.0 s4.0 s
  6. proquimia.com at 4.8 s4.8 s
  7. proquimia.com at 5.6 s5.6 s
  8. proquimia.com at 6.4 s6.4 s

Speed

13 to fix35
  • Reduce unused JavaScript

    5.9 s · 1.6 MB

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

  • Use efficient cache lifetimes

    5.0 s · 1.6 MB

    103 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

  • Render-blocking requests

    3.1 s

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 5.2 s

    A phone's processor spends 5.2 s on main-thread work while loading, 2.4 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 CDN, Google Tag Manager and timbal.ai and others), adding 8.8 MB and 1.2 s of main-thread time.

  • Vimeo adds 132 ms

    132 ms

    Vimeo costs a phone 132 ms of main-thread work and 6.2 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.

  • Reduce unused CSS

    450 ms · 137 KiB

    About 137 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Google CDN adds 429 ms

    429 ms

    Google CDN costs a phone 429 ms of main-thread work and 742 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.

  • Google Tag Manager adds 427 ms

    427 ms

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

  • timbal.ai adds 149 ms

    149 ms

    timbal.ai costs a phone 149 ms of main-thread work and 1.2 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.

  • 20 long tasks on the main thread

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

  • 2,041 HTML elements

    The page has 2,041 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    171 KiB

    9 images could be 171 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    50 ms · 27 KiB

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

  • Font display

    50 ms

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

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

1 checks passed
  • Server response: 225 ms

    225 ms

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

Core Web Vitals

11 to fix33
  • 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: 18.9 s

    18.9 s

    Your largest element takes 18.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 27.6 s

    27.6 s

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

  • Speed Index: 12.1 s

    12.1 s

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

  • Total Blocking Time: 847 ms

    847 ms

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 3.4 s

    3.4 s

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

  • Real-user CLS: 0.17

    0.17

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

  • Real-user FCP: 2.4 s

    2.4 s

    Real 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 s

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

  • Cumulative Layout Shift: 0.138

    0.138

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

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

    +13%

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

2 checks passed
  • Real-user INP: 143 ms

    143 ms

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

  • Tap response (INP) got 32% faster for real visitors

    -32%

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

Images and page weight

1 to fix70
  • Page weight: 11.0 MB in 193 requests

    11.0 MB

    Your homepage downloads 11.0 MB in 193 requests on a phone: other files 6.1 MB (42), scripts 3.2 MB (54) and images 1.0 MB (33). Under 2 MB keeps phones on slow connections fast.

  • 4 images below the first screen load straight away

    4 images further down the page (93 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.1 g of CO₂ per visit

    3.12 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

9 to fixGoogle 8589
  • Unlabelled dropdowns

    2 dropdowns have no label.

  • 10 text elements with low contrast

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

  • Frames without titles

    2 frames have no title, so screen-reader users cannot tell what they contain.

  • 6 images without alt text

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

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

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

  • 33 links without text

    33 visible links have no text or label, so screen readers cannot say where they go.

  • 9 form fields without a label

    9 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9288
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Productos de limpieza industrial - Proquimia, la química sostenible”.

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

  • 190 internal links, 10 external

    The homepage links to 190 pages on proquimia.com and 10 external pages.

6 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “PROQUIMIA, fabricantes y proveedores de productos de limpieza industrial y profesional sostenible y soluciones para pro…”.

  • One H1 headline

    Your main headline reads: “Soluciones químicas y productos de limpieza industrial sostenibles”.

  • Canonical URL set

    The canonical URL is https://www.proquimia.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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.proquimia.com/sitemap_index.xml.

AI search readiness

100
4 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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.proquimia.com/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 74 found) and read each the way a search engine does.

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

  • Every page has a meta description

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

Best practices

3 to fixGoogle 5488
  • 4 third-party cookies

    4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 10-field form

    Your longest form asks for 10 fields (4 required). Every extra field lowers completion.

  • 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 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 767 words of copy

    The homepage carries about 767 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Start search”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 3 of them by other companies (measured from a US location before any click).

  • 18 other companies contacted

    Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 proquimia.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
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Clouding

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on proquimia.com, including 24 speed issues, 3 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

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