Website review, no card needed
nido.cl website review
Visit site (opens in a new tab)Reviewed 4 November 202654 issues · 94 checks
This review found 54 issues worth fixing on nido.cl, 21 of them high impact, across 94 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
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 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.3 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 152 ms |
| May 23, 2026 | 151 ms |
| May 30, 2026 | 144 ms |
| Jun 6, 2026 | 144 ms |
| Jun 13, 2026 | 141 ms |
| Jun 20, 2026 | 138 ms |
| Jun 27, 2026 | 135 ms |
| Jul 4, 2026 | 134 ms |
| Jul 11, 2026 | 135 ms |
| Jul 18, 2026 | 139 ms |
| Jul 25, 2026 | 142 ms |
| Aug 1, 2026 | 145 ms |
| Aug 8, 2026 | 147 ms |
| Aug 15, 2026 | 142 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 153 ms |
| Sep 5, 2026 | 157 ms |
| Sep 12, 2026 | 167 ms |
| Sep 19, 2026 | 167 ms |
| Sep 26, 2026 | 165 ms |
| Oct 3, 2026 | 166 ms |
| Oct 10, 2026 | 166 ms |
| Oct 17, 2026 | 169 ms |
| Oct 24, 2026 | 167 ms |
| Oct 31, 2026 | 169 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
Speed
Use efficient cache lifetimes
7.0 s · 1.9 MB47 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).
Reduce unused JavaScript
4.1 s · 872 KiBAbout 872 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.
Render-blocking requests
2.9 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Mobile performance score: 11
11/100Your mobile performance score is 11. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.1 s
A phone's processor spends 7.1 s on main-thread work while loading, 3.0 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 (Google Tag Manager, Facebook and weglot.com and others), adding 1.5 MB and 2.0 s of main-thread time.
Google Tag Manager adds 827 ms
827 msGoogle Tag Manager costs a phone 827 ms of main-thread work and 313 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
150 ms · 619 KiB9 images could be 619 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
450 ms · 120 KiBAbout 120 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 402 ms. During a long task the page ignores taps.
Facebook adds 367 ms
367 msFacebook costs a phone 367 ms of main-thread work and 231 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.
2,584 HTML elements
The page has 2,584 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
juicer.io adds 151 ms
151 msjuicer.io costs a phone 151 ms of main-thread work and 553 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.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Legacy JavaScript
150 ms · 40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
13 KiB13 KiB could be saved by minifying JavaScript.
Minify CSS
7 KiB7 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: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 15.3 s
15.3 sYour largest element takes 15.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “online”.
Time to Interactive: 17.7 s
17.7 sThe page becomes fully interactive after 17.7 s. Good is under 3.8 s.
Total Blocking Time: 2.2 s
2.2 sScripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.494
0.494The layout shifts by 0.494 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 953 ms
953 msReal visitors wait 953 ms for your server to start answering (75th percentile). Good is under 800 ms.
59 images without width and height
59 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 152 ms to 169 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 199 ms
199 msReal visitors wait 199 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Images and page weight
5 images far larger than shown
524 KiB5 images are downloaded at several times the size a phone draws them, for example AMISA-logo-white-background.png at 2,917 px wide, shown at 123 px. Resized copies would save about 524 KiB.
Page weight: 3.5 MB in 106 requests
3.5 MBYour homepage downloads 3.5 MB in 106 requests on a phone: scripts 1.6 MB (16), images 1.5 MB (55) and fonts 167 KiB (7). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Screenshot2026-10-30at122249PM.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
10 images in older formats
10 images (925 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.
13 images below the first screen load straight away
13 images further down the page (998 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
0.98 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.98 g of CO₂e: 117.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Orphan list items
Some list items are not inside a list.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 41 images in the HTML carry an alt attribute.
55 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 64 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (252 characters)
Your meta description is 252 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.nido.cl/sitemap.xml, so Google discovers your pages only by following links.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
125 internal links, 19 external
The homepage links to 125 pages on nido.cl and 19 external pages.
3 checks passed
Title: 47 characters
Your title is a healthy 47 characters: “Home - The International School Nido de Aguilas”.
Canonical URL set
The canonical URL is https://www.nido.cl/.
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.
Some text only appears after JavaScript runs
44%The HTML your server sends has 446 of the 1,018 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.nido.cl/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
2 pages without a title
https://www.nido.cl/fs/pages/1362 and https://www.nido.cl/fs/pages/154 have no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.nido.cl/quicklinks is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://www.nido.cl/discover-nido/our-mission-vision-values and https://www.nido.cl/discover-nido/strategic-plan all use the title “Our Mission & Values - The International School Nido de Aguilas”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.nido.cl/fs/pages/1362 and https://www.nido.cl/fs/pages/154 have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.nido.cl/discover-nido/our-mission-vision-values and https://www.nido.cl/discover-nido/strategic-plan use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://www.nido.cl/fs/pages/1362, https://www.nido.cl/fs/pages/154 and https://www.nido.cl/quicklinks have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.nido.cl/discover-nido/nido-at-a-glance took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 113 found) and read each the way a search engine does.
2 checks passed
Linked pages load
12 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
138 of 149 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 1,018 words of copy
The homepage carries about 1,018 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “INQUIRE” and “APPLY (OPENS IN NEW WINDOW/TAB)”.
10 calls to action
The homepage has 10 calls to action, for example “Contact Us”, “Inquire” and “Apply(opens in new window/tab)”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel, Hotjar, HubSpot, LinkedIn Insight and Cloudflare Web Analytics.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 2 mores (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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies (measured from a US location before any click).
22 other companies contacted
Loading the homepage contacts 22 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 nido.cl, 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 © 2025.
Stack
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 54 issues on nido.cl, including 23 speed issues, 7 SEO issues and 1 conversion gap. 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.