Website review, no card needed
ipesa.com.pe website review
Visit site (opens in a new tab)Reviewed 30 October 202649 issues · 90 checks
This review found 49 issues worth fixing on ipesa.com.pe, 15 of them high impact, across 90 checks. The most urgent: page weight: 30.8 MB in 150 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 93 ms |
| May 16, 2026 | 93 ms |
| May 23, 2026 | 92 ms |
| May 30, 2026 | 93 ms |
| Jun 6, 2026 | 95 ms |
| Jun 13, 2026 | 97 ms |
| Jun 20, 2026 | 98 ms |
| Jun 27, 2026 | 102 ms |
| Jul 4, 2026 | 106 ms |
| Jul 11, 2026 | 108 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 111 ms |
| Aug 1, 2026 | 109 ms |
| Aug 8, 2026 | 109 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 120 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 126 ms |
| Sep 12, 2026 | 123 ms |
| Sep 19, 2026 | 130 ms |
| Sep 26, 2026 | 138 ms |
| Oct 3, 2026 | 144 ms |
| Oct 10, 2026 | 159 ms |
| Oct 17, 2026 | 161 ms |
| Oct 24, 2026 | 187 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.8 s
1.7 s
2.5 s
3.3 s
4.1 s
5.0 s
5.8 s
6.6 s
Speed
Google Tag Manager adds 1.3 s
1.3 sGoogle Tag Manager costs a phone 1.3 s of main-thread work and 1.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.3 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Improve image delivery
200 ms · 3.5 MB43 images could be 3.5 MB 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Unpkg and others), adding 2.0 MB and 1.6 s of main-thread time.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
924 KiBAbout 924 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
200 ms · 454 KiB11 files are served with short cache lifetimes, so returning visitors download them again (454 KiB).
Font display
600 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Facebook adds 250 ms
250 msFacebook costs a phone 250 ms of main-thread work and 296 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 245 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 32 KiBAbout 32 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 JavaScript
16 KiB16 KiB could be saved by minifying JavaScript.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Minify CSS
7 KiB7 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.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 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.
Time to Interactive: 45.0 s
45.0 sThe page becomes fully interactive after 45.0 s. Good is under 3.8 s.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 670 ms
670 msScripts block taps and scrolling for 670 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 219 ms
219 msReal visitors wait 219 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 87% slower for real visitors
+87%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 93 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 875 ms
875 msReal visitors wait 875 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.2 s
3.2 sYour largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 30.8 MB in 150 requests
30.8 MBYour homepage downloads 30.8 MB in 150 requests on a phone: images 28.5 MB (78), scripts 2.1 MB (32) and fonts 181 KiB (5). Under 2 MB keeps phones on slow connections fast.
9 images over 500 KB
9 images weigh 24.5 MB together. On a phone connection a single image that size takes seconds.
4 images far larger than shown
893 KiB4 images are downloaded at several times the size a phone draws them, for example final-2.png at 1,920 px wide, shown at 390 px. Resized copies would save about 893 KiB.
30 images in older formats
30 images (28.2 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.
9 images below the first screen load straight away
9 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 8.7 g of CO₂ per visit
8.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.74 g of CO₂e: 1048.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
17 text elements with low contrast
17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
173 form fields without a label
173 form fields have no label, so screen readers announce an empty box and autofill guesses.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (84 characters)
Your title is 84 characters, so Google will cut it off around 60: “Venta de Maquinaria Pesada | Máquinas industriales, Construcción y agrícolas | Ipesa”.
Structured data has 1 problem
Structured data found (LocalBusiness, Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("{search_term_string}")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
78 internal links, 14 external
The homepage links to 78 pages on ipesa.com.pe and 14 external pages.
4 checks passed
Meta description: 99 characters
Your meta description is 99 characters: “Venta de maquinaria pesada, máquinas industriales, máquinas agrícolas y maquinaria de construcción.”.
Canonical URL set
The canonical URL is https://www.ipesa.com.pe/.
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.ipesa.com.pe/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.ipesa.com.pe/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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (549 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.ipesa.com.pe/catalogo/agricola/equipos-yanmar and https://www.ipesa.com.pe/catalogo/agricola/dron-agricola all use the title “IPESA SAC”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.ipesa.com.pe/catalogo/agricola/equipos-yanmar and https://www.ipesa.com.pe/catalogo/agricola/dron-agricola 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 58 found) and read each the way a search engine does.
6 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.
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
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
6 small tap targets
6 of 8 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'insertBefore')”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
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.
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 8-field form
Your longest form asks for 8 fields (0 required). Every extra field lowers completion.
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 387 words of copy
The homepage carries about 387 words of visible text.
4 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and 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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
9 other companies contacted
Loading the homepage contacts 9 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 ipesa.com.pe, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- DigitalOcean
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on ipesa.com.pe, 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.