Programmable

Website review, no card needed

verisure.cl logo

verisure.cl website review

Visit site (opens in a new tab)Reviewed 4 November 202631 issues · 79 checks

This review found 31 issues worth fixing on verisure.cl, 15 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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

Site score

80B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
5.4 s2.9 sMay 16Oct 314.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.2 s
May 23, 20263.2 s
May 30, 20263.2 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.2 s
Jul 25, 20263.3 s
Aug 1, 20263.5 s
Aug 8, 20263.7 s
Aug 15, 20263.9 s
Aug 22, 20263.9 s
Aug 29, 20263.9 s
Sep 5, 20264.0 s
Sep 12, 20264.1 s
Sep 19, 20264.4 s
Sep 26, 20264.7 s
Oct 3, 20265.0 s
Oct 10, 20265.1 s
Oct 17, 20265.1 s
Oct 24, 20264.8 s
Oct 31, 20264.7 s
Real-visitor tap response (INP)75th percentile, phones
266 ms189 msMay 16Oct 31252 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026202 ms
May 23, 2026203 ms
May 30, 2026200 ms
Jun 6, 2026198 ms
Jun 13, 2026201 ms
Jun 20, 2026199 ms
Jun 27, 2026200 ms
Jul 4, 2026199 ms
Jul 11, 2026198 ms
Jul 18, 2026199 ms
Jul 25, 2026201 ms
Aug 1, 2026208 ms
Aug 8, 2026222 ms
Aug 15, 2026236 ms
Aug 22, 2026238 ms
Aug 29, 2026238 ms
Sep 5, 2026236 ms
Sep 12, 2026232 ms
Sep 19, 2026239 ms
Sep 26, 2026248 ms
Oct 3, 2026255 ms
Oct 10, 2026257 ms
Oct 17, 2026255 ms
Oct 24, 2026250 ms
Oct 31, 2026252 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

www.verisure.cl (opens in a new tab)
Full-page screenshot of verisure.cl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. verisure.cl at 0.5 s0.5 s
  2. verisure.cl at 0.9 s0.9 s
  3. verisure.cl at 1.3 s1.3 s
  4. verisure.cl at 1.8 s1.8 s
  5. verisure.cl at 2.2 s2.2 s
  6. verisure.cl at 2.7 s2.7 s
  7. verisure.cl at 3.1 s3.1 s
  8. verisure.cl at 3.6 s3.6 s

Speed

11 to fix35

  • Reduce unused JavaScript

    2.0 s · 577 KiB

    About 577 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

  • Render-blocking requests

    2.0 s

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

  • Use efficient cache lifetimes

    1.1 s · 617 KiB

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 6.9 s

    A phone's processor spends 6.9 s on main-thread work while loading, 3.4 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 (Facebook, TikTok and Clarity and others), adding 589 KiB and 1.1 s of main-thread time.

  • Reduce unused CSS

    390 ms · 205 KiB

    About 205 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 390 ms faster on a phone.

  • Improve image delivery

    350 ms · 87 KiB

    2 images could be 87 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Facebook adds 332 ms

    332 ms

    Facebook costs a phone 332 ms of main-thread work and 225 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 325 ms. During a long task the page ignores taps.

  • 2,050 HTML elements

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

  • Legacy JavaScript

    33 KiB

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

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

  • 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: 75 ms

    75 ms

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

Core Web Vitals

10 to fix100

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

  • Largest Contentful Paint: 14.2 s

    14.2 s

    Your largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 20.0 s

    20.0 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Tap response (INP) got 24% slower for real visitors

    +24%

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

  • Largest content (LCP) got 49% slower for real visitors

    +49%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 867 ms

    867 ms

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

4 checks passed

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 193 ms

    193 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85

  • Page weight: 2.7 MB in 151 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 151 requests on a phone: scripts 1.7 MB (54), images 368 KiB (29) and fonts 339 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.77 g

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

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9697

  • Certain ARIA roles must be contained by particular parents (4 elements)

    Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.

  • ARIA role should be appropriate for the element (4 elements)

    ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

2 checks passed

  • Every image has alt text

    All 72 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 2 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9296

  • Structured data has 5 problems

    Structured data found (EducationalOccupationalCredential and Organization) but with 5 problems, for example “EducationalOccupationalCredential: mainEntityOfPage is not an absolute URL ("URL_DE_LA_PAGINA")”.

  • 239 internal links, 25 external

    The homepage links to 239 pages on verisure.cl and 25 external pages.

7 checks passed

  • Meta description: 130 characters

    Your meta description is 130 characters: “El sistema de alarmas líder en el mercado para la protección de su hogar y negocio. Entra y conoce nuestros servicios d…”.

  • One H1 headline

    Your main headline reads: “Alarmas de seguridad para casas y negocios de Verisure”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Alarmas Verisure para Hogar y Negocio - Verisure Chile”.

  • Canonical URL set

    The canonical URL is https://www.verisure.cl/.

  • 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.verisure.cl/sitemap.xml.

AI search readiness

1 to fix83

  • Parts of the site are closed to 6 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • Opted out of AI training for 4 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, description and contact details; logo and sameAs (social profiles) would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,775 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.verisure.cl/llms.txt (15 KiB, 96 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95

  • 14 pages without an H1

    https://www.verisure.cl/alarmas-casas, https://www.verisure.cl/alarmas-casas/departamentos, https://www.verisure.cl/alarmas-casas/condominios, https://www.verisure.cl/alarmas-casas/alarma-para-segunda-vivienda, https://www.verisure.cl/alarmas-casas/alarmas-casa-campo and https://www.verisure.cl/alarmas-casas/alarma-exterior and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.verisure.cl/alarmas-casas/ninos-pequenos took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 84 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

1 to fixGoogle 10084

  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=15000951&tm=gtm002&Ver=2&mid=2d0c4ad6-3b66-49f1-b716-41cd2996defd&bo=1&sid=b94deb80d85611f192aad36bf009c192&vid=b94e0b60d85611f18a90dbd6af0424ad&vids=1&msclkid=N&pi=91.

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    81 of 81 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67

  • 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 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 2,259 words of copy

    The homepage carries about 2,259 words of visible text.

4 checks passed

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 7 testimonial or review blocks, a star rating and 5 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 6 phone links and 0 email links.

Privacy and tracking

1 to fix

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 3 mores (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.

  • 21 cookies set on arrival

    21

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

  • 36 other companies contacted

    Loading the homepage contacts 36 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 verisure.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
Drupal
Framework
Bootstrap
Analytics
Google Tag Manager
Hosting
Imperva

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on verisure.cl, including 21 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