Website review, no card needed
hwp.cr website review
Visit site (opens in a new tab)Reviewed 25 October 202648 issues · 94 checks
This review found 48 issues worth fixing on hwp.cr, 22 of them high impact, across 94 checks. The most urgent: render-blocking 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
69DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
2.1 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Use efficient cache lifetimes
1.1 s · 945 KiB83 files are served with short cache lifetimes, so returning visitors download them again (945 KiB).
YouTube adds 1.3 s
1.3 sYouTube costs a phone 1.3 s of main-thread work and 2.9 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.
Mobile performance score: 43
43/100Your mobile performance score is 43 (desktop: 57). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.6 s
A phone's processor spends 7.6 s on main-thread work while loading, 3.7 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 (YouTube, Google CDN and Google Tag Manager and others), adding 4.9 MB and 2.0 s of main-thread time.
Reduce unused JavaScript
2.4 MBAbout 2.4 MB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
600 ms · 300 KiBAbout 300 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Google CDN adds 363 ms
363 msGoogle CDN costs a phone 363 ms of main-thread work and 734 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 378 ms. During a long task the page ignores taps.
1,502 HTML elements
The page has 1,502 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
behance.net adds 83 ms
83 msbehance.net costs a phone 83 ms of main-thread work and 437 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.
Vimeo adds 34 ms
34 msVimeo costs a phone 34 ms of main-thread work and 514 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
200 ms · 134 KiB6 images could be 134 KiB 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.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need.
Minify CSS
21 KiB21 KiB could be saved by minifying CSS.
Minify JavaScript
18 KiB18 KiB could be saved by minifying JavaScript.
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: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 47.8 s
47.8 sThe page becomes fully interactive after 47.8 s. Good is under 3.8 s.
Speed Index: 13.4 s
13.4 sVisually, the page fills in at 13.4 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.3 s
5.3 sYour largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
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.
Total Blocking Time: 914 ms
914 msScripts block taps and scrolling for 914 ms in total while the page loads. Good is under 200 ms.
33 images without width and height
33 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 9.4 MB in 224 requests
9.4 MBYour homepage downloads 9.4 MB in 224 requests on a phone: scripts 4.6 MB (71), images 2.9 MB (68) and fonts 842 KiB (9). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
236 KiB3 images are downloaded at several times the size a phone draws them, for example Logo-Esencial-cr-hwp.png at 3,300 px wide, shown at 350 px. Resized copies would save about 236 KiB.
11 images below the first screen load straight away
11 images further down the page (492 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
6 images in older formats
6 images (433 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.7 g of CO₂ per visit
2.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.67 g of CO₂e: 320.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must be contained by particular parents (2 elements)
Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.
Unlabelled dropdowns
1 dropdown has no label.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (3 elements)
Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail 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.
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.
40 links without text
40 visible links have no text or label, so screen readers cannot say where they go.
11 form fields without a label
11 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 52 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 13 failed. 4 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.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
28 internal links, 22 external
The homepage links to 28 pages on hwp.cr and 22 external pages.
6 checks passed
Title: 58 characters
Your title is a healthy 58 characters: “Inicio - HWP COSTA RICA | Agencia de Publicidad y Negocios”.
Canonical URL set
The canonical URL is https://hwp.cr/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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://hwp.cr/sitemap.xml.
AI search readiness
No llms.txt
There is no https://hwp.cr/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: 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 (606 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages point its canonical at the homepage
https://hwp.cr/page/2, https://hwp.cr/page/3 and https://hwp.cr/page/7 declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
4 pages share a title
/, https://hwp.cr/page/2, https://hwp.cr/page/3 and https://hwp.cr/page/7 all use the title “Inicio - HWP COSTA RICA | Agencia de Publicidad y Negocios”. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://hwp.cr/blog, https://hwp.cr/healthcare, https://hwp.cr/creatividad-humana-vs-ia-nadie-pierde, https://hwp.cr/category/sin-categoria, https://hwp.cr/hwp-culmina-el-2025-con-tres-reconocimientos-internacionales-por-su-innovacion-y-transparencia-empresarial and https://hwp.cr/5-oportunidades-claves-para-empresas-en-costa-rica-estrategias-publicitarias-para-impulsar-su-crecimiento and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://hwp.cr/page/2, https://hwp.cr/page/3, https://hwp.cr/page/7 and https://hwp.cr/en have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://hwp.cr/healthcare took over 3 s to send its HTML from our server.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 13 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
9 small tap targets
9 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
7 third-party cookies
7 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.”).
1 JavaScript error while loading
1 error was 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”).
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.
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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 569 words of copy
The homepage carries about 569 words of visible text.
5 checks passed
1 call to action
The homepage has 1 call to action, for example “Sign Up”.
3 short forms
3 short forms (5 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 30 customer or partner logos and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and HubSpot.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
5 trackers load before any consent
5Before 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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 3 of them by other companies (measured from a US location before any click).
32 other companies contacted
Loading the homepage contacts 32 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 hwp.cr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on hwp.cr, including 19 speed issues, 3 SEO 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.