Website review, no card needed

changinglife.cl logo

changinglife.cl website review

Visit site (opens in a new tab)Reviewed 23 October 202633 issues · 89 checks

This review found 33 issues worth fixing on changinglife.cl, 12 of them high impact, across 89 checks. The most urgent: render-blocking requests. 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
2.6 s1.5 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.3 s
May 16, 20262.1 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20261.9 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
147 ms134 msMay 2Oct 17135 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026140 ms
May 9, 2026139 ms
May 16, 2026143 ms
May 23, 2026145 ms
May 30, 2026143 ms
Jun 6, 2026143 ms
Jun 13, 2026138 ms
Jun 20, 2026137 ms
Jun 27, 2026138 ms
Jul 4, 2026139 ms
Jul 11, 2026143 ms
Jul 18, 2026138 ms
Jul 25, 2026136 ms
Aug 1, 2026136 ms
Aug 8, 2026135 ms
Aug 15, 2026138 ms
Aug 22, 2026144 ms
Aug 29, 2026137 ms
Sep 5, 2026137 ms
Sep 12, 2026137 ms
Sep 19, 2026135 ms
Sep 26, 2026137 ms
Oct 3, 2026137 ms
Oct 10, 2026137 ms
Oct 17, 2026135 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 changinglife.cl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. changinglife.cl at 0.5 s0.5 s
  2. changinglife.cl at 0.9 s0.9 s
  3. changinglife.cl at 1.4 s1.4 s
  4. changinglife.cl at 1.9 s1.9 s
  5. changinglife.cl at 2.4 s2.4 s
  6. changinglife.cl at 2.8 s2.8 s
  7. changinglife.cl at 3.3 s3.3 s
  8. changinglife.cl at 3.8 s3.8 s

Speed

11 to fix48
  • Render-blocking requests

    8.0 s

    10 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.0 s.

  • Mobile performance score: 48

    48/100

    Your mobile performance score is 48 (desktop: 58). 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 (website-files.com, Cookie-Script.com and cloudfront.net and others), adding 5.5 MB and 645 ms of main-thread time.

  • website-files.com adds 425 ms

    425 ms

    website-files.com costs a phone 425 ms of main-thread work and 4.5 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 JavaScript

    600 ms · 213 KiB

    About 213 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 89 KiB

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

  • Improve image delivery

    403 KiB

    7 images could be 403 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Main-thread work: 2.8 s

    A phone's processor spends 2.8 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 1,892 HTML elements

    The page has 1,892 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Adobe TypeKit adds 16 ms

    16 ms

    Adobe TypeKit costs a phone 16 ms of main-thread work and 506 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.

  • sleak.chat adds 5 ms

    5 ms

    sleak.chat costs a phone 5 ms of main-thread work and 409 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.

  • 7 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Use efficient cache lifetimes

    43 KiB

    10 files are served with short cache lifetimes, so returning visitors download them again (43 KiB).

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

  • Legacy JavaScript

    5 KiB

    Polyfills for old browsers add 5 KiB JavaScript that modern phones do not need.

1 checks passed
  • Server response: 5 ms

    5 ms

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

Core Web Vitals

5 to fix100
  • First Contentful Paint: 12.5 s

    12.5 s

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

  • Largest Contentful Paint: 14.9 s

    14.9 s

    Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “JOUW DOEL PLAN RESULTAAT Van alles geprobeerd, maar val je …”.

  • Speed Index: 12.5 s

    12.5 s

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

  • Time to Interactive: 14.9 s

    14.9 s

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

  • Total Blocking Time: 343 ms

    343 ms

    Scripts block taps and scrolling for 343 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) held steady for real visitors

    -3%

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

8 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.6 s

    1.6 s

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

  • Real-user INP: 136 ms

    136 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 393 ms

    393 ms

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

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

    -29%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 6.1 MB in 123 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 123 requests on a phone: images 3.8 MB (47), fonts 1.5 MB (33) and scripts 651 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    211 KiB

    3 images are downloaded at several times the size a phone draws them, for example 69e92dd228b391c644fa6350_Het-persoonlijke-plan-van-Yvonne-tr at 1,080 px wide, shown at 168 px. Resized copies would save about 211 KiB.

  • About 1.7 g of CO₂ per visit

    1.73 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.73 g of CO₂e: 207.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

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

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • 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 (96 elements)

    All page content should be contained by landmarks: 96 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 9 links without text

    9 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 64 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096
  • Structured data has 2 problems

    Structured data found (FAQPage, LocalBusiness, OfferCatalog and VideoObject) but with 2 problems, for example “VideoObject: contentUrl is not an absolute URL ("URL_NAAR_VIDEO_1")”.

  • 80 internal links, 10 external

    The homepage links to 80 pages on changinglife.cl and 10 external pages.

7 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Afvallen, sterker of fitter worden? Ontvang een op maat gemaakt plan van onze experts en online coaching, met Resultaat…”.

  • One H1 headline

    Your main headline reads: “Bouw aan blijvend resultaat met een persoonlijk plan en 1-op-1 begeleiding.”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “Jouw persoonlijke plan met 1-op-1 coaching”.

  • Canonical URL set

    The canonical URL is https://www.changinglife.nl/.

  • 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://www.changinglife.nl/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.changinglife.nl/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.

2 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 (3,664 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 2 pages without an H1

    https://www.changinglife.nl/starten and https://www.changinglife.nl/algemene-voorwaarden 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 26 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 9687
  • 21 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

  • 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 4,522 words of copy

    The homepage carries about 4,522 words of visible text.

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Neem contact op” and “Contact”.

  • Social proof on the page

    Social proof on the homepage: a star rating and “4.900+ reviews”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email 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

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 17 other companies contacted

    Loading the homepage contacts 17 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 changinglife.cl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on changinglife.cl, including 16 speed issues, 1 SEO issue 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

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