Website review, no card needed
corachan.com website review
Visit site (opens in a new tab)Reviewed 29 October 202635 issues · 85 checks
This review found 35 issues worth fixing on corachan.com, 11 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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
80BClosest 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.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 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.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 112 ms |
| May 16, 2026 | 113 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 114 ms |
| Jun 20, 2026 | 115 ms |
| Jun 27, 2026 | 115 ms |
| Jul 4, 2026 | 115 ms |
| Jul 11, 2026 | 115 ms |
| Jul 18, 2026 | 115 ms |
| Jul 25, 2026 | 116 ms |
| Aug 1, 2026 | 116 ms |
| Aug 8, 2026 | 116 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 115 ms |
| Aug 29, 2026 | 115 ms |
| Sep 5, 2026 | 113 ms |
| Sep 12, 2026 | 114 ms |
| Sep 19, 2026 | 115 ms |
| Sep 26, 2026 | 115 ms |
| Oct 3, 2026 | 117 ms |
| Oct 10, 2026 | 117 ms |
| Oct 17, 2026 | 116 ms |
| Oct 24, 2026 | 117 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.1 s
2.8 s
3.5 s
4.2 s
4.9 s
5.6 s
Speed
Use efficient cache lifetimes
2.4 s · 1.2 MB62 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).
Render-blocking requests
3.5 s28 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.
Reduce unused JavaScript
1.2 s · 321 KiBAbout 321 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Sentry and Facebook and others), adding 866 KiB and 862 ms of main-thread time.
Improve image delivery
300 ms · 254 KiB8 images could be 254 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 344 ms
344 msGoogle Tag Manager costs a phone 344 ms of main-thread work and 515 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.
Legacy JavaScript
150 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
150 ms · 21 KiB21 KiB could be saved by minifying JavaScript.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 170 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 15 KiBAbout 15 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.
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 CSS
4 KiB4 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 925 ms of it running JavaScript. That is comfortably low.
Server response: 98 ms
98 msYour server sent the HTML in 98 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.5 s
10.5 sYour largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CLÍNICA CORACHAN Fans of health Book an appointment via Wha…”.
Time to Interactive: 14.0 s
14.0 sThe page becomes fully interactive after 14.0 s. Good is under 3.8 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Speed Index: 7.0 s
7.0 sVisually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 217 ms
217 msScripts block taps and scrolling for 217 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 112 ms to 117 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 103 ms
103 msReal visitors wait 103 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 637 ms
637 msReal visitors wait 637 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 2.0 MB in 107 requests
2.0 MBYour homepage downloads 2.0 MB in 107 requests on a phone: scripts 1.0 MB (31), images 835 KiB (41) and fonts 96 KiB (3). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
50 KiB1 image is downloaded at several times the size a phone draws it, for example default.png at 300 px wide, shown at 40 px. Resized copies would save about 50 KiB.
3 images in older formats
3 images (334 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 0.6 g of CO₂ per visit
0.57 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.57 g of CO₂e: 68.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 6 failed. 2 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 structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
18 H1 headlines
There are 18 <h1> headlines (“image/svg+xml”, “Main navigation” and “Manage your appointments without waiting”). One clear main headline is easier for people and search engines.
No XML sitemap
No XML sitemap at https://www.corachan.com/sitemap.xml, so Google discovers your pages only by following links.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
130 internal links, 31 external
The homepage links to 130 pages on corachan.com and 31 external pages.
3 checks passed
Title: 35 characters
Your title is a healthy 35 characters: “Clínica Corachan | Clínica Corachan”.
Canonical URL set
The canonical URL is https://www.corachan.com/en.
robots.txt in place
robots.txt is in place.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.corachan.com/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.
1 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.
Other pages
5 pages share 2 titles
https://www.corachan.com/en, https://www.corachan.com/es and https://www.corachan.com/ca all use the title “Clínica Corachan | Clínica Corachan”, and 1 other title repeat too. 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://www.corachan.com/es, https://www.corachan.com/ca, https://www.corachan.com/en/patients-access_103141, https://www.corachan.com/en/citaonline, https://www.corachan.com/resultados-analiticas_251111 and https://www.corachan.com/en/clinica-corachan_4071 and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.corachan.com/resultados-analiticas_251111, whose canonical is https://www.corachan.com/en/analysis-results_251111. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages slow to respond
https://www.corachan.com/en/patients-access_103141, https://www.corachan.com/resultados-analiticas_251111, https://www.corachan.com/en/clinica-corachan_4071, https://www.corachan.com/en/who-we-are_4501 and https://www.corachan.com/en/insurance-companies_4769 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 88 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 14 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 38 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 122 words
The homepage has only about 122 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book an appointment via WhatsApp” and “Request an appointment online”.
9 calls to action
The homepage has 9 calls to action, for example “Contact”, “Contact phone numbers” and “Contact form”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
14 cookies set on arrival
14Opening the homepage sets 14 cookies (measured from a US location before any click).
26 other companies contacted
Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 corachan.com, 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 Tag Manager
- Hosting
- Akamai Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on corachan.com, including 13 speed issues, 5 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.