Website review, no card needed
parquedelcafe.co website review
Visit site (opens in a new tab)Reviewed 28 October 202644 issues · 93 checks
This review found 44 issues worth fixing on parquedelcafe.co, 20 of them high impact, across 93 checks. The most urgent: improve image delivery. 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
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.8 s |
| Oct 10, 2026 | 4.6 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 4.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 173 ms |
| May 16, 2026 | 173 ms |
| May 23, 2026 | 174 ms |
| May 30, 2026 | 175 ms |
| Jun 6, 2026 | 177 ms |
| Jun 13, 2026 | 177 ms |
| Jun 20, 2026 | 177 ms |
| Jun 27, 2026 | 176 ms |
| Jul 4, 2026 | 177 ms |
| Jul 11, 2026 | 178 ms |
| Jul 18, 2026 | 177 ms |
| Jul 25, 2026 | 177 ms |
| Aug 1, 2026 | 174 ms |
| Aug 8, 2026 | 176 ms |
| Aug 15, 2026 | 181 ms |
| Aug 22, 2026 | 187 ms |
| Aug 29, 2026 | 194 ms |
| Sep 5, 2026 | 197 ms |
| Sep 12, 2026 | 199 ms |
| Sep 19, 2026 | 202 ms |
| Sep 26, 2026 | 202 ms |
| Oct 3, 2026 | 206 ms |
| Oct 10, 2026 | 210 ms |
| Oct 17, 2026 | 213 ms |
| Oct 24, 2026 | 216 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.7 s
1.4 s
2.2 s
2.9 s
3.6 s
4.3 s
5.0 s
5.7 s
Speed
Improve image delivery
5.4 s · 2.4 MB16 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.4 s faster on a phone.
Reduce unused JavaScript
1.3 s · 801 KiBAbout 801 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Render-blocking requests
1.9 s33 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Use efficient cache lifetimes
1.0 s · 323 KiB26 files are served with short cache lifetimes, so returning visitors download them again (323 KiB).
Mobile performance score: 32
32/100Your mobile performance score is 32 (desktop: 56). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 2.0 MB and 824 ms of main-thread time.
Reduce unused CSS
450 ms · 174 KiBAbout 174 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.
YouTube adds 371 ms
371 msYouTube costs a phone 371 ms of main-thread work and 998 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.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 256 ms
256 msGoogle Tag Manager costs a phone 256 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.
2,822 HTML elements
The page has 2,822 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
mailerlite.com adds 20 ms
20 msmailerlite.com costs a phone 20 ms of main-thread work and 309 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 197 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 7 KiB7 KiB could be saved by minifying CSS.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
50 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
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: 65 ms
65 msYour server sent the HTML in 65 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.
Real-user LCP: 5.8 s
5.8 sReal visitors wait 5.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.66
0.66For real visitors the layout shifts by 0.66 (75th percentile). Good is under 0.1.
Real-user FCP: 4.7 s
4.7 sReal visitors see the first content after 4.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.8 s
3.8 sReal visitors wait 3.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 26.1 s
26.1 sYour largest element takes 26.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BIENVENIDO A NUESTRO SITIO WEB OFICIAL ____________________…”.
Time to Interactive: 36.5 s
36.5 sThe page becomes fully interactive after 36.5 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.674
0.674The layout shifts by 0.674 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 9.3 s
9.3 sVisually, the page fills in at 9.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Real-user INP: 216 ms
216 msReal visitors wait 216 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 173 ms to 216 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 78% slower for real visitors
+78%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.8 s to 4.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 208 ms
208 msScripts block taps and scrolling for 208 ms in total while the page loads. Good is under 200 ms.
Images and page weight
Page weight: 8.4 MB in 152 requests
8.4 MBYour homepage downloads 8.4 MB in 152 requests on a phone: images 5.6 MB (31), scripts 1.7 MB (45) and fonts 685 KiB (17). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (425 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 2.4 g of CO₂ per visit
2.38 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.38 g of CO₂e: 285.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
7 text elements with low contrast
7 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.
All page content should be contained by landmarks (85 elements)
All page content should be contained by landmarks: 85 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (2 elements)
Contentinfo landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 19 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
86 internal links, 23 external
The homepage links to 86 pages on parquedelcafe.co and 23 external pages.
8 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Visita el Sitio Web oficial del Parque del Café. Uno de los principales parque temáticos de Latinoamérica situado en Qu…”.
One H1 headline
Your main headline reads: “Bienvenido al Parque Del Café”.
Title: 64 characters
Your title is a healthy 64 characters: “Parque del Café - Diversión con Sabor a Café - Sitio Web Oficial”.
Canonical URL set
The canonical URL is https://parquedelcafe.co/.
Structured data in place
Structured data found: BlogPosting, BreadcrumbList, Event, ImageObject and LocalBusiness.
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.
XML sitemap found
Your XML sitemap is reachable at https://parquedelcafe.co/sitemap.xml.
AI search readiness
No llms.txt
There is no https://parquedelcafe.co/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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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, sameAs (social profiles), description and contact details; logo would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,431 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages without a meta description
https://parquedelcafe.co/ruta-enamorate-del-cafe, https://parquedelcafe.co/atracciones/sala-de-experiencia-sensorial, https://parquedelcafe.co/tiendas/enamorate-del-cafe, https://parquedelcafe.co/atracciones/el-arte-del-cafe, https://parquedelcafe.co/arquitectura-y-cultura and https://parquedelcafe.co/atracciones and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://parquedelcafe.co/ruta-enamorate-del-cafe and https://parquedelcafe.co/arquitectura-y-cultura 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 41 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
6 small tap targets
6 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://assets.mailerlite.com/css/universal.css' from origin 'https://parquedelcafe.co' ha…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
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,034 words of copy
The homepage carries about 1,034 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, 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.
7 cookies set on arrival
7Opening the homepage sets 7 cookies, 1 of them by other companies (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.
24 other companies contacted
Loading the homepage contacts 24 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 parquedelcafe.co, 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
- Cloudflare
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 parquedelcafe.co, including 26 speed issues and 2 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.