Website review, no card needed
caterpillarpa.com website review
Visit site (opens in a new tab)Reviewed 5 November 202642 issues · 87 checks
This review found 42 issues worth fixing on caterpillarpa.com, 11 of them high impact, across 87 checks. The most urgent: fails Core Web Vitals for real visitors. 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
71C- #100,544 of 124,862 reviewed websitesbeats 17%
- #61,367 of 70,056 online storesbeats 10%
- #56,909 of 63,671 Shopify storesbeats 9%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.2 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 4.4 s |
| Jul 4, 2026 | 5.0 s |
| Jul 11, 2026 | 5.3 s |
| Jul 18, 2026 | 5.2 s |
| Jul 25, 2026 | 4.7 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 218 ms |
| May 23, 2026 | 193 ms |
| May 30, 2026 | 198 ms |
| Jun 6, 2026 | 188 ms |
| Jun 13, 2026 | 177 ms |
| Jun 20, 2026 | 159 ms |
| Jun 27, 2026 | 197 ms |
| Jul 4, 2026 | 258 ms |
| Jul 11, 2026 | 291 ms |
| Jul 18, 2026 | 318 ms |
| Jul 25, 2026 | 344 ms |
| Aug 1, 2026 | 376 ms |
| Aug 8, 2026 | 392 ms |
| Aug 15, 2026 | 383 ms |
| Aug 22, 2026 | 348 ms |
| Aug 29, 2026 | 313 ms |
| Sep 5, 2026 | 301 ms |
| Sep 12, 2026 | 314 ms |
| Sep 19, 2026 | 341 ms |
| Sep 26, 2026 | 360 ms |
| Oct 3, 2026 | 368 ms |
| Oct 10, 2026 | 358 ms |
| Oct 17, 2026 | 340 ms |
| Oct 24, 2026 | 318 ms |
| Oct 31, 2026 | 303 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.6 s
2.4 s
3.2 s
4.0 s
4.7 s
5.5 s
6.3 s
Speed
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Facebook and huracdn.com and others), adding 1.1 MB and 823 ms of main-thread time.
Google Tag Manager adds 457 ms
457 msGoogle Tag Manager costs a phone 457 ms of main-thread work and 487 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.
Reduce unused CSS
300 ms · 74 KiBAbout 74 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
300 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Reduce unused JavaScript
283 KiBAbout 283 KiB of JavaScript is downloaded but never used on this page.
2,744 HTML elements
The page has 2,744 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 78 ms
78 msShopify costs a phone 78 ms of main-thread work and 351 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.
Use efficient cache lifetimes
205 KiB7 files are served with short cache lifetimes, so returning visitors download them again (205 KiB).
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 204 ms. During a long task the page ignores taps.
Improve image delivery
197 KiB7 images could be 197 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Duplicated JavaScript
63 KiB63 KiB JavaScript is shipped twice across bundles.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 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: 11.1 s
11.1 sThe page becomes fully interactive after 11.1 s. Good is under 3.8 s.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 376 ms
376 msReal visitors wait 376 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 51% slower for real visitors
+51%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 218 ms to 303 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 416 ms
416 msScripts block taps and scrolling for 416 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Speed Index: 3.7 s
3.7 sVisually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 38% faster for real visitors
-38%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.2 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.7 MB in 300 requests
3.7 MBYour homepage downloads 3.7 MB in 300 requests on a phone: images 1.4 MB (38), scripts 1.2 MB (145) and other files 757 KiB (101). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
ecom_1080x1080_ee600258-70ca-4ce5-a8ba-36d58c86abe9.jpg 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).
6 images in older formats
6 images (383 KiB) 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.
About 1.1 g of CO₂ per visit
1.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 127.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
3 elements use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
Hidden but focusable
15 elements hidden from screen readers can still receive keyboard focus.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
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.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (11 elements)
Alternative text of images should not be repeated as text: 11 elements on the page fail this check, rated minor by axe-core.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 106 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (6 characters)
Your title is only 6 characters: “Panamá”. Between 30 and 65 characters leaves room to say what you do and for whom.
164 internal links, 8 external
The homepage links to 164 pages on caterpillarpa.com and 8 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Panamá”.
Canonical URL set
The canonical URL is https://caterpillarpa.com/.
Structured data in place
Structured data found: 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://caterpillarpa.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (1,090 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://caterpillarpa.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://caterpillarpa.com/collections/calzado-hombre, https://caterpillarpa.com/collections/botas-hombre, https://caterpillarpa.com/collections/botas-industrial-hombre, https://caterpillarpa.com/collections/tenis-hombre, https://caterpillarpa.com/collections/ropa-hombre-1 and https://caterpillarpa.com/collections/camisetas-hombre and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://caterpillarpa.com/collections/calzado-hombre, https://caterpillarpa.com/collections/botas-hombre, https://caterpillarpa.com/collections/botas-industrial-hombre, https://caterpillarpa.com/collections/tenis-hombre, https://caterpillarpa.com/collections/ropa-hombre-1 and https://caterpillarpa.com/collections/camisetas-hombre and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 72 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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
25 of 28 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 241 words
The homepage has only about 241 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Shop New Arrivals”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager 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.
9 cookies set on arrival
9Opening the homepage sets 9 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 caterpillarpa.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Encuestas Cat · huracdn.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on caterpillarpa.com, including 21 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.