Website review, no card needed

calypso.la logo

calypso.la website review

Visit site (opens in a new tab)Reviewed 26 October 202646 issues · 71 checks

This review found 46 issues worth fixing on calypso.la, 22 of them high impact, across 71 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
6.3 s2.4 sMay 9Oct 243.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.9 s
May 16, 20264.9 s
May 23, 20265.9 s
May 30, 20265.8 s
Jun 6, 20265.8 s
Jun 13, 20265.8 s
Jun 20, 20265.7 s
Jun 27, 20265.6 s
Jul 4, 20262.8 s
Jul 11, 20262.9 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20263.3 s
Aug 8, 20263.4 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Sep 26, 20263.4 s
Oct 3, 20263.3 s
Oct 10, 20263.4 s
Oct 17, 20263.3 s
Oct 24, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
803 ms60 msMay 9Oct 17146 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026717 ms
May 16, 2026632 ms
Sep 26, 2026150 ms
Oct 3, 2026146 ms
Oct 10, 2026150 ms
Oct 17, 2026146 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

Full-page screenshot of calypso.la (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. calypso.la at 0.4 s0.4 s
  2. calypso.la at 0.8 s0.8 s
  3. calypso.la at 1.1 s1.1 s
  4. calypso.la at 1.5 s1.5 s
  5. calypso.la at 1.9 s1.9 s
  6. calypso.la at 2.3 s2.3 s
  7. calypso.la at 2.6 s2.6 s
  8. calypso.la at 3.0 s3.0 s

Speed

6 to fix42
  • Use efficient cache lifetimes

    38.5 s · 20.7 MB

    45 files are served with short cache lifetimes, so returning visitors download them again (20.7 MB).

  • Improve image delivery

    38.5 s · 20.4 MB

    48 images could be 20.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 38.5 s faster on a phone.

  • Render-blocking requests

    1.6 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.6 s.

  • Mobile performance score: 42

    42/100

    Your mobile performance score is 42 (desktop: 51). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Other Google APIs/SDKs, dapta.ai and Cloudflare CDN and others), adding 21.1 MB and 37 ms of main-thread time.

  • cloudfront.net adds 0 ms

    0 ms

    cloudfront.net costs a phone 0 ms of main-thread work and 20.7 MB 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

    150 ms · 18 KiB

    About 18 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.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 97 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Reduce unused JavaScript

    25 KiB

    About 25 KiB of JavaScript is downloaded but never used on this page.

  • 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.

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 344 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

    Your server sent the HTML in 1 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix33
  • 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 CLS: 0.46

    0.46

    For real visitors the layout shifts by 0.46 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 55.7 s

    55.7 s

    Your largest element takes 55.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Usamos cookies para mejorar tu experiencia de navegación, a…”.

  • Time to Interactive: 56.3 s

    56.3 s

    The page becomes fully interactive after 56.3 s. Good is under 3.8 s.

  • First Contentful Paint: 4.6 s

    4.6 s

    The first text or image appears after 4.6 s on a phone. Good is under 1.8 s.

  • Cumulative Layout Shift: 0.522

    0.522

    The layout shifts by 0.522 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user LCP: 3.8 s

    3.8 s

    Real visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 2.9 s

    2.9 s

    Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

  • Speed Index: 4.6 s

    4.6 s

    Visually, the page fills in at 4.6 s (Speed Index). Good is under 3.4 s.

  • 18 images without width and height

    18 images have no width and height attributes, so the layout jumps as each one loads.

5 checks passed
  • Real-user INP: 138 ms

    138 ms

    Real visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user TTFB: 767 ms

    767 ms

    Real visitors wait 767 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 78% faster for real visitors

    -78%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 717 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 28% faster for real visitors

    -28%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.9 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 62 ms

    62 ms

    Scripts block the page for only 62 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix25
  • Page weight: 21.6 MB in 84 requests

    21.6 MB

    Your homepage downloads 21.6 MB in 84 requests on a phone: images 20.9 MB (49), fonts 332 KiB (6) and scripts 321 KiB (22). Under 2 MB keeps phones on slow connections fast.

  • 21 images over 500 KB

    21 images weigh 15.2 MB together. On a phone connection a single image that size takes seconds.

  • 37 images far larger than shown

    15.4 MB

    37 images are downloaded at several times the size a phone draws them, for example BX0EBC1DlGF0O10.png at 1,000 px wide, shown at 138 px. Resized copies would save about 15.4 MB.

  • 39 images in older formats

    39 images (18.7 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.

  • About 6.1 g of CO₂ per visit

    6.13 g

    By the Sustainable Web Design model, a visit to your homepage emits about 6.13 g of CO₂e: 735.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

7 to fixGoogle 8190
  • 17 buttons without a name

    17 buttons have no accessible name, so screen readers announce just “button”.

  • 17 tap targets too small

    17 tap targets are too small or too close together to hit reliably with a finger.

  • 6 text elements with low contrast

    6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 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.

  • Alternative text of images should not be repeated as text (32 elements)

    Alternative text of images should not be repeated as text: 32 elements on the page fail this check, rated minor by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

9 to fixGoogle 8352
  • 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.

  • Title is short (7 characters)

    Your title is only 7 characters: “Calypso”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://calypso.la/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at calypso.la/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

AI search readiness

2 to fix42
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 227 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://calypso.la/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.

Best practices

2 to fixGoogle 9287
  • 15 small tap targets

    15 of 55 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Permissions policy violation: Geolocation access has been blocked because of a permissions policy applied to the curren…”.

  • 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

6 to fix25
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 227 words

    The homepage has only about 227 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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.

Privacy and tracking

  • 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.

  • 6 other companies contacted

    Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 calypso.la, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on calypso.la, including 16 speed issues, 9 SEO issues and 6 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25